Understanding the Load Bank Statement Program

The Load Bank Statement program loads data from the F09610 and F09611 staging tables to the F0916 and F0917 bank statement tables in the JD Edwards EnterpriseOne General Accounting system. This program formats data according to the type of electronic format used (BAI2 or SWIFT) and edits values in the bank statement tables to ensure that they are valid. The Load Bank Statement report (R09612) shows the number of records loaded and, if applicable, not loaded.

To accommodate reference numbers such as those for receipts, payments, and bank wire transfers, the F09611 table includes a Customer Reference (CUSTREF) field that allows up to 16 alphanumeric characters and maps to the Receipt Number (CKNU) field in the F09617 table. The contents of the CUSTREF field also map to the Document Number (DOCM) and Reference 1 (REF1) fields and are truncated in the F09617 table.

If data was successfully mapped to the bank statement tables, the system sets a flag in the header record in the F09610 table that allows the record to be purged. You can set a processing option to purge the data from the staging tables when you run the Load Bank Statement program or you can purge the data at a later time.

If a bank statement does not contain transactions, the bank statement is not mapped to the bank statement tables because no detail records exist. The statement is, however, mapped to the staging tables to provide an exact duplicate of the bank flat file.