IMPORTANT Actions and Considerations

Check for Redwood Pages That Are Enabled by Default

Some Redwood pages might be enabled by default in this update. For details, check these resources:

Classic to Redwood Page Mapping: This document maps Classic pages to their corresponding Redwood pages, and gives you step-by-step paths to locate the Redwood pages. This document also specifies, where applicable, which profile options or opt-in features you must enable to display the Redwood pages. Additionally, this document specifies whether additional privileges are required for users to access and use each Redwood page.
Features with Opt-In Expiration: This page lists opt-in features and identifies the update in which each feature will be enabled by default. SCM Redwood feature names are prefaced by "Redwood."

If a Redwood page that's controlled by a profile option is enabled by default in an update, you can change the profile option setting to revert to the classic version of the page if you're not ready to move to the Redwood version of the page.

Replaced and Removed Features

From time to time, Oracle replaces existing Cloud service features with new features, or removes existing features. Replaced features may be put on a path to removal. As a best practice, you should use the newer version of a replaced feature as soon as the newer version is available.

This section identifies the features in this Cloud service that have been replaced or will be removed.

Module	Removed Feature	Target Removal	Replacement Feature	Replaced In	Additional Information
Order Management	Get Order Details operation of the Order Information Service web service.	26D	Get One Sales Order action of the Sales Orders for Order Hub REST API.	25D
Order Management	Planning for Orchestration Processes	26D	None	-	Starting in update 26D, you can no longer use the planning feature for orchestration processes: - You can't use the Planning section when you define your orchestration, and you can't use any of that section's attributes, including Planning Default Branch, Fulfillment Completion Step, Default Lead Time, Lead-Time UOM, Lead-Time Expression, and Next Expected Task Status. - You must set the Enable Orchestration Process Planning and Calculate Jeopardy order management parameter to No. - You can no longer use the Plan Orchestration Processes scheduled process.
Global Order Promising	Available Supplies REST resource Order Promises REST resource	26A	Global Order Promises REST resource	20D	No additional enhancements will be made to the Available Supplies and Order Promises REST resources. The resources will continue to work until they're removed in 25C, but you should move to the replacement Global Order Promises resource at your earliest convenience. The Global Order Promises REST resource provides more comprehensive access to order promising features, including availability checking, allocation rules, order scheduling, and supply information. It also delivers higher performance. For details about the Global Order Promises REST resource, see REST API for Oracle Fusion Cloud SCM, available on the Oracle Help Center.
Order Management	Purge Recent Objects scheduled process Purge Recent User Requests scheduled process	25D	Delete Nontransactional Entities from Closed Sales Orders and Fulfillment Lines scheduled process	24C	For details about the replacement scheduled process, see Delete Nontransactional Entities from Closed Sales Orders and Fulfillment Lines.
Order Management	RequestHold and ReleaseHold operations in the Receive Order Request SOAP service	25D	Apply Hold and Release Hold actions in the Sales Orders for Order Hub REST resource	23C	See Use REST API to Apply and Release Holds. For additional details about the Sales Orders for Order Hub REST resource, see REST API for Oracle Fusion Cloud SCM, available on the Oracle Help Center.
Order Management	Receive Order Request SOAP service - the following operations are replaced: ProcessOrderRequest and ProcessOrderRequestSync GetOrderDetails and GetOrderDetailsSync SubmitDraftOrder and SubmitDraftOrderSync CheckAvailability, GetAvailabilityCheck, and GetAvailabilityCheckSync RequestHold ReleaseHold ReleasePausedTasks	25D	The replacements are: Create Sales Orders action or the Update One Sales Order action in the Sales Orders for Order Hub REST resource for small sales orders; file-based data import (FBDI) for large orders Get All Sales Orders action or the Get One Sales Order action in the Sales Orders for Order Hub REST resource Update One Sales Order action in the Sales Orders for Order Hub REST resource for small sales orders; FBDI for large orders Quick Availability Check action in the Global Order Promising REST resource Apply Hold action in the Sales Orders for Order Hub REST resource - see the previous row in this table for details about enabling this action Release Hold action in the Sales Order For Order Hub REST resource - see the previous row in this table for details about enabling this action Create one sales action request in the Sales Order Action Requests REST resource	23C	The Receive Order Request Service SOAP service imports source orders from your order capture system into Oracle Order Management. This service and all of its operations (except for ReleasePausedTasks) have been replaced. You should move to the replacement options as soon as possible. For details about REST resources, see REST API for Oracle Fusion Cloud SCM. For details about FBDI imports, see File-Based Data Import (FBDI) for SCM. Both guides are available on the Oracle Help Center.
Order Management	Order Import SOAP service - the following operations are replaced: createOrders and createOrdersAsync submitDraftOrder and submitDraftOrderAsync stageOrders and stageOrdersAsync	25D	The replacements are: Create Sales Orders action or the Update One Sales Order action in the Sales Orders for Order Hub REST resource for small sales orders; file-based data import (FBDI) for large orders Update One Sales Order action in the Sales Orders for Order Hub REST resource for small sales orders; FBDI for large orders Create Sales Orders action or the Update One Sales Order action in the Sales Orders for Order Hub Requests REST resource	23C	The Order Import SOAP service imports source orders from your order capture system into Oracle Order Management. This service and all of its operations have been replaced. You should move to the replacement options as soon as possible. For details about REST resources, see REST API for Oracle Fusion Cloud SCM. For details about FBDI imports, see File-Based Data Import (FBDI) for SCM. Both guides are available on the Oracle Help Center.
Order Management	Original way to process holds	25C	New way to process holds	24C	Starting in update 24C, you could enable the FOM_NEW_HOLDS_PROCESSING profile option to use a faster and more efficient way to process holds. Starting in update 25C, Order Management comes predefined to use this new way to process holds, by default. You won't have to enable the profile option and it isn't available. Also starting in update 25C, you must make sure that the order line you want to hold is in a wait state before you apply or release the hold. If it isn't, then Order Management will put the request to apply or release the hold in error. For details, see the Use a Wait Step subtopic in Guidelines for Setting Up Holds on Sales Orders.

Changes to Pricing Algorithms

Some algorithms in Oracle Pricing have changed in this update, and the changes may require you to take action.

Pricing Process	Algorithm Name	Type of Change (New/Update)	Description of Change
Price Sales Transactions	Get Sales Pricing Strategy	Update	Support for customer-based strategy derivation
Price Sales Transactions	Price Sales Transactions	Update	Support for shipping benefits in pricing promotions.
Price Sales Transactions	Calculate Shipping Charges	Update	Incorporates shipping benefit changes.
Price Sales Transactions	Populate Charge Component Explanation Message	Update	Checks the header currency unit price to populate the promotion explanation message.
Price Sales Transactions	Apply Pricing Terms	Update	Support shipping related benefits and model item benefits for promotions.
Price Sales Transactions	Apply Promotions	Update	Apply free and discounted shipping benefits.
Price Sales Transactions	Calculate Tax Cost and Margin	Update	Changes to exclude rollup charge in resequencing and resetting running unit price for Channel Program Adjustments.

If you have any algorithms that are at version 1 or greater, then you must reconcile and promote each time you update or patch. Some new features might include new or updated algorithms and will work correctly only after you reconcile and promote. If all of your algorithms are at version 0, then you don’t need to reconcile and promote.

If you no longer need your extended algorithms, then remove all of the ones that are at version 2 or higher, and then use the Delete All Version 1 action. This way, you won't need to reconcile and promote algorithms when you update or patch. For details, see Promote Pricing Algorithms Into the Latest Update.

Make Sure the Relationship Type is Contact

If you use Oracle Order Management's classic pages, then you must make sure the relationship type is Contact for the value that you select in the Bill-to Contact, Sold-to Contact, and Ship-to Contact attributes on the order line. If you don't, Order Management will still submit the sales order but you might encounter problems in Oracle Receivables.

You specify the relationship type in the Persons work area under Customer Data Management when you click Relationships on the Edit Person page, edit the relationship, and set the Relationship attribute. You can't modify a person's relationship after you save your changes on the Edit Person page, but you can revise the sales order and select another contact.

As an alternative, you can use Order Management's redesigned pages in the Redwood experience or import through REST API, and Order Management will automatically validate whether the relationship type is correct.

Constrain Updates on Split Order Lines for Partial Shipments or Drop Shipments

You no longer need to opt into these features starting in update 26A:

Update Attributes on Split Order Lines for Partial Shipments
Update Attributes on Split Order Lines for Partial Drop Shipments

This means that you can update attributes on a split order line that Order Management automatically created during a partial shipment or partial drop shipment on sales orders that you submit after you opt in, or after 25D without opting in.

If you already enabled these features, then you don't need to do anything. However, if you want to continue to restrict users from updating these lines, then you must set up this constraint:

Go to the Setup and Maintenance work area, click Tasks > Search, then search for and open Manage Processing Constraints.
On the Manage Processing Constraints page, click Constraints.
Click Actions > Add Row, then set these values:

Attribute	Values
Constraint Name	SPLIT ORDER LINE CONSTRAINT
Display Name	Constrain update on split line for partial shipments or partial drop shipments.
Constraint Entity	Order Fulfillment Line
Constrained Operation	Update
Attribute Name	Contains no value.
Enabled	Contains a check mark.

In the Details section, in the Conditions list, click Actions > Add Row, then set these values:

Attribute	Values
Group Number	10
Validation Entity	Order Fulfillment Line
Validation Rule Set	Order Management Created Split Line for Partial Shipment
Record Set	Fulfillment Line Default Record Set
Message	You can’t update a split line that Order Management created during a partial shipment or partial drop shipment.

Reserve Order Lines That Fail Reservation

Starting in update 25D, the Redwood: Prioritize Order Lines for Reservations and Simplify the Integration feature comes predefined as enabled. You no longer need to opt in. If you haven’t already enabled this update 25B feature, then make sure you carefully review the feature’s What’s New content, especially the Tips and Considerations section. This section provides important information about the ramifications of this feature on your implementation, and the details will help you take the appropriate steps to prepare for the feature.

Privilege Required to Opt In to Features

To opt in to the Redwood: Create and Manage Sales Orders feature, you must be assigned a configured job role that includes this existing privilege:

Administer Tasks for Opt-in Features (DOO_ADMINISTER_TASKS_FOR_OPTIN_FEATURES_PRIV)

Use Change Instead of Revision

You can revise a sales order or you can make a change on it. For example, if you open an order and click Create Revision, then Order Management copies the entire order and adds a revision number to it. You can also make a change in the order without revising it. For example, before update 26A, if you manually updated a scheduling attribute or an extensible flexfield after you submitted the order, then you could use the Revision Reason and Revision Comments attributes to provide detail about your change. However, that wasn't entirely accurate because you didn't make the change in a revised order. Starting in update 26A, the redesigned pages replace the term Revision with the term Change so the attributes more accurately reflect whether you made the change in a revision or not.

Update 26A will continue to get the value for the Change Reason attribute from the ORA_FOM_REVISION_REASON lookup.

Here's a summary of what's different:

List of old and new attribute names

Old Attribute Name	New Attribute Name
Revision Reason and Revision Comments on the order header and order line	Change Reason Change Comments
Revision Reason in the AI Assist window when you enable the enableChangeCommentsAIAssist parameter	Change Reason
Revision Comments in the Revisions tab of the Revisions and related orders section	Change Comments
Order Revision Reason on the Sales Orders search page	Order Change Reason
Order Revision Reason and Revision Reason in the Sales Order Lines search page	Order Change Reason Change Reason
Order Revision Comments in the Sales Order Lines search page	Order Change Comments
Revision Reason and Revision Comments in Visual Builder Studio	Change Reason Change Comments

If you used an old attribute name in a custom business rule before update 26A, such as a form rule or collection rule, then you must rewrite the rule so it uses the new name.

Rerun the Update or Close Sales Orders Scheduled Process

Starting in update 26B, you must use the revised Update or Close Sales Orders scheduled process. Oracle has added some new parameters to this scheduled process and removed some of the old parameters. You will need to set the parameters so they meet your business requirements and schedule the process again.

