OPT IN FEATURES WITH FUTURE EXPIRATION

The features in the table below were originally delivered as Opt In but will, in a future update, no longer require Opt In to enable. You may still need to do some additional setup or configuration, as indicated in Column C. This advance notice of upcoming Opt In Expiration will help you plan for these changes. Once the Opt In has expired the feature will be included in the table above.

Important Note: If you have already enabled these features then NO further action is necessary.

		(A)	(B)	(C)
Feature	Module	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 24A
Approve Customer Programs with BPM Workflow	Channel Revenue Management	24A	25A
Update 23D
Approve Customer Claims with BPM Workflow	Channel Revenue Management	23D	24D
Hold Changes from Manufacturing Until Purchase Orders Are Ready in Outside Processing Flows	Supply Chain Orchestration	23D	24D	(1)

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	Module	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 24C
Add Postprocessing Days When You Modify Ship Dates in Your Back-to-Back Flows	Supply Chain Orchestration	24A	24C	(1)
Update 24B
Improve Processing After Supply Chain Orchestration Updates Supply or Demand	Supply Chain Orchestration	24A	24B	(1)
Update 24A
Use the Supply Chain Orchestration Work Area to Synchronize Supply Documents	Supply Chain Orchestration	23C	24A	(1)
View Manual Reservations for Your Back-to-Back Sales Orders	Supply Chain Orchestration	23C	24A	(1)
Update 23D
Include Reference Details for Supply Requests on REST API Error Messages	Supply Chain Orchestration	23B	23D	(1)
Update 23C
Improve Supply Tracking for Sales Orders in Your Back-to-Back Flows	Supply Chain Orchestration	23A	23C	(2)
Update 22D
Configure Preferred Date Format for the Planning Table Data REST Service	Supply Planning	22D	23B	(1)
Review Sales Order Line Number	Supply Planning	22D	23B	(1)
Update 21D
Collect Ship-to Party and Party Sites Not Associated with a Customer Account	Global Order Promising	21D	22D
Include Planned Supply in Order Promising Calculations	Global Order Promising	21D	22D	(2)
Update 22C
Create a Transfer Supply Request That Includes Project Details	Supply Chain Orchestration	22A	22C	(1)

(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.