Structure & Interpretation Document — ORDERS05 Purchase Order IDoc
1. Overview
| Attribute | Value |
|---|---|
| Basic Type | ORDERS05 |
| IDoc Type | ORDERS05 |
| Message Type | ORDERS |
| Document Name | Purchase Order |
| Direction | Inbound |
| IDoc Control Number (docNumber) | 3 |
| Sender Logical System | PIDCLNT120 (partner type LS, port SAPPID) |
| Receiver Logical System | ECDCLNT190 (partner type LS, port SAPECD) |
| Reference (control record) | SG33 |
This is an inbound ORDERS05 IDoc representing a Purchase Order flowing from logical system PIDCLNT120 into logical system ECDCLNT190. The reference "SG33" together with the E1EDK03/reference qualifier 001 value SG3332000000001 (see §2) suggests this IDoc is tied to a specific source document/order number series "SG33...".
2. Header
| Field | Value | Interpretation |
|---|---|---|
| Currency | VND | Vietnamese Dong — document currency for header and confirmed at line-item level (currency: VND in the line item as well) |
| Payment Terms | Z003 | Custom (client-defined) payment terms key; exact meaning (e.g., net days) is not resolvable from the data provided |
| Control reference (EDI_DC40) | SG33 | Free-text reference carried in the control record |
| Document reference (E1EDK03, qualifier 001) | SG3332000000001 | A referenced document number (qualifier 001 typically denotes a customer/purchase order reference in E1EDK03/E1EDK03 segments); exact business meaning of qualifier 001 in this client's configuration is not explicitly confirmed but is consistent with standard "Purchase Order Date/Number" usage |
| Dates (E1EDK03) | Qualifier 012 → 2022-03-15; Qualifier 002 → 2022-03-15 |
Qualifier 002 is the standard SAP code for Document Date (PO issue date). Qualifier 012 is a client/scenario-specific date qualifier (not a universally standard SAP code) — both dates coincide at 15 March 2022. Recommend confirming 012's exact business meaning against the customer's IDoc configuration if not already known. |
3. Partners (E1EDKA1)
| PARVW | Role (Interpreted) | Partner Number | Notes |
|---|---|---|---|
| AG | Sold-to Party | 9999990142 | Standard SAP partner function AG = Sold-to Party (Auftraggeber) |
| Z1 | Custom partner function (Z1) | 5000010685 | Z-prefixed code — client-specific extension to the standard partner function catalogue; exact role (e.g., alternate payer, subsidiary) cannot be determined from the data alone |
| Z8 | Custom partner function (Z8) | 5555555555 | Another client-specific (Z) partner role; number 5555555555 appears to be a generic/placeholder-style ID, but is taken as-is from the data |
Total partner segments: 3 (matches partnerCount: 3 in stats).
4. Line Items (E1EDP01 / E1EDP05)
| Position | Material | Quantity | Unit | Currency | Notable Conditions (E1EDP05) |
|---|---|---|---|---|---|
| 10 | 000000000010000001 | 1.00 | CAI | VND | See breakdown below |
Condition detail for Item 10 (KSCHL = condition type):
| Condition Type | Sign | Amount | Rate | Interpretation |
|---|---|---|---|---|
| VKP1 | + | 11,450,000 | 11,450,000 | Likely a base/gross price condition (client-specific "VKP" naming suggests "sales price 1") |
| ZDC1–ZDC5 | − | — (no amount populated) | — | A series of five custom discount/deduction conditions (Z-prefixed "DC" = likely "Discount") flagged negative; no amounts transmitted in this IDoc instance |
| NETW | + | 10,409,091 | — | Net value of the item after discounts — standard-style condition type representing net worth |
| ZMSI | + | 1,040,909 | — | Custom condition, positive sign; amount ≈ 9.09% of NETW — plausibly a tax or surcharge (e.g., VAT-like component), but exact meaning not confirmed |
| ZSC1 | + | — | — | Custom surcharge condition ("SC" = Surcharge), no amount transmitted |
| ZCC1 | + | — | — | Custom condition ("CC"), no amount transmitted |
| ZDI1, ZDI2 | − | — | — | Custom deduction/discount conditions, no amounts transmitted |
| ZSC2, ZCC2 | − | — | — | Second surcharge/CC conditions, negative sign, no amounts transmitted |
| ZGP1 | (unsigned) | 0 | 0 | Custom condition, explicit zero amount and rate |
| ZGP2 | (unsigned) | 0 | — | Custom condition, explicit zero amount |
Observation: Only VKP1, NETW, and ZMSI carry explicit non-zero amounts in this IDoc; the remaining 13 condition types (ZDC1–5, ZSC1/2, ZCC1/2, ZDI1/2, ZGP1/2) are present as condition records but largely without populated amount/rate values — they may represent condition types configured in the pricing procedure but not active/relevant for this specific item, or the values were simply not transmitted in this IDoc segment set.
Total E1EDP05 condition segments for this item: 16 (matches histogram count).
5. Segment Structure Summary
Total segment count in IDoc: 181, comprising 1 line item and 3 partners, across the following segment types:
| Segment | Count | Role |
|---|---|---|
| EDI_DC40 | 1 | IDoc control record (header metadata: sender/receiver, message type, direction) |
| E1EDK01 | 1 | Document header (order type, currency, etc.) |
| E1EDK02 | 1 | Header reference/organizational data |
| E1EDK03 | 2 | Header dates (qualifiers 012 and 002) |
| E1EDK05 | 1 | Header condition (pricing at header level) |
| E1EDK14 | 5 | Header-level organizational/qualifier data (5 occurrences — e.g., order type, sales org details) |
| E1EDKA1 | 3 | Header partner segments (Sold-to AG, custom Z1, custom Z8) |
| E1EDKT1 | 29 | Header text identifier segments (large volume — multiple text types/languages at header level) |
| E1EDKT2 | 49 | Header text line segments (actual text content lines, corresponding to E1EDKT1 headers) |
| E1EDP01 | 1 | Line item segment (Item 10) |
| E1EDP02 | 1 | Item reference data |
| E1EDP05 | 16 | Item pricing conditions (detailed in §4) |
| E1EDP19 | 1 | Item object identification (e.g., material long number/EAN) |
| E1EDPA1 | 4 | Item-level partner segments |
| E1EDPT1 | 31 | Item text identifier segments |
| E1EDPT2 | 33 | Item text line segments |
| E1EDC01 | 1 | Configuration/classification segment (change indicator or similar control data) |
| E1EDC05 | 1 | Additional configuration/condition control segment |
Key structural observation: The IDoc is dominated by text segments — E1EDKT1/E1EDKT2 (header texts, 29+49 = 78 segments) and E1EDPT1/E1EDPT2 (item texts, 31+33 = 64 segments) — together accounting for 142 of 181 segments (~78%). This indicates the source system is transmitting extensive free-text/long-text content (e.g., order notes, terms, item remarks) alongside a comparatively simple transactional structure of just 1 line item and 3 partners.