Scribd
Upload
45 views10 pages

Bank-Reconcile 1

The document discusses the process of loading bank statement files in BAI2 format into an Oracle E-Business Suite cash management system. It covers setting up transaction codes, mapping the bank file format, loading the file using SQL Loader, validating the data in interface tables, importing to base tables, and reconciling the transactions.

Uploaded by

Prasanna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
45 views10 pages

Bank-Reconcile 1

The document discusses the process of loading bank statement files in BAI2 format into an Oracle E-Business Suite cash management system. It covers setting up transaction codes, mapping the bank file format, loading the file using SQL Loader, validating the data in interface tables, importing to base tables, and reconciling the transactions.

Uploaded by

Prasanna
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 10

The seeded Bank Statement Mapping Formats of BAI2 cannot be updated.

To meet the Bank Data requirements mapping


you need to create a new mapping template which defaults the current seeded template.

Sample File Format:-


Below format illustrates BAI2 file format and most of the banks uses this format. Here this file represents bank account
number, bank account available balances, transaction details and much more based on your requirement.
Fields within the record are delimited by the comma (,).
The end of the record is delimited by the slash (/)

01 FILE HEADER Begins the file


02 GROUP HEADER Begins a new group
03 ACCOUNT IDENTIFIER Begins the account
16 TRANSACTION DETAIL Begins a new transaction
88 CONTINUATION Continues the transaction
16 TRANSACTION DETAIL Begins a new transaction
88 CONTINUATION Continues the transaction
49 ACCOUNT TRAILER Ends the account
03 ACCOUNT IDENTIFIER Begins a new account
16 TRANSACTION DETAIL Begins a new transaction
88 CONTINUATION Continues the transaction
88 CONTINUATION Continues the transaction
49 ACCOUNT TRAILER Ends the account
98 GROUP TRAILER Ends the group
02 GROUP HEADER Begins a new group
03 ACCOUNT IDENTIFIER Begins a new account
88 CONTINUATION Continues the account summary information
49 ACCOUNT TRAILER Ends the account
98 GROUP TRAILER Ends the group
99 FILE TRAILER Ends the file

Below diagram talks about how typically BAI2 file structure. What is file header, group header and line, where
it starts and ends.
Sample Transaction codes and descriptions: - The below transaction codes need to define in the oracle cash management
system, in order to process bank BIA2 file and reconcile bank transactions with oracle system.

System Setups for BAI2 file loading in Oracle:

We need to complete bank account setups in order to run bank file load program. We need to setup a bank transaction
codes in system, define a code belongs which type of account like Payment, Receipt or Miscellaneous payments and along
with that transaction source (based on requirement).
We setup a transaction codes based on account number in cash management application.
After transaction code setups need to modify the BAI2 file template based on the bank requirements.
If required change the BAI2 control file or create your own control file to understand bank file format and load into oracle
interface (temp) tables. Control file location is cd $CE_TOP/bin.

Tables:
select * from ce_bank_stmt_int_map;
select * from ce_bank_stmt_map_hdr;
select * from ce_bank_stmt_map_line;
Date format and time stamp format should be same with BAI2 file format otherwise we will get data errors while loading
file into Oracle.
Position talks about line number in which position statement number/other fields are positioned in the BAI2 file.
Here we have headers and lines, generally 16 code represents the lines/transactions and 03 code contains the account
number.
These all details are followed by most of the banks BAI2 file format and details may change based on bank and customer
requirement.
Bank Statement Loader:
After successful setups we can run Bank Statement Loader program to load data into interface tables in oracle system.
Here we have to provide the path where we placed/copy bank reconciliation file and bank file name.

Load: It is used to run the loader program only.


Load and Import: The Bank Statement Import program starts after the Bank Statement Loader completes
successfully.
Load, Import and Auto Reconciliation: Both Bank Statement Import program and the Auto Reconciliation programs
are launched after successful completion of the Bank Statement Loader program.

Data will be loaded into CE_STMT_INT_TMP table.


Select * from CE_STMT_INT_TMP;
select * from CE_SQLLDR_ERRORS; - Error table

Below concurrent programs are submitted (Inner) along with the Bank Statement Loader program.
 Run SQL*Loader- BAI2
 Load Bank Statement Data
 Bank Statement Loader Execution Report

Copy the statement number from Bank Statement Loader Execution Report and select the data from interface tables.
Generally statement number is the date in BIA2 file with format of YYMMDD.

select * from CE_STATEMENT_HEADERS_INT where statement_number = 171115;


select * from CE_STATEMENT_LINES_INTERFACE where statement_number = 171115;

Error Tables:
select * from CE_LINE_INTERFACE_ERRORS where statement_number = 171115;
select * from CE_HEADER_INTERFACE_ERRORS where statement_number = 171115;

Program/Report Output:
Check the data which is loaded into interface tables by above program. If we see any errors/warnings in bank statement
loader execution report, rectify those errors and re-run the process again.

We can find those errors in interface error tables or SQL loader error tables as well.

To verify data is loaded properly or not we can check in the system based on the bank account number and statement
number.

We will have statues called new, error and transferred. We should check for status as New against statement number and
bank account number.

Here interface data should be matched with data available in above screen short i.e. amount totals from header tables
and transaction amounts from lines interface tables against the statement number and bank account number.

All these amounts should be available in the bank BAI2 file.

select * from CE_STATEMENT_HEADERS_INT where statement_number = 171115;


select * from CE_STATEMENT_LINES_INTERFACE where statement_number = 171115;

Transaction codes we defined in system prior to load, if any transaction doesn’t exist in system loader program will give
an error. We can find in the log files/execution report.

Here the invoice information, line description, number (bank transaction number) and agent information will be loaded
into lines interface tables based on the mapping we did at bank statement mapping screen.

Bank Statement Import & Auto Reconcile Program:

After reviewing of interface tables data and everting seems to be good then go ahead and run the import program and
auto reconciliation program.
AutoReconciliation API’s are CE_AUTO_BANK_REC.statement , CE_AUTO_BANK_MATCH.match_process

Supplier payments entered in Payables can be reconciled to the bank statement lines in CM. The payment
status against each check is updated as “Reconciled”.

This program will import the data into CE base tables and perform reconcile activity automatically by system. If any
errors/warnings we can check in execution report (AutoReconciliation Execution Report).

Navigation: Cash Management Application -> Bank Statements -> Bank Statement Interface/Bank Statements and
Reconcile
Lines will tell us the reconcile status for each transaction.

Program Output:
If we have any exceptions/errors while reconciling we will be notified in this report, based on the exceptions/errors
correct the data in the system and re-run the auto reconcile program again or manually reconcile the data.

Finally data will be loaded into CE base tables.


select * from CE_STATEMENT_HEADERS where statement_number = '171115';
select * from CE_STATEMENT_LINES where statement_header_id = 1234; (We can check status
column for reconciliation)
select * from CE_RECONCILIATION_ERRORS; --Error Table
select * from CE_STATEMENT_RECONCILS_ALL;(Reconciliation history)
select * from CE_200_TRANSACTIONS_V -- AP payments
select * from CE_222_TRANSACTIONS_V -- AR cash receipts
select * from CE_260_TRANSACTIONS_V -- Bank statement lines available for reconciling bank errors
select * from CE_AVAILABLE_TRANSACTIONS_V -- Transactions from all the views

You might also like