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

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:

  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.

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

Get Pricing Recommendations

Get Pricing Recommendations

New

New pricing process service to return pricing promotion recommendations for a sales order. This supports the feature “Redwood: Use AI Services with Your Pricing Promotions.”

Price Sales Transaction

Aggregate Roll Up Charge Components

Update

Changes to the roll-up calculations to support the feature “Round Values in Header Currency for Coverages and Configured Items.”

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 Holds

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 don't have to enable the profile option and it isn't available.
  • 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.
  • You can't apply but you can release a hold on an order line from a fulfillment view or through REST API.

Assume you have an order line where SourceLineId equals 1, a quantity of 10 for the AS54888 Computer item, and one free, included item, Mouse, on order line 2. The computer and the mouse have the same SourceLineId. Assume Order Management splits line 1 into three lines during fulfillment with quantities of 2,3, and 5. You now have 3 fulfillment lines for the computer and 1 for the mouse, and all of them have the same SourceLineId. Now you can:

  1. Use REST API to apply or release a hold only on fulfillment line 1. Send that line's ID.
  2. Use REST API to apply or release a hold on all 4 fulfillment lines. Send SourceLineId = 1.
  3. If you use SourceLineId = 1 to apply a hold through a web service, then Order Management will apply it on line 1. You can use SourceLineId = 1 to release it through REST API. 

For details, see the Use a Wait Step subtopic in

Guidelines for Setting Up Holds on Sales Orders

.

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:

  1. Go to the Setup and Maintenance work area, click Tasks > Search, then search for and open Manage Processing Constraints.
  2. On the Manage Processing Constraints page, click Constraints.
  3. 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.
  1. 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)