Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-BL-PT-BS-EL (Application Component) Electronic Bank Statement⤷
FIN_EB_BSIMP (Package) Electronic Bank Statement - Import
IMG Activity
| ID | FIBL_BADI_BSIMP_BKST | BAdI: Bank Statement Processing |
| Transaction Code | S_EBS_44000148 | (empty) |
| Created on | 20101011 | |
| Customizing Attributes | FIBL_BADI_BSIMP_BKST | BAdI: Bank Statement Processing |
| Customizing Activity | FIBL_BADI_BSIMP_BKST | BAdI: Bank Statement Processing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FEB_BSIMP_BANK_STATEMENT |
Use
This Business Add-In (BAdI) is used in the component Electronic Bank Statement (FI-BL-PT-BS-EL).
You only process this Customizing activity if you want to import and forward the bank statement data automatically. You can schedule an automatic import of bank statement data using the appropriate transaction. On the SAP Easy Access screen, choose Accounting -> Financial Accounting -> Banks -> Incomings -> Bank Statement -> Import and Forward (Automatically).
With this BAdI, for each format you implement how a file containing the bank statements in this format is processed.
By implementing method GET_BANK_STATEMENTS, you define how a bank statement file is split into individual bank statements. You define bank account, account number, bank statement number and date, currency, and opening and closing balance for each statement.
By implementing method SAVE_BANK_STATEMENT, you define how bank statements for a particular format are uploaded to bank data storage (tables FEBxx).
Requirements
Standard settings
The BAdI is filter-dependent.
The standard system contains the following implementations:
- Formats I, S, G - corresponds to MT940 and MT942
- Format A - corresponds to BAI
You can obtain details about these implementations from the documentation for classes CL_FEB_BSIMP_IMPL_BS_MT940 and CL_FEB_BSIMP_IMPL_BS_BAI.
You can create a new format with transaction SM30 in table/view FEBV_IMP_FORMAT.
For format-specific parameters, such as you have created for format BAI, you can create a new structure that you then register with transaction SM30 in table/view FEBV_IMP_STRUCT.
For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element Definitions tab in the BAdI Builder (transaction SE18).
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
Business Attributes
| ASAP Roadmap ID | 153 | Design enhancements |
| 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 | 20101011 |
| SAP Release Created in | 606 |
