SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

SAP IDoc Message Types Reference

An IDoc message type tells SAP what business event a document represents, while the basic IDoc type defines the segment structure. This reference lists the message types integration developers meet most often, with the basic type and the EDI set they usually pair with.

Download:

Message type	Typical basic IDoc type	Business meaning	Typical flow	Usual X12 set	Usual EDIFACT message
ORDERS	ORDERS05	Purchase order (outbound) or customer order (inbound)	Both	850	ORDERS
ORDRSP	ORDERS05	Order response / confirmation	Both	855	ORDRSP
ORDCHG	ORDERS05	Purchase order change	Both	860	ORDCHG
DESADV	DELVRY03	Delivery / advance ship notice	Outbound from supplier	856	DESADV
SHPMNT	SHPMNT05	Shipment (transportation) data	Both	204	IFTMIN
INVOIC	INVOIC02	Billing document / invoice	Both	810	INVOIC
REMADV	PEXR2002	Payment advice from payer	Both	820	REMADV
PAYEXT	PEXR2002	Extended payment order (payment run)	Outbound	820	PAYEXT
DELFOR	DELFOR02	Delivery schedule / forecast	Both	830	DELFOR
DELINS	DELFOR02	Delivery schedule with JIT detail	Both	862	DELJIT
INVRPT	INVRPT01	Inventory report / stock status	Both	846	INVRPT
MATMAS	MATMAS05	Material master distribution	ALE distribution	None standard	PRODAT
DEBMAS	DEBMAS07	Customer master distribution	ALE distribution	None standard	PARTIN
CREMAS	CREMAS05	Vendor master distribution	ALE distribution	None standard	PARTIN
BOMMAT	BOMMAT05	Bill of material for a material	ALE distribution	None standard	None standard
CLFMAS	CLFMAS02	Classification (class assignment) master	ALE distribution	None standard	None standard
ADRMAS	ADRMAS02	Address master	ALE distribution	None standard	None standard
COND_A	COND_A01	Pricing condition records	ALE distribution	832 (price/sales catalog)	PRICAT
WMMBXY	WMMBID02	Goods movement posting from external WM or MES	Inbound	None standard	None standard
HRMD_A	HRMD_A07	HR master data (org units, positions, persons)	ALE distribution	None standard	None standard

Basic type version suffixes (05, 07 and so on) depend on your release. Check WE60 for the segments in your system and WE82 for the message type to basic type assignment. The X12 and EDIFACT columns show the usual business equivalents, not a fixed standard mapping.

Want IDoc errors explained automatically?

Ask for a short review of how an on-prem AI assistant could read your IDoc error logs and suggest fixes.

Optional. The tool and every export work without this. No spam.

How to use the reference

Type a message type, a basic type or a business word such as invoice into the search box and the table filters instantly. Use the basic type column to open the structure in WE60 and the flow column to decide whether you need a partner profile in WE20 for inbound or outbound. Export the filtered rows to Excel to attach to an interface specification or a mapping workshop.

Message type versus basic type versus extension

The message type (WE81) names the business meaning. The basic type (WE30) is the segment layout. An IDoc extension adds custom segments to a basic type. The link between them is maintained in WE82. One basic type can serve several message types, which is why ORDERS, ORDRSP and ORDCHG all use ORDERS05.

WE81 lists message types, WE82 assigns them to basic types
WE30 is the IDoc type development editor
WE60 shows the documentation of a type and its segments
Custom fields normally go in a Z extension, never a modified standard type

Master data versus transactional IDocs

MATMAS, DEBMAS and CREMAS are master data messages usually distributed through ALE with change pointers (BD50, BD61 and BD21). ORDERS, DESADV and INVOIC are transactional messages normally generated from output control (NACE or the newer output management in S/4HANA). The delivery mechanism matters when you troubleshoot why an IDoc was or was not created.

Common mistakes

Teams often copy a standard type to a Z type instead of using an extension, which makes upgrades painful. Others assume the X12 set is fixed, when in practice the EDI subsystem or CPI mapping decides it. Always confirm the exact basic type version for your release before writing a mapping.

Frequently Asked Questions

What is the difference between an IDoc message type and basic type?

The message type describes the business meaning, such as INVOIC for an invoice. The basic type defines the segments and fields, such as INVOIC02. The assignment between the two is stored in WE82, and several message types can share one basic type.

Which IDoc type is used for a purchase order?

A purchase order is normally sent with message type ORDERS and basic type ORDERS05 through output control. The same basic type is used for order responses (ORDRSP) and changes (ORDCHG). Check your release in WE60 to confirm the version.

How do I find all IDoc types in my system?

Use WE30 for basic types, WE81 for message types and WE82 for the assignment between them. WE60 gives the documentation view with segments and field descriptions, which is the most useful for mapping work.

Is the X12 column an official SAP mapping?

No. It shows the EDI transaction set that normally carries the same business content. The actual mapping is built in your EDI subsystem, SAP CPI or PI/PO, and varies by trading partner and implementation guideline.

If you are building or monitoring many IDoc interfaces, Netray can help you add an AI layer that explains failed IDocs in plain language, on-prem if needed.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools