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.

Keep Contract Dates Accurate

Before Update 25B, if you set the Coverage Start Date order management parameter to Delivery Date, then Order Management set the coverage's contract start date to the delivery date. However, if Order Management split the line during fulfillment, then it might not have set the contract start date to the delivery date on the split lines. Starting with Update 25B, Order Management sets the contract start date to the delivery date on the split lines. 

Before Update 25B, Order Management recalculated the contract start date and contract end date on closed or cancelled coverage lines. Starting with Update 25B, Order Management no longer recalculates these dates on closed or cancelled coverage lines. 

Oracle reference 32705728

Get Accurate Delivery Dates on Split Lines

Before Update 25B, if Order Management split an order line into two lines during fulfillment because there wasn't enough supply to meet the line's demand, then it set the actual delivery date to the latest date even though it delivered at least some of the quantity on time. For example, assume that:

  1. You used the SAC_SYSTEM_EVENT_POD_PAUSE event on a pause step in your orchestration process.
  2. You submitted a sales order with a quantity 10. You only had 4 in inventory, so Order Management split the line into line 1-1 with a quantity of 4 and line 1-2 with a quantity of 6.
  3. Order Management shipped line 1-1 and moved it to Awaiting Billing with an actual delivery date of 04/01/2025.
  4. Order Management paused line 1-2 and put it on back order.
  5. Supply became available on 04/15/2025, so Order Management shipped line 1-2 and moved it to Awaiting Billing with an actual delivery date of 04/15/2025.
  6. Order Management also updated line 1-1's actual delivery date to 04/15/2025.

Starting with Update 25B, Order Management won't update line 1-1's actual delivery date to line 1-2's delivery date. You also no longer have to use the SAC_SYSTEM_EVENT_POD_PAUSE event to update the fulfillment date. You can use some other event, such as SAC_TYPE_TIMER. This is most useful when you need to set the completion date to the system date.

Oracle reference 32705728

Get Accurate Contract End Dates on Configuration Models

Before Update 25B, if your configuration model had more than one coverage for a covered line, and if the coverage duration across lines was different, then Order Management applied the same duration to all lines. For example, assume that you had these order lines for an assemble-to-order model:

  • Line 1 had a 1 month coverage.
  • Line 2 had a 2 month coverage.

If you set up Order Management to start coverage on the delivery date, and if the actual delivery date was April 1, then Order Management set the contract end date to May 1 on lines 1 and 2.

Starting with Update 25B, Order Management will set the contract end date to May 1 on line 1 and to June 1 on line 2.

Oracle reference 32705728

Don't Reconfigure Configured Items That Were Split

Before Update 25B, if you had a configured item that was already split and you reconfigured it while revising the sales order, then you might have experienced an unexpected change in that item and in other configurations that were part of the same split.

Starting with Update 25B, if a configured item is already split, then the Order Management work area won't display the pencil icon so you can't edit it. If you attempt to import it, you will encounter an error.

Oracle reference: 36781550

Remove Empty Sales Orders from Interface Tables

 Before Update 25B, if you uploaded empty sales orders into the order interface table, then you couldn't use the Delete Orders from Interface Tables scheduled process to delete them. An empty sales order doesn't have any data in the order header or order lines. A large quantity of empty sales orders in the table might have affected performance.

 Starting with Update 25B, The Delete Orders from Interface Tables scheduled process will delete empty sales orders every time you run it. To maintain optimal performance, the scheduled process will delete no more than 10,000 orders each time you run it.

 Oracle reference: 37346880

Steps to Enable

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