Last updated on MARCH 06, 2017
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
A Fatal PeopleCode SQL Error gets triggered by the system when submitting for approval an Expense Report, or opening the routed transaction as an Approver, when in at least one of the Expense Report Lines, the Transaction Amount has surpassed the defined Expense Location Amount for a specific Expense Type and Currency Code, and Risk Templates have been defined with Expense Type Amount Limits, and linked to any of the Approver Levels active at the Expense Report Transaction Definition level.
Should the User's expense amount be over the Expense Location Amount limit, and the one defined at the Risk Template level, a comment would need to be provided as a justification. Even though that is done, and Auto Approval is defined at the Business Unit Payables Definition level for a greater amount threshold, the Error prevents the transaction from properly responding to the approval workflow steps, delaying the reimbursement of the amounts owed to the Employee.
Upon submitting the Expense Report, the Error Message confuses the Users, as the Approval Train is not being displayed. Also, the Error Message gets triggered each time the User wants to view the submitted transaction. Additionally, for the Expense Approvers in question, the Expense Report gets routed, but upon trying to open the transaction, the Error Message is triggered, and the page would not load, meaning that the submitted Expenses cannot be reviewed, nor approved.
1.- At the Transaction Definition set up page for Expense Reports, activate HR Supervisor, and Pre Pay Auditor, as well as the Auto Approval flag from the Pre Pay Auditor line
2.- For the Risk Template on Expense Report, and Pre Pay Auditor approver, define at the 'Expense Type Amount Limits' section an Expense Type, Business Unit, and Amount
3.- On the Prepay Auditor Approver Profile, enter the Prepay Auditor Risk Template within the Expense Report transaction type line
4.- On the Business Unit 2 tab of the Payables Business Unit Definition level, enter 1500.00 in the Monetary Amount Threshold, and Turn on “Auto Approve Only if No Risk”
5.- Create, and submit a brand new Expense Report with a Line using the Expense Type defined at the Risk Template, and a Transaction Amount that exceeds the limit entered at the Risk Template
6.- Click on the Refresh Approval Status button, or View the submitted Expense Report, and an Error Message is triggered by the system
7.- Login as the HR Supervisor, and select the transaction in question to approve it, and receive an Error Message as well
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.
" A fatal PeopleCode SQL error occurred. Please consult your system log for details.
The following error occurred during accessing pending approval: (10502,317) EX.Approval.MISC.PendingApprovers.OnExecute Name:PendingApprovers PCPC:2672 Statement:55
Called from:EX.Approval.MISC.ApprovalPermission.OnExecute Name:ApprovalPermission Statement:2
Called from:EX_UI.ApproveTransactions.ProfileAttributes.ProfileAttributes.OnExecute Name:SetProfileAttributes Statement:11
Called from:EX_SHEET_APPR.GBL.PreBuild Statement:24
SQL error. Function: SQLExec
Error Position: 0
Return: 0 -
Original Statement: UPDATE PS_EX_RISK_ER_DTL SET LINE_NBR = %DecDiv(LINE_NBR,-1) WHERE SHEET_ID = :1 AND LINE_NBR = :2 AND RISK_LEVEL = :3 AND APPROVAL_OPRID =:4 AND RISK_CRITERIA IN ( 'Expense Type Amount Limits' )
Caught Exception: Invalid SQLExec update for this type of PeopleCode program. (2,146) EX_APPRV.Risk.OnExecute Name:ProcessRisk PCPC:33575 Statement:493
Called from:EX_APPRV.Risk.OnExecute Name:GetRisks Statement:42
Called from:EX.Approval.List.EXApproverList.OnExecute Name:GetUsers Statement:62
Called from:EOAW_CORE.ENGINE.DefStepInst.OnExecute Name:FindApprovers Statement:28
Called from:EOAW_CORE.ENGINE.DefStepInst.OnExecute Name:Bind Statement:201
Called from:EOAW_CORE.ENGINE.PathInst.OnExecute "
The Expenses Approval Workflow should work correctly, not triggering the Error Message in question, routing the transaction to the proper approvers, displaying the Approval Train at all times, and allow review/approval by the Expense Approver Users.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms