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_FILE | BAdI: File Processing |
| Transaction Code | S_EBS_44000147 | (empty) |
| Created on | 20101011 | |
| Customizing Attributes | FIBL_BADI_BSIMP_FILE | BAdI: File Processing |
| Customizing Activity | FIBL_BADI_BSIMP_FILE | BAdI: File Processing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FEB_BSIMP_FILE |
Use
This Business Add-In (BAdI) is used in the Electronic Bank Statement (FI-BL-PT-BS-EL) component.
You only process this Customizing activity if you want to import 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).
Format determination
You can specify the format for a bank statement by implementing method DETERMINE_FILE_FORMAT. The format specified in Customizing activity Define Import Parameters is then overwritten.
The method is called before a file is processed.
Blocking mechanism for files
When importing, you must ensure that the bank statement file is complete, and nothing more is written to the file. You can set up various blocking mechanisms for this, for example:
- By assigning a termporary file name during file creation, so that the file is ignored when reading the directory (the name does not match the search pattern from Customizing).
- By the existence of an indicator file
- By changing the file size or change date
You can implement the following methods for checking such blocking mechanisms:
- Method CHECK_FILE_BEFORE_READING is called directly before importing the file
- Method CHECK_FILE_BEFORE_RPROCESSING is called directly before processing the logical bank statements
You can terminate processing of the current file using exception SKIP_FILE. The file remains in the source directory and is read again when you next call the program.
Requirements
Standard settings
The BAdI is not filter-dependent.
There is an example implementation in the standard system: FEB_BSIMP_FILE. Method File Check Before Processing Start (CHECK_FILE_BEFORE_PROCESSING) checks the change to the file size and the change date.
For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot Element Definitions tab in 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 | 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 | 20101011 |
| SAP Release Created in | 606 |
