# SAP ECC ORDERS05 IDoc Segments and Qualifiers Reference > Source: https://netray.co/tools/sap-ecc-orders05-idoc-segments-and-qualifiers-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer The ORDERS05 segments and qualifier values used for inbound sales orders and outbound purchase orders, with the SD and MM fields they map to. ## Category sap ## Erp SAP ECC 6.0 ## Audience - SAP EDI consultant - SAP SD consultant - Integration developer - SAP support analyst ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Segment **Key:** seg **Type:** text #### Parent **Key:** parent **Type:** text #### Description **Key:** desc **Type:** text #### Key fields **Key:** fields **Type:** text #### Qualifier value **Key:** q **Type:** text #### Qualifier meaning **Key:** qm **Type:** text #### Maps to **Key:** map **Type:** text **Rows:** **Seg:** E1EDK01 **Parent:** Root **Desc:** Document header general data **Fields:** ACTION, CURCY, BSART, BELNR, ZTERM, AUGRU **Q:** - **Qm:** - **Map:** VBAK-WAERK (CURCY); EKKO-EBELN (BELNR, outbound PO) **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data **Fields:** QUALF, ORGID **Q:** 006 **Qm:** Division **Map:** VBAK-SPART **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data **Fields:** QUALF, ORGID **Q:** 007 **Qm:** Distribution channel **Map:** VBAK-VTWEG **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data **Fields:** QUALF, ORGID **Q:** 008 **Qm:** Sales organization **Map:** VBAK-VKORG **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data **Fields:** QUALF, ORGID **Q:** 010 **Qm:** Sales group **Map:** VBAK-VKGRP **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data **Fields:** QUALF, ORGID **Q:** 012 **Qm:** Order type **Map:** VBAK-AUART **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data **Fields:** QUALF, ORGID **Q:** 016 **Qm:** Sales office **Map:** VBAK-VKBUR **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data **Fields:** QUALF, ORGID **Q:** 019 **Qm:** PO type (SD) **Map:** VBKD-BSARK **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data (outbound PO) **Fields:** QUALF, ORGID **Q:** 011 **Qm:** Company code **Map:** EKKO-BUKRS **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data (outbound PO) **Fields:** QUALF, ORGID **Q:** 013 **Qm:** Purchase order type **Map:** EKKO-BSART **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data (outbound PO) **Fields:** QUALF, ORGID **Q:** 014 **Qm:** Purchasing organization **Map:** EKKO-EKORG **Seg:** E1EDK14 **Parent:** Root **Desc:** Header organizational data (outbound PO) **Fields:** QUALF, ORGID **Q:** 009 **Qm:** Purchasing group **Map:** EKKO-EKGRP **Seg:** E1EDK03 **Parent:** Root **Desc:** Header date segment **Fields:** IDDAT, DATUM, UZEIT **Q:** 002 **Qm:** Requested delivery date (customer) **Map:** VBAK-VDATU **Seg:** E1EDK03 **Parent:** Root **Desc:** Header date segment **Fields:** IDDAT, DATUM, UZEIT **Q:** 012 **Qm:** Document date **Map:** EKKO-BEDAT (outbound PO) **Seg:** E1EDK03 **Parent:** Root **Desc:** Header date segment **Fields:** IDDAT, DATUM, UZEIT **Q:** 022 **Qm:** Purchase order date **Map:** VBKD-BSTDK **Seg:** E1EDK04 **Parent:** Root **Desc:** Header taxes **Fields:** MWSKZ, MSATZ, MWSBT **Q:** - **Qm:** - **Map:** Tax information; not normally used to create SD pricing **Seg:** E1EDK05 **Parent:** Root **Desc:** Header conditions **Fields:** ALCKZ, KSCHL, BETRG, KPERC **Q:** - **Qm:** - **Map:** Header pricing conditions (KONV) **Seg:** E1EDKA1 **Parent:** Root **Desc:** Header partner information **Fields:** PARVW, PARTN, LIFNR, NAME1 **Q:** AG **Qm:** Sold-to party **Map:** VBAK-KUNNR / VBPA **Seg:** E1EDKA1 **Parent:** Root **Desc:** Header partner information **Fields:** PARVW, PARTN **Q:** WE **Qm:** Ship-to party **Map:** VBPA (PARVW WE) **Seg:** E1EDKA1 **Parent:** Root **Desc:** Header partner information **Fields:** PARVW, PARTN **Q:** RE **Qm:** Bill-to party **Map:** VBPA (PARVW RE) **Seg:** E1EDKA1 **Parent:** Root **Desc:** Header partner information **Fields:** PARVW, PARTN **Q:** RG **Qm:** Payer **Map:** VBPA (PARVW RG) **Seg:** E1EDKA1 **Parent:** Root **Desc:** Header partner information (outbound PO) **Fields:** PARVW, PARTN **Q:** LF **Qm:** Vendor **Map:** EKKO-LIFNR **Seg:** E1EDK02 **Parent:** Root **Desc:** Header reference data **Fields:** QUALF, BELNR, DATUM **Q:** 001 **Qm:** Customer purchase order **Map:** VBKD-BSTKD **Seg:** E1EDK02 **Parent:** Root **Desc:** Header reference data **Fields:** QUALF, BELNR, DATUM **Q:** 002 **Qm:** Vendor order **Map:** Order number at the vendor (order response) **Seg:** E1EDK17 **Parent:** Root **Desc:** Header terms of delivery **Fields:** QUALF, LKOND, LKTEXT **Q:** 001 / 002 **Qm:** Incoterms part 1 / part 2 **Map:** VBKD-INCO1 / VBKD-INCO2 **Seg:** E1EDK18 **Parent:** Root **Desc:** Header terms of payment **Fields:** QUALF, TAGE, PRZNT, ZTERM_TXT **Q:** 001 to 003 **Qm:** Payment term 1 to 3 (days and percentage) **Map:** Cash discount terms **Seg:** E1EDKT1 **Parent:** Root **Desc:** Header text identification **Fields:** TDID, TSSPRAS **Q:** - **Qm:** - **Map:** Header texts (STXH) **Seg:** E1EDKT2 **Parent:** E1EDKT1 **Desc:** Header texts **Fields:** TDLINE, TDFORMAT **Q:** - **Qm:** - **Map:** Text lines **Seg:** E1EDP01 **Parent:** Root **Desc:** Document item general data **Fields:** POSEX, ACTION, MENGE, MENEE, VPREI, WERKS **Q:** ACTION 001 / 002 / 003 **Qm:** Item added / changed / cancelled **Map:** VBAP-POSEX, VBAP-KWMENG, VBAP-VRKME; EKPO **Seg:** E1EDP02 **Parent:** E1EDP01 **Desc:** Item reference data **Fields:** QUALF, BELNR, ZEILE **Q:** 001 **Qm:** Customer purchase order **Map:** VBKD-BSTKD at item level **Seg:** E1EDP03 **Parent:** E1EDP01 **Desc:** Item date segment **Fields:** IDDAT, DATUM, UZEIT **Q:** 002 **Qm:** Requested delivery date (customer) **Map:** Item requested date **Seg:** E1EDP04 **Parent:** E1EDP01 **Desc:** Item taxes **Fields:** MWSKZ, MSATZ, MWSBT **Q:** - **Qm:** - **Map:** Item tax information **Seg:** E1EDP05 **Parent:** E1EDP01 **Desc:** Item conditions **Fields:** ALCKZ, KSCHL, BETRG, KRATE **Q:** - **Qm:** - **Map:** Item pricing conditions (KONV) **Seg:** E1EDP20 **Parent:** E1EDP01 **Desc:** Item schedule lines **Fields:** WMENG, AMENG, EDATU, EZEIT **Q:** - **Qm:** - **Map:** VBEP-WMENG, VBEP-EDATU; EKET **Seg:** E1EDPA1 **Parent:** E1EDP01 **Desc:** Item partner information **Fields:** PARVW, PARTN **Q:** WE **Qm:** Ship-to at item level **Map:** VBPA at item level **Seg:** E1EDP19 **Parent:** E1EDP01 **Desc:** Item object identification **Fields:** QUALF, IDTNR, KTEXT **Q:** 001 **Qm:** Customer's material number **Map:** VBAP-KDMAT (converted through KNMT) **Seg:** E1EDP19 **Parent:** E1EDP01 **Desc:** Item object identification **Fields:** QUALF, IDTNR, KTEXT **Q:** 002 **Qm:** Vendor's material number **Map:** VBAP-MATNR (inbound); EKPO-IDNLF (outbound PO) **Seg:** E1EDP19 **Parent:** E1EDP01 **Desc:** Item object identification **Fields:** QUALF, IDTNR **Q:** 003 **Qm:** EAN (International Article Number) **Map:** Material found through EAN **Seg:** E1EDPT1 **Parent:** E1EDP01 **Desc:** Item text identification **Fields:** TDID, TSSPRAS **Q:** - **Qm:** - **Map:** Item texts **Seg:** E1EDPT2 **Parent:** E1EDPT1 **Desc:** Item texts **Fields:** TDLINE, TDFORMAT **Q:** - **Qm:** - **Map:** Text lines **Seg:** E1EDS01 **Parent:** Root **Desc:** Summary segment general **Fields:** SUMID, SUMME, SUNIT **Q:** - **Qm:** - **Map:** Control totals, not posted **Notes:** Qualifier values are the fixed values of the qualifier domains in SAP ECC 6.0. Field mappings show where standard IDOC_INPUT_ORDERS puts the data; user exits in IDOC_INPUT_ORDERS and customer-specific conversion can change this. Confirm against WE60 documentation for ORDERS05 in your system. ## Content **Intro:** This reference lists the ORDERS05 IDoc segments and qualifier values used for inbound sales orders (message type ORDERS, process code ORDE, function module IDOC_INPUT_ORDERS) and outbound purchase orders in SAP ECC 6.0. Each row shows where the data lands in VBAK, VBAP, VBKD, VBPA, VBEP or EKKO/EKPO. **Sections:** #### How ORDERS05 is structured **Body:** ORDERS05 is a flat list of header segments followed by repeating item segments and a summary. All header segments (E1EDK01, E1EDK14, E1EDK03, E1EDKA1, E1EDK02 and others) sit at root level, not under E1EDK01. Many segments carry a qualifier field (QUALF, IDDAT or PARVW) that says what the value means: one E1EDK14 segment with QUALF 008 carries the sales organization, another with 012 carries the order type. Each E1EDP01 item owns its own E1EDP19, E1EDP20, E1EDP05 and text children. Use WE60 for the official documentation of every field, WE30 for the tree, and WE19 to copy an IDoc and test inbound processing. **Bullets:** - WE60: IDoc type documentation - WE19: test tool for inbound and outbound IDocs - WE02 / WE05: IDoc display; data records stored in EDID4 - BD87: reprocess IDocs in error #### Worked example: a minimal inbound sales order **Body:** A customer sends PO 4500012345 for 100 EA of their part ABC-77, wanted on 2026-11-20. The minimum set is: E1EDK01 with CURCY USD; E1EDK14 008 = 1000, 007 = 10, 006 = 00 and 012 = OR (or let the sales area be derived from the partner); E1EDKA1 AG with the sold-to customer number and WE with the ship-to; E1EDK02 001 with BELNR 4500012345; E1EDK03 002 with 20261120; then E1EDP01 with POSEX 000010, MENGE 100, MENEE EA, plus E1EDP19 001 with IDTNR ABC-77. IDOC_INPUT_ORDERS converts ABC-77 to your material through the customer-material info record (KNMT) and creates the order through VA01 call transaction logic. #### Version differences and gotchas **Body:** Unit of measure in MENEE must be the ISO code, not the internal one: send EA or PCE as set in CUNI, otherwise status 51 with a unit error. Partner function in E1EDKA1 uses the internal codes AG, WE, RE, RG, not the language-dependent SP or SH you see on screen in English. If the sales area is missing, inbound processing tries to find it from the sold-to and table EDSDC (transaction VOE2). E1EDK14 019 is the SD purchase order type (BSARK), which is different from 013, the MM purchase order type. ORDERS05 is the current basic type in ECC 6.0; older partners may still send ORDERS02 or ORDERS04. #### How to check the result in the system **Body:** Open the IDoc in WE02 and check status 53 with the created sales order number. If it is in status 51, the status text usually names the segment and the VA01 message. For mapping problems, copy the IDoc in WE19 and process it in the foreground with the standard function module, which shows the VA01 screens as they are filled. In the order, VBKD-BSTKD should carry the E1EDK02 001 value and VBAK-VDATU the E1EDK03 002 date. **Cta:** If you want your support team to ask in plain English why an ORDERS IDoc failed and what the order should have looked like, we can add a private AI layer over your SAP ECC system on your own servers. **Faq:** #### What is the IDoc type for a sales order in SAP? **Answer:** Inbound sales orders use message type ORDERS with basic type ORDERS05 in SAP ECC 6.0. The inbound process code is ORDE, which calls function module IDOC_INPUT_ORDERS. Order changes use message type ORDCHG and order responses use ORDRSP, all on the same ORDERS05 structure. #### What does E1EDK14 QUALF 012 mean? **Answer:** E1EDK14 with qualifier 012 carries the order type, which becomes VBAK-AUART on an inbound sales order. Other common E1EDK14 qualifiers are 006 division, 007 distribution channel, 008 sales organization, 016 sales office and 019 SD purchase order type. For outbound purchase orders, 011 company code, 013 PO type and 014 purchasing organization are used. #### Where is IDoc data stored in SAP? **Answer:** The control record is in EDIDC, the data records (segments) in EDID4, and the status records in EDIDS. You normally read them through WE02 or WE05 rather than SE16 because EDID4 stores each segment as a long SDATA string that must be split by the segment structure. #### Which E1EDP19 qualifier is the customer material number? **Answer:** E1EDP19 QUALF 001 is the customer's material number and 002 is the vendor's material number, which on an inbound sales order is your own material. 003 is the EAN. Send 001 when you maintain customer-material info records in VD51, or 002 when the customer already knows your material numbers. ## Search terms sap idoc type for sales order, sap idoc structure, sap idoc example structure, sap idoc segment table, sap idoc format details, orders05 idoc segments, e1edk14 qualifier, e1edk03 iddat 002 --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json