Description
Program &REPORT& imports bank statements into the SAP System, and thencreates batch input sessions to post to G/L and subledger accounts.
By selecting the parameters, you can specify whether the two sessionsare generated in one run or whether only the session for G/L accountsis generated first. The batch input session names are generated by theprogram, 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 /.

Precondition
The program checks whether the business transaction codes (externaltransactions) used by the bank were allocated to aninternal transaction within system configuration.This is a necessary since the system posts to the G/L and subledgeraccounts using the posting rules stored for the internal transaction.
If the program finds an external transaction that is not maintained inthe corresponding table, it terminates after fully importing the bankstatement, and outputs a list with the missing entries (error log).

Procedure
You must maintain these missing entries so that the system can generatethe posting transactions in the appropriate sessions. You then mustrestart 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 thatare not yet indicated as posted in the respective posting area. A lineitem 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 thattable T028G -"Allocate external transactions to internal transactions"-is maintained correctly.
Enter all external transaction codes. Obtain acomplete list of each transaction code used by your bank.
Normally, banks use every bank transaction code excluding the codes forincoming and outgoing payments. Fill the Sign field with "+" forcash receipts and "-" for cash disbursements.
The Processing type field is used only in the United Kingdom andspecifies further processing. The following entries need to bedescribed:
01 - clearing with check: To be able to make a clearing, the data forthe transmitted check number must already exist in the system.
05 - customer cash receipt: Customer payments in our favor are to beindentified by the transferred reference text. The reference textnormally contains the invoice or document number.
05 - BACS transfer/ BACS bank collection: The bank confirms paymentorders or bank collections that have been executed. The referencenumber transferred identifies the affected payment documents.
Note
To use processing type 05, always maintain the two entries. Todifferentiate the entries, the system supplements the externaltransaction code in BACS with the character string "SAPBACS" after thethird character.
Example:
"17 ","-","17_A","05","00"
"17 SAPBACS","-","17_B","05","19"
06 - bank charges / interest / dividends: In this processing type, theparameter enables you to store various G/L accounts for one accountsymbol in account determination.
To do this, enter, for example, "INTEREST" or "CHARGE" in theAccount modification field in table "Account determination:replace account symbols". To determine the required G/L account duringG/L account determination, the system compares the note to payeetransferred by the bank with the values in the "account modification"field.
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 postingarea, on all postings put into the batch input session. It also liststhe external business transaction codes and the internal transactionswhich 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.