Está en la página 1de 26

Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

R12/CE: How To Create New Bank Statement Mapping Template To To


Requirement, Latest Patch (Doc ID 563476.1) Bottom

In this Document Was this document helpful?

Goal
Yes
Solution
No
1. Mapping Data Structure:BAI2:
References

Document Details

APPLIES TO:

Type: HOWTO
Oracle Cash Management - Version 11.5.10.0 to Status: PUBLISHED
12.2.6 [Release 11.5 to 12.2]
Last Major Update: 25-Apr-2017
Information in this document applies to any
platform. Last Update: 22-May-2018

GOAL

Related Products
How to create a new Bank
Statement Mapping Template to Oracle Cash Management
meet your requirements:
Information Centers
1. BAI2 Information Center: R12: OVERVIEW: Oracle Cash
Management [1516805.2]
2. SWIFT940
3. EDIFACT
4. MT940
Document References
5. Non Standard Format
R12/CE: Mapping Of
Balance for BAI2 Bank
Statemant Data files,
Mapping Balances and
Control Totals [1281394.1]
SOLUTION
R12: Cash Management
Recommended Patch
(1).Entering Bank Statements Collection (RPC)
Before you can reconcile transactions against a [1367845.1]
bank statement, you need to enter the bank
statement information into Oracle Cash R12/CE: CEXTRXCD Bank
Transaction Codes
Management. You can accomplish this task by [1352123.1]
doing one of the following:
- Using the Bank Statement Loader program R11i Bank Statement
Loader Program White
- Using a custom loader program Paper [221133.1]
- Manually entering the information
R12/CE: Bank Statement
The seeded Bank Statement Mapping Formats of Format Masking for
Mapping BAI2, SWIFT940:
BAI2 or SWIFT940 or EDIFACT can not be BANK_ACCOUNT_NUM,
updated. To meet the Bank Data requirements BANK_TRX_NUMBER,
mapping you need to create a new mapping BANK_ACCOUNT_TEXT,
Agent Bank account
templates which defaults the current seeded number And Others
template. Once the new template is created with [752532.1]
defaults setups you can update the setups to your
requirement.
Recently Viewed
BANK_TRX_NUMBER: Mapped to: R12/CE: How To Create New Bank Statement
Mapping Template To Requirement, Latest Patch
[563476.1]
 Payables Transactions:Payment Number,
Payment Batch, Payment Instruction ID Oracle E-Business Suite Release 12.2: Technical
 Receivables Transactions: Receipt Planning, Getting Started, and Go-Live Checklist
[1585857.1]
Number, remittance batch, Remittance
Batch Deposit Number or Receipt Batch Oracle E-Business Suite Release 12.2.6 Readme
Name [2114016.1]
 Payroll Payments: Payroll Payment
Number, EFT BATCH NUMBER, Oracle E-Business Suite Release 12.2.7 Readme
[2230783.1]
 General Ledger Journals: journal line
Description Beginner''s Guide: Create a Custom Event Alert to
 Cash Management Transactions: Bank Fire against a Custom Table [103418.1]
Account Transfer NUMBER,
 Miscellaneous Transactions: Misc Show More
Payment Misc Receipt Number
 Open Interface Transaction: Payment
number , Receipt number

Navigate: CE>Setup>Bank>Bank Statement


Mapping:

1. Mapping Data Structure:BAI2:

Example Data File:

01,121345678,7777777,100119,1431,1431,80,1,2
/
02,7777777,121345678,1,100118,0000,USD,/
03,<YOUR BANK
ACCOUNT>,USD,10,100.00,15,1163083,400,11
53083,4,/
16,100,76995,V,011020,,Bank Reference
Text,26446,Office Supplies/
16,100,812213,V,011015,,323532,A39599,Travel
expenses/
16,100,242500,V,011017,,5434634N,46400-
333,Rent expense/
16,100,21375,V,011019,,264,83832,Team
Building Event/
49,2306166,6/
98,2306166,1/
99,2306166,1,10/

1. Open the Bank Statement Mappings window.

2. If you want to review a mapping template,


