Use Negotiation Options for Catalog Shopping-Based Items

You can choose whether a catalog item-based requisition line requires negotiation or indicate if it has already been negotiated. For requisition lines created using a master item with or without a blanket purchase agreement as well as description-based lines with a blanket purchase agreement, you can enable these attributes while editing the line details. Additionally, lines created using Punchout flows are also eligible for this.

The Negotiated and Negotiation Required attributes are hidden by default. You can make them visible via Extensibility.

When enabled to display on the Edit Lines Details page, this will be the default behavior:

• Negotiation Required: It will be deselected by default.
• Negotiated:
  • For agreement-based lines: If enabled on the agreement, then it's read-only and selected. If not enabled on the agreement, then it is editable and deselected by default.
  • For non-agreement lines: It will be editable and deselected by default.

Here is an illustration of the Line Details page where these attributes are available.

Negotiation Required and Negotiated Attributes on the Line Details Page

You should not enable both of these attributes for a line. If both attributes are enabled, the "Negotiation Required" attribute will take precedence, and the line will be placed in the Process Requisitions queue. 

Here is an illustration of a scenario where the line has already been negotiated in the agreement, it will be read-only on the requisition line.

Line Negotiated on an Agreement and Is Read-Only on the Line

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 the Use Negotiation Options for Catalog Shopping-Based Items feature, then you must opt in to one or both of these features:

• Enable the Redwood Version as the Default Self Service Procurement Application: Makes the Purchase Requisitions (New) work area available to all your users, and hides the Purchase Requisitions work area from all your users.
• Procure Goods and Services Using the Redwood Self Service Procurement Application: Keeps the Purchase Requisitions work area available to all your users, and makes the Purchase Requisitions (New) work area available to the users who are assigned this privilege: Manage Requisition with the Redwood Self Service Procurement Application (POR_MANAGE_REQ_WITH_PWA_PRIV).

If you’ve already opted in, then you don’t have to opt in again.

Key Resources

• To know more about how to use the Redwood Self Service Procurement application, refer to the Procure Goods and Services Using the Redwood Self Service Procurement Application readiness training.
• To know how to provide the required privileges to your requesters to use your own configured role instead of the Requisition Self Service User role, refer to the Privileges Required for a Predefined Role for a Requisition Self Service User topic. 
• For information about using Oracle Visual Builder Studio to extend your Redwood application pages, see Oracle Fusion Cloud HCM and SCM: Extending Redwood Applications for HCM and SCM Using Visual Builder Studio

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

• Manage Requisition with the Redwood Self Service Procurement Application (POR_MANAGE_REQ_WITH_PWA_PRIV) to access the Redwood Self Service Procurement application.

NOTE: This privilege isn’t required if you have opted in to the Enable the Redwood Version as the Default Self Service Procurement Application feature to access the Redwood Self Service Procurement application.

• Create Requisition with Changes to Negotiated Indicator (POR_CREATE_REQUISITION_CHANGE_NEGOTIATED_FLAG_PRIV) to view and edit the 'Negotiated' flag.

These privileges was available prior to this update.