IDoc
Intermediate Document
SAP’s standard container for asynchronous EDI and ALE messages, for example ORDERS or MATMAS, exchanged between systems and partners.
An IDoc has a message type, which names its business meaning (for example MATMAS for material master data), and a basic type, which defines its structure. Master data changes are typically distributed as IDocs that are created from change pointers.
In cloud targets, some IDoc basic types cannot be used; for many interfaces SAP names business events or released APIs as successors.
In ERP Preflight
Change Pointer Coverage Auditor checks the configuration that decides whether change IDocs are created; ECC2Cloud Navigator classifies the IDoc interfaces of a legacy system as supported, replaceable by an event or API, or blocked.
Problems that involve IDoc
- BlockerIDoc type not supported in the cloud target
- MajorCustom field omitted from BD52
- MajorDuplicate change pointers for the same change (retry anomaly)
- CriticalScheduled integrations depend on the target
- BlockerClassic transaction prohibited in S/4HANA Cloud
- CriticalLegacy object has no equivalent in the cloud target
- MajorUnreleased BAPI / RFC interface
- MajorLegacy object needs a cloud extension
Related terms
Free tools
- Knowledge & error search
Search the reviewed knowledge base, SAP objects and the finding codes of the analysis engines.
Background articles
- Change pointers and BD52: why master data changes are not distributedHow ALE change pointers work end to end — global activation, message type activation, BD52 field assignment and BD21 processing — and the configuration gaps that silently stop IDoc distribution.
Written for ERP Preflight · reviewed September 27, 2026
All glossary termsERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.