choose one from the list of values. Otherwise,
cancel
the list of values.
3. Create a new record for the new mapping
template.
4. In the Name field, enter the name of the new
mapping template. > TEST_BAI2
5. In the Description field, enter the description
for the new mapping template.>TEST BAI2
6. Control File: select: BAI2.ctl

7. Precision: 2

Please note: If you need Currency Precision to be


used then leave the Precision null.
"If bank statement already has a precision defined,
then that is the precision used to derive the header
and line amounts. If there is no precision defined
at the bank statement level then the system takes
the precision from the currency setup as that is the
general precision business would want the
amounts to be displayed."

Reference:

Bug: 20135535 - NO DECIMAL PLACES


BANK STATEMENTS MAPPINGS NOT
WORKING CORRECTLY IN R12
Functional Description - With this bug, precision
order while loading BAI2 bank statements is
modified.

ce patch/115/sql cebsldrb.pls 120.54.12020000.13

R12.2:
Patch: 21524341:R12.CE.C This patch fixes the
issue where Bank statement Loader program fails
to load the '/' in the statement line description field
ce patch/115/sql cebsldrb.pls 120.54.12020000.16

R12.1:
Patch: 20135535:R12.CE.B This patch fixes the
issue wherein precision order while loading BAI2
bank statement is incorrect.
ce patch/115/sql cebsldrb.pls 120.34.12010000.40

8. Date Format: YYMMDD


9. Time Stamp Format: HH24MI *

*Please note: If Time Stamp is not available in


data file at Rec_Id 02 then this is not required
example:

02,ANSER420,121000248,1,110826,,,/ This line


do not have Time Stamp.

02,<bank customer ID>,<bank originator


ID>,<group status>,<as of date>, <as of
time>,<currency code>,<as of date modifier>/

10. Bank File Format Type: BAI2


11. Press Button: Populate.. it should populate
default Header and Lines mapping.
12. This you can correct as per your
requirements:
BANK_TRX_NUMBER 16 -2
Insure to Remove: Example(xxx)

Column Name Rec_Id Posi


Header:
STATEMENT_NUMBER 02 4
BANK_ACCOUNT_NUM 03 1
STATEMENT_DATE 02 4
CURRENCY_CODE 03 2
STATEMENT_TIMES TAMP 02 5

Lines:
TRX_CODE 16 1
AMOUNT 16 2
TRX_TEXT 16 -1
INVOICE_TEXT 16 -2
BANK_TRX_NUMBER 16 -1
CUSTOMER_TEXT 16 -3

Please Note: Mapping columns > Form


Column Names (Bank Statement
Reconciliation Form)

CUSTOMER_TEXT > Agent


BANK_ACCOUNT_TEXT> Agent Bank
Account
TRX_TEXT > Description

Note: The above mapping is an EXAMPLE.

1). The BANK_TRX_NUMBER column and the


TRX_TEXT column are mapped to the Text field
as Record ID 16 and Position -1. The
INVOICE_TEXT column is mapped to the
Customer Ref No field as Record ID 16 and
Position -2. The CUSTOMER_TEXT column is
mapped to the Bank Ref No field as Record ID 16
and Position -3.

2). You can map the same field to two different


columns. For example, in the BAI2 mapping
template, the BANK_TRX_NUMBER column
and the TRX_TEXT column are both mapped to
Record ID 16 and Position -1.

12. Save
13. Recheck by :
14. Open the Bank Statement Mappings window.
15. Choose the one from the list of values.. if you
see your TEST_BAI2 that means this is created
and now you can use it.

Please Note:

User tryies to map "STATEMENT_NUMBER"


(RECORD 02) to a value in RECORD 01, which
is a file header record. This is not allowed. As per
the LOAD_BAI2 code, the mapping for
STATEMENT_NUMBER cannot be done on a
position outside of RECORD 2. For ex : This is
the query that looks for the mapping position for
statement number -

SELECT nvl(position,0),
format,
include_format_ind,
concatenate_format_flag
FROM ce_bank_stmt_map_hdr_v
WHERE map_id = &map_id
AND column_name =
'STATEMENT_NUMBER';

as seen, it will only retrieve the position and then


get the value for the position WITHIN RECORD
02 and will not search across records of different
types to find the position.
So Rec02, position X will work . But Rec01,
position X - will NOT work for mapping
statement number and it will default record02,
position 3

