Document 1589622.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-sta...

How To Change The Buyer On RFQ/RFI Is Published or Saved As Draft ? (Doc ID 1589622.1)
In this Document
Goal
Solution
What is Updated
What is Not Updated
References

APPLIES TO:
Oracle Sourcing - Version 12.1.3 and later
Information in this document applies to any platform.

GOAL
How to Change the Buyer on RFQ / RFI once it is Published or Saved as a Draft?
This might be needed in the following Business Cases
- Buyer A initiate the RFQ/RFI/Auction.
- Buyer A retires/quits/leaves/changes company
- Buyer A is not anymore responsible for that particular sourcing document

SOLUTION
This Functionality to change the Buyer was not available Earlier which is now made available by applying Patch 17333489:R12.PON.B
After applying the patch you will see a New Concurrent Request - "Mass Update Of Sourcing Documents"
Note: This concurrent program is available in the newly created request group Sourcing Admin Group which is associated to the
Sourcing Super user responsibility.

Parameters used for this Concurrent Program are as below,

1 of 2

02-11-2015 01:31

Document 1589622.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-sta...

Old Person: The Buyer to be replaced.

New Person: The new buyer. The person entered here should a valid buyer with Create Negotiation (function
PON_CREATE_NEW_NEG) privileges.
Document number From: The starting document number (inclusive)
Document Number To: Ending document number (inclusive)
Date From : Creation Date from
Date To: Creation date to
Commit Interval: After how many records should the program write the data to the database. If this is null, the program writes the data
to the db at the end of the program.

Simulate: This flag can be used for dry run of the program. If this flag is yes while running the concurrent program, no records are
updated. But the report will show the negotiations selected for update with the filter conditions specified. It is advised to run the
program with Simulate as Yes first after specifying the other filter paramaters and verify the data selected for update, before the actual
run of the program.

What is Updated
The Negotiation header: The trading partner contacts are updated for negotiations which are not Cancelled, Deleted, or Paused. The bid
headers, contract deliverables etc are also updated.
Collaboration Team: If the New user is already present in the collaboration team we are updating the user as owner and giving him
the full access. Otherwise we are inserting a new record and giving him the creator role and full access to the negotiation. The old user
still present in the collaboration team and can perform all the activities a team member can do(if he is still a active member). If the old
person is approver (negotiation approval or award approval) we will forward the notification of the old person to the new person. Also
we will update the workflow attributes so the new person receives the approval notifications.

What is Not Updated

The templates, private reusable lists are not updated. Sourcing Super User can create the public attribute lists. Any Sourcing super user
can update the public lists, hence this table is not required for updation.
In the discussions we are not transferring the discussions performed by the old user to new user. As the old person still be present the
collaboration team. New user can view all the discussions and start new discussions.

REFERENCES
BUG:9056214 - NEED AN OPTION TO CHANGE THE BUYER ONCE RFQ/RFI IS PUBLISHED OR SAVED AS DRAFT
Didn't find what you are looking for?

2 of 2

02-11-2015 01:31