If you're currently using the old version of Update or Close Sales Orders and haven't upgraded to 26B, then you must enable the FOM_USE_NEW_CLOSE_ORDERS profile option, revise your parameter settings on the new version, and then upgrade to 26B. If you don't do this and upgrade, then the old version won't close any sales orders and you will encounter error messages in the scheduled process log. If you already upgraded to 26B and didn't enable the profile in an earlier release, then cancel all instances of the Update or Close Sales Orders scheduled process that are currently running, then set up and run the new version of Update or Close Sales Orders. Note that the old process updated the order header's status to Partially Closed but the new process doesn't.

Prepare for Changes to Import Behavior

Starting in update 27B, the Import and Fulfill Large Volumes of Sales Order opt-in feature will come predefined as enabled, by default. The Import Sales Orders scheduled process will use behavior that's similar to the SalesOrderForOrderHub REST API. Use these guidelines to help you prepare.

Create Customers

Old	New	Recommendation
If you set the CreateCustomerInformationFlag attribute to true, then the import could create party, site, contact, account, site use, and account role data.	You can't set the CreateCustomerInformationFlag attribute. If the customer doesn't exist in the customer master before you import the order, then you can no longer import that order.	Use the Customer for Sales Orders REST API to create the sold-to, ship-to, and bill-to data, then use that data to create your sales orders.

Use Extenstions Instead of Transformation Rules

Old	New	Recommendation
You could use pretransformation, transformation, and posttransformation rules.	You can't use transformation rules any more, starting in update 27B.	Use an order management extension instead.

Use Objects in Extensions to Read Data

Old

New

Recommendation

An On Start of Submission Request extension runs after you submit the order, so:

Sales order data is already in the database and you can use a public view object (PVO) to query the order.
The order number is available because the commit is done.

On Start of Submission Request runs before you submit the order, so:

You can't use a PVO to query data.
The order number isn't available. It contains a default value of -1 (negative 1).

Use the Extension objects that are available in your extension to read the current sales order's data.

Use a PVO to query order data only for related orders, such as a processing order when working on a revision, or the original order when working on a return.

Split Your Order Lines

Old

New

Recommendation

You could use the SourceLineId attribute in your REST payload to revise an order. You modified the revision's overall line quantity, and Order Management accurately adjusted the quantity across split lines.

For example:

Split a quantity of 15 on line x into a quantity of 7 on line y and 8 on line z.
Submit a revision that has a quantity of 10 on line x, revised down from the original order's quantity of 15. You now have a new split quantity of 7 on line y and 3 on line z.

If you use SourceLineId to revise an order, then Order Management applies that update only on the original, first fulfillment line. It doesn’t update any new or subsequent split lines, and that can lead to unintended and incorrect order changes.

Example:

You split an original quantity of 15 on line x into 7 on y and 8 on z.
You submit a revision to reduce the quantity on x from 15 to 10.
After the revision, the split lines become 10 and 8. Order Management updates only line y from 7 to 10, while line z remains unchanged.
As a result, the total quantity incorrectly increases from 15 to 18 instead of being reduced to 10.

Use FulfillLineId when you update a fulfillment line after a split during a revision.
Don't use SourceLineId in this scenario.

Consider Case Sensitivity

Old	New	Recommendation
The import wasn't case sensitive when converting a lookup's value to its ID.	The Import Sales Orders scheduled process is case sensitive.	Make sure your import payload uses the correct case.

Set Default Values for Ship-to and Bill-to Attributes

Old	New	Recommendation
Order import couldn't set default values for the ship-to and bill-to attributes.	If you don't include values for these attributes, then the import will populate default addresses and other attributes from your customer's party data.	If you were setting these values manually after import, you no longer need to do it.

Changes to File-Based Data Import (FBDI) Templates

The following Global Order Promising FBDI template has changed in this update. For details of the specific changes, refer to the Instructions tab of the FBDI template:

ERP Integration Service Parameters(ScpErpIntegrationServiceParamsImportTemplate)

You can find the latest templates in the Supply Chain Planning section of Oracle Fusion Cloud SCM: File-Based Data Import (FBDI) for SCM, available on the Oracle Help Center.