Performing Follow-Up Activities for Application Link Enabling (ALE)

Context

If you are using Application Link Enabling Shared Master Data Management, you need to migrate the change pointers to the new table BDCP2 after the update. Until you have migrated all change pointers, both the former and the new table are used. For performance reasons, migrate the change pointers as soon as possible after the update.

Procedure

To check which message types are affected and how many change pointers need to be migrated, run report RBDCPMIG_ALL_WITHOUT_MIG_FLAG in test mode.
Decide if you want to run the report for all message types at once or separately.

Running the report for each message type separately splits up the total runtime into smaller sections.
Run report RBDCPMIG_ALL_WITHOUT_MIG_FLAG in production mode.
Recommendation

If you directly access tables BDCP, BDCPS and BDCPV from your own programs, you need to adjust the source code. We recommend that you do not directly access the SAP tables, but use the interfaces provided for this purpose instead.
When you use change pointers, use the following function modules:
- For generation
  
  CHANGE_POINTERS_CREATE
  
  CHANGE_POINTERS_CREATE_DIRECT
  
  CHANGE_POINTERS_CREATE_LONG
- For reading
  
  CHANGE_POINTERS_READ
- For changing the status
  
  CHANGE_POINTERS_STATUS_WRITE
- For deletion
  
  CHANGE_POINTERS_DELETE