Ansicht
Dokumentation
FSBP_CC_B_MERGE_BP_D - BAdI: Rules for Merging of Business Partner Data
CL_GUI_FRONTEND_SERVICES - Frontend Services SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
This Business Add-In (BAdI) is used in the SAP Business Partner for Financial Services (FS-BP) component.
You can use this BAdI (FSBP_CC_B_MERGE_BP_DATA) to control the merging of business partner data. The data returned by the BAdI (E_MESSAGESparameter) changes the way in which the system processes the data cleansing case.
You can define the rules used by the system to merge business partner data and to inform the user about the results and activities during this process.
For this purpose, the BAdI implementation provides the following parameters in the MERGE_BUSINESS_PARTNER_DATA method via the interface IF_FSBP_CC_B_MERGE_BP_DATA:
- C_TARGET_PARTNER
- You use this parameter to obtain the data of the business partner master record that was specified as the target business partner. You can now apply your rules for merging business partner master records to this data.
- C_SOURCE_PARTNERS
- You use this parameter to obtain the data of the business partner master records that were specified as business partner duplicates. You can now apply your rules for merging business partner master records to this data.
- C_RELATIONSHIPS
- This parameter provides the data of the business partner relationship master records for the business partner master records transferred in the C_TARGET_PARTNER and C_SOURCE_PARTNERS parameters. You can now apply your rules for merging business partner relationship master records to this data.
- E_MAPPING_INFO
- This parameter is used to specify which data of the business partner duplicates has been merged with which data of the target business partner and which data of the target business partner replaces which data of a business partner duplicate. The calling program evaluates only the key for address data, bank details, and payment cards.
- E_MESSAGES
- You use this parameter to return information about the results and activities of your merge rules. You can control how the system behaves after the BAdI is called based on the type of returned messages:
- If an error message (E)is returned, the system terminates the processing of the cleansing case and the data is not cleansed.
- If a warning message (W) and a status message (S) are returned, the system does not cancel the merging of business partner master records or its simulation.
- Both message types should be used to provide the user with information about which data has been merged or why data could not be merged, for example.
The data cleansing function does not support change pointers in the structures of parameters C_TARGET_PARTNER and C_SOURCE_PARTNERSand C_RELATIONSHIPS. When you implement the merge methods, make sure that:
- The change pointers have not been filled
- The OBJEKT_TASK checkbox in the header of the target business partner and the duplicates is still set to C (CURRENT STATE).
If you do not make any further changes, a sample implementation of the BAdI (fallback class) is called. Note that the sample implementation of the BAdI serves as orientation and as a template. Since the rules for automating the data cleansing of business partner master records depend heavily on the user's environment, we recommend you define and implement your own rules.
For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
The example below describes how to implement the merging of birth dates and payment cards.
A data cleansing case contains two business partner master records: A (target business partner) and B (business partner duplicate). They contain the following data:
Master record A:
- Date of birth: 22.04.91
- Payment card:
| ID | Type | Name | Card Number |
|---|---|---|---|
| 0001 | 0004 | DinersCard | 36444444****40 |
Master record B:
- Date of birth: April 22, 1992
- Payment card:
| ID | Type | Name | Card Number |
|---|---|---|---|
| 0001 | 0004 | MasterCard | 30569309****04 |
The C_TARGET_PARTNER parameter contains master record A and the C_SOURCE_PARTNERS parameter contains master record B. The merge rule for the date of birth transfers the later date (April 22, 1992), the merge rule for the payment cards adds the cards of the business partner duplicates to the target business partner (if they have not already been added).
This means that the data in the target business partner master record is changed accordingly in the C_TARGET_PARTNER parameter and returned to the calling program:
Master record A:
- Date of birth: April 22, 1992
- Payment card:
| ID | Type | Name | Card Number |
|---|---|---|---|
| 0001 | 0004 | DinersCard | 36444444****40 |
| 0002 | 0004 | MasterCard | 30569309****04 |
The payment card ID has changed because data has been added. This information is also returned in the E_MAPPING_INFO parameter in case other objects refer to this ID. This mapping takes the following form:
| SOURCE_PARTNER_ID | SOURCE_BANKDETAIL_ID | TARGET_BANKDETAIL_ID |
|---|---|---|
| B | 0001 | 0002 |
The E_MESSAGES parameter informs the user about the results and activities by means of status messages:
- The later date of birth of business partner B has been transferred to business partner A
- Payment card DinersCard 30569309****04 of business partner B has been transferred
You run this BAdI in a simulation and also to process a data cleansing case. When a data cleansing case is being processed the system enter the messages from the BAdI in the log.
rdisp/max_wprun_time - Maximum work process run time General Material Data
This documentation is copyright by SAP AG.
Length: 9047 Date: 20240523 Time: 195426 sap01-206 ( 173 ms )
