Hierarchy

⤷

⤷

IMG Activity
ID | BDCP_BEFORE_WRITE | Reduce Change Pointers for Message Type |
Transaction Code | S_BCE_68001581 | (empty) |
Created on | 20001117 | |
Customizing Attributes | BDCP_BEFORE_WRITE | Limit Creation of Change Pointers for Message Type |
Customizing Activity | BDCP_BEFORE_WRITE | Limit Creation of Change Pointers for Message Type |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | BDCP_BEFORE_WRITE |
The process of determining and distributing changes using the SMD tool (ALE Shared Master Data) can be speeded up by using Business Add-in BDCP_BEFORE_WRITE. This reduces the scope of change pointers to be written to changes relevant to the distribution.
Use
In Customizing you can set the writing of change pointers altogether and for each message type. Whereas, if you are developing, you set the fields in change documents and the message types for which change pointers are written.
- You would like to implement a filter that reduces the scope of the change pointers still further.
- You would like to update further data when change pointers are written.
Requirements
Change pointers are created in the following interfaces:
- The change document interface calls the change pointer function module CHANGE_POINTERS_CREATE.
- The application program calls the ALE interface CHANGE_POINTERS_CREATE_DIRECT.
Standard settings
In the standard system no filter has been set up. The standard functions therefore do not change the behavior of the change pointer interface.
Activities
Execute the function in the Implementation Guide.
- Enter an implementation name and choose Further.
The initial screen for implementations appears.
- Create a short text for your implementation.
- Under filter types select the message types that you want to filter out.
- Save your entries.
Example
Many application cases show that the granularity of change document field and message type does not always match the application requirements, when the change pointers are written.
Unnecessary change pointers are often written.
- Usually only change pointers for application objects that are actually distributed should be written. If materials with material numbers in a certain range only are distributed, only change pointers specifically for these need to be written.
- In an initial data transfer large datasets are imported into several systems. If changes are made, the data is maintained centrally and then distributed using the SMD tool. If the inital data transfer takes place when the system is in operation, change pointers cannot be written altogether because data changes would not be recognized and therefore not distributed. However, because the initial data transfer is usually carried out with specific user contexts, you should deactivate the writing of change pointers for specific users.
Examples of code for BADI BDCP_BEFORE_WRITE can be found in the BADI Builder under the menu path "Goto -> Example Code -> Display.
Business Attributes
ASAP Roadmap ID | 105 | Define functions and processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | BDCP_BEFORE_WRITE | 0 | HLB0100224 | Replication |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20001117 |
SAP Release Created in | 610 |