Expenses - Anyone Using ERPostAudit Approval Process (For Non-SHARE)?

We are on 9.1 (just upgraded two weeks ago from 8.9 and very cleanly as well) and tools 8.52.12

I have discovered a most entertaining issue that requires more research on my part but the problem that our approvers are seeing is from their approval page they select the "Employee Expense History" link which then brings up another list (expense reports and cash advances). If the approver then selects an item that is Paid they get a fatal PeopleCode error.

I have traced it down to the issue where the system has determined that the expense report is Paid (or Paid and Billable) so it then changes the approval process from ERApprove to ERPostAudit and then attempts to find all the approvers for post auditing. The problems include:
1) We have not set up post auditing
2) The delivered ERPostAudit definition exists for SHARE but we use UWMSN

I have an open case with Oracle and have figured out a simple workaround (comment out the "offending" Evaluate statement) but am wondering who out there is either successfully using Post Audit OR are NOT using Post Audit and have seen this issue?

The magic trick is that there can NOT be any setup for ERPostAudit for the specific SETID so if you use SHARE and kept this delivered definition then it is hanging around and the code will find it and process it.

We encountered this undocumented "feature" a couple months ago.
We don't use the ERPostAudit functionality either.

But to avoid a customisation at a key point in our project, we:
(1) created the ERPostAudit approval process under our own setid, and
(2) deactivated the SHARE version of the ERPostAudit approval process
FYI - We didn't activate the corresponding PostPayAuditor functionality on the Transaction Definition.

This setup was enough for the problem to stop occurring. We did not have enough time to fully work out the reason for this weird code taking place when we weren't even using ERPostAudit.

Cheers
Jeremy

Help the community by fixing grammatical or spelling errors, summarizing or clarifying the solution, and adding supporting information or resources. Always respect the original author.

Popular White Paper On This Topic

We encountered this undocumented "feature" a couple months ago.
We don't use the ERPostAudit functionality either.

But to avoid a customisation at a key point in our project, we:
(1) created the ERPostAudit approval process under our own setid, and
(2) deactivated the SHARE version of the ERPostAudit approval process
FYI - We didn't activate the corresponding PostPayAuditor functionality on the Transaction Definition.

This setup was enough for the problem to stop occurring. We did not have enough time to fully work out the reason for this weird code taking place when we weren't even using ERPostAudit.

That was pretty much it. Once I cloned the CAPostAudit and ERPostAudit process definition from SHARE to it resolved the problem.

The good news is that the Expense Transaction does not need to reference it just that the Approval Process Definition exists in the Approval Framework.

Did discover an entertaining side effect: the Post Liabilities application engine looks for this approval process and if it is defined it will push through the items (CA and ER) into the Post Payment Approval process (this can be quite a few messages published in IB all at once)