Entering Bank Statements per EDI (FI-BL-PT-BS)
Use
Bank statements that were previously imported into the system on disk can imported using EDI. Bank statement information then enters the R/3 System automatically and you can post the resulting line items or clearing postings directly. Payments received from your business partner can for example be used to clear open invoice items automatically.
The bank statement consists of a:
This contains the data on the house bank account and the present account balance.
These contain the transactions on the bank account. You can enter the line items in more detail in separate messages (credit or debit memos) in which case the bank statement contains only a reference to these messages.
An account balance request is a special kind of bank statement (polling information) and does not include any line items.
Prerequisites
Application Component
You must carry out this step before maintaining the partner profiles, since it is only when maintaining these profiles that you can select the EDI-compatible banks.
Proceed as follows:
a. In Customizing for Bank Accounting choose ® Bank Accounts ® Define House Banks.
b. Carry out the activity.
c. Enter a company code and choose Goto ® House banks.
d. Select the house bank you require (double-click).
e. Choose Goto ® DME.
f. Enter a partner number (the bank key for example).
You can branch to the partner profiles from this screen. For information on what you can define under partner profiles, refer to the section on IDocs.
To enable the system to post amounts that arise from the bank statement to the appropriate accounts automatically, you need to make the following settings for electronic bank statements. Under Customizing for Bank Accounting choose Business Transactions ® Payment Transactions ® Electronic Bank Statement
Create Transaction Types
Assign Banks to Transaction Types
Create Keys for Posting Rules
Assign External Transactions to Posting Rules
Define Posting Rules
Specify Report and Variant Selection
For more information on electronic bank statements, see the R/3 Library under Financial Accounting ® Bank Accounting ® Electronic Bank Statement
Since ISO codes can be transferred using EDI, your Customizing entries for the conversion of SAP codes into ISO codes for currencies, units of measurement, and countries must be entered in full and contain no errors.
For more information, refer to Global Settings in the Implementation Guide (IMG) and the activities Set Countries, Check Currency Codes, Check Units of Measurement.
IDoc interface
Enter the following parameters in the in-bound parameter profiles:
Field |
Value |
Message type |
FINSTA |
Partner type |
B |
Process code |
FINS |
Processing |
Immediate processing for example |
Permitted processor |
Organizational unit (an R/3 user for example) |
Activities
Inbound processing
Bank statements are processed in three stages:
It then searches for the credit memos and debit memos that are referred to in the account statement and stores the relevant key belonging to the advice note database in the account statement. The system obtains the information required to clear payments from the payment advice notes. The latter can contain the document number or any other item of information required by the user.
If the credit or debit memo does not contain any detailed data (no payment advice note items) the system enters the data into the line items of the bank statement, following which the payment advice note is deleted.
If the bank statement is solely an account balance request (polling information), the information in the bank data storage is stored in a separate area in stage 1. In stage 2, the system then generates cash management and forecast notes and not postings. At stage 3, you can the postprocess the bank statement using report RFEBPI20.
Dealing with exceptions
In the event of an error, the system generates a workitem (it starts the task FINSTA_ERROR) and determines the processor using the
IDoc interface standard method
Ensure that an administrator (who can be notified of errors automatically) is defined for the Workflow basic data. To do so, on the R/3 System screen choose Tools ® SAP Business Workflow ® Development ® Definition tools ® Tasks/Task groups ® Change.
Modifying data using customer exits
When processing IDocs, you can use interfaces to access the database either to read or to change data. To enable you to do so, the system supports several customer exits that can be called up at different stages of a program. These function modules are stored in the enhancement "FEDI0005". For more information, access Customizing for Bank Accounting and choose Business Volume ® Payment Transactions ® Electronic Bank Statement ® Develop Enhancements for Elec.Bank Statement (Format Spec.).
The following customer exits are called up when processing type FINSTA01 IDocs and can be used for customer modifications:
Function module 201 is called up immediately before bank statement data is written. For more information, refer to the documentation on function module EXIT_SAPLIEDP_201 in the enhancement FEDI0005 (transaction CMOD).
Equally, you can access the database per customer exit when writing individual segments. To do so, first define for which segments an appropriate callup should take place by maintaining table "FEDICUS".
Having done so, function module "202" is then called up for processing the segments defined in this table. For more information, see the documentation on function module EXIT_SAPLIEDP_202 in enhancement FEDI0005.
Enhancement FEB00001 for the electronic bank statement is also reached when processing inbound IDocs (report RFEBKA30 starts report RFEBBU10 from where the user exit is called up). It follows that you do not need to transfer any coding that may exist in this report to one of the customer exits of enhancement FEDI0005.