ECM: Issues with Importing BAI2 Bank Statements
Last updated on AUGUST 21, 2017
Applies to:PeopleSoft Enterprise FIN Cash Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
ISSUE # 1
When importing a BAI2 bank statement file with multiple accounts, the system created multiple Statement IDs. For some bank statements, the same Statements ID was shared with multiple accounts, and in other cases, a Statement ID was generated for just one account.
Expect that all the created bank statements (for different accounts) should have the same Statement ID since they were created using the same File.
1. Navigate to Banking > Bank Statements > Import Bank Statements.
2. Upload BAI2 statement with multiple accounts.
Message log shows 4 Statement IDs created.
A total of 7 statements were created for 7 bank accounts.
For some bank statements, 2 bank accounts shared the same statement ID, and for others the statement ID was unique for the bank statement.
7 bank statements (one statement for each account) to be created but all having the same Statement ID.
ISSUE # 2
BAI2 bank statement import (IMPORT_FILES) fails when the file has more than 100000 lines.
Assignment of "10000100000" to BS_TRANS_PD_EC.RECORD_SEQ_NUMBER failed. (2,119)
TR_MSG_PROCESSING.Su bscription.BankStatementLoad.OnExecute Name:traverseMessage PCPC:11673 Statement:225 Called from:TR_MSG_PROCESSING.Subscription.BankStatementLoad.OnExecute Name:traverseMessage Statement:246 Called from:TR_MSG_PROCESSING.Subscription.BankStatementLoad.OnExecute Name:traverseMessage Statem ent:246 Called from:TR_MSG_PROCESSING.Subscription.BankStatementLoad.OnExecute Name:msgImplStatement:73 C (0,0)
1. Import a BAI2 bank statement file that has more than 100,000 transaction lines
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms