You can use the Intra-Day Bank Statement Loader program to load bank statements updated with the latest transactions that occur on the day the statements are created. If the intra-day bank statements include the time they are created, the Intra-Day Bank Statement Loader program can also load the timestamp information.

You can run the Intra-Day Bank Statement Loader in one of two modes:

• Load

• Load and Import

If you choose the Load option, the program loads the bank statement information into the Bank Statement Open Interface tables, and you can make corrections to the statements prior to importing them into Oracle Cash Management. Alternatively, you can choose the Load and Import option to automatically start the Intra-Day Bank Statement Import program after the Intra-Day Bank Statement Loader program completes successfully. If the Intra-Day Bank Statement Loader program encounters any errors or warnings, the concurrent request stops. You can review the exceptions using the Bank Statement Loader Execution Report.

Prerequisites

• Set up Oracle Treasury for integration with Oracle Cash Management. See: Setting Up Oracle Treasury for Oracle Cash Management Integration.

• Create a SQL*Loader script for the format of your bank statement, if it is neither BAI2 nor SWIFT940.

• Define a mapping template for the format of your bank statement file. See: Bank Statement Mapping.

• Save your bank statement file in a directory.

To submit the Intra-Day Bank Statement Loader Program

1. Navigate to the Requests window.

2. Submit the Intra-Day Bank Statement Loader program.

3. Select one of the following options:

   • Load

   • Load and Import

4. Enter the name of the mapping template.

5. Enter the name of the bank statement file.

6. Enter the directory path in which the bank statement file is located.

7. If you want to limit loading records from a particular bank branch and branch account, then specify the bank branch name and the bank account number, else the program will import all records in the bank statement file.

8. Submit the program.

9. Check the SQL*Loader log file and the Bank Statement Loader Execution Report to see any exceptions generated during the loading process.