In transaction WE20, create an inbound partner profile for the EDI partner: set partner type KU (customer) or LI (vendor), partner number, and message type ORDERS.
Assign process code ORDE in the inbound parameters tab of the partner profile; this links to function module IDOC_INPUT_ORDERS which creates the sales order via standard SD processing.
Populate the EDPAR table (transaction SM30, view V_EDPAR) to map the external partner number in the IDoc to the SAP KUNNR customer number and PARVW partner function.
Verify segment E1EDK14 carries the required sales area data (ORGID for sales org, QUALF = 012 for sales organization); missing values cause the IDoc to post with error status 51.
Test inbound processing using transaction WE19: load a sample ORDERS05 IDoc, modify key segments, and use the standard inbound function to simulate processing without sending from a real partner.
Monitor IDoc status in BD87; status 53 means successful posting to a sales order, status 51 indicates application error — drill into the status record for the ABAP message class and message number.
Known gotchas
If segment E1EDK14 with QUALF = 008 (purchase order number) is missing or malformed, the resulting sales order will lack the customer PO reference, causing downstream invoice matching failures.
The EDPAR table lookup is case-sensitive for external partner numbers; mismatches between what the trading partner sends in the SNDPRN segment and what is in EDPAR result in a 'partner not found' status 26 error.
Process code ORDE triggers synchronous posting by default; for high-volume EDI, configure parallel IDoc processing via the IDoc workflow or use the ALE distribution model to route to a dedicated inbound queue.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp