Supplier Change Request is Pulling Data from Previous Effective Dated Rows

(Doc ID 2398533.1)

Last updated on MAY 14, 2018

Applies to:

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

Symptoms

When using the Supplier Change Request (SCR) to change supplier data, the system is pulling in data, i.e. phone numbers, from previously created effective dated rows into the most recent effective dated row on the change request page.

When they try and save the request, an error appears.

ERROR
Update Error - Errors on Submit of Supplier Change Request

Data being added conflicts with existing data (18,2)
Error saving Component Interface . {SCR_SUP_ID_CI} (91,37)

The issue can be reproduced at will with the following steps:
1. Ensure that a supplier has a contact that has at least 2 Effective Dated rows on the Details page. One should be an older dated row, and a recent dated row.
2. Ensure that the older dated rows has at least the phone number and that the most recent dated row, has no phone/fax/ etc. information
3. Initiate a Supplier Change Request for this supplier
4. Click on the Contact trainstop and click on the Edit button for the contact with 2 effective dated rows
5. The phone number(s) from the older dated row appears on the page, when the most recent dated row does not have this information
6. Try to save and submit the change request. (for customer this results in an error)

The issue has the following business impact:
Due to this issue, users are not able to save and process Supplier Change Requests.

Changes

 

Cause

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