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.

Use Order Management Extensions to Assign Orchestration Processes

Starting with Update 22C, to improve performance and reduce processing time, you could specify the orchestration process name when you imported an order through REST API. You could provide the orchestration process name in the REST API payload or you could specify it in an order management extension.

Starting with Update 24C, you can now use this extension to assign the orchestration process to an order line that you create in the Order Management work area or that you import through a web service. Use the OrchestrationProcessName attribute in your extension to specify the orchestration process name on the order line, and use the On-Save or the On Start of Submission Request extension point. For example:

line.setAttribute("OrchestrationProcessName","ManualSchedulingProcess");

For details, see Overview of Creating Order Management Extensions.

Oracle reference: 35963368

Don't Register Connectors That Reference Oracle Internal Web Services

Before Update 24C, if you registered a connector that referenced an Oracle internal web service, then you might have encountered runtime errors.

Starting with Update 24C, the Manage External Interface Web Service Details page prevents you from registering a connector that references an Oracle internal web service. For details, see Guidelines for Setting Up Your Integration.

Oracle reference: 36427720

Set the Charge Rollup Flag When You Import Manual Price Adjustments

Before Update 24C, if you used REST API or file based data import (FBDI) with REST API to import a manual price adjustment into Oracle Order Management, and if your import didn't include a value for the charge rollup flag, then you might have encountered a pricing error during the import.

Starting with Update 24C, if you don't include a value for the rollup flag, then Order Management will set it to N. Note that you set this value in the ChargeRollupFlag attribute on the manualPriceAdjustments resource in REST API, or on the Charge Rollup Flag attribute on the DOO_ORDER_MANUAL_PRICE_ADJ_INT worksheet in FBDI. For background, see Overview of Importing Orders Into Order Management.

Oracle reference: 36129255

Steps to Enable

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