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:

  • SCM Redwood Pages with Profile Options: This article includes an attached list of the SCM Redwood pages that are controlled by profile options. Check the Default On Release column to find out which pages are enabled by default in an update.
  • 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
Global Order Promising

Available Supplies REST resource

Order Promises REST resource

 25C 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

 25C

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

To use the Apply Hold and Release Hold actions in the REST resource, you must first create and enable a specific profile option. For instructions, see Use REST API to Apply and Release Holds.

For 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:

  1. ProcessOrderRequest and ProcessOrderRequestSync

  2. GetOrderDetails and GetOrderDetailsSync

  3. SubmitDraftOrder and SubmitDraftOrderSync

  4. CheckAvailability, GetAvailabilityCheck, and GetAvailabilityCheckSync

  5. RequestHold

  6. ReleaseHold

  7. ReleasePausedTasks

 25D

The replacements are:

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

  2. Get All Sales Orders action or the Get One Sales Order action in the Sales Orders for Order Hub REST resource

  3. Update One Sales Order action in the Sales Orders for Order Hub REST resource for small sales orders; FBDI for large orders

  4. Quick Availability Check action in the Global Order Promising REST resource

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

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

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

  1. createOrders and createOrdersAsync

  2. submitDraftOrder and submitDraftOrderAsync

  3. stageOrders and stageOrdersAsync

 25D

The replacements are: 

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

  2. Update One Sales Order action in the Sales Orders for Order Hub REST resource for small sales orders; FBDI for large orders

  3. 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 method to process holds 25C New method to process holds 24C

Starting in update 24C, you had the option to 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 will come predefined to use this new method of processing by default. You won't have to enable the profile option, and the profile option will no longer be available.

For details, see Use Order Management Extensions to Apply Holds.

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 Transaction

Process Free and Promotion Item Terms

Update

Changes to incorporate the Cost element charge component to free item.

Price Sales Transaction

Set Initial Values

Update

Changes to persist the free item promotion with all closed lines in the revised order.

Price Sales Transaction

Price Sales Transactions

Update

Changes to fix the manual price adjustment issue in the prepriced order with shipping charges calculation.

Price Sales Transaction

Spread Adjustments

Update

Changes to fix the negative spread distribution for model item discounts.

Price Sales Transaction

Populate Charge Component Explanation Message

Update

Changes to incorporate new pricing messages for promotions flow.

Price Sales Transaction

Apply Tiered Pricing

Update

Changes to populate PromotionCode attribute on charge component.

Price Sales Transaction

Apply Pricing Terms

Update

Changes to populate PromotionCode attribute on charge component.

Price Sales Transaction

Apply Promotions

Update

Changes to process promotion codes.

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.

Changes to Currency Conversion

If you set the CurrencyConversionType attribute in your import payload or order management extension to:

  • User: You must include values in CurrencyConversionRate and CurrencyConversionDate.
  • Any other value: Don’t include values in CurrencyConversionRate and CurrencyConversionDate.

Oracle Receivables will default the values according to your setup. Also, you can't modify the currency and currency exchange while you revise a sales order.

Starting in update 25C, Order Management will validate these values when you submit the sales order. It will reject any sales order that doesn't have the correct currency details. You must verify and, if necessary, correct your implementation before you update to 25C.

Changes to File-Based Data Import (FBDI) Templates

A Supply Chain Planning FBDI template has changed in this update. For details of the specific changes, refer to the Instructions tab of this FBDI template:

  • Sourcing (ScpSourcingImportTemplate)

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

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.

Order Management Automatically Populates Split Lines

Oracle Order Management added a profile option in update 23A that controlled whether to automatically populate values on a new split line with values from the original line when you split a line in the Split Fulfillment Line dialog. Starting in update 25B, Order Management no longer uses that profile on redesigned pages in the Redwood user experience, but instead automatically populates the values. Order Management still uses the profile on classic pages.

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)