IMPORTANT Actions and Considerations

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	25C	Apply Hold and Release Hold actions in the Sales Orders for Order Hub REST service	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.

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

25C

Apply Hold and Release Hold actions in the Sales Orders for Order Hub REST service

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.

Use Only Supported Public View Objects in Your Order Management Extensions

Before update 24C, if you used a public view object (PVO) in an order management extension to get data from an Oracle application, then Oracle Order Management didn't look to see whether it supported that PVO when you validated your extension.

Starting with update 24C, Order Management makes sure it supports that PVO when you validate your extension. You must use only the PVOs that Oracle supports. For a list of supported PVOs, see Public View Objects in Oracle Applications Cloud (Document ID 2386411.1) on My Oracle Support. For additional details, see Guidelines for Using Extensions to Get Data from Oracle Applications.

Changes to Pricing Algorithms

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

Modified Algorithms

Pricing Process	Algorithm Name	Description of Change
Price Sales Transaction	Apply Pricing Terms	Updated algorithm to support simple and tiered promotional adjustments for sales orders.
Price Sales Transaction	Set Initial Values	Updated algorithm to support simple and tiered promotional adjustments for sales orders.
Price Sales Transaction	Calculate Pricing Charges	Updated algorithm to support simple and tiered promotional adjustments for sales orders.
Price Sales Transaction	Calculate Covered Item Charges	Updated algorithm to fix a Groovy syntax issue

New Algorithm

Pricing Process	Algorithm Name	Description
Price Sales Transaction	Apply Promotions	Applies simple and tiered promotional adjustments to sales orders.

In addition, refer to the topic Promote Pricing Algorithms into the Current Release in Oracle Fusion Cloud SCM: Administering Pricing on the Oracle Help Center. Oracle recommends that you review and promote algorithms in every quarterly update.

Changes to File-Based Data Import (FBDI) Templates

Some Supply Chain Planning FBDI templates have changed in this update. For details of the specific changes, refer to the Instructions tab of these FBDI templates:

Work Order Supplies (ScpWorkOrderSuppliesImportTemplate)
Routings (ScpRoutingsImportTemplate)

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.

Changes to Hold Codes

Starting in update 24C, to avoid problems when processing holds on sales orders, Oracle will not allow you to include a comma ( , ) or an apostrophe ( ' ) in the Code attribute when you set up new holds in the Setup and Maintenance work area. If you currently have a comma or an apostrophe in the Code attribute of a hold code in your implementation, then you can’t apply that hold to sales orders, and you must end date that hold code to avoid errors. Create a new hold without including a comma or apostrophe in the Code attribute. For details, see Use Holds to Stop Orchestration Processes.

Changes to Applying Holds on Sales Orders

Starting in update 24B, Oracle has improved performance and reliability for placing holds on sales orders. Use these guidelines to make sure your holds work successfully. The recommendations in the guidelines will become requirements for all customers in a future update, so you should adopt these recommendations immediately.

Guidelines

If you apply a hold on a change order, then we recommend you apply it only after you receive the Compensation Completed event for the change order from Order Management. Order Management won't hold any task that it's currently compensating. For background, see Overview of Managing Change That Happens During Order Fulfillment.

Order Management won't process a hold request or release a hold request on a sales order or order line that's in error recovery. You must fix the error, then retry the hold.

If a hold request fails, and if the response from the hold request contains the FOM-4515574 error code, then make sure:

You aren't currently updating the order line.
The orchestration process is currently on a wait step and it isn't attempting to process the line.
The order line isn't in an error status.

Use an Extension or REST API

You can use an order management extension or REST API to apply your hold.

If You Apply the Hold	Then
Immediately after you create a new sales order, and then submit it.	Use an Order Management Extension. For more, see Use Order Management Extensions to Apply Holds.
Immediately after you revise a sales order, and then submit it.	Use REST API. For more, see Use REST API to Apply and Release Holds.

Use Your Own Task Type

If you use your own task type:

You must use a wait step. For more, see Guidelines for Setting Up Holds on Sales Orders.

Apply the hold only after you send an immediate response, and then wait for at least two minutes. For more, see Overview of Connecting Order Management to Your Fulfillment System.

Examine the response and make sure it's successful. If the response fails, then resend it.

For more information, see Use Your Own Task Type to Apply Holds.

Make Sure Your Scheduled Dates Are Correct

If you use the Sales Orders for Order Hub REST API to create or revise a sales order, then follow these guidelines:

If you set the Override Schedule attribute to Yes on the order line, then make sure you include a value in the Scheduled Ship Date attribute or the Scheduled Arrival Date attribute on that line.

If you specify a value for the Scheduled Ship Date attribute and the Scheduled Arrival Date attribute, then make sure the value that you specify in the Scheduled Ship Date attribute doesn’t happen after the Scheduled Arrival Date.

Make sure:

You apply these guidelines on each order line that isn't yet shipped, is fulfilled, delivered, closed, cancelled, or has started billing.
Your order management extensions meet the guidelines.
The import payload that you use to create or revise each sales order meets the guidelines.
You meet the guidelines before Update 25A.

Starting in update 25A, if you use the Sales Orders for Order Hub REST API to submit a new sales order or revise an existing one, and if one or more of the order's lines don't meet the guidelines, then you'll receive an error and Order Management won't submit the order. These validations will be implemented in Order Management 25A to make sure that the scheduled dates on the order lines are consistent with each other.