Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
FS-BP (Application Component) Business Partner⤷
FS_BP_FSP_CLEANSING_DOCU (Package) FS Business Partner Data Cleansing - Documentation Objects
IMG Activity
| ID | FSBP_CC_B_RELEASE_TO | BAdI: Rules for Release-Relevance |
| Transaction Code | S_FPD_79000148 | (empty) |
| Created on | 20100823 | |
| Customizing Attributes | FSBP_CC_B_RELEASE_TO | BAdI: Rules for Release-Relevance |
| Customizing Activity | FSBP_CC_B_RELEASE_TO | BAdI: Rules for Release-Relevance |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FSBP_CC_B_RELEASE_RELEVANCE |
Use
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_RELEASE_RELEVANCE) to control the release-relevance for data cleansing cases. You can define the rules based on which the system decides whether a data cleansing case is transferred to a release process.
For this purpose, the BAdI implementation provides the following parameters in the IS_RELEASE_RELEVANT method via the interface IF_FSBP_CC_B_RELEASE_RELEVANCE:
- I_TARGET_PARTNER_OLD
This parameter provides the dataset of the target business partner master record before it was merged. You can use this parameter together with the data of the other parameters to determine the release-relevance of the changed data.
- I_SOURCE_PARTNERS_OLD
This parameter provides the dataset of the business partner duplicates before they were merged. You can use this parameter together with the data of the other parameters to determine the release-relevance of the changed data.
- I_RELATIONSHIPS_OLD
This parameter provides the dataset of the business partner relationship master records of the business partner in I_TARGET_PARTNER_OLD and I_SOURCE_PARTNERS_OLD before they were merged. You can use this parameter together with the data of the other parameters to determine the release-relevance of the changed data.
- I_TARGET_PARTNER_NEW
This parameter provides the dataset of the target business partner master record after it was merged. You can use this parameter together with the data of the other parameters to determine the release-relevance of the changed data.
- I_SOURCE_PARTNERS_NEW
This parameter provides the dataset of the business partner duplicates after they were merged. You can use this parameter together with the data of the other parameters to determine the release-relevance of the changed data.
- I_RELATIONSHIPS_NEW
This parameter provides the dataset of the business partner relationship master records of the business partner in I_TARGET_PARTNER_NEW and I_SOURCE_PARTNERS_NEW after they were merged. You can use this parameter together with the data of the other parameters to determine the release-relevance of the changed data.
- I_MAPPING_INFO
This parameter provides information about 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. This information consists only of the key for address data, bank details, and payment cards.
- C_IS_RELEASE_RELEVANT
This parameter informs the calling program of your decision as regards release-relevance. You can use this parameter to control whether a processed data cleansing case is relevant for release.
- C_MESSAGES
This parameter returns information about the results of your implemented release-relevance check. 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 cancels the process step.
If a warning message (W) and a status message (S) are returned, the system does not cancel the process step.
Both message types should be used to provide the user with information about whether a data cleansing case need to be released.
Requirements
You have made an implementation of this BAdI available.
You can use the sample implementation of the BAdI 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.
If you are using the Framework for the Principal of Dual Control (CA-GTF-TS-PDC) to control the release process, make sure that the release object FSBP_CC (Data Cleansing Case - SAP Business Partner for Financial Services) has been configured accordingly.
Standard settings
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
The following example describes a release-relevance check.
A data cleansing case contains two business partner master records: A (target business partner) and B (business partner duplicate). They contain the following data before and after merging. This data is provided in the corresponding parameters of the BAdI method:
Master record A before merging (I_TARGET_PARTNER_OLD):
- Date of birth: April 22, 1991
Master record B before merging (I_SOURCE_PARTNERS_OLD):
- Date of birth: April 22, 1992
Master record A after merging (I_TARGET_PARTNER_NEW):
- Date of birth: April 22, 1992
Master record B after merging (I_SOURCE_PARTNERS_NEW):
- Date of birth: April 22, 1992
If the birth date of a business partner master record is changed by the merge process, the data cleansing case needs to be released. In the example above, the merge rule transfers the later birth date (April 22, 1992) to the target business partner master record. This means that the data cleansing case is relevant for release and the system returns the results true (X) in parameter C_IS_RELEASE_RELEVANT.
Parameter C_MESSAGES informs the user about the reason for the release decision:
- Release required because partner A and B have different birth dates
Further notes
You run this BAdI when you process a data cleansing case.
If this BAdI classifies the data cleansing case as relevant for release and transfers it to the release process, the master records for the business partner business partner relationship are not changed by this process in the database until the data cleansing case has been released.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20130129 |
| SAP Release Created in | 400 |
