IDoc ORDERS05
SAP basic type for purchase orders · message type ORDERS
IDoc ORDERS05 is the basic type in which SAP systems exchange purchase orders as an IDoc (Intermediate Document), SAP's own format for business documents between systems. An ORDERS05 IDoc carries an SAP customer's order to their supplier with header data, partners, items and totals; the same basic type also serves order changes and order confirmations.
Last updated:
- Publisher
- SAP
- Message types
- ORDERS (order), ORDCHG (order change), ORDRSP (order confirmation)
- Structure
- Control record EDI_DC40, data segments, status records
- Transfer
- EDI or ALE, for example as XML over HTTP, as a file or through middleware
- Related
- cXML, openTRANS
/01
Basic type and message type
With IDocs, SAP separates purpose from structure. The message type says what is transferred: ORDERS for a purchase order, ORDCHG for an order change, ORDRSP for an order confirmation. The basic type defines the structure. ORDERS05 is the latest version of this structure after ORDERS01 to ORDERS04 and is used by all three message types; companies can extend it with segments of their own.
/02
Structure of an ORDERS05 IDoc
An IDoc consists of a control record, the data records and status records. The control record EDI_DC40 names sender, receiver, message type (MESTYP) and basic type (IDOCTYP). The data records are hierarchical segments: E1EDK01 with general header data such as the currency, E1EDK03 with dates, E1EDKA1 with partners such as the ordering party and the delivery address, E1EDK02 with document numbers, E1EDP01 with one item each including quantity and unit, below it E1EDP19 with material numbers and E1EDP20 with schedule lines, and finally E1EDS01 with totals.
/03
Transfer
SAP creates the IDoc from the purchase order, usually through the purchasing document's output determination, and sends it through a port. Besides classic EDI transfer through a subsystem, there are ports for files and for XML over HTTP; often a middleware such as SAP Integration Suite sits in between. The supplier then receives the order, for example, as an XML document whose elements carry the names of the segments and fields.
/04
IDoc ORDERS05, cXML and openTRANS
All three formats carry purchase orders. IDoc ORDERS05 is the format of the SAP world and comes straight from the customer's ERP system. cXML is used by procurement systems such as SAP Ariba and Coupa; openTRANS is an open standard that matches the BMEcat catalog format. Which format a supplier has to accept is usually decided by the customer's system.
/05
IDoc ORDERS05 with orcamultimedia
orcamultimedia's IDoc ORDERS05 interface accepts purchase orders from SAP in XML format and creates them in Magento, Shopware or OXID eShop. Order change, order confirmation, ship notice, invoice and payment advice are possible as further IDoc messages.
/06 questions
What is the difference between ORDERS and ORDERS05?
ORDERS is the message type for a purchase order, ORDERS05 the basic type that defines its structure. A purchase order IDoc from SAP therefore names both in its control record: MESTYP ORDERS and IDOCTYP ORDERS05.
Can an online shop receive IDoc ORDERS05?
An online shop can receive IDoc ORDERS05 when an interface accepts the IDoc in XML format, reads its segments and creates an order in the shop from them. orcamultimedia offers such an interface for Magento, Shopware and OXID eShop.
Is ORDERS05 used for order confirmations too?
ORDERS05 is used for order confirmations too: the message type ORDRSP uses the same basic type as the purchase order (ORDERS) and the order change (ORDCHG).