Seeded BAI2 Bank Statement Map:


Header:

Lines:

Please Note: As per CE UG: Bank Statement


Mapping Templates D-5
Since the number of fields in record ID 16 varies,
depending upon information such as funds type,
the location of these fields in the intermediate
table cannot be determined in advance.
However, Text,Customer Ref No, and Bank Ref
No are always located at the end of the record,
where Text is the last field, Customer Ref No is
the second to the last field, and Bank Ref No is
the third to the last field.
They are represented by negative positions.
- Text field is mapped to the
BANK_TRX_NUMBER column and the
TRX_TEXT column as position -1.
- Customer Ref No field is mapped to the
INVOICE_TEXT column as position -2.
- Bank Ref No field is mapped to the
CUSTOMER_TEXT column as position -3.

If your bank uses different locations for these


fields, you need to modify the mapping
accordingly.
In addition, the BANK_TRX_NUMBER column
is populated with data from the Text field that
matches the default format of Example (xxx). You
must change the format to the actual format used
by your bank.

Please note:
Agent: Cash Management displays some
additional fields where you can enter a Customer
Name and Customer Number to use when finding
Receivables transactions. You can also enter a
Supplier Name and Supplier Number to use when
finding Payables transactions. You can also select
a Counterparty Bank Account when searching for
Cash Management cashflows associated with
Bank Account Transfers.

In bank statement line, reference tab, there are


columns: Agent, Agent Bank account and
Invoice. You can map Supplier Name or
Customer Name to: Agent.

General Structure of a BAI2 files is as follows:

Record 01 - Mandatory: This should be your first


record in the file. It should be of the following
format:
01,<bank originator ID>,<bank customer
ID>,<file creation date>,<file creation time>,<file
identification number>,<physical record
length>,<block size>,<version number>/

Record 02 - Mandatory: This should be the


second record in the file. It should be of the
following format:
02,<bank customer ID>,<bank originator
ID>,<group status>,<as of date>,<as of
time>,<currency code>,<as of date modifier>/

Record 03 - Mandatory: This should be the third


record in the file. It should be of the following
format:
03,<bank account number>,<currency
code>,<type code>,<sign&gt;<amount>,<item
count>,<funds type>/
Continuation rec..
88, <type code>,<sign><amount>,<item
count>,<funds type>/

Record 16:
16,<transaction code>,<amount>,<funds
type>,<bank ref #>,<customer ref #>,<text>/
Continuation rec..
88,

Record 49:

49,<account control total>,<number of records for


account>/
The account control total sums all the amounts in
records 03, 16 and 88 and includes an amount
sign. The record count for the account is for all
records up to and including the 49 record itself.

Record 98:

98,<group control total>,<number of


accounts>,<number of records in group>/
Group control total is the sum of all control totals
in 49 records for this group. The number of
accounts will be the same as the number of 03
records in the file.

Record 99:

99,<file control total>,<number of


groups>,<number of records>
File control total is the sum of all group control
totals in 98 records. The number of groups should
match the number of 02 records.

Please do Review: Official specifications for


BAI2 available @ www.bai.org
https://businessonline.huntington.com/common/c
ms/help/BAI1Technical%20Ref%20Manual.pdf

Note:1281394.1 - Mapping Of Balance for BAI2


Bank Statemant Data files
Note:752532.1 - When Mapping BAI2 Bank
Statement Format Masking And
BANK_TRX_NUMBER

You can download the file from this note:


BAI2_Standards_Cash_Management_2005.pdf

Please note: BAI2 Format Bank statement data


file you receive from Bank to be uploaded in Cash
Management for balances and also Reconciliation.

Bug: 12899632: AVAILABLE BALANCE (040)


IS NOT EXTRACTED AND SUPPORTED BAI2
FORMAT

This is generally done and mapped in Cash


management as follows:
Example Data file: Code 010, 015, 020, 040,
045,050, 072, 074, 100, 110, 400 are the examples
in the following recc_id: 03 and it's continuation
record: 88:

