SAP ECC ORDERS05 IDoc Segments and Qualifiers Reference
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.
| Segment | Parent | Description | Key fields | Qualifier value | Qualifier meaning | Maps to |
|---|---|---|---|---|---|---|
E1EDK01 | Root | Document header general data | ACTION, CURCY, BSART, BELNR, ZTERM, AUGRU | - | - | VBAK-WAERK (CURCY); EKKO-EBELN (BELNR, outbound PO) |
E1EDK14 | Root | Header organizational data | QUALF, ORGID | 006 | Division | VBAK-SPART |
E1EDK14 | Root | Header organizational data | QUALF, ORGID | 007 | Distribution channel | VBAK-VTWEG |
E1EDK14 | Root | Header organizational data | QUALF, ORGID | 008 | Sales organization | VBAK-VKORG |
E1EDK14 | Root | Header organizational data | QUALF, ORGID | 010 | Sales group | VBAK-VKGRP |
E1EDK14 | Root | Header organizational data | QUALF, ORGID | 012 | Order type | VBAK-AUART |
E1EDK14 | Root | Header organizational data | QUALF, ORGID | 016 | Sales office | VBAK-VKBUR |
E1EDK14 | Root | Header organizational data | QUALF, ORGID | 019 | PO type (SD) | VBKD-BSARK |
E1EDK14 | Root | Header organizational data (outbound PO) | QUALF, ORGID | 011 | Company code | EKKO-BUKRS |
E1EDK14 | Root | Header organizational data (outbound PO) | QUALF, ORGID | 013 | Purchase order type | EKKO-BSART |
E1EDK14 | Root | Header organizational data (outbound PO) | QUALF, ORGID | 014 | Purchasing organization | EKKO-EKORG |
E1EDK14 | Root | Header organizational data (outbound PO) | QUALF, ORGID | 009 | Purchasing group | EKKO-EKGRP |
E1EDK03 | Root | Header date segment | IDDAT, DATUM, UZEIT | 002 | Requested delivery date (customer) | VBAK-VDATU |
E1EDK03 | Root | Header date segment | IDDAT, DATUM, UZEIT | 012 | Document date | EKKO-BEDAT (outbound PO) |
E1EDK03 | Root | Header date segment | IDDAT, DATUM, UZEIT | 022 | Purchase order date | VBKD-BSTDK |
E1EDK04 | Root | Header taxes | MWSKZ, MSATZ, MWSBT | - | - | Tax information; not normally used to create SD pricing |
E1EDK05 | Root | Header conditions | ALCKZ, KSCHL, BETRG, KPERC | - | - | Header pricing conditions (KONV) |
E1EDKA1 | Root | Header partner information | PARVW, PARTN, LIFNR, NAME1 | AG | Sold-to party | VBAK-KUNNR / VBPA |
E1EDKA1 | Root | Header partner information | PARVW, PARTN | WE | Ship-to party | VBPA (PARVW WE) |
E1EDKA1 | Root | Header partner information | PARVW, PARTN | RE | Bill-to party | VBPA (PARVW RE) |
E1EDKA1 | Root | Header partner information | PARVW, PARTN | RG | Payer | VBPA (PARVW RG) |
E1EDKA1 | Root | Header partner information (outbound PO) | PARVW, PARTN | LF | Vendor | EKKO-LIFNR |
E1EDK02 | Root | Header reference data | QUALF, BELNR, DATUM | 001 | Customer purchase order | VBKD-BSTKD |
E1EDK02 | Root | Header reference data | QUALF, BELNR, DATUM | 002 | Vendor order | Order number at the vendor (order response) |
E1EDK17 | Root | Header terms of delivery | QUALF, LKOND, LKTEXT | 001 / 002 | Incoterms part 1 / part 2 | VBKD-INCO1 / VBKD-INCO2 |
E1EDK18 | Root | Header terms of payment | QUALF, TAGE, PRZNT, ZTERM_TXT | 001 to 003 | Payment term 1 to 3 (days and percentage) | Cash discount terms |
E1EDKT1 | Root | Header text identification | TDID, TSSPRAS | - | - | Header texts (STXH) |
E1EDKT2 | E1EDKT1 | Header texts | TDLINE, TDFORMAT | - | - | Text lines |
E1EDP01 | Root | Document item general data | POSEX, ACTION, MENGE, MENEE, VPREI, WERKS | ACTION 001 / 002 / 003 | Item added / changed / cancelled | VBAP-POSEX, VBAP-KWMENG, VBAP-VRKME; EKPO |
E1EDP02 | E1EDP01 | Item reference data | QUALF, BELNR, ZEILE | 001 | Customer purchase order | VBKD-BSTKD at item level |
E1EDP03 | E1EDP01 | Item date segment | IDDAT, DATUM, UZEIT | 002 | Requested delivery date (customer) | Item requested date |
E1EDP04 | E1EDP01 | Item taxes | MWSKZ, MSATZ, MWSBT | - | - | Item tax information |
E1EDP05 | E1EDP01 | Item conditions | ALCKZ, KSCHL, BETRG, KRATE | - | - | Item pricing conditions (KONV) |
E1EDP20 | E1EDP01 | Item schedule lines | WMENG, AMENG, EDATU, EZEIT | - | - | VBEP-WMENG, VBEP-EDATU; EKET |
E1EDPA1 | E1EDP01 | Item partner information | PARVW, PARTN | WE | Ship-to at item level | VBPA at item level |
E1EDP19 | E1EDP01 | Item object identification | QUALF, IDTNR, KTEXT | 001 | Customer's material number | VBAP-KDMAT (converted through KNMT) |
E1EDP19 | E1EDP01 | Item object identification | QUALF, IDTNR, KTEXT | 002 | Vendor's material number | VBAP-MATNR (inbound); EKPO-IDNLF (outbound PO) |
E1EDP19 | E1EDP01 | Item object identification | QUALF, IDTNR | 003 | EAN (International Article Number) | Material found through EAN |
E1EDPT1 | E1EDP01 | Item text identification | TDID, TSSPRAS | - | - | Item texts |
E1EDPT2 | E1EDPT1 | Item texts | TDLINE, TDFORMAT | - | - | Text lines |
E1EDS01 | Root | Summary segment general | SUMID, SUMME, SUNIT | - | - | Control totals, not posted |
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.
Get your ORDERS mapping checked
Send a sample ORDERS05 IDoc and your partner profile and we will check qualifiers, partner functions and units against your sales order setup.
Optional. The tool and every export work without this. No spam.
How ORDERS05 is structured
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.
- 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
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
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
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.
Frequently Asked Questions
What is the IDoc type for a sales order in SAP?
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?
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?
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?
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.
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.
Related Tools
SAP IDoc Message Types Reference (ORDERS, DESADV, INVOIC, MATMAS, DEBMAS)
Searchable list of common SAP IDoc message types with the basic IDoc type, business meaning and the X12 or EDIFACT message they usually map to.
SAPSAP IDoc Status Codes Reference
Look up any IDoc status code, see whether it is inbound or outbound, whether it is an error, and which transaction to use to fix it.
SAPSAP IDoc Control Record (EDIDC) Fields Reference
Look up every commonly used field of the IDoc control record (table EDIDC and structure EDI_DC40) with its meaning and data type.
SAPSAP ECC MATMAS05 Material Master IDoc Segments Reference
The MATMAS05 segment tree with the material master table each segment carries, so you can build, reduce or debug material master distribution.
More SAP tools
See all- SAP ECC Private AI Layer Blueprint Generator
- SAP ECC AI Assistant Sizing and Value Calculator
- SAP ECC SD User Exit Forms Reference (MV45AFZZ, RV60AFZZ, MV50AFZ1)
- SAP ECC Customer Exits (SMOD Enhancements) by Module Reference
- SAP ECC Classic BAdI Definitions Reference (MIGO, ME21N, MIRO, Deliveries, PM Orders)
- SAP ECC Background Job Tables Reference (TBTCO, TBTCP, Job Status Codes)
- SAP ECC Output Determination Tables and Codes Reference (NAST, TNAPR, NACE)
- SAP ECC Movement Type Configuration Tables Reference (T156, T156T, T157D)
- SAP ECC Stock Type and Location Transfer Movement Type Matrix
Keep exploring
Free tools
- SAP ECC MATMAS05 Material Master IDoc Segments ReferenceThe MATMAS05 segment tree with the material master table each segment carries, so you can build, reduce or debug material master distribution.
- SAP IDoc Status Codes ReferenceLook up any IDoc status code, see whether it is inbound or outbound, whether it is an error, and which transaction to use to fix it.
- SAP IDoc Database Growth CalculatorEstimate IDoc table growth from daily volume, segments per IDoc and retention days, and see when archiving pays off.
ERP fixes and how-tos
- SAP IDoc Status 51: Application Document Not PostedIDoc status 51 means Application document not posted, a category, not a diagnosis. Find the real cause in WE02 or SLG1 and reprocess safely with BD87.
- How to add AI to SAP ECC 6.0 on-prem without moving data to a cloudReference architecture for a private on-prem AI assistant on SAP ECC 6.0: RFC and BAPI reads, SLT replica, retrieval index, local LLM, permission mirroring.
- IDocs for SAP PP: LOIPRO, LOIROU and PORDCR Configuration and MonitoringWhich IDoc message types SAP PP uses for orders and routings, how to configure partner profiles and ALE, and how to monitor and reprocess failures.
Integrations
- How to automate email into SAP ECC 6.0Turn inbound emails into SAP ECC 6.0 transactions: customer POs into sales orders, supplier confirmations, RFQs and invoices, with review and BAPI posting.
- How to use ChatGPT with SAP ECC 6.0Using ChatGPT with SAP ECC 6.0: custom GPT actions, exports versus live access, an OData or MCP bridge, enterprise data controls, and when a private model is safer.