Change Pointers

The change pointers technique is based on the change document

technique, which tracks changes made to key documents in SAP, such
as the Material Master, Customer Master and Sales Orders. Changes
made to a document are recorded in the change document header
table. CDHDR, and additional change pointers are written in the
BDCP table for changes relevant to ALE.

The change pointer technique is used to initiate the outbound process

automatically when master data is created or changed. For example,
if a user changes the basic description of a material master or creates
a new material, the system automatically generates an IDoc for the
material and sends it to the destination system.
The Change Pointer Technique for Distributing Master Data.

The application writes change documents. SAP maintains change

documents for several objects in the system, such as materials, customers,
invoices and bank data, to provide and audit trail for changes made to an
object. A change document object represents a set of tables for which changes
are recorded.
The SMD (Shared Master Data) tool writes change pointers. When
changes are made to an object, the SMD tool checks the ALE settings and
consults the ALE distribution model to determine whether a receiver is
interested in the object that was changed. If the system finds and appropriate
receiver, the system creates change pointers in the BDCP table that point to
change documents in the CDHDR table.

The ALE programs analyze change pointers and generate IDocs.

SAP provides standard function modules that read the change pointer table
and generated IDocs for the objects that were changed. These programs are
designed to ignore multiple changes and create only one IDoc.
A standard program, RBDMIDOC, is scheduled
to run on a periodic basis to evaluate the change
pointers for a Message Type and start the ALE
process for distributing the master data to the
appropriate destination. The RBDMIDOC
program reads the TBDME table to determine
the IDoc selection program for a message type.
Entries in this table also link a message type to
the change pointer table. The IDoc selection
program is started.
 The settings required for activating Change Pointers
Enable change pointers globally. T-code : BD61.

This option enables the change pointer process globally. Make sure that
the flag is checked.

Enable Change Pointers for a Message Type. T-Code : BD50.

This option is required for activating change pointers for a specific
message type. On this setting screen make sure that the Active flag is
checked for your message type.

Specify the Fields for which change pointers are to be written. T-Code : BD52.

For Standard Master data objects such as the material, customer, and vendor
objects, SAP already provides a list of fields for which change pointers are
written. If you are satisfied with the standard set of fields, you can skip this
step. If you want to add new fields, you must add entries for the required
fields.
 Master Data Distribution Via Change Pointers
Create or change
master data

Create or change
document

Master
Data
Analyze ALE
Changes Distribution
Change model
Pointers

Change
Pointers

Program RBDMIDOC:
Analyze change pointers
Generate IDocs
Update status of change pointers

Outbound ALE processing

Communication IDoc
Change Pointers
When you change and save
conditions, the system updates
specific change pointers that
characterize the type of change in
database table BDCP. In addition
to technical data, this table also
contains the user name of the
person making the change and the
time at which the change was