SAP ABAP IMG Activity FSBP_GDPDU_DATA_GET (BAdI: Extraction of Additional Business Partner Data to DART)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ CA-FS-BP (Application Component) Business Partner Enhancements for Financial Services
     ⤷ FSBP_GDPDU (Package) Data Extraction of SAP BP-FS for GDPdU
IMG Activity
ID FSBP_GDPDU_DATA_GET BAdI: Extraction of Additional Business Partner Data to DART  
Transaction Code S_ALN_01002497   (empty) 
Created on 20031211    
Customizing Attributes FSBP_GDPDU_DATA_GET   BAdI: Extraction of Additional Business Partner Data to DART 
Customizing Activity FSBP_GDPDU_DATA_GET   BAdI: Extraction of Additional Business Partner Data to DART 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FSBP_GDPDU_DATA_GET    

Use

This Business Add-In (BAdI) is used in the Business Partner (FS-BP) component.

You can use this BAdI to extract additional business partner data to the Data Retention Tool (DART).

The BAdI is used within the function module Extract Business Partner Data to the Data Retention Tool (FSBP_GDPDU_EXTRACT_PARTNERDATA), and called when the relevant business partner tables for data extraction are read. The business partner data that is read in the tables is placed in the transfer structure C_TAB_PARTNER_DATA and extracted to the Data Retention Tool.

You should only implement the BAdI in the following cases:

  • A field with the same name already exists in the structure

    Assign a different field name in the structure and supply the field in the BAdI

  • You want to transfer a field that does not exist in CHAR format

    Define the same length for the structure field as for the table field, and format the field value for the DART.

  • You want to read additional business partner tables that were not automatically read by the system

You do not need to implement the BAdI if you want to transfer additional fields in CHAR format from the tables already read by the system. An automatic transfer is only possible this way.

Note that the field names of the customer include CI_FSBP_GDPDU_STR_DATA must match the field names of the read tables.

You extract data to the Data Retention Tool in the Extract Data transaction (FTW1A). You can display the extracted data in the Data Extract Browser transaction (FTWF). The additional fields implemented by the BAdI are also displayed here.

Requirements

You have extended the customer include structure CI_FSBP_GDPDU_STR_DATA to incorporate the fields to be added, and are reading tables that are not automatically taken into account by the system.

Standard settings

The Business Add-In is activated in the standard system.

The BAdI cannot be implemented for multiple use, and is not dependent on a filter.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

You could carry out the following steps in the BAdI implementation:

You receive the internal structure C_TAB_PARTNER_DATA. With the business partners from this internal structure, read the additional tables for the business partner and transfer the table fields in the customer include CI_FSBP_GDPDU_STR_DATA.

See also

Method

Read Additional Business Partner Data

Further information on the DART is available in the SAP Library under Data Retention Tool (DART) (CA-GFT-DART).

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_GDPDU_DATA_GET 0 KFM0000891 O PAB0000001 O KI43000001  
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20031216 
SAP Release Created in 500