03,123-123-
123,USD,010,185487700,,,015,316426300,,,020,3
53569387,,/
88,040,337591743,,,045,0,,,050,0,,,072,23963380
0,,/
88,074,76792500,,,100,3477884685,110,,400,334
6946085,27,/

Please note as per :


BAI2_Standards_Cash_Management_2005.pdf,
this is uploaded to this, Appendix A Page: 47:

Type Code Transaction Level Description


040 NA Status Opening Available
045 NA Status Closing Available
072 NA Status 1-Day Float
074 NA Status 2 or More Days Float

CE UG: Bank Statement Mapping Templates D-


3
CASHFLOW_BALANCE copied from record
ID 03 and record ID 88 using the predefined
transaction code of 045 >>> THIS SHOULD BE
040??
INT_CALC_BALANCE copied from record ID
03 and record ID 88 using the predefined
transaction code of 045
ONE_DAY_FLOAT copied from record ID 03
and record ID 88 using the predefined transaction
code 072
TWO_DAY_FLOAT copied from record ID 03
and record ID 88 using the predefined transaction
code 074

Please note: the record 88 is an extension of 03


record. The account status codes are mentioned
from 001-099.
For example,
One bank can provide the Aggregate Balance
Adjustments with the status code 022 in record
088.
Another bank can provide the ACH Net Position
with the status code 037.

So banks can provide the balances in the bank


statement file for any of the status codes with
balance from 001 to 099 as a part of record 88.

Cash Management provides an out of box


mapping template where we have described the
mapping of some of the account status codes. The
cash management documentation clearly describes
for which account status codes the mapping is
provided and only those status codes are mapped
in the system.

2. Mapping Data Structure: SWIFT940:

1. Open the Bank Statement Mappings window.


2. If you want to review a mapping template,
choose one from the list of values. Otherwise,
cancel the list of values.
3. Create a new record for the new mapping
template.
4. In the Name field, enter the name of the new
mapping template. > SWIFT940_NEW
5. In the Description field, enter the description
for the new mapping
template.>SWIFT940_NEW
6. Control File: select: SWIFT940.ctl
7. DATE FORMAT: YYMMDD
8. TIME STAMP FORMAT : HH24MI
9. BANK FILE FORMAT TYPE:SWIFT940
10. Press Button: Populate.. it should populate
default Header and Lines mapping.
11. This you can updated as per your
requirements.

Please note: Please note: Line Information:


SWIFT940 line information is stored in record ID
61. Record ID 61A and record ID 86 are
continuation records that contain overflow
information from record ID 61.
You can map: BANK_TRX_NUMBER: 61 7

Column Name Rec_Id P


Header:
STATEMENT_NUMBER 28 1
BANK_ACCOUNT_NUM 25 1
CONTROL_BEGIN_BALANCE 60 5
STATEMENT_DATE 62 3
CURRENCY_CODE 60 4
CONTROL_END_BALANCE 62 5

Lines:
TRX_DAT 61 1
BANK_ACCOUNT_TEXT 61 8
AMOUNT 61 5
CUSTOMER_TEXT 61 7
BANK_TRX_NUMBER ** 61A or 61 1
TRX_TEXT 61A 1
TRX_CODE 61 6

** Possible changes: Please down load file


attached to this note as;
SWIFT_MT940__2_.pdf. This has MT940 Tag
& (sub)Field Specifications. This hels in
mapping.

12. Save
13. Recheck by:
14. Open the Bank Statement Mappings window.
15. Choose the one from the list of values.. if you
see your SWIFT940_NEW that means this is
created and now you can use it.

Please note:
Agent: Cash Management displays some
additional fields where you can enter a Customer
Name and Customer Number to use when finding
Receivables transactions. You can also enter a
Supplier Name and Supplier Number to use when
finding Payables transactions. You can also select
a Counterparty Bank Account when searching for
Cash Management cashflows associated with
Bank Account Transfers.

In bank statement line, reference tab, there are


columns: Agent, Agent Bank account and
Invoice. You can map Supplier Name or
Customer Name to: Agent.

You can download the file from this note:


swift_mt940_942.pdf
Please review and compare your setup as per
following seeded: SWIFT940 Bank statement
Mapping:

1). Hearder:

2). Lines Tabs:

