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 API Order Promises REST API	25C	Global Order Promises REST API	20D	No additional enhancements will be made to the Available Supplies and Order Promises REST services. The services will continue to work until they're removed in 25C, but you should move to the replacement Global Order Promises service at your earliest convenience. The Global Order Promises REST service 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 service, 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 API

Order Promises REST API

25C

Global Order Promises REST API

20D

No additional enhancements will be made to the Available Supplies and Order Promises REST services. The services will continue to work until they're removed in 25C, but you should move to the replacement Global Order Promises service at your earliest convenience. The Global Order Promises REST service 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 service, 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 use a public view object (PVO) in an order management extension to get data from an Oracle application, then Oracle Order Management doesn't look to see whether it supports that PVO when you validate your extension.

Starting with update 24C, Order Management will make sure it supports that PVO when you validate your extension. You must use only the PVOs that Oracle supports. To prepare for this change, you should use only supported PVOs in your extensions starting in update 24B.

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
Get Sales Pricing Strategy	Get Sales Pricing Strategy	Support Id to Value conversions for returning DefaultCurrencyName, PricingSegment, and PricingStrategyName.
Price Sales Transaction	Create Zero Charge	Updated algorithm to address rollup charges for subscription models termination flow.
Price Sales Transaction	Process Line Currency Conversion	Added mode to perform header currency conversion for prepriced tax-only case.
Price Sales Transaction	Calculate Tax Cost and Margin	Invoke process line currency conversion for prepriced tax-only case.
Price Sales Transaction	Apply Matrices	Enhanced to support item category-based price adjustments and category-based attribute discounting rules in matrices.
Price Sales Transaction	Aggregate Roll Up Charge Components	Enhanced to support item category-based price adjustments and category-based attribute discounting rules in matrices.

New Algorithm

Pricing Process	Algorithm Name	Description
Price Sales Transaction	Get Item Categories	Populates item categories data from PIM into the PriceRequest DataObject to support category based pricing.

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:

ATP Rules (ScpATPRulesImportTemplate)
Bill of Resources (ScpBillOfResourcesImportTemplate)
Purchase Order Shipments Receipt History (ScpPurchaseOrderRcvHistoryImportTemplate)

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 the Integration from Shipping and Receivables to Order Management

Starting with update 24B, the integration from Oracle Shipping and Oracle Receivables to Oracle Order Management now goes through an interface table. The Process Responses from Order Fulfillment scheduled process now comes predefined to automatically process data in the table. It runs one time every day with the Record Set parameter set to Process Records That Failed, and with the Task Type parameter set to one of these values:

Invoice
Shipment

One instance of the scheduled process runs for invoices and another instance runs for shipments. Both instances start at 00:00:00 AM UTC.

During any given day, Shipping confirms shipments and Receivables invoices sales orders. The Manage Shipment Interface scheduled process stores data in the interface table when Shipping confirms the shipment, and the Notify Feeder System of Receivables Transactions scheduled process stores data in the table when Receivables invoices the sales order.

Over time, a large number of failed records might accumulate in the table. These records might prevent fulfillment from moving order lines past the shipment step in your orchestration process when Shipping confirms the shipment, or past the invoice step when Receivables invoices the sales order. Failed records might also degrade performance when Process Responses from Order Fulfilment must process a lot of them simultaneously. Running the Process Responses from Order Fulfilment scheduled process one time each day helps to prevent these problems. You can modify how frequently it runs according to your daily volume and the time of day when you notice that records typically fail.

Changes to Hold Codes

Starting in update 24C, to avoid problems when processing holds, Oracle will update hold codes so you can't include a comma ( , ) or an apostrophe ( ' ) in the Code attribute. If you currently have a comma or an apostrophe in the Code attribute in your 24B implementation, then we recommend that you end date that hold code so it’s no longer available to apply on sales orders. Create a new hold that doesn't include a comma or apostrophe in the Code attribute. This change applies whether you import the hold code or define it in the Setup and Maintenance work area. 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.

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.

Operations to Be Deprecated

Oracle will deprecate the RequestHold operation and the ReleaseHold operation in the Receive Order Request SOAP service starting in update 24C. If you're currently using those operations, then we recommend that you start using the Apply Hold and Release Hold actions in the Sales Orders for Order Hub REST resource instead. 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.

New Order Management Parameter

Don't use the Cascade Order Header Values to Order Lines parameter in Oracle Order Management until further notice. This parameter is for future use.