Oracle Procurement Cloud
What's New

FEATURES ORIGINALLY ENABLED VIA THE OPT IN USER INTERFACE

The features in the table below were originally delivered Disabled. That is, the features required you to take action in the Opt In UI to enable for end users (plus possibly take additional setup or configuration steps). Column A shows when these features were originally delivered.

Beginning in the update version specified in Column B, these features will no longer require the Opt In UI to enable for end users. However, you may still need to take additional setup or configuration steps to enable the feature, per Column C. If additonal customer action is still required to enable, click on the feature name to get more information.

Important Note: If you have already enabled these features in the Opt In UI then NO further action is necessary.

(A) (B) (C)
Feature Product Feature
*Required*
the Opt In UI to Enable,
Originally Delivered in:
Feature
*No Longer Requires*
the Opt In UI to Enable,
Beginning in:
Action still required to enable for end users?
NO,
Delivered Ready
to Use
YES,
Customer Action Still
Required
Update 19D
Fulfill Project Material Requirements from Internal Sources Self Service Procurement 19B 19D (1)
Override Agreement Price on RequisitionsSelf Service Procurement19B19D (1)
Reinstate Unfulfilled Requisition Demand When Cancelling a Purchase Order Under Budgetary ControlPurchasing19B19D (1)
Update 19C
Configure In-App Supplier Invitation Notification with Business Intelligence PublisherSourcing19A19C
View Order and Schedule Life Cycle in Bar GraphsPurchasing19A19C (1)
Compare New Response Attachments with Prior Response AttachmentsSupplier Qualification Management19A19C (1)
Update 19B
Configure Purchase Order Approval Notifications Using Business Intelligence PublisherPurchasing18C19B (2)
Configure In-App Purchase Requisition Approval Notifications with Business Intelligence PublisherSelf Service Procurement18C19B (2)
Update 19A
Upload Price Tiers with Negotiation Lines SpreadsheetSourcing18B19A (2)

(1) SMALL Scale UI or Process-Based Feature: These features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

(2) LARGER Scale UI or Process-Based Feature: These features have more complex designs. Therefore, the potential impact to users is higher, meaning these features should be the focus of customer acceptance testing.