3. Mapping Data Structure: EDIFACT:

You can create new mapping templates by


copying the existing templates.
1. Open the Bank Statement Mappings window.
2. If you want to review a mapping template,
choose one from the list of values. Otherwise,
cancel the list of values.
3. Create a new record for the new mapping
template.
4. In the Name field, enter the name of the new
mapping template. > TEST_EDIFACT
5. In the Description field, enter the description
for the new mapping template.>Mapping template
for TEST_EDIFACT
6. Control File: select: EDIFACT.ctl
7. DATE FORMAT: DDMMYY
8. BANK FILE FORMAT TYPE: EDIFACT_FR

9. Press Button: Populate.. it should populate


default Header and Lines mapping.
10. This you can updated as per your
requirements.

Column Name Rec_Id P


Header:
STATEMENT_NUMBER 01 9
BANK_ACCOUNT_NUM 01 7
CONTROL_BEGIN_BALANCE 01 1
PRECISION 01 5
STATEMENT_DATE 07 9
CURRENCY_CODE 01 4
CONTROL_END_BALANCE 07 1

Lines:
TRX_DATE 04 9
TRX_CODE 04 8
AMOUNT 04 1
PRECISION 04 5
BANK_TRX_NUMBER 04 1
TRX_TEXT 04 1
CURRENCY_CODE 04 4
EFFECTIVE_DATE 04 1

11. Save
12. Recheck by :
13. Open the Bank Statement Mappings window.
14. Choose the one from the list of values.. if you
see your TEST_EDIFACT that means this is
created and now you can use it.

4. Mapping Data Structure: MT940:

1. Open the Bank Statement Mappings window.


2. If you want to review a mapping template,
choose one from the list of values. Otherwise,
cancel the list of values.
3. Create a new record for the new mapping
template.
4. In the Name field, enter the name of the new
mapping template. > MT940_NEW
5. In the Description field, enter the description
for the new mapping
template.>SWIFT940_NEW
6. Control File: select: SWIFT940 **
7. DATE FORMAT: YYMMDD
8. TIME STAMP FORMAT :
9. BANK FILE FORMAT TYPE:SWIFT940
10. Press Button: Populate.. it should populate
default Header and Lines mapping.
11. This you can updated as per your
requirements.

** there is no MT940.ctl file exist. You have to


use: swift940.ctl

Column Name Rec


id Position Format

HEADER

STATEMENT_NUMBER 28 1
BANK_ACCOUNT_NUM 25 1
CONTROL_BEGIN_BALANCE 60 5
STATEMENT_DATE 62 3
CURRENCY_CODE 60 4
CONTROL_END_BALANCE 62 5

LINES
TRX_DATE 61 1
BANK_ACCOUNT_TEXT 61 9
AMOUNT 61 5
CUSTOMER_TEXT 61 1
/BENM/NAME/(~)
BANK_TRX_NUMBER 61A 7
TRX_TEXT 61A 1
TRX_CODE 61 6
CURRENCY_CODE 61A 1
/OCMT/(aaa)
Exchange_Rate 61A 1 /EXCH(aaa)
INVOICE_TEXT 61A 1
/INV/(~),/REMI/(~)
ORIGINAL_AMOUNT 61A 1
/OCMT/EUR(~),.... MORE SUCH IF ANY
CHARGES_AMOUNT 61A 1
/CHG1/EUR(~), ..... MORE SUCH IF ANY

12. Save
13. Recheck by:
14. Open the Bank Statement Mappings window.
15. Choose the one from the list of values.. if you
see your MT940_NEW that means this is created
and now you can use it.

Please note:
Agent: Cash Management displays some
additional fields where you can enter a Customer
Name and Customer Number to use when finding
Receivables transactions. You can also enter a
Supplier Name and Supplier Number to use when
finding Payables transactions. You can also select
a Counterparty Bank Account when searching for
Cash Management cashflows associated with
Bank Account Transfers.
In bank statement line, reference tab, there are
columns: Agent, Agent Bank account and
Invoice. You can map Supplier Name or
Customer Name to: Agent.

Tag :21: Related Reference 16x If the MT 940 is


