Upload Bank Statements - Using Format Selection
Application component: SAP Cash Management
App type: SAP GUI
Description:  You use this function to import bank statements and then create batch input sessions for updating in G/L accounting and in the subsidiary ledger. Using parameters, you can specify whether both input sessions are generated in one run or whether only the session for G/L accounting is generated first. The batch input session names are generated by the report. In the report you can select various rules, such as:   House bank short key plus account key. For example, DREBA-GIRO. House bank identification code and bank statement number. For example, DREBA-034.   You can take the individual rules from the entry help for the session names field. The batch input session name for subledger accounting always starts with /. You can define the following parameters:   Only Bank Accounting: This parameter relates to the Post Immediately field .  Session Names: This parameter relates to the Generate Batch Input field. Assign Value Date: This parameter is independent of the posting mode.  Interpretation of the note-to-payee fields    When the bank statement contains incoming payments, you can have the system search the note-to-payee fields for either document numbers or reference document numbers. This way you obtain the relevant information for clearing customer payments. If you want the system to perform this search, specify the BELNR or XBLNR selection field,   If you don't specify a selection field, the note-to-payee fields aren't interpreted.   For outgoing payments, the program always searches for the document number.   Using the length of the selection field and the corresponding number range, you can narrow down the search for document numbers or reference document numbers and accelerate processing. The program ignores values that don't correspond to the predefined length and that are outside the specified number interval. As a result, these values aren't used as clearing information.    Requirements The program checks whether the business transaction codes (external transactions) that are used by the bank were allocated to an internal transaction within the system configuration. This is necessary because the system uses the posting rules that are defined for an internal transaction to post to the G/L and subledger accounts. If the program finds an external transaction that isn't maintained in the corresponding table, the program terminates after importing the bank statement, and outputs a list with the missing entries (error log). Procedure You must maintain these missing entries so that the system can generate the posting transactions in the appropriate sessions. The report must then be restarted. Note that the statement x - Import Data is not selected this time since the bank statement is already in the SAP system. When the program is restarted, it searches the buffer for all line items not yet indicated as posted in the respective posting area. The program considers a line item to be posted only if a posting is included in an input session. Output The posting log provides information about all postings that are included in the batch input session and this information is separated according to posting area. 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 or how many couldn't be created due to an error. 
Business roles: Administrator - Accounts Payable and Receivable (FI-CA)| Cash Management Specialist
Administrator - Accounts Payable and Receivable (FI-CA): (is an add-on role to the Administrator)
Is responsible for the planning, scheduling and execution of jobs and mass activities within FI-CA, including critical Business processes, such as payment run, payment lot, dunning run. 

Accounts Receivable Accountant : 
Carries out the most important functions in accounts receivable accounting with a special focus on creation and execution.

Cash Management Specialist : 
Executes cash transactions and centrally manages bank accounts with a wide range of attributes, including overdraft limit and signatories, utilizing approval process for opening or closing bank accounts, and the regular inventory/auditing process.