Ansicht
Dokumentation

RFEBGB00 - Import Bank Statement: Great Britain

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Description

Program RFEBGB00 imports bank statements into the SAP System, and then creates batch input sessions to post to G/L and subledger accounts.

By selecting the parameters, you can specify whether the two sessions are generated in one run or whether only the session for G/L accounts is generated first. The batch input session names are generated by the program, in which case you can choose from two rules:

• house bank ID and account ID (for example, LL001-CURR1)

• house bank ID and bank statement number (for example, LL001-034)

The session name for subledger accounts always begins with /.

Requirements

The program checks whether the business transaction codes (external transactions) used by the bank were allocated to an internal transaction within system configuration. This is a necessary since the system posts to the G/L and subledger accounts using the posting rules stored for the internal transaction.

If the program finds an external transaction that is not maintained in the corresponding table, it terminates after fully importing the bank statement, and outputs a list with the missing entries (error log).

You must maintain these missing entries so that the system can generate the posting transactions in the appropriate sessions. You then must restart the program, making sure not to select the "Import data" field this time since the bank statement is already in the SAP System.

When restarted, the program searches the buffer for all line items that are not yet indicated as posted in the respective posting area. A line item is only regarded as posted if a posting is put into a session.

Customizing

To ensure that the program runs properly, you have to make sure that table T028G -"Allocate external transactions to internal transactions"- is maintained correctly.

1. Enter all external transaction codes. Obtain a complete list of each transaction code used by your bank.
2. Normally, banks use every bank transaction code excluding the codes for incoming and outgoing payments. Fill the Sign field with "+" for cash receipts and "-" for cash disbursements.
3. The Processing type field is used only in the United Kingdom and specifies further processing. The following entries need to be described:

• 01 - clearing with check: To be able to make a clearing, the data for the transmitted check number must already exist in the system.

• 05 - customer cash receipt: Customer payments in our favor are to be indentified by the transferred reference text. The reference text normally contains the invoice or document number.

• 05 - BACS transfer/ BACS bank collection: The bank confirms payment orders or bank collections that have been executed. The reference number transferred identifies the affected payment documents.
  Note
  To use processing type 05, always maintain the two entries. To differentiate the entries, the system supplements the external transaction code in BACS with the character string "SAPBACS" after the third character.
  Example:
  "17 ","-","17_A","05","00"
  "17 SAPBACS","-","17_B","05","19"

• 06 - bank charges / interest / dividends: In this processing type, the parameter enables you to store various G/L accounts for one account symbol in account determination.
  To do this, enter, for example, "INTEREST" or "CHARGE" in the Account modification field in table "Account determination: replace account symbols". To determine the required G/L account during G/L account determination, the system compares the note to payee transferred by the bank with the values in the "account modification" field.

1. Only specify the interpretation algorithm for BACS transactions (processing type 05). Use algorithm 19 as the interpretation algorithm.

Output

The posting log provides information, separated according to posting area, on all postings put into the batch input session. It also lists the external business transaction codes and the internal transactions which control posting.

The processing statistics show you

• how many postings

• were created per session

• could not be created due to an error

• for how many line items by definition, postings could not be created.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 5205 Date: 20240520 Time: 105933     sap01-206 ( 86 ms )