sent in response to an MT 920 Request Message,
this field must contain the field 20 Transaction
Reference Number of the request message.
You can download the file from this note:
MT940 Document.pdf

5. Mapping Data structure: Non Standard


Formats: Example: Bank Statement in format
CBI (Italian format), .csv file: comma-separated
values (CSV) file stores tabular data (numbers and
text) in plain-text form, etc.

The Non Standard bank statement can be


uploaded into Cash Management using a custom
loader program. First, create your custom loader
program. Then:
1. Run the custom loader program against the
bank statement file to populate the Bank
Statement Open Interface tables.
2. Verify that the bank statement information was
loaded into the open interface tables correctly.

You can use the Bank Statement Interface


window to ensure that bank statement header
information is correctly inserted into the
CE_STATEMENT_HEADERS_INT table.
You can use the Bank Statement Lines Interface
window to ensure that bank statement transaction
lines are correctly inserted into the
CE_STATEMENT_LINES_INTERFACE table.

The Bank Statement Interface and Bank Statement


Lines Interface windows show you the statement
header and lines information in the open interface
tables. You can correct the information using
these windows, or you can correct the original
bank statement file and reload it using your
custom loader program.

Table: CE_STATEMENT_HEADERS_INT

The CE_STATEMENT_HEADERS_INT_ALL
table stores information about bank statement
details for importing. Each row contains the bank
statement number, bank account number, control
balances, and other statement- related
information. After populating this table, you can
run the Bank Statement Import program to
transfer the statement information into the
CE_STATEMENT_HEADERS_ALL table.
The Bank Statement Interface form allows you to
modify the statement interface information or to
correct any errors encountered while uploading
the data.

Table:
CE_STATEMENT_LINES_INTERFACE

The CE_STATEMENT_LINES_INTERFACE
table stores information about bank statement line
details for open interface. Each row contains the
bank statement number, bank account number,
statement line amount, and others. After
populating this table, you can run the Bank
Statement Import program to transfer the
statement line information into the
CE_STATEMENT_LINES table.
The Bank Statement Interface form allows you to
modify the statement line interface information or
correct any errors encountered while uploading
the data.

Please note: To Insure that your Bank statement


Transaction codes are valid insure to define these
using:Note:1352123.1 - CEXTRXCD Bank
Transaction Codes Latest

Once the Bank statement is loaded into Interface


then same can be Imported and Autoreconciled.

(2). Mapping sql:

Format Name: BAI2 or SWIFT940 or


EDIFACT substitue the value as required in
following:

1)select map_id from ce_bank_stmt_int_map


where format_name='BAI2'
2)select * from ce_bank_stmt_map_hdr where
map_id=<as obtained from query1>
3)select * from ce_bank_stmt_map_line where
map_id=<as obtained from query1>

(3). Latest Patch:


11i.CE.K or CU1..any will work fine.

Patch:
7135400 1OFF:7010644:CE.J:FP.F:11.5.10:BAN
K STATEMENT MAPPING FORM DOESN'T
MAINTAIN RECO
patch/115/sql/cexsldrb.pls 115.9
forms/US/CEXBSLDR.fmb 115.28
Patch must be applied over patchset
11i.CE.K/CU1

11.5.10: Patch must be applied over patch


11i.CE.K / 11.CE.J
Patch: 9373448 UNABLE TO UPLOAD THE
BANK STATEMENT - RUN SQL*LOADER-
SWIFT940
bin/SWIFT940.ctl 115.6

11i ce bin/ BAI2.ctl 115.4

R12: Version must be:


ce forms/US/CEXBSLDR.fmb 120.8

R12.1.x
Patch: 8478551:R12.CE.B NOT ABLE TO
LOAD SWIFT940 BANK STATEMENT
CE_STMT_INT_TMP
The patch is applicable over 12.1
ce bin SWIFT940.ctl 120.4.12010000.2

Patch: 13324534:R12.CE.B IMPORT BANK


STATEMENTS - SOME CONTROL FIELDS
ARE MISSING FOR BAI2 DATA FILE
This patch can be applied over 12.1.1
Bank Statement loader should load control total
amount and lines for receipts and payments.
ce bin BAI2.ctl 120.0.12010000.2

