From 850 to ORDERS05

Every Monday, Great Lakes Fleet Services sends Contoso Motor Co. a batch of X12 850 purchase orders over AS2. SAP Process Orchestration 7.5 on XP1 validates each interchange, returns a 997, translates each 850 into an ORDERS IDoc with basic type ORDERS05, and hands it to SAP S/4HANA CMP, where process code ORDE creates a sales order. This course follows one of those orders, GLF-PO-55120 for 50 alternators, all the way to sales order 1000457, and shows every place where it can go wrong.

Start with the structure. SAP's documentation lists ORDERS01 to ORDERS05 as the IDoc types for inbound sales orders, with ORDERS05 adding segments such as E1EDK17 (terms of delivery) and E1EDP19 (item object identification) to the earlier versions. The segments are shared across purchasing and sales, which is why their names say "document" rather than "sales order".

Above the data records sits the control record. For Great Lakes' orders, PO fills it with direction 2 (inbound), message type ORDERS, basic type ORDERS05, the sender partner type KU and number 17100001, and Contoso's own logical system CMPCLNT100 as the receiver. The sender fields are what the partner profile lookup uses; nothing in the data records can rescue an IDoc whose control record names the wrong partner. That is why the first check on any odd inbound order is the control record, and the second is the data.

Qualifiers carry the meaning

ORDERS05 reuses generic segments and qualifies them, exactly like X12 does. E1EDK14 with qualifier 008 carries a sales organization, while the same segment with 012 carries an order type. SAP's segment documentation for inbound processing lists 006 division, 007 distribution channel, 008 sales organization, 010 sales group, 012 order type and 016 sales office among the qualifiers the inbound program reads. E1EDP19 identifies the material: qualifier 001 is the customer's material number and 002 the supplier's, as SAP's mapping tables state. A map that writes the customer's part number with qualifier 002 makes SAP look for a material called GLF-ALT-100 in its own material master, which fails.

Great Lakes' 850 mapped

The EDIFACT twin

If a European distributor sent an EDIFACT ORDERS message instead, the same targets apply with different sources: BGM provides the order number for E1EDK02, DTM+2 the requested delivery date for E1EDK03 002, NAD+BY and NAD+DP the sold-to and delivery party for E1EDKA1 AG and WE, and each LIN group with QTY+21 and PRI one E1EDP01 with its children. That is the point of the IDoc layer: SAP sees one structure, whatever standard the partner speaks, and the middleware owns the differences.