Q: 4
With decentralized EWM, you can skip certain document categories. Which document category
combination is still mandatory?
Options
Discussion
A tbh. Outbound delivery order and outbound delivery are always required in decentralized EWM, you can't skip those for standard outbound processes. Trap here is D, but outbound delivery request isn’t always mandatory.
A
Nah, not D. The outbound delivery request can be skipped, but pretty sure A is always required in decentralized EWM.
A tbh, outbound delivery order and outbound delivery are the key docs you can't skip with decentralized EWM.
Not seeing how D could ever be right here, since the outbound delivery request isnt always mandatory in decentralized setups. A is needed because you cant avoid either the ODO or the outbound delivery itself if you want end-to-end stock sync. Saw similar question on a practice test, pretty sure this is it. If anyone thinks C should be right due to posting change flows, would love to hear why.
D is out, A is needed. The outbound delivery order and outbound delivery always have to be there in decentralized EWM.
Why not C? Some practice exams trip people up with posting change flows, official guide helps clarify.
C/D? I'm stuck between posting change pairs (C) and outbound docs (D). In some scenarios, posting change flow feels just as required, but maybe I'm mixing up process steps. Anyone else think posting changes matter more here?
A , had something like this in a mock and it was always outbound delivery order plus outbound delivery for decentralized EWM. Those can’t be skipped, so pretty confident here. Anyone disagree?
You actually can't skip the outbound delivery order and outbound delivery in decentralized EWM, so it's A. They're both needed for warehouse tasks and stock consistency. Pretty sure that's how SAP designs the core process, correct me if I'm wrong.
Be respectful. No spam.
