Data Conflict Error When Creating A New PO By Copying An Existing PO With Default Ship To Comments
(Doc ID 2518671.1)
Last updated on DECEMBER 12, 2019
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Data conflict error when creating a new PO by copying an existing PO with default Ship To Comments
Creating a new PO by copying an existing PO which was first copied from a Req when default Ship To comments are set to copy to transactions causes a data conflict error.
Data being added conflicts with existing data. (18,2)
When adding a new item to the database, the system found a conflicting item already exists.
This problem can happen if another user has entered similar information at the same time as you. Note the changes you have made, cancel the page, then retry your changes.
If the problem persists, it may be because of an application or other programming error and should be reported to technical support staff.
This error occurs when the keys on the record being inserted match a record that is already in the database. The application must ensure that each inserted record has unique keys.
The issue can be reproduced at will with the following steps:
1.Set up Default Ship To comments for BU US001:
Navigate to:Set Up Financials/Supply Chain > Product Related > Procurement Options > Purchasing > Ship To Locations
Add new effdt row to SetID= SHARE, Ship To Location = US001
Enter Test in the Delivery Instructions text box and check the Copy To Transactions option.
2.Create a requisition for BU US001. Default Ship To comment should be added to the req. (I created ReqID:0000000151 for BU US001)
3.Create a new PO by copying from the req. The PO is created with two Default Ship To comment rows - One row with SOURCE_FROM = REQ and another row with SOURCE_FROM = PO. This can be seen in the record PS_PO_COMMENTS. (I created PO_ID:0000000254)
4.Create another new PO by copying the PO created in the previous step. Try to save and get the following data conflict error. Presumably because it is trying to insert both default comment rows from PS_PO_COMMENTS, but with the SOURCE_FROM = PO for both rows this time.
The issue has the following business impact:
Due to this issue, users cannot copy an existing PO with ship to comments to a new PO
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