Integration
SAP change pointer problems: why changes are not distributed
Change Pointer Coverage Auditor compares the fields a receiver needs with the exported change pointer configuration and runtime state, and reports every gap that silently stops IDoc distribution.
Detected by:Change Pointer Coverage Auditor
Documented problems
- CriticalChange pointers globally deactivated (BD61)
CP_GLOBAL_DEACTIVATED
- CriticalMessage type change pointers inactive (BD50)
CP_MSG_TYPE_DEACTIVATED
- MajorCustom field omitted from BD52
CP_CUSTOM_FIELD_OMITTED_BD52
- MajorData element not change-document relevant
CP_FIELD_DD04L_CHGFLAG_MISSING
- MajorExpected field not linked in BD52
CP_FIELD_NOT_CONFIGURED_BD52
- MajorDuplicate change pointers for the same change (retry anomaly)
CP_RUNTIME_DUPLICATE_POINTER
- MajorBusiness change without the expected change pointer (expected vs observed)
CP_RUNTIME_POINTER_MISSING
- MajorUnprocessed change pointer backlog (BDCP2)
CP_RUNTIME_UNPROCESSED_BACKLOG
- MinorField filtered by reduced message type (BD53)
CP_FIELD_FILTERED_BD53
Terms used in this area
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.
ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.