Define Mappings for Contract Owners to Buyers in External Purchase Prices

Map contract owner names provided by source systems to the buyer names defined in Oracle Fusion Cloud Procurement for every procurement business unit. When you import external purchase prices, these mappings align the buyer names as per the mapping definitions.

Prior to this update, the name of the buyer for creating purchase agreements was determined based on the value that was specified in the Default Buyer parameter of the Import Purchase Agreements from External Purchase Prices scheduled process. This resulted in all purchase agreements created in that run of the scheduled process to get the same default buyer assigned to them. If the default buyer was not passed, the Procurement default was used.

With this update, you now have the flexibility to pass different buyers for different source contracts by defining mappings between source contract owners and buyers. You can now pass a source contract owner at the header level by using the file-based data import (FBDI) template for External Purchase Prices or by using the externalPurchasePricesRequests REST API.

If you pass the source contract owner and the corresponding buyer mapping is defined, then the derived buyer name is passed on to the blanket purchase agreement from the external purchase prices. In case of updates to an existing purchase price, if there is a change to the buyer, then it is passed as an update to the corresponding purchase agreement.

The External Purchase Prices Mappings page has a new Buyer tab where you can define and manage source contract owner to buyer mappings.

Buyer Mapping

Buyer Mapping

Alternatively, from the external purchase price mappings page, you can download the template for external purchase price mappings. This predefined template uses the Oracle Visual Builder Add-in for Microsoft Excel to download, update, and create external purchase price mappings. The template now has a Buyer tab where you can define and manage buyer mappings.

Buyer Mapping Spreadsheet

Buyer Mapping Spreadsheet

Buyer mapping enables you to translate the value of the source contract owner from the source system to the buyers defined in Oracle Procurement for every procurement business unit .

The Buyer tab in the Oracle Visual Builder Add-in enabled Excel template enables you to achieve significant reduction in data entry efforts by updating the mapping data in bulk.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Procurement

If you want to use this feature, then you must opt in to its parent feature: Create Blanket Purchase Agreements by Source Contract Number. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

Tips And Considerations

The source contract owner is optional while importing external purchase prices from the source. If the source contract owner is not passed or if the mapping has not been defined, the existing logic of deriving the buyer for the purchase agreement will continue. The existing logic  assigns the buyer based on the value specified in the Default Buyer parameter of the Import Purchase Agreements from External Purchase Prices scheduled process. If no value is specified for the Default Buyer parameter, then the defaults defined in Oracle Procurement are taken. 

Access Requirements

Users who are assigned a configured job role that contains these privileges can manage or update the buyer mappings using this feature:

  • Manage External Purchase Prices Mappings (SCH_MANAGE_EXTERNAL_PURCHASE_PRICES_MAPPINGS_PRIV)
  • View Procurement Buyers List of Values using REST Service (PO_VIEW_BUYER_LOV_REST_SERVICE_PRIV)

Users who are assigned a configured job role that contains these privileges have a view-only access of the buyer mappings using this feature:

  • View External Purchase Prices Mappings (SCH_VIEW_EXTERNAL_PURCHASE_PRICES_MAPPINGS_PRIV) 
  • View Procurement Buyers List of Values using REST Service (PO_VIEW_BUYER_LOV_REST_SERVICE_PRIV)

These privileges were available prior to this update.