2 weeks ago
Dear SAP,
can you please explain why the goods recipient in the EWM outbound delivery items is empty?
The goods recipient field is empty.
First question is: why is this even pulled from another table. Second question is why it is empty.
Request clarification before answering.
In SAP S/4HANA Cloud, public edition, the Goods Recipient field in the EWM Outbound Delivery Order (ODO) is not filled at item level by design. The system behavior differs from on-premise versions, as partner information is managed centrally at header level and not replicated down to each item.
Below are clarifications to your questions:
Why it is pulled from another table:
In the public cloud, the Goods Recipient information is stored at the delivery header level and transferred to EWM during delivery document creation through the standard integration layer. The data originates from the Ship-To Party (partner function WE) in the ERP delivery header, which is used by EWM for process execution. Since partner data is maintained separately from item data, EWM reads it from the partner table associated with the delivery header rather than directly from the item table.
Why it is empty:
The Goods Recipient field is intentionally not populated at item level, as EWM in the public cloud uses the Ship-To Party (WE) maintained in the delivery header for all outbound processing steps (including picking, staging, and goods issue).
This is standard system behavior — there is no separate Goods Recipient value stored at item level in the Outbound Delivery Order in S/4HANA Cloud.
If you need to use this information operationally (for example, in picking structure or RF transactions), you can refer to the Ship-To Party field instead, as it represents the same business entity for outbound processes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 22 | |
| 13 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.