EPC: PC_PO_TO_PC Fails With Error 805 – ORA-00001: Unique Constraint at Step PC_PO_TO_PC.11000000.INSRT_WO
(Doc ID 2505702.1)
Last updated on NOVEMBER 19, 2023
Applies to:
PeopleSoft Enterprise FIN Project Costing - Version 9.2 to 9.2 [Release 9]PeopleSoft Enterprise SCM Purchasing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Symptoms
PC_PO_TO_PC fails with Unique Constraint error at Step PC_PO_TO_PC.11000000.INSRT_WO.
Error Position: 0 Return: 805 - ORA-00001: unique constraint (SYSADM.PS_PC_RES_PO_TAO4) violated Failed SQL stmt:INSERT INTO PS_PC_RES_PO_TAO4
Steps
1. Create a project and an activity.
2. Add a resource to the project.and to the activity.
3. Create a Work Order.
4. Open the WO and click on Schedules tab and then on Purchase/On-hand link.
5. Add 5 WO lines.
6. Click on Load Purchase Order(s).
7. Run PO_AUTO_SRC to create the PO from the WO.
8. The PO has been created. PO Auto Sourcing Program inserts a row in IN_PEGGING table for each PO Lines.
9. Delete PO line 4. Line number 5 was renumbered to 4.
10. Delete PO line 1. Line number 2 was renumbered to 1.
11. Delete PO line 1. Save the page.
12. The system should update the PEG_STATUS for the PO lines 1, 2, 4 to 40 (Cancelled).
It updated PEG_STATUS for PO Line Number 4, 1 as expected but PO Line Number 2 is not updated.
PO Line Number 2 is not deleted from IN_PEGGING Table and present as an Orphan Record with same HASH Key Value.
13. Dispatch the PO.
14. Run PC_PO_TO_PC.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |