Ansicht
Dokumentation
RFEBFR00 - Do not use this program. Use RFEBKA00.
Addresses (Business Address Services) General Material DataThis documentation is copyright by SAP AG.
Description
Program RFEBKA00 imports bank statements into the SAP System, and then creates batch input sessions for posting in G/L and subledger accounting.
By stating parameters, you can specify whether both sessions are created in one run or whether only the session for G/L accounting is created 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 DREBA-GIRO)
- house bank ID and bank statement number (for example DREBA-034)
The batch input session name for subledger accounting always starts with /.
Interpretation of the note-to-payee fields
With incoming payments, you can search the note-to-payee items of the bank statement according to document numbers or reference document numbers by specifying the selection field (BELNR or XBELNR). Therefore, you obtain the relevant information for clearing customer payments.
If you do not specify a selection field, the note-to-payee fields are not interpreted.
With outgoing payments, the system 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, 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 program as 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 the insurance industry, for example).
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 necessary because the system uses the posting rules stored under an internal transaction to post to the G/L and subledger accounts.
If the program finds an external transaction not maintained in the corresponding table, it aborts after 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 you do not select the "Import data" field 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. A line item is regarded as posted only if a posting is put into a session.
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 postings could not be created (by definition).
RFUMSV00 - Advance Return for Tax on Sales/Purchases TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 3634 Date: 20240520 Time: 143606 sap01-206 ( 66 ms )
