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 | 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:
|
25D |
The replacements are:
|
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:
|
25D |
The replacements are:
|
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 |
Populate Charge Component Explanation Message |
Update |
Performance improvement to skip populate explanation message on tax charge components when CalculateTaxFlag is false. |
Price Sales Transaction |
Derive Price List |
Update |
Performance improvement to derive price lists. |
Price Sales Transaction |
Roll Up Errors To Root |
Update |
Performance improvement to skip populating error when there is no RootCoverageLineId and RootLineID |
Price Sales Transaction |
Apply Tiered Pricing |
Update |
Convert ParentEntityKeyColumn1 and ParentEntityKeyColumn2 of Promotion Term to Long before stamping them in to charge component. |
Price Sales Transaction |
Set Initial Values |
Update |
Changes to split the reference lines and their associated data. |
Price Sales Transaction |
Get Item Categories |
Update |
Changes to derive the item categories for the reference lines. |
Price Sales Transaction |
Process Free and Promotion Item Terms |
New |
This is a new algorithm to process the promotional item lines and their charges and charge components. |
Price Sales Transaction |
Apply Promotions |
Update |
Changes to process the free item promotional pricing terms and to use the Line.PriceAsOf to compare the effectivity on the promotions. |
Price Sales Transaction |
Apply Pricing Terms |
Update |
Changes to process the pricing terms to create the free item promotional lines. |
Price Sales Transaction |
Price Sales Transactions |
Update |
Changes to split and merge promotional item lines and their associated data as well as to merge back the reference lines and their associated data at the end of 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.
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.
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 AI Assist in Order Management
To use Generative AI features in Oracle Order Management, the Order Entry Specialist must be assigned a job role that includes the Use Generative AI (FOM_USE_GEN_AI_PRIV) privilege. If not, Order Management won't display the AI Assist button on any page.
Oracle modified the names of these properties in Oracle Visual Builder Studio to avoid confusion with AI functionality:
Property Name in Update 24D |
Property Name in Update 25A |
showChangeDetailsAISuggestionDrawer |
enableChangeDetailsSuggestionDrawer |
enableChangeEmailConfirmationAISuggestionPage |
enableChangeEmailConfirmationSuggestionPage |
enableSalesOrderAcknowledgementAISuggestionPage |
enableSalesOrderAcknowledgementSuggestionPage |
Only the names are changed. There are no changes to the application's behavior. If you used a 24D name, then you must change it to the 25A name.
In addition, these Visual Builder Studio properties are new in update 25A:
- enableChangeCommentsAIAssist
- enableChangeEmailConfirmationAIAssist
- enableSalesOrderAcknowledgementAIAssist
- enableReturnCommentsAIAssist
- enableReturnCommentsSuggestionDrawer
For details about these properties, see the topic about Visual Builder Studio in the attachment at Implement Oracle Order Management's New and Redesigned Pages (Doc ID 3048488.1).
Make Sure the Relationship Type is Contact
You must make sure you use the correct relationship type for the Contact attribute on the order header or line. For details, see the My Order Lines Get Stuck During Invoicing known issue for update 25A at Oracle Fusion Cloud SCM Known Issues and Maintenance Packs (Doc ID 1563075.1).
Cascade Values on Redesigned Pages
Before update 24D, if you modified an order line's attribute on one of Oracle Order Management's classic pages, then Order Management assumed that the entire line was overridden. For example, let's say that you modified the warehouse on the order line, and then sometime later, you modified the shipment priority on the order header. Order Management wouldn't cascade the shipment priority to the line because it assumed that the entire line was overridden.
Starting with update 24D, Order Management's redesigned pages in the Redwood experience will cascade the shipment priority because the redesigned page considers each individual attribute, not the entire line, when it determines whether to cascade. For details, go to Technical Reference for Oracle Order Management (Doc ID 2051639.1) on My Oracle Support, then download the Cascade Headers to Lines attachment.