/SCWM/PRDI — Maintain EWM Inbound Delivery
/SCWM/PRDI is used to display and process EWM inbound deliveries including goods-receipt relevant status and item details. It is most useful when inbound delivery data, GR processing or ERP-to-EWM distribution needs operational analysis. Start from the exact business object, organizational scope and status, then prove the result through document flow, logs or master data before applying a corrective action.
This ERPClimb practitioner page covers /SCWM/PRDI — Maintain EWM Inbound Delivery. It focuses on the transaction's real operational role, the parameters that matter, the evidence needed to diagnose problems, S/4HANA context, and the mistakes that cause most support rework.
Published 19 Sept 2026· 629 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
display and process EWM inbound deliveries including goods-receipt relevant status and item details. /SCWM/PRDI is most useful when treated as part of an end-to-end process rather than a shortcut. The object status you see here is usually influenced by upstream master data, configuration, planning or document history, so capture those inputs before changing anything.
When it is used
/SCWM/PRDI is typically used when inbound delivery data, GR processing or ERP-to-EWM distribution needs operational analysis. It is also valuable during project testing because it exposes a repeatable state that can be compared before and after configuration or master-data changes. In production, narrow the population first and distinguish display/analysis from actions that post, approve, replicate or change status.
How to use it in practice
- Find the inbound delivery by EWM or ERP reference.
- Review document and item status before changing anything.
- Check product, quantity, batch/HU and process data.
- Resolve queue/integration errors before forcing warehouse processing.
- Post/confirm the intended inbound step and verify ERP synchronization.
Key data objects
These are the most useful anchors when working in /SCWM/PRDI. Capture them in screenshots, test evidence and incident handovers so another consultant can reproduce the same result and identify whether the issue is data, configuration, status or integration.
- EWM inbound delivery — verify the exact value, validity/date context and relationship to the affected process.
- ERP reference — verify the exact value, validity/date context and relationship to the affected process.
- product/quantity — verify the exact value, validity/date context and relationship to the affected process.
- warehouse process/status — verify the exact value, validity/date context and relationship to the affected process.
- goods-receipt status — verify the exact value, validity/date context and relationship to the affected process.
How to prove it in the data
Build an evidence chain rather than relying on one message: identify the source requirement or master record, show the transaction status or worklist entry, then show the resulting document, posting, warehouse object, planning element or replication log. Use the same date and organizational scope throughout. That makes the diagnosis repeatable and separates a true fix from a coincidental retry.
ECC vs S/4HANA
SAP documents /SCWM/PRDI for maintaining inbound deliveries in EWM; it remains important in embedded S/4HANA EWM as well as decentralized deployments. Where a Fiori app or cloud service becomes the strategic user experience, the SAP GUI transaction can still remain valuable for support, migration and deep technical analysis, but it should not be used to justify a legacy design for new work.
Common pitfalls and how to diagnose them
- Editing EWM delivery data to mask an ERP mapping problem. Return to the exact object status and chronology before applying a workaround.
- Posting GR before warehouse prerequisites are complete. Return to the exact object status and chronology before applying a workaround.
- Looking only in ERP VL33N when the execution error is inside EWM. Return to the exact object status and chronology before applying a workaround.
Whose problem this is
Primary ownership is the WM EWM team, with adjacent functional, Basis, Security or integration teams joining when the evidence crosses system boundaries. Escalate with the object/document number, organization, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/scwm-prdiERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.