CDM Vs Change Pointer

[Former Member]

If we can distribute master data using CDM (bd64), then what is the use of change pointers?

If data can be distributed using cdm (bd64) then wht is the use of change pointer concept?

Please explain ,

points will be rewarded

[ashok_kumar24]

Hi,

Change Pointers are triggered when there is a requirement to distribute data, on change in Master data.
For Eg: when a new material is added then change pointers are triggered and the Material Master is distributed to the recieving system.

Normally you configure the change pointers for large sets of master data when data has to be pumped out to the recieving system continously whenever a new material has been added to the material master.

If you want to distribute master data changes with the SMD tool (Shared Master Data), changes to the master data objects are flagged for distribution by change pointers ( ® Master Data Distribution).

The SMD tool is connected to the change document interface. If the master data changes are to be distributed, the application writes a change document. The contents of this are passed to the SMD tool. The tool writes change pointers, reads the application data and creates the master IDoc.

The master IDoc is then passed to the ALE layer, which sends it to all interested systems.

The change pointer tables (BDCP und BDCPS) should be as small as possible. Use as few change pointers as possible and delete change pointers which you no longer need.

You can increase the rate of processing by using the Analyze Change Pointer and Reorganize Change Pointer functions.

Checklist to keep the change pointer tables as small as possible:

1. Do you really need change pointers?

You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.

You can deactivate change pointers and activate them again with the transaction BD61.

2. Do you really need to activate change pointers for this messages type?

If some messages types are no longer to be distributed by change pointers, you can deactivate change pointers for this messages type.

You can deactivate change pointers for the message type

and reactivate them again.

For reduced message types, deactivate the change pointer with the

Reduction tool (transaction BD53).

From Basis Release 6.10, you can restrict the creation of change pointers in customer exits. This functionality is provided in advance in the Note 'Reducing the amount of data for change pointers' (0420562).

The report RBDCPCLR deletes processed and/or obsolete change pointers.

Features
This report deletes change pointer entries from the database tables. In Test mode, only a list of the selected entries is output. Entries are only physically deleted from the database when the test flag is not set.

You can select obsolete and/or processed change pointers, or select by date and time.

· Obsolete change pointers are those created before a specified date and time. If this flag is set, the obsolete change pointers are reorganized, whether or not they have already been processed.

· Processed change pointers are those which were processed within a specified period (date and time). If this flag is set, the processed change pointers are reorganized.

The report outputs the number of change pointers deleted, or, in test mode, selected.

Activities
1. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Services ® Change Pointers ® Reorganize (BD22).

2. Select Test if you only want to display the selection result.

3. Specify a message type.

4. Specify whether you want to reorganize obsolete and/or processed change pointers, and run the report.

Thanks
Ashok