Selected Order Management Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Order Management works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

Specify Orchestration Process Name on Order Lines

If you create or revise a sales order through REST API or through the redesigned page in the Order Management work area, and if you specify the orchestration process name on an order line, then you must specify the name on all lines in the order. If you revise the order and add new lines, then you must specify the name on all of the new lines or none of them.

Before update 25C, if you created a sales order, specified the orchestration process name on all lines, used REST API or the redesigned page to revise the order and add new lines but didn’t specify the orchestration process name on all the new lines, then you would get an error:

The request wasn’t successful because an order line is missing a value for the orchestration process. (FOM-4515547) Details: Make sure the Orchestration Process attribute contains a value on each line in the sales order, or is empty on all lines.

Starting with update 25C, you don’t have to specify the name on the new lines, but if you do specify it, then you must specify it on all new lines.

For example, assume that you import a revision that has 4 lines, and lines 3 and 4 are new. These imports will work:

Line 1, "ProcessNumber" : ShipOrderGenericProcess,
Line 2, "ProcessNumber" : ShipOrderGenericProcess,
Line 3, "ProcessNumber" : ReturnOrderGenericProcess,
Line 4, "ProcessNumber" : ReturnOrderGenericProcess,

Line 1, "ProcessNumber" : ShipOrderGenericProcess,
Line 2, "ProcessNumber" : ShipOrderGenericProcess,
Line 3, "ProcessNumber" : null,
Line 4, "ProcessNumber" : null,

Line 1, "ProcessNumber" : null,
Line 2, "ProcessNumber" : null,
Line 3, "ProcessNumber" : null,
Line 4, "ProcessNumber" : null,

Line 1, "ProcessNumber" : null,
Line 2, "ProcessNumber" : null,
Line 3, "ProcessNumber" : ReturnOrderGenericProcess,
Line 4, "ProcessNumber" : ReturnOrderGenericProcess,

These imports will fail:

Line 1, "ProcessNumber" : ShipOrderGenericProcess,
Line 2, "ProcessNumber" : ShipOrderGenericProcess,
Line 3, "ProcessNumber" : ReturnOrderGenericProcess,
Line 4, "ProcessNumber" : null,

Line 1, "ProcessNumber" : null,
Line 2, "ProcessNumber" : null,
Line 3, "ProcessNumber" : ReturnOrderGenericProcess,
Line 4, "ProcessNumber" : null,

Oracle reference: 37569288

Validate Duration Period During Import

Before update 25C, if you used REST API to import a sales order that had a subscription, and if you specified the contract start date, contract end date, service duration, and duration period, then the import was successful even if the duration period wasn't valid.

Starting with update 25C, Order Management will check to make sure the duration period is valid. If it isn't, the import will fail.

Oracle reference: 37594502

Steps to Enable

You don't need to do anything to enable this feature.