Q: 8
What is the default requirement for an asynchronous goods receipt process in SAP Extended
Warehouse Management?
Options
Discussion
Option C is it. Inbound delivery starts the whole EWM receipt process, not the PO or production order directly. Pretty sure about that from practice runs.
C , inbound delivery is the actual object that triggers the async goods receipt flow in EWM. B (expected goods receipt) is more for planning, but the system really runs off C. That's what you'd see in most standard SAP setups. Someone correct me if you've seen a different default though.
I don't think it's C here. B makes sense because expected goods receipt can be used to anticipate incoming stock before inbound delivery is created. I might be off, but that's how I remember the process.
C for sure. Inbound delivery is what actually starts the process in EWM, not just a planning doc like B. Pretty standard in SAP setups from what I've seen, but let me know if someone had a case where it was different.
A isn't it, definitely C. Seen similar on practice exams and the inbound delivery is always the trigger.
Isn't "expected goods receipt" (B) more of a forecasting tool, not the required document for standard async receipt flows? In practice, EWM usually kicks off with the inbound delivery (C). Curious what makes people pick B here.
C imo, saw a similar one in exam dumps. Inbound delivery is the trigger for EWM processes.
Be respectful. No spam.
