Hierarchy

⤷

⤷

IMG Activity
ID | FSBP_CC_B_READINESS_ | BAdI: Rules for Readiness Checks |
Transaction Code | S_FPD_79000146 | (empty) |
Created on | 20100823 | |
Customizing Attributes | FSBP_CC_B_READINESS_ | BAdI: Rules for Readiness Checks |
Customizing Activity | FSBP_CC_B_READINESS_ | BAdI: Rules for Readiness Checks |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FSBP_CC_B_READINESS_CHECK |
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_READINESS_CHECK) to control the checks that are run by the system before the data cleansing case is processed. You can define the rules used by the system to run preliminary checks and specify when the data of the participating business partner master records can (or cannot) be cleansed.
For this purpose, the BAdI implementation provides the following parameters in the CHECK_CLEANSING_CASE_READINESS method via the interface IF_FSBP_CC_B_READINESS_CHECK:
- I_TARGET_PARTNER
This parameter provides the data of the business partner master record that was specified as the target business partner.
- I_SOURCE_PARTNERS
This parameter provides the data of the business partner master records that were specified as the business partner duplicate.
- I_RELATIONSHIPS
This parameter provides the data of the business partner relationship master records for the business partner master records transferred in the I_TARGET_PARTNER and I_SOURCE_PARTNERS parameters.
- C_MESSAGES
This parameter returns the result of your preliminary check. You can control how the system behaves after the BAdI is called based on the type of messages returned:
- If an error message (E) is returned, the system cannot cleanse data. Processing is terminated.
- If a warning message (W) is returned, the system issues a warning but can still cleanse data.
- If a status message (S) is returned, you can view the information about the successful check. Data is cleansed.
The method definition does not contain any exceptions. Therefore, errors cannot trigger exceptions. Instead, errors must be returned in type E messages in parameter C_MESSAGES.
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.
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
If data cleansing cases contain business partner master records with different categories (such as Person and Organization), the business partner master records should not be merged.
The BAdI implementation reads the information about the category of business partner master records from parameters I_TARGET_PARTNER and I_SOURCE_PARTNERS and, if these are different, returns a type E message in C_MESSAGES.
Further notes
The system processes this BAdI's rules before it processes the rules for merging business partner data. You call this BAdI when you simulate or process a data cleansing case.
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 |