SAP® Documentation

Single view

/CCEE/FISIRFEBKA00 - Bank Statement: Various Formats (SWIFT, MultiCash, BAI...)

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book


The report RFEBKA00 imports bank statements into the SAP system and then generates batch input sessions for posting in General Ledger and Subsidiary Ledger Accounting.

You can use parameter instructions to specify whether both sessions should be created in one run, or if only the session for General Ledger Accounting should be created at first. The report generates the session names, whereby you can choose between various rules, for example:

  • House bank ID and account ID (for example, DREBA-GIRO)
  • House bank ID and account statement number (for example, DREBA-034)

See the input help for the Session Names field for information on the individual rules.

The session name for Subsidiary Ledger Accounting always begins with /.

Interpretation of the Note to Payee Fields

For incoming payments, you can search for document numbers or reference document numbers in the note to payee lines of the account statement by entering the selection field (BELNR or XBLNR). This gathers the relevant information for clearing customer payments.

If you do not enter a selection field, the note to payee fields are not interpreted.

For outgoing payments, the document number is always used for the search.

You can restrict the search for document numbers or reference document numbers by using the selection field length and the corresponding number range interval, and thus speed up processing. The report considers values that do not match the specified length and that are not within the specified number range as invalid and does not provide them as clearing information.

You can program a custom user exit for specific interpretations of note to payee fields (possible for insurance companies, for example).


The report checks if the business transaction codes used by the bank (external transactions) have been assigned to an "internal transaction" when the system was configured. This is required because posting to General Ledger and Subsidiary Ledger accounts is done using posting rules that are stored for an internal transaction.

If the report finds an external transaction that has not been maintained in the corresponding table, it cancels processing once the account statement has been entirely imported and outputs a list with the missing entries (error log).

The missing entries must be maintained subsequently so that the posting transactions can be created in the corresponding sessions. Then the report needs to be restarted. Note that the instruction x - Import Data is not selected this time since the bank statement already exists in the SAP system.

On restarting, the report searches the buffer for all line items that are not yet indicated as posted in the respective posting area. A line item is regarded as posted once a posting has been placed in a session.


The posting log provides you with information about all the postings sent to the batch input session, separated according to posting area. In addition, the external business transaction codes and the internal transactions that control the posting are listed.

The processing statistics show you the following:

  • How many postings
  • were generated per session

  • could not be generated due to an error

  • For how many line items per definition no posting could be created
  • how many postings
  • were created per session

  • could not be created due to an error

  • for how many line items no postings could be created by definition

BAL_S_LOG - Application Log: Log header data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4221 Date: 20200223 Time: 044328     sap01-206 ( 32 ms )

Our Service

Looking for Support? Questions?




Leave us your contact details and we will call you back. Panels marked with * are mandatory.