SAP IDoc Segment Explorer
IntegrationNewExplore IDoc types and their segment structures for the most common SAP IDocs: ORDERS05, INVOIC02, DESADV01, MATMAS05, DEBMAS06. Find fields and data types.
Complete IDoc Reference
ORDERS05Message Type: ORDERS — Purchase Order · 3 segments
| Field | Type | Len | Description |
|---|---|---|---|
| ACTION | CHAR | 3 | Action code (002=Change, 003=Delete, 004=Undo) |
| KZABS | CHAR | 1 | Flag: Order acknowledgement required |
| CURCY | CHAR | 3 | Currency |
| ZTERM | CHAR | 17 | Terms of payment |
| BELNR | CHAR | 35 | Document number |
| Field | Type | Len | Description |
|---|---|---|---|
| PARVW | CHAR | 3 | Partner function (AG=Sold-to, WE=Ship-to, RE=Bill-to) |
| PARTN | CHAR | 17 | Partner number |
| NAME1 | CHAR | 35 | Name 1 |
| STRAS | CHAR | 35 | Street address |
| ORT01 | CHAR | 35 | City |
| PSTLZ | CHAR | 9 | Postal code |
| LAND1 | CHAR | 3 | Country |
| Field | Type | Len | Description |
|---|---|---|---|
| POSEX | CHAR | 6 | Item number |
| MATNR | CHAR | 35 | Material number |
| MENGE | QUAN | 15 | Quantity |
| MENEE | CHAR | 3 | Unit of measure |
| PREIS | CURR | 15 | Price |
| CURCY | CHAR | 3 | Currency |
INVOIC02Message Type: INVOIC — Invoice / Billing Document · 3 segments
| Field | Type | Len | Description |
|---|---|---|---|
| ACTION | CHAR | 3 | Action code |
| BELNR | CHAR | 35 | Invoice document number |
| NTGEW | QUAN | 15 | Net weight |
| GEWEI | CHAR | 3 | Weight unit |
| Field | Type | Len | Description |
|---|---|---|---|
| PARVW | CHAR | 3 | Partner function |
| PARTN | CHAR | 17 | Partner number |
| Field | Type | Len | Description |
|---|---|---|---|
| SUMME | CURR | 18 | Total amount |
| SUNIT | CHAR | 3 | Currency |
| WAERK | CHAR | 3 | Currency key |
DESADV01Message Type: DESADV — Despatch Advice (Shipping Notification) · 3 segments
| Field | Type | Len | Description |
|---|---|---|---|
| VBELN | CHAR | 10 | Delivery number |
| LFART | CHAR | 4 | Delivery type |
| WADAT | CHAR | 8 | Goods issue date (YYYYMMDD) |
| VSTEL | CHAR | 4 | Shipping point |
| KUNNR | CHAR | 10 | Ship-to customer |
| Field | Type | Len | Description |
|---|---|---|---|
| VHILM | CHAR | 18 | Packaging material |
| ANZPK | QUAN | 15 | Number of packages |
| Field | Type | Len | Description |
|---|---|---|---|
| POSNR | CHAR | 6 | Delivery item number |
| MATNR | CHAR | 18 | Material number |
| LFIMG | QUAN | 13 | Actual quantity delivered |
| VRKME | CHAR | 3 | Sales unit |
MATMAS05Message Type: MATMAS — Material Master · 3 segments
| Field | Type | Len | Description |
|---|---|---|---|
| MATNR | CHAR | 18 | Material number |
| MTART | CHAR | 4 | Material type |
| MBRSH | CHAR | 1 | Industry sector |
| MEINS | CHAR | 3 | Base unit of measure |
| BRGEW | QUAN | 13 | Gross weight |
| GEWEI | CHAR | 3 | Weight unit |
| Field | Type | Len | Description |
|---|---|---|---|
| SPRAS | CHAR | 1 | Language key |
| MAKTX | CHAR | 40 | Material description |
| Field | Type | Len | Description |
|---|---|---|---|
| WERKS | CHAR | 4 | Plant |
| EKGRP | CHAR | 3 | Purchasing group |
| DISPO | CHAR | 3 | MRP controller |
DEBMAS06Message Type: DEBMAS — Customer Master · 2 segments
| Field | Type | Len | Description |
|---|---|---|---|
| KUNNR | CHAR | 10 | Customer number |
| KTOKD | CHAR | 4 | Customer account group |
| NAME1 | CHAR | 35 | Name 1 |
| LAND1 | CHAR | 3 | Country |
| SPRAS | CHAR | 1 | Language key |
| Field | Type | Len | Description |
|---|---|---|---|
| BUKRS | CHAR | 4 | Company code |
| AKONT | CHAR | 10 | Reconciliation account |
| ZTERM | CHAR | 4 | Terms of payment |
Advertisement
About SAP IDoc Segment Explorer
Debugging an EDI/ALE interface means matching data against the exact segment structure of an IDoc type — ORDERS05, INVOIC02, DESADV01, and similar — which isn't obvious from WE02/WE05 output alone. This explorer lists the segment structures for the most common SAP IDoc types with their fields and data types, so you can map source data to the right segment without opening WE60/WE31.
How to use this tool
- Select an IDoc type (ORDERS05, INVOIC02, DESADV01, MATMAS05, DEBMAS06, etc.).
- Browse the segment hierarchy and expand a segment to see its fields.
- Search for a field name to find which segment it belongs to.
- Use the field list to map incoming EDI/ALE data to the correct IDoc segment before processing.
All processing happens locally in your browser. No data is sent to any server. Your SAP code and business data remain private at all times.
Frequently Asked Questions
What is an IDoc in SAP?
An IDoc (Intermediate Document) is SAP's standard data format for electronic data interchange (EDI) between SAP systems and external partners. Each IDoc type has a hierarchical structure of segments, where each segment contains specific business fields.
What is the difference between IDoc type and message type?
The IDoc type (Basic Type) defines the technical structure of segments and fields (e.g., ORDERS05). The message type describes the business meaning (e.g., ORDERS for purchase orders). One message type can be implemented by multiple IDoc types.
How do I monitor IDocs in SAP?
Use transaction WE02 or WE05 to display IDocs, BD87 to process failed IDocs, and WE19 to create test IDocs. The IDoc status codes (01–75) indicate whether an IDoc was sent successfully, is waiting, or has errors.
Advertisement