EAP 9.2: Error Messages When Clicking Edit Payment Request Available Link During Approvals
Last updated on MARCH 14, 2018
Applies to:PeopleSoft Enterprise FIN Payables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Payable Approvers are receiving an Error Message when trying to edit Payment Request transactions that have been submitted for approval.
1.- Log into the FSCM Online Application as a Payables User
2.- Create a new Payment Request transaction, and submit it for approval
3.- Log into the FSCM Online Application as a Payables Reviewer
4.- Review the Payment Request transaction, and submit it further in the workflow
5.- Log into the FSCM Online Application as a Payables Approver
6.- Navigate to the Accounts Payable WorkCenter
7.- Search in the Payment Request Pending Approval link, for the routed transaction, and open it
8.- Having the Payment Request transaction displayed, click on the 'Edit Payment Request' link available
9.- The system throws a couple of Error Messages
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.
" GetField: Field 'PR_WRK.DIST_DETAIL_PB' not found in scroll level 0. (2,155) PR_APPROVAL.GBL.PR_DIST_VW.RowInit PCPC: 39 Statement: 1
The specified field was not found in the indicated scroll level. This may occur with various PeopleCode built-in functions that specify a "scroll context" via a series of records and a field name.
Review the PeopleCode that is generating the message and the page definition and correct as appropriate. "
" Error in PeopleCode ScrollSelect processing. (2,213) PR_REVIEW_SEC.Activate PCPC: 6463 Statement: 72
A SQL error occurred during the processing of the PeopleCode ScrollSelect (or ScrollSelectNew, RowScrollSelect, RowScrollSelectNew) built-in function.
This error may have been described by a preceding message.
Examine the error messages and the PeopleCode program containing the ScrollSelect call to determine the cause of the error. "
Payment Request transactions that have already been created, and routed for approval, cannot be modified/edited should a mistake be identified. This prevents correcting transaction data, and proceed with the creation of the final Voucher.
The system should not trigger any Error Message, and allow the User to perform the needed changes on the Payment Request transaction accordingly.
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