Reset a Bank Statement

This document explains how you reset a bank statement that was involved in a job that ended abnormally.

Tables

The statuses, block codes, and amounts in these four tables indicate how far the bank statement has been processed. When a job has finished, the values in these four tables should reconcile. Even if a job is interrupted, before it has finished completely, the values in these four tables will continue to reconcile, and it will be possible to restart the job.

Block codes

Three main steps are taken during processing of a bank statement in (ABS100):

1. Validation
2. Allocation (automatic, or manual, or both)
3. Update to general ledger (GL)

During processing of a bank statement, block codes are set for the header, or for the line, depending on where the job is started. If the job is started in (ABS100), the block code is set for the header in FABHED. If the job is started in (ABS101), the block code is set for the line in FABLIN. The purpose of the block codes is to prevent other users from processing the same bank statement, or line, at the same time.

If the job ends normally, the block code is automatically removed, but if the job is interrupted, the block code will remain on the header, or on the line. Block codes for both the header and the lines can be removed by using correction ID 'AB01' in 'Program Problem. Solve' (CRS418). When the block code has been removed, the job can be restarted in (ABS100), or (ABS101).

Validation

During validation, bank transactions are created in FCR040 table. Either, one bank transaction is created for the entire bank statement, or one bank transaction is created for each bank statement line. If a validation job is interrupted, all transactions in FCR040 might not have been created yet. After having removed the block code in (CRS418), the validation can be restarted in (ABS100).

Automatic allocation

During allocation, allocation records are created in FABDET and in FCR040, and allocation information is updated in FABLIN and in FABHED. If an automatic allocation job is interrupted, all allocations may not yet have been made, but the allocation information in FABLIN and FABHED should continue to reconcile with the total of the allocation records created in FABDET and FCR040. If the interrupted allocation job was started in (ABS100), a block code would be found for the header in FABHED. If the interrupted allocation job was started in (ABS101), a block code would be found for the line in FABLIN. After having removed the block code in (CRS418), the allocation should first be released, and then restarted, in (ABS100) or (ABS101).

Update of the general ledger

During update of GL, the transactions in FCR040 are updated in the general ledger, as well as in accounts receivable and accounts payable, if applicable. The records in FCR040 are processed differently, depending on whether the voucher is created for the entire bank statement, or for each bank statement line.

If one voucher is created for each bank statement line, the transactions in FCR040 are handled for one batch number (= one bank statement line) at a time. A voucher number is retrieved for the batch, and the status is changed from 1 to 0 for all transactions included in that batch in FCR040, allowing GLS040 to update the voucher in the general ledger and other tables. When one bank statement line has been processed, the voucher number is updated for that line, and the status is set to 9 in FABLIN, and the next batch number is processed in FCR040. If such an update job is interrupted, some bank statement lines could have been updated to status 9 already, whereas others might not have been processed yet. As long as all bank statement lines have not been updated to status 9, the header remains in status 6 in FABHED. After having removed the block code in (CRS418), the update of the remaining lines can be restarted in (ABS100). If a GLS040 job remains in 'Trans Work File. Restart Interrupted Jobs' (GLS047), it can be restarted from there.

If one voucher is created for the entire bank statement, a voucher number is retrieved and updated for the bank statement header in FABHED. The status is changed from 1 to 0 for all transactions in FCR040 for the job number, allowing GLS040 to update the voucher in the general ledger and other tables. After that, the status of all the bank statement lines is set to 9 in FABLIN, and finally the status of the bank statement header is set to 9 in FABHED. If such an update job is interrupted, the job would be found in (GLS047), where it should be restarted. The status of all the bank statement lines might not have been raised to 9 yet, but in this situation, the status of the header will still be set to 9, to avoid further updates by the user. If the user attempts to perform changes in (ABS100), (ABS101), or (ABS102), this error message is received: ‘Option &1 is not allowed. Check (GLS047) for an interrupted job.’

If a voucher created during update of a bank statement to the general ledger would be deleted from 'Voucher. Open Erroneous' (GLS038), or reversed in 'Voucher. Reverse' (GLS900), the bank statement tables (FABHED, FABLIN, and FABDET) would not be updated. The bank statement (line) would remain in status 9.