Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Change Pointers?

Former Member
0 Kudos

Is it possible that the Idocs of basic type OILDEB Generated using the Program "RBDMIDOC" with Variant "OILDEB" miss the few segments/Values when the Customers are changed?

In BD50,The Change Pointers are Active.

If yes,Kindly suggest what configurations should be checked for proper creation of Idoc with all Values of the Customer?

Regards,

Shashank.

3 REPLIES 3

Former Member
0 Kudos

Hi,

When you are using the change pointers concept, it won't send the complete information all the times, when you are creating a new customer then only it will send complete information, and when you are changing something in the customer master then only that new information alone will go.

This is the FM MASTERIDOC_CREATE_SMD_DEBMAS which is being called internally from the RBDMIDOC program, and that FM works on the change pointers concept.

Thanks,

Mahesh.

former_member206760
Active Contributor
0 Kudos

1. Change pointers are not globally active. Execute transaction BD61 to verify this condition.

2. Change pointers have not been activated for the message type. Execute transaction BD50 to verify

this condition.

·

3.The fields for which ALE change pointers are written do not include the field you are modifying.

Execute transaction BD52 to verify this condition.

If this step is successful, an entry should appear in the BDCP table for the change. Use transaction SE16 orSE17 to view entries in this table. If everything looks good, you should execute program RBDMIDOC to start the IDoc generation process from change pointers

Edited by: Tarang Shah on Mar 27, 2009 1:55 PM

Former Member
0 Kudos

Hi,

Follow the below steps...

1) Transaction: BD61 Activate change pointers generally. You must activate this flag in order for ANY change pointers to be written.

2) Transaction: BD50 Activate change pointers for message type. This sets up data change detection for individual message types.

3) Transaction: BD52 Define change-relevant fields.This allows you to set which fields in the master data record should trigger the writing of a change pointer. SAP proposes a default set, which usually, but not always, includes every field in the table. This is optional u2013 if you want to use SAP's default set of fields, you do not need to configure this.

Schedule IDoc creation job. This program (RBDMIDOC) will look for records that have changed, and send them to the appropriate receiving systems, based on the distribution model.

Thanks,

Asit Purbey