POA_ALERTS Run To No Success. Failed With Unique Constraint Error

(Doc ID 2368209.1)

Last updated on MARCH 01, 2018

Applies to:

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


On : 9.1 version, Purchase Orders
Answer: Tools Version :8.52.20
Bundle 20

POA_ALERTS run to No Success. Failed with unique constraint error

Purchase orders Run Acknowledgement Alerts process fails with unique constraint error.

Unique constraint error

The issue can be reproduced at will with the following steps:
Replication steps:
1. Open two internet browsers.
2. Purchasing > Purchase Orders > Dispatch POs. Take one already dispatched PO. Dispatch the same PO in both the windows same time. (It can be also multiple user dispatching same PO same time).
3. PS_PO_DISPATCHED table is populated with two entries for the same PO with same DATETIME_DISP field but with different Process Instance.
4. Purchasing > Purchase Orders > Acknowledgements > Run acknowledgement Alerts. Run the acknowledgement alert process for the PO related BU/Buyer/Vendor.
5. Job runs to No Success with the unique constraint error.

Process 8738024 ABENDED at Step POA_ALERTS.ChckViol.AckDisp (SQL) -- RC = 805

The issue has the following business impact:
Due to this issue, users encounter a Unique Constraint error when multiple users attempt to dispatch the same PO


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