Ansicht
Dokumentation
RFEBCK10 - Cashed Checks
CPI1466 during Backup Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
Description
Program RFEBCK00 imports the cashed checks data supplied by the bank.
The program can process both prenumbered checks and FI checks (checks that have a document number allocated by the system as the check number).
When you set the indicator "Prenumbered checks" you determine the type of checks requiring processing.
In the case of prenumbered checks the report differentiates between payroll checks and other checks.
Payroll Checks
All payroll checks, identified as such by the system by means of the check number included in the file, and which are neither voided nor already cashed, are flagged as "Paid".
When checks are already cashed or voided, the system issues a message to that effect.
The system groups the payroll checks from the check register according to the following criteria:
- Identifier
- Date of execution
- Business area
- Currency
The checks grouped according to the above criteria are listed with their check numbers.
If the flag "Post payroll checks" is set, the amounts in each group can be combined to form one posting total for posting on account.
If the posting is successful, the document number of the posting is saved in the check register for each check in the compressed posting. Thus, it is possible to determine which checks were posted together as one document.
You enter the date of execution and the identifier in the "Assignment number" field of the document line items.
If the flag "Post payroll checks" is not set, no posting takes place. In this case, in addition to the total amount and the currency, the totals posting is displayed in the list. The posting has to be carried out manually.
Note
You always have to set the flag "Post immediately" if payroll checks are to be posted.
Other Checks
The program RFEBCK00 creates clearing entries (outgoing checks account to bank account) for these checks. In addition it marks the successfully posted checks as "Paid" in the check register.
The clearing entries can either be placed in a batch input session (batch input mode) or can be posted immediately (call transaction mode).
General Information
An initial report is required due to the fact that no standard exists for check cashing data in the USA and most other countries. This converts the bank format into the incoming format of this program. The incoming format of this report consists of two record types: Header records (CHECK_HEAD) and single records (CHECK_REC).
- A header record (CHECK_HEAD) is required for each bank account from which checks are debited. The bank key (bank number) and the bank account are stored in this type of record. This information is used to read the house bank table for the purpose of determining the company code and the general ledger account for the bank.
- One single record is required for each check (CHECK_REC).
The structures CHECK_HEAD and CHECK_REC are defined in the R/3 Repository (ABAP Dictionary).
Batch input mode:
If there are no errors, the program creates a batch input session, the name of which ends in "-OK". If there are errors, two sessions are created, one for error-free posting records, and one containing errors. The session with posting records containing errors is created if the amount in the bank check file does not agree with the amount in the payment document in the system. The name of the session containing errors always ends in "-ERR".
The following scenarios might occur:
- Scenario: Document found (PAYR and BKPF); Document not yet cleared; Amounts agree.
Result: Update in PAYR; FB05 posting record in error-free folder.
- Scenario: Document found (PAYR und BKPF); Document not yet cleared; Amounts do not agree.
Result: No update in PAYR; FB05 posting record in folder containing errors; Message in processing log.
In this case the check has to be flagged as "Paid" in table PAYR after successful processing of the batch input session with transaction "FCH6".
- Scenario: Document found (PAYR and BKPF); Check already paid according to PAYR.
Result: No update in PAYR; no batch input; Message in processing log.
- Scenario: Document found (PAYR and BKPF); According to PAYR check not paid; Document already cleared in BSEG.
Result: Update in PAYR; no batch input; Message in processing log.
Call transaction mode:
This mode behaves in the same way as the batch input mode. The difference is that all error-free postings are carried out straight away. Postings containing errors are stored in a batch input session. The name of the session is made up of the report parameters and "-ERR", for error.
Requirements
- Before you use the program for the first time, a short program must be written to convert the record structure of the bank data into the structure of this program. The system expects a row by row structure of the input file. This means that the data recor <LF> (=Carriage Return, Line Feed).
- The file can be imported from the UNIX file system or from a diskette. If it is imported from a diskette the disk drive name has to be entered before the import takes place (for example A:CHECK.TXT). In addition, the relevant field must be marked in the initial screen.
- In the configuration menu for Financial Accounting, the bank where the checks are paid has to be maintained in the house bank table. The general ledger account has to be entered.
- You need to determine the clearing account from which payroll checks are posted as a total. You do this in bank selection in Customizing for the payment program.
You have to maintain a relevant G/L account as a bank subaccount for the company code, the house bank, the house bank account, the currency, and the payment method used.
Output
The following is displayed:
- Log of imported data records
- Processing log (short or in detail)
- Posting log
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 7067 Date: 20240520 Time: 113845 sap01-206 ( 123 ms )
