EAP: SQL Error Displays When Looking Up Bank Statement Data
(Doc ID 2172096.1)
Last updated on NOVEMBER 04, 2019
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
SQL error displays when looking up Bank Statement data.
After applying fixes from PUM's 13-18, SQL error is getting encountered that does not prevent us from seeing the Bank Statement data but it a nuisance.
A SQL error occurred. Please consult your system log for details.
Error from appserver log:
Stmt #: 686 Error Position: 0 Return: 8601 - [Microsoft][SQL Server Native Client 11.0][SQL Server]Ambiguous column name 'BANK_ACCOUNT_NUM'.
[Microsoft][SQL Server Native Client 11.0][SQL Server]Statement(s) could not be prepared. (SQLSTATE 37000) 8180
Failed SQL stmt: SELECT DISTINCT C.BNK_ID_NBR , B.BANK_ACCOUNT_NUM , A.DESCRSHORT , A.DESCR FROM PS_BANK_ACCT_DEFN A , PS_BANK_ACCT_CPTY B , PS_BANK_CD_TBL C WHERE (A.SETID = B.SETID AND A.BANK_CD = B.BANK_CD AND A.BANK_CD_CPTY = B.BANK_CD_CPTY AND A.BANK_ACCT_KEY = B.BANK_ACCT_KEY AND C.SETID = B.SETID AND C.BANK_CD = B.BANK_CD) AND (BNK_ID_NBR=:1 AND BANK_ACCOUNT_NUM=:2) ORDER BY 1, 2
The issue can be reproduced at will with the following steps:
1. Navigate to Main Menu > Banking > Bank Statements > Enter Bank Statements
2. Supply External Bank Id
3. Supply Bank Account #
Error message is displayed: A SQL error occurred. Please consult your system log for details.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document