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: 

How to synchronize the changes to our application documents to other systems? I have checked BDCP table, but no changes updated. Why?

Former Member
0 Kudos

How to synchronize the changes to our application documents to other systems?

I have checked BDCP table, but no changes updated. Why?

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi David,

First , when an application transaction makes changes to an object ,

the application writes change documents , which are stored in the

CDHDR and CDPOS tables.

Next , the SMD tool checks the ALE settings and the distribution model

and sees if there is a receiver interested in the object that was

changed (records which have message types to be sent are determined

from table TBD62). If the system finds an appropriate receiver, the

system creates change pointers in the BDCP(BDCP2) table that point to

change documents in the CDHDR table.

As of the releases/Support Packages entered in SAP Note 1165059, storage

has been switched to BDCP2 only and you can refer to the details in note 305462:

305462 - MOD: Migrating change pointers to table BDCP2

So you can check table BDCP2 if the change documents are stored here.

Finally, ALE standfard Function Module reads the change pointers and generate

the IDocs(Report RBDMIDOC).

Usually , the 3 steps in activating / de-activating change pointers are:

1. Activate Change Pointers Globally - Transaction BD61

2. Enable change Pointers for a Message Type - Transaction BD50

3. Specify fields for which change pointers are to be written -

   Transaction BD52.

Please ensure that you have all of the following in place and let me

know if this information has been helpful. Thank you.

Best regards

Helen

1 REPLY 1

Former Member
0 Kudos

Hi David,

First , when an application transaction makes changes to an object ,

the application writes change documents , which are stored in the

CDHDR and CDPOS tables.

Next , the SMD tool checks the ALE settings and the distribution model

and sees if there is a receiver interested in the object that was

changed (records which have message types to be sent are determined

from table TBD62). If the system finds an appropriate receiver, the

system creates change pointers in the BDCP(BDCP2) table that point to

change documents in the CDHDR table.

As of the releases/Support Packages entered in SAP Note 1165059, storage

has been switched to BDCP2 only and you can refer to the details in note 305462:

305462 - MOD: Migrating change pointers to table BDCP2

So you can check table BDCP2 if the change documents are stored here.

Finally, ALE standfard Function Module reads the change pointers and generate

the IDocs(Report RBDMIDOC).

Usually , the 3 steps in activating / de-activating change pointers are:

1. Activate Change Pointers Globally - Transaction BD61

2. Enable change Pointers for a Message Type - Transaction BD50

3. Specify fields for which change pointers are to be written -

   Transaction BD52.

Please ensure that you have all of the following in place and let me

know if this information has been helpful. Thank you.

Best regards

Helen