Patch: 14578532:R12.CE.B SWIFT940


STATEMENT CANNOT PROCESS MORE
THAN 2 CONTINUATION RECORDS.
This patch can be applied over 12.1.1

Latest:
Patch: 14578532:R12.CE.B SWIFT940
STATEMENT CANNOT PROCESS MORE
THAN 2 CONTINUATION RECORDS
ce bin BAI2.ctl 120.0.12010000.2 +
ce bin EDIFACT.ctl 120.0.12010000.3 +
ce patch/115/sql cebsldrb.pls 120.34.12010000.
31

Patch: 16547142:R12.CE.B BANK


STATEMENT LOADING PROGRAM ERRORS
WITH ORA-06502: PL/SQL: NUMERIC OR
VALUE
ce patch/115/sql cebsldrb.pls 120.34.12010000.
32

4). Patch: 13781825:R12.CE.B This patch fixes


the issue wherein the tax code info is not
defaulted on selecting the receivable activity when
creating misc receipt from CE.
The patch is applicable over 12.1
ce bin SWIFT940.ctl 120.4.12010000.2

R12.0.x:
Patch: 8478551:R12.CE.A NOT ABLE TO
LOAD SWIFT940 BANK STATEMENT
CE_STMT_INT_TMP
The patch can be applied over any RUP
ce bin SWIFT940.ctl 120.4.12000000.2

Patch: 13831088:R12.CE.A 12.1.3


CE_STATEMENT_LINES_INTERFACE"."TRX
_TEXT" (ACTUAL: 266, MAXIMUM: 255)
ce patch/115/sql cebsldrb.pls
120.33.12000000.28
This patch can be applied over any 12.0.6.

Oracle Support strongly recommend you to apply


following:
1). Note: 1367845.1 R12: Cash Management
Recommended Patch Collection (RPC)
2). Note: 1393113.1 R12 CE Diagnostics BAT,
Cashflows, Payment and Receipt
3). Note: 1335039.1 New Archive, Purge and
Restore Bank Statement Concurrent Programs
4). Note: 1481222.1 R12.1: Sub Ledger
Accounting (SLA) Recommended Patch
Collection (XLA RPC), August 2012

Oracle Support proactively provides Fixes which


improves your application experience.
Hope you appreciate.

(8). Issue / Resolution:

Issue 1:
Bank statement Loader not populating Original
amount and Charge Amount for MT940 data file,
Even when Bank statement mapping for MT940
has appropriate mapping
Bug: 12708348 - BANK STATEMENT
LOADER NOT POPULATING ORIGINAL
AMOUNT AND CHARGE AMOUNT FOR
MT940
Resolution:
Patch: 12708348:R12.CE.B BANK
STATEMENT LOADER NOT POPULATING
ORIGINAL AMOUNT AND CHARGE
AMOUNT FOR MT940
ce patch/115/sql cebsldrb.pls
120.34.12010000.20

Issue 2: APP-CE-53045 THE FORMAT


ENTERED IS INCORRECT

Navigation: CE>SETUP>BANKS>BANK
STATEMENT MAPPING>
Create New statement mapping for BAI2 format,
use a format indicator where the indicator follows
the format: (~) Acct or (~) Recv ID Try and
Save.. it erros as:
ERROR : APP-CE-53045 the format entered is
incorrect. see Oracle Cash Management User
Guide for Formatting standards.

CE UG: 2 34 Oracle Cash Management User


Guide: Bank Statement Mapping:
A format may contain an indicator. An indicator is
a token that always appears with, before, or after
the data. If you expect to find spaces between the
indicator and the source data, you must explicitly
specify these spaces in the format. The chart in
step 13 describes the types of formats supported
by the Bank Statement Loader program.

The notations used to define fixed length


formats are:
- n a digit
- a a non-digit character, like a letter or a special
character
- x any character, including digit, letter, or special
character

Variable formats use only the ~ notation, which


stands for any number of alphanumeric and
special characters. While fixed length formats
may come with or without an indicator, variable
length formats must be accompanied by an
indicator. If you use either the fixed length format
without an indicator or the variable format to
extract the source data from a field that contains
multiple segments of information, these segments
must be delimited by white spaces.

