/CCEE/FISIRFEBKA00 - Bank Statement: Various Formats (SWIFT, MultiCash, BAI...)
ROGBILLS - Synchronize billing plans CPI1466 during BackupThis documentation is copyright by SAP AG.
Description
The report RFEBKA00 imports account statements into the SAP System and then creates batch input sessions for updating in G/L accounting and in the subsidiary ledger.
By specifying parameters, you can specify whether both sessions should be created in one run or onlythe session for G/L accounting first. The batch input session names are generated by the report, in which case you can choose from various rules, such as:
- house bank identification code and account identification code (for example DREBA-GIRO)
- house bank identification code and account statement number (for example DREBA-034)
Take the individual rules from the entry help (F4) for the folder names field.
The batch input session name for subsidiary ledger always starts with /.
Interpretation of the note to payee fields
For incoming payments, the notes to payee lines of the account statement can be searched either fordocument numbers or reference document numbers by specifying the selection field (BELNR or XBELNR). Thus, the relevant information for clearing customer payments is obtained.
If you do not specify a selection field, the note to payee fields are not interpreted.
For outgoing payments, one always searches for the document number.
Via the length of the selection field and the corresponding number range, you can narrow down the searchfor document numbers or reference document numbers and, in this respect, accelerate processing: Values,which do not correspond to the predefined length and are outside the specified number interval, are recognized by the report as being invalid and, consequently, are not used as clearing information.
An individual user exit can be programmed for a specific interpretation of the note-to-payee fields (feasible for insurance, for example).
Requirements
The report checks whether the business transaction codes (external transactions) used by the bank wereallocated to an "internal transaction" within the default settings. This is necessary because the updateon the G/L accounts and the subsidiary accounts is carried out via posting rules that are stored for an internal transaction.
If the report encounters an external transaction that is not maintained in the corresponding table, the report aborts after having imported the account statement and outputs a list with the missing entries (error log).
The missing entries must be maintained so that the update transactions can be created in corresponding sessions. Then the report must be restarted. Please note here that the statement"x - importing data" is not selected this time since the account statement is already in the SAP System.
When the report is restarted, it searches in the buffer for all line items not yet characterized as updated in the respective posting area. A line item is regarded as updated only when a posting is put into a session.
Output
The audit trail gives you information, separated according to posting area, on all postings put intothe batch input session. In addition, the external business transaction codes and the internal transactions controlling the update are listed.
The processing statistics tells you
- 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
ABAP Short Reference General Material Data
This documentation is copyright by SAP AG.
Length: 3715 Date: 20120523 Time: 003232 triton ( 162 ms )
