Change Pointer Method

[Former Member]

Hi All,

I am using object OIF_PBL for change pointer method.Whenever I make any changes by Transaction O402, table CDHDR and CDPOS. But I need that changes should also reflect in table BDCP.Because it is required for change pointer method. What should I exactly do achieve this?

Please help.

Regards,

Jeetu

[Former Member]

Please check if the change pointers are active for the message type.

To check this, use table: TBDA2.

Kind Regards

Eswar

[Former Member]

Hi Eswar,

Yes, It is there.

DO u have any other alternative why changes not going to BDCP table.

Regards,

Jeetu

[Former Member]

Please check if number range is defined for the same.

To check it:

1. Go to table NRIV.

2. Give object: ALE_CP.

Check if an entry exists for internal assignment.

Kind Regards

Eswar

[Former Member]

Eswar,

Yes there is an entry for object ALE_CP.

I have another doubt.Actually BDCP2 table is being updated not BDCP.Is it OK? Is this sufficient for change pointer method? Please clarify.

Regards,

Jeetu

[Former Member]

Also check whether Change Pointers are activated Generally via transaction <b>BD61</b>.

Table: BDCP2 gets updated when itz specified via transaction BD60.

Kind Regards

Eswar

[Former Member]

Eswar,

I want to know whether it is accepted BDCP or BDCP2 is updated.Still can I achieve my requirements?

Regards,

Jeetu

[Former Member]

Hope the following will help :

Information on Whether Change Pointers are Written to BDCP2

ALE change pointers are stored in the database tables BDCP/BDCPS and BDCP2. If message types support the use of BDCP2, you should make use of this option, since it considerably improves the speed at which change pointers are accessed both in read and write mode. The message types are characterized by the indicator BDCP2_SUP = 'X' in table TBDME.

If you already have change pointers stored in BDCP/BDCPS for a message type that you want to use with new change pointers, you must migrate the change pointers. Proceed as follows to do this:

During the migration process, change pointers of the message types to migrated must not be processed. From an organizational point of view, ensure that they cannot be processed, and then proceed as follows for

migration:

o Process the open change pointers, if possible.

o Delete processed and old change pointers.

o Set the change pointer destination for the message types to be

migrated to 'M', i.e. migration from BDCP/BDCPS to BDCP2.

In productive operation, do not switch from BDCP2 storage back to

BDCP/BDCPS storage. Back-migration is not supported. The change pointers in table BDCP2 are then not visible for the application, and data may be inconsistent as a result.

Cheers.