Skip to content
ERP Preflight

Change pointer

Change pointer (ALE)

A record SAP writes when a relevant master data field changes, so that ALE can later distribute the change as an IDoc.

The chain has several settings that must fit together: change pointers activated globally (BD61) and for the message type (BD50), the fields that create pointers assigned to the message type (BD52), the distribution model (BD64), and a job that processes open pointers (BD21, report RBDMIDOC).

A field only creates change pointers if its data element is change-document relevant. Reduced message types (BD53) can filter fields out of the IDoc.

Changes are silently not distributed when a field is missing in BD52, the message type is not activated, the processing job is not scheduled or fails, or configuration differs between systems because a transport is missing.

In ERP Preflight

Change Pointer Coverage Auditor compares the fields a receiver needs with the exported BD61/BD50/BD52 configuration and the pointer backlog, and reports every gap with evidence.

Problems that involve Change pointer

Written for ERP Preflight · reviewed September 27, 2026

All glossary terms

ERP Preflight is independent and not affiliated with SAP SE. SAP, ABAP, Fiori and S/4HANA are trademarks of SAP SE.

What is Change pointer? Change pointer (ALE) explained | ERP Preflight