Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FS-BP (Application Component) Business Partner⤷
FSBP_ARCH (Package) Archiving FSBP Business Partner
IMG Activity
| ID | FSBP_ARCH_RFC_DATA | BAdI: Read RFC Destination |
| Transaction Code | S_PLN_62000527 | (empty) |
| Created on | 20040428 | |
| Customizing Attributes | FSBP_ARCH_RFC_DATA | BAdI: Read RFC Destination |
| Customizing Activity | FSBP_ARCH_RFC_DATA | BAdI: Import RFC Control Data |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FSBP_ARCH_RFC_DATA |
Use
This Business Add-In (BAdI) is used in the following components:
- CA-BP-FS extensions for financial service providers
- FS-BP business partner
Before a business partner is archived, all SAP Business Partner for Financial Services users must check whether the business partner can be archived or deleted from the perspective of the application. You cannot assume that the business partner and the application exist in the same physical system. With this scenario, you need to run the application checks on the external system.
In the BAdI implementation to be created, you can convey the RFC destination on which the corresponding check module for the Business Data Toolset (BDT) events ARCH1, DELE1, ADDEL, BKDEL and RLDEL are to be executed.
Requirements
You have activated your application in the BDT Customizing for the business partner under Control -> Applications. If the application is active, the function module to be called for the application must either be active in the local system, or you must specify the corresponding RFC destination in the BAdI implementation. If you specify the RFC destination in the BAdI implementation, a check is performed to ascertain whether the function module is active in the external system.
Standard settings
The BAdI is not active in the standard system.
The BAdI is dependent on a filter. You can create an implementation for each application. As the RFC destination is only known in the customer system, no BAdI implementation is supplied with the standard system.
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
Use by the Collateral Management System (CMS) application
The necessary events have been created for the CMS application in the function group FSA1_ARCH. These function modules act as function module holders, and contain the call for the application check module. Before a check module is called, the parameters required for the RFC call are checked with the function module FSBP_CENTRAL_RFC_DATA_CHECK. The application to be checked in BDT Customizing is called FSA1FS-BP: Archiving CMS Check.
See also
This BAdI uses interface IF_EX_FSBP_ARCH_RFC_DATA. For more information, display the interface in the Class Builder.
Methods
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 |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | FSBP_ARCH_RFC_DATA | 0 | PAB0000001 O KFM0000891 O KI43000001 O HLA0100105 |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20040503 |
| SAP Release Created in | 500 |
