Process documentationReceiving a Bank Statement per EDI

 

The account statement that was previously retrieved using data medium exchange can now be imported by electronic data interchange (EDI). This process is automatic and allows you to process bank statement information in the system. For information on the EDI interface in the SAP system, refer to the IDoc Interface / Electronic Data Interchange documentation.

Note Note

End of the note.

You can find additional information about the various forms of data transfer under Start of the navigation path SAP ERP Next navigation step Cross-Application Functions in SAP ERP Next navigation step Scenarios in Applications End of the navigation path then ALE/EDI Business Processes.

A bank statement consists of two levels. On the summary level, the house bank account is identified and the current account balance is transmitted. On the transaction amount level, transactions for the bank account are logged. The transaction amounts can be described in detail in seperate messages (credit or debit memo). In this case, only a reference to these messages is transferred in the bank statement.

EDI bank statement processing takes place in three steps. In the first step, data is automatically imported into the system and stored in bank data storage or in the payment advice note database. In the next step, you have to plan program RFEBKA30, which generates the postings from the bank statement. For more information, see the documentation for the report. The subsequent processing transaction for the electronic bank statement (FEBAN) is also available for processing the bank statement.

The account balance request (polling information) is a special kind of bank statement. In this case, no transaction amounts are transferred. The information is stored in a separate area in bank data storage. Instead of postings, payment advice notes from cash management and forecast are generated. You can use program RFEBPI20 for postprocessing. For more information, see the documentation for the report.

Prerequisites

  • You require an EDI subsystem on an EDI server.

  • Process partner profiles for EDI

    To set up a partner for inbound bank statements using EDI, you have to maintain the partner profiles for EDI in the system administration menu. Choose Start of the navigation path Tools Next navigation step Business Communication Next navigation step IDoc Basis Next navigation step IDoc Next navigation step Partner Profile End of the navigation path. Create a partner with process code FINS (inbound parameters) for input. The related message name is FINSTA. For the credit memo display, use process code CREA and message CREADV; for the debit display, use process code DEBA, message DEBADV.

    For more information, read the IDoc Interface / Electronic Data Interchange documentation.

  • Process ISO codes

    As ISO codes are transmitted by EDI, you must maintain the tables for converting the SAP codes into ISO codes for currency, units of measure and countries accurately and completely.

    For more information, read the documentation for the following steps in SAP Customizing implementation guide (IMG) under Global Settings in the following steps:

    • Define countries

    • Check currency codes

    • Check units of measure

  • Customizing the Electronic Bank Statement

    Input of bank statements by EDI is one form of the electronic bank statement. You need, therefore, to maintain the Customizing tables for the electronic bank statement. When you use the bank statement to request an account balance (polling information), you must enter a planning type for the assignment of banks to the transaction types. The system then generates cash management and forecast payment advice notes automatically.

    For more information about Customizing, see the SAP Customizing implementation guide (IMG) under Start of the navigation path Financial Accounting Next navigation step Bank Accounting Next navigation step Business Transactions Next navigation step Payment Transactions Next navigation step Electronic Bank Statement End of the navigation path.

Process

The payee's bank sends a bank statement as an EDI message (like FINSTA in EDIFACT standard) to its customers. The customer's EDI subsystem generates an intermediate document (IDoc type FINSTA01, logical message FINSTA) from the EDI message, and the intermediate document is forwarded to the SAP system. The process code from the partner profile controls processing of the intermediate document.

Processing

When the intermediate document is processed, its data is transferred to SAP data storage for the bank statement and the payment advice notes. The system evaluates Customizing and the Customizing data (postings rules, company code, house bank account data, and so on) is added to the bank statement. The system then searches for the credit and debit memos referenced in the bank statement and stores the key from the payment advice note database in the bank statement. The system uses the information contained in the payment advice notes to clear payments. The payment advice notes may also contain the document number and any other criterion required by the user. If the credit or debit memo does not include any detailed information (no payment advice note items), the data is transferred to the bank statement item and the advice note then deleted. If no errors occur, inbound processing ends with an update of bank data storage. The postings that result from the bank statement must then be generated by a program (RFEBKA30, see above).

Effect of Errors on the Dataset

In the event of an error, the system starts the standard workflow task FINSTA_ERROR You must make sure that an administrator is defined in the basic task data who can be informed automatically if an error occurs. You maintain tasks using transaction PFTC.

Using Customer Exits to Modify Data

There are clearly defined interfaces that you can use to read or change the dataset when processing the interim document. To this end, the system supports a number of customer functions that are accessed at certain times. The function modules are stored in enhancement FEDI0005.

The following customer functions are accessed during processing of type FINSTA01 interim documents and can be used to create customer modifications:

  1. Saving a bank statement – calling function module 201:

    The function module is called immediately before the bank statement data is written. For detailed information, see the documentation for function module EXIT_SAPLIEDP_201 in enhancement FEDI0005.

  2. Dynamic Calls

    You can also access the dataset when writing individual segments for each customer function. You must first define the segments for which such access is to be made. To this end, maintain table FEDICUS. The system then accesses function module 202 for processing the segments you specify in table FEDICUS.

    For detailed information, see the documentation for function module EXIT_SAPLIEDP_202 in enhancement FEDI0005.

    Note Note

    Enhancement FEB00001 of the electronic bank statement is also run during IDoc entry (report program RFEBKA30 accesses report program RFEBBU10 (from where the customer exit is called up). This means that it is not necessary to transfer any code defined there to one of the customer functions in enhancement FEDI0005.

    End of the note.
Changes in System Administration

Within a test system, you can change any IDoc data created that you want You require the following authorization for this: Object S_IDOCMONI Activity: 02.

The system logs all the changes made to an IDoc: To ensure that the subsystem actually processes the original data for a payment IDoc, authorization can only be given within a productive system in exceptional circumstances and for a limited period of time.

Further Information

The EDI Interface Enhancement Concept enables you to add further segments (for example, for industry-specific or customer-specific data) to existing IDoc structures. These must be supplied by the converter as appropriate.