EAP: Payment Inquiry link from Voucher Payments page (VCHR_PAYMENT_PNL) Open New Window, But Without New Window Instance, Which Causes Later On 'onReadyState' Errors On Original Window
(Doc ID 2619775.1)
Last updated on DECEMBER 12, 2019
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The Accounts Payable Functional Users have detected that the system throws an Error Message, or simply kicks them out their session, when clicking on the Return To Search button from the Voucher Payments tab, after having navigated back and forth from the Voucher's Regular Entry Payments tab, and the Payment Inquiry feature, which is opened into a new window.
The problem is due to the fact that when a new window is opened by the system at the time of clicking the Payment Inquiry link at the Voucher Payments tab (Page VCHR_PAYMENT_PNL), the URL Link generated does not have the new Instance Value (_XX) next to the Database Name (DatabaseName_XX). This confuses the system having two open Internet Browsers with the same URL Link main information.
1.- Log into the FSCM Online Application as a Payables User
2.- Navigate to: Accounts Payable > Vouchers > Add/Update > Regular Entry
3.- Perform a search for any existing Voucher transaction that has been successfully paid, and open it
4.- Go to the Payments tab
5.- Click on the Payment Inquiry link available
6.- This open a brand new window with the Payment Inquiry search page, with that Voucher's Payment information
7.- Click on the available link of the Payment Reference ID column
8.- The system displays the Vouchers For a Payment page
9.- Click on the available link of the Voucher ID column
10.- The system now displays the Voucher Inquiry page
11.- Click on the 'Back To Payment Vouchers' link
12.- At the Vouchers For a Payment page, click now at the ‘Back To Payment Inquiry’ link
13.- At this stage, the User has returned to the Payment Inquiry window that was open from the Voucher Payments tab (the original window)
14.- Without touching anything else, go to the original Internet Browser window from the Voucher component
15.- The system still displays the Payments tab, then, click on the Return To Search button
16.- The system throws an Error Message
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.
" Function 'onReadyState' Error: ChartLoad is not defined
@http://XXXXXXXXXX.com:XXXX/cs/DBNAME/cache/PT_AJAX_NET_MIN_89.js line 1347 > eval:29:1
The Users are getting kicked out of their session, and/or loosing any transaction data changes performed, or tasks to be completed, on the original browser window. The Users will then need to log once again into a new session, and repeat all their steps and tasks from scratch. This is not user-friendly, and causes loss of time, and resources.
The Error Message should not be triggered by the system, and for that to happen, when the Payment Inquiry link is clicked from the Voucher Payments tab, the new window should have a URL Link generated where the Database Name is followed with an '_XX' instance number.
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