SAP ABAP IMG Activity FIBL_BADI_MAPPING_X (BAdI: Mapping the Bank Statement to Internal Structures)
Hierarchy
☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FIN-FSCM-CLM-CM-CM (Application Component) Basic Functions
     ⤷ FTE (Package) Bank accounting: External payment information
IMG Activity
ID FIBL_BADI_MAPPING_X BAdI: Mapping the Bank Statement to Internal Structures  
Transaction Code S_EBS_44000598   (empty) 
Created on 20120223    
Customizing Attributes FIBL_BADI_MAPPING_X   BAdI: Mapping the Bank Statement to Internal Structures 
Customizing Activity FIBL_BADI_MAPPING_X   BAdI: Mapping the Bank Statement to Internal Structures 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FIEB_MAPPING_X    

Use

This Business Add-In (BAdI) is used in the component Electronic Bank Statement (FI-BL-PT-BS-EL). You can use this BAdI to import bank statement data in XML format or in a bank-specific format.

You can use the BAdI with the following functions:

  • Report RFEBKA00 for the manual import of bank statements: Bank Statement: Various Formats (SWIFT, MultiCash, BAI...)
  • Transaction for automatically scheduling the import. In the SAP Easy Access screen, choose Accounting -> Financial Accounting -> Banks -> Incomings -> Bank Statement -> Import and Forward (Automatically).

By a filter-dependent implementation of method MAPP_BANK_STATEMENT, you can define how a bank statement in an XML format or a bank-specific format is to be mapped to internal ABAP structures. The bank statement file is transferred in parameter I_STRING.

As an alternative to the BAdI implementation, you can define the mapping using an XSL transformation. In this instance, the implementation is not a requirement, but you can if you need to still use it, for example, if the amount display in the file does not correspond to the ISO norm. In the mapping result, the display of date fields, amounts and currency codes must correspond to the ISO standard.

Requirements

The BAdI is called if the following conditions have been met:

  • There is an entry in Customizing activity Define Mapping Procedure for the format of the bank statement to be downloaded (for example, camt.053.001.02).

    There SAP and customers can define the required mapping procedure in separate key areas.

  • The appropriate entry defines a filter value for the BAdI.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

BAdI Implementations

For bank statement format camt.054, there is BAdI implementation FIEB_MAPPING_CAMT054001 in the standard system. It is called following the XSLT (transformation FIEB_CAMT054_V2_TO_FEB). The implementation checks and enhances the data that the transformation supplies as necessary, in accordance with the following aspects:

  • It checks whether all items in the bank statement file have the status Posted (meaning it checks <Sts>BOOK</Sts> at the level<Ntry>).
  • If the file does not contain a bank statement number, a number is automatically assigned.
  • If the IBAN of the house bank account is missing and in addition the bank number and account number in the <Acct><ID><Othr><ID> field are without a separator, then the implementation determines the bank number and account number using the house bank master data.

Example

See also

For information on how you implement BAdIs in the Enhancement Framework, see SAP Library for the SAP NetWeaver Platform on the SAP Help Portal under http://help.sap.com/nw_platform. Choose a Release and then Application Help. In the SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development -> Enhancement Framework.

Business Attributes
ASAP Roadmap ID 105   Define functions and processes 
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  20120531 
SAP Release Created in 606