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.
Include User Defined Names for Currency Conversion Types When You Import Sales Orders
Before update 26A, you couldn't use the user defined name to identify a currency conversion type when you imported sales orders through the SalesOrdersforOrderHub or the SalesOrdersforOrderHubRequests REST API, or through the SourceSalesOrderImportTemplate.xlsm FBDI template.
Starting with update 26A, you can now include the user defined name in the UserConversionType attribute when you import through SalesOrdersforOrderHub or SalesOrdersforOrderHubRequests. You can include the user defined name in the User Currency Conversion Type attribute when you import through SourceSalesOrderImportTemplate.xlsm.
Oracle reference: 38027027
Keep Your Conversion Types, Conversion Rates, and Conversion Dates Accurate
Before update 26A, you might encounter:
- Incomplete currency details. If you set the conversion type to User, then Order Management didn't require you to provide the conversion rate and the conversion date.
- Incorrect data. If you changed the conversion type from User to another value, such as Corporate or Spot, then Order Management didn't delete the old conversion rate and conversion date.
- Inconsistent currency conversion and accounting. If you revised a sales order, then you could modify the conversion type, conversion rate, and conversion date.
Starting in update 26A:
- If you revise a sales order, and if that order has a conversion type, conversion rate, or conversion date, then you can't edit that type, rate, or date. Order Management applies this behavior in the Redwood work area, classic work area, and during import.
- If you change the conversion type from User to another value, then Order Management will automatically delete any values that are currently in the conversion rate and conversion date.
- If you set the conversion type to User, then you must include a value for the conversion rate and conversion date.
Not Valid
Before update 26A, Order Management allowed you to set the conversion type to Corporate, Spot, custom, or leave it empty, and set a value in:
- The conversion rate or conversion date
- The conversion rate and conversion date
Starting with update 26A, these combinations aren't valid.
Oracle reference 37096303
Make Sure Orchestration Process Can Process Returns
In update 26A, Order Management introduced the DOO_VALIDATE_CREATE_OUTBOUND_REQUEST processing constraint:
- If a return line specifies an orchestration process that doesn't process returns, then don't send the return line to shipping. Display a message instead.
It comes predefined as enabled.
| Validation Entity | Validation Rule Set | Record Set | Message |
|---|---|---|---|
| Create Shipment Service | Create Shipping Request Validation | Fulfillment Line Default Record Set | Assignment rule assigned fulfillment line where line's Category contains Return, but the orchestration process doesn't process returns. Assign it to one that processes returns. |
| Order Fulfillment Line | Return Line Specifies Orchestration Process That Ships | Fulfillment Line Default Record Set | Create an assignment rule to specify an orchestration process that processes returns. |
Oracle reference: 38506725
Steps to enable and configure
You don't need to do anything to enable this feature.