Hierarchy

⤷

⤷

IMG Activity
ID | FIBL_FEB_IMP_DOCU | Make Settings for Import |
Transaction Code | S_EBS_44000414 | (empty) |
Created on | 20110221 | |
Customizing Attributes | FIBL_FEB_IMP_DOCU | Make Settings for Import |
Customizing Activity |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FIBL_FEB_IMP_DOCU |
Use
You make the following settings in Customizing only if you are using report Bank Statement Processing: Import and Forward (Automatically) (FEB_FILE_HANDLING) to import your bank statements.
If you are using the report for the manual import of bank statements, Bank Statement: Various Formats (SWIFT, MultiCash, BAI...) (RFEBKA00), you do not need to make any settings here.
For more information about which of the two transactions you use for which format, see the corresponding report documentation:
Activities
If you are using the report Bank Statement Processing: Import and Forward (Automatically) (FEB_FILE_HANDLING), make the following settings required for the import:
- Define logical paths from which the bank statement files are imported or in which processed bank statements are stored (see Define Logical Paths).
- Specify the import parameters in the Customizing activity Define Import Parameters.
If you want the bank statement to be downloaded to bank data storage and processed further, you have to process Customizing activity .
Customizing activity Define Transfer Information is optional. This activity supports you in correctly forwarding the bank statements in the system if you define additional parameters there.
A bank statement file to be processed is first split into individual bank statements. If such a split is not possible, the file is stored in the error directory, otherwise stored in the storage directory.
After the split, the bank statements are further processed individually in accordance with your settings:
- If the bank statement bank account is a house bank account and you have defined posting parameters, the bank statement is downloaded to bank data storage and posted in accordance with your settings.
- If the bank statement is incorrect or cannot be downloaded, it is stored in the error directory. You can define this error directory in Customizing activity Define Import Parameters for the bank statement file. If you would like to specify a different error directory for the individual bank statement, you can enter this in the optional Customizing activity Define Transfer Information.
- Storing a bank statement in transfer directories is independent of downloading and posting. In addition, the bank account in the statement must not be a house bank account. If you want to provide a bank statement for retrieval by a different system, carry out the Customizing activity Define Transfer Information.
Note
To split a bank statement file and download an individual bank statement, you must have implemented the methods in BAdI: Bank Statement Processing.
Requirements
Standard settings
Activities
Example
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | FIBL_FEB_IMP_DOCU | 0 | HLA0100028 | Electronic Bank Statement |
Maintenance Objects
Maintenance object type |
History
Last changed by/on | SAP | 20110221 |
SAP Release Created in | 606 |