EEX 9.1+: How To Avoid Expense Report Header And Line Statuses Being Out Of Sync Due To Error Message (10502,312) Present In Record PS_EX_SUM_APPR_ERR?

(Doc ID 2332706.1)

Last updated on NOVEMBER 27, 2017

Applies to:

PeopleSoft Enterprise FIN Expenses - Version 9.1 to 9.2 [Release 9]
Information in this document applies to any platform.

Goal

Some customers have reported to the Expenses OSS Team issues with Expense Report Header Status (Record Field PS_EX_SHEET_HDR.SHEET_STATUS), and Expense Report Line Status (Record Field PS_EX_SHEET_LINE.EX_LINE_STATUS), becoming out of sync when Expense Approvers are taking actions on the submitted transactions. In such cases, the Header level keeps being in SUB status (Submitted For Approval), while the Lines are in APY (Approved For Payment). When digging further, the below Error Message, or similar ones, are found, and stored in Table PS_EX_SUM_APPR_ERR:

     " The following error occurred when approving the transaction: (10502,312) EX.Approval.Actions.ExpenseApproval.OnExecute Name:ProcessAction_ PCPC:27424 Statement:552
       Called from:EX.Approval.Actions.ExpenseApproval.OnExecute Name:Approve Statement:142
       Approval action not allowed for your profile.
       Accounting date is invalid (10502,390) EX.Business.ExpenseReport.OnExecute Name:ValidateAcccountingDate PCPC:11464 Statement:219
       Called from:EX.Business.ExpenseReport.OnExecute Name:IsValid Statement:189
       Called from:EX.Approval.Actions.ExpenseAppr"
       The following error occurred when approving the transaction: (10502,312) EX.Approval.Actions.ExpenseApproval.OnExecute Name:ApproveAll PCPC:8288 Statement:187
       Called from:EX_APPR_WF.TxnProcessing.Messaging.ApprovalSubscriber.OnExecute Name:ExecuteAp "

Due to this out of sync problem, the affected Expense Reports are not being placed in Approved For Payment status (PS_EX_SHEET_HDR.SHEET_STATUS = 'APY'), and this means they cannot be posted, nor staged for payment.

Unfortunately, this happens on rare, and random occasions, and customer nor OSS Team has been able to replicate such scenarios. While there is no official fix, would there be a workaround to avoid such out of sync transactions becoming corrupted?

 

Solution

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