My Oracle Support Banner

EAP: AP_MATCH Fails With Unique Constraint Issue At AP_MATCH.NoRecpt.Step03 (Doc ID 2384551.1)

Last updated on NOVEMBER 23, 2020

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.1 and later
Information in this document applies to any platform.



AP_MATCH process fails at step AP_MATCH.NoRecpt.Step03 with an Unique Constraint Error. This happens when receipts are actively being entered when AP_MATCH process is running in the background.


1) Create 2 POs.
2) Partially receive one of the PO
3) Completely Invoice both the POs
4) Run the AP_MATCH process. While the process is running, between the step AP_MATCH.NoRecpt.Step02 and AP_MATCH.NoRecpt.Step03 create receipts for the above POs. In PROD, once a week, users create receipts will this process is running and if a receipt is created between both 2 steps, the process fails. IN DEMO and non-PROD instance, we put in a PeopleCode sleep command to replicate the issue. (in the attached AET file, the step AP_MATCH.NoRecpt.Step06 is the sleep command)
5) Process goes to 'No Success' with the unique constraint error.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.