Issue 3: CEBSLDR module: Load Bank


Statement Data
ORACLE error 1400 in FDPSTP
Cause: FDPSTP failed due to ORA-01400: cannot
insert NULL into
("CE"."CE_SQLLDR_ERRORS"."BANK_ACCT
_CURRENCY_CODE")
ORA-06512: at
"APPS.CE_SQLLDR_ERRORS_PKG", line 10
ORA-06512: at
"APPS.CE_BANK_STATEMENT_LOADER",
line 3619
ORA26-AUG-2014 11:48:25

1. The bank to provide the currency code in the


statement. as it seems the statement is missing the
currency code for which the issue has occurred.
Please default the currency code in the statement
provided by bank as the same can not be defaulted
in the application.

2. As per: Bug 18173664 - BANK


STATEMENT LOADER COMPLETED WITH
STATUS ERROR : CANT INSERT NULL INTO
CURRE
We can't add default value in the code as this is a
customer specific case. For standard formats the
bank account currency code is always present in
the statement file, and we derive it from the file.
What we can suggest as a:

WORK AROUND: is try to include the default


currency code value in the ctl file , say for BAI2
format currency code is in second field in
record_id 03.
So, while populating ce_stmt_int_tmp table for
that record id, column 2 can be populated with the
currency code with a value in the ctl if possible
(i.e populate the ce_stmt_int_tmp table with
default currency value). This can be extended to
other file formats as well. This appears to be
customer specific issue and not related to any of
the standard formats. 9). Question /Answers:

Q1: DFF at 'Bank Statement Mapping Line'


does not work, Setup a Descriptive Flexfield
for the form 'Bank Statement Mapping' in
Cash management. Clicking on the DFF on the
form does not open the DFF?

A1:
1. The current functionality does not support the
loading of Descriptive Flexfields into the Bank
Statement mapping tables.
This issue has been reported to CE DEV. It does
appear that with the form, CEXBSLDR - Bank
Statement Mapping , development cannot enable
the DFF for this setup at this time.
The following ER is created to request that DFF
be enabled for the Bank Statement Mapping to
allow the loading of DFF.

Enhancement Request Bug: 7047430 : DFF IN


BANK SATEMENT MAPPING FORM

DFF on CE BANK STATEMENT MAPPING


form (DFF Title -> Bank Statement Mapping) is
sucessfully enabled and compiled, but is not
visible in the form CEXBSLDR.fmb

Q2: How rec id is used during Load process?

A2: The SQL*Loader script must populate the


REC_NO column and the REC_ID column in the
intermediate table for each record loaded from the
bank statement file. REC_NO indicates the order
of a record in the file. You can use the SQL
function of RECNUM to populate the REC_NO
column. REC_ID is an identifier of the record
type. Common record types found in most bank
statement file formats are Header, Line, and
Trailer.

REFERENCES

NOTE:1281394.1 - R12/CE: Mapping Of Balance


for BAI2 Bank Statemant Data files, Mapping
Balances and Control Totals
BUG:12708348 - BANK STATEMENT
LOADER NOT POPULATING ORIGINAL
AMOUNT AND CHARGE AMOUNT FOR
MT940
BUG:12899632 - AVAILABLE BALANCE IS
NOT EXTRACTED AND SUPPORTED BAI2
FORMAT
NOTE:1367845.1 - R12: Cash Management
Recommended Patch Collection (RPC)

BUG:13324534 - IMPORT BANK


STATEMENTS - SOME CONTROL FIELDS
ARE MISSING FOR BAI2 DATA FILE
BUG:8478551 - NOT ABLE TO LOAD
SWIFT940 BANK STATEMENT
CE_STMT_INT_TMP
NOTE:1352123.1 - R12/CE: CEXTRXCD Bank
Transaction Codes
NOTE:221133.1 - R11i Bank Statement Loader
Program White Paper
NOTE:752532.1 - R12/CE: Bank Statement
Format Masking for Mapping BAI2, SWIFT940:
BANK_ACCOUNT_NUM,
BANK_TRX_NUMBER,
BANK_ACCOUNT_TEXT, Agent Bank account
number And Others

Didn't find what you are looking for? Ask in Community...