In SAP IDoc processing, explain the difference between a Segment, a Basic Type, and a Message Type ?

DPM125 — Wed, 27 Aug 2025 08:21:39 +0000

Segment

Definition: The smallest building block of an IDoc.
Represents a logical grouping of fields (like a table structure).
Each segment corresponds to a set of related data — for example:
- E1KNA1M → Customer general data (Name, Address, etc.)
- E1KNB1M → Company code–specific customer data.
Segments can be mandatory or optional, and they can repeat (e.g., multiple items in a sales order).

When to use:
Use a segment when you want to define a structure for holding related data fields inside an IDoc.

Message Type

Definition: Defines what business process or message is being sent.
It acts like a label for the IDoc to indicate its purpose.
Examples:
- ORDERS → Purchase Order / Sales Order
- INVOIC → Invoice
- DEBMAS → Customer Master
A message type is linked to a basic type (the structure of the IDoc).

When to use:
Use a message type when you want to represent a business scenario for communication between systems (e.g., sending a sales order, invoice, or master data).

Basic Type (IDoc Type)

Definition: Defines the structure of the IDoc — which segments it contains, their order, and hierarchy.
Example:
- Basic type: ORDERS05
- Segments: E1EDK01 (header data), E1EDP01 (item data), etc.
Multiple message types can be linked to the same basic type.

When to use:
Use a basic type when you need to specify the technical structure/layout of the IDoc that holds the data.

Concept	What it is	Example	Usage
Segment	Structure with fields (smallest unit)	`E1KNA1M`, `E1EDP01`	Holds related data inside IDoc
Message Type	Represents the business meaning of the IDoc	`ORDERS`, `INVOIC`, `DEBMAS`	Identifies why the IDoc is sent
Basic Type	Technical structure/layout of the IDoc	`ORDERS05`, `DEBMAS06`	Defines how the data is organized

What is IDOC and Basic Tcode used for IDOCS ?

DPM125 — Wed, 27 Aug 2025 08:18:05 +0000

An IDoc (Intermediate Document) is SAP’s standard format for electronic data interchange (EDI) between SAP systems or between SAP and external systems. It acts as a structured container for data, ensuring that the information exchanged follows a predefined format, making communication consistent and reliable across different systems.

Structure of an IDoc

Control Record – Contains metadata (sender, receiver, IDoc type, etc.).
Data Records – Actual business data (sales order, material, etc.).
Status Records – Processing status (success, error, etc.).

Used for inbound (into SAP) and outbound (from SAP) communication.

Common Scenarios for IDocs

Sending sales orders from a non-SAP system into SAP.
Transferring master data (customer, material) between SAP systems.
Sending invoices, deliveries, purchase orders electronically.

Tcode	Purpose
`WE30`	Create IDoc type
`WE31`	Create segment
`WE81`	Create message type
`WE82`	Assign message type to IDoc type
`WE20`	Partner profile configuration
`WE19`	Test tool for IDoc processing (very common)
`WE02`	Display IDocs (overview & details)
`WE05`	Display IDocs (alternative to WE02, with more selection options)
`BD87`	Reprocess failed IDocs
`WE09`	Search IDocs for specific data values
`WE60`	Documentation for IDoc types
`WE21`	Port definition (RFC, File, etc.)

Quick Example Workflow

Create a new IDoc type: WE30.
Define segments: WE31.
Link to a message type: WE81 + WE82.
Configure partner profile: WE20.
Send/Receive IDocs → Check with WE02 / WE05.
Reprocess errors → BD87.
Test → WE19.

idocs – SAP EWM Help