Reschedule Shipment of an Order Line When Back-to-Back Supply Arrives Early
You can now ship an item early when supply becomes available before the current scheduled date. You can recalculate an order line's scheduled ship date and arrival date when you move the supply's availability date to an earlier date.
For example, if you move a purchase order's promise date or a work order's completion date to a date that happens before the date that's currently scheduled, then Oracle Order Management can recalculate the order line's scheduled ship and scheduled arrival dates.
Realize these benefits:
- Reduce your inventory's carrying cost. Before this update you had to wait until the scheduled ship date to ship the item. Now you can get that item out the door early and reduce the amount of inventory you have to hold.
- Reduce scheduling error. You can now decide how you want to override the schedule after Order Management updates the scheduling attributes.
- Improve fulfillment accuracy and customer satisfaction. Improve fulfillment lead times when supply is ready to ship early. Customers love to receive their shipment early.
Use this feature in your back-to-back flow.
Assume your supplier agrees to deliver the item early for a preferred customer or for a high priority order and moves the purchase order's promised delivery date to earlier than the scheduled date. For another example, you place a higher production priority for a critical customer order, and that means the work order's completion date happens earlier than expected.
Before update 25D, Order Management didn't recalculate the scheduled ship date and scheduled arrival date on the order line when supply arrived early. Now, Order Management will get the recalculated scheduled dates from Global Order Promising and use them to update the order line's dates.
Let's look at an example:
- You set the item's post-processing lead time to 2 days and the pick-pack lead time to 1 day in the warehouse.
- You don't ship on Sunday.
- The transit time between your warehouse and the customer's ship-to location is 3 days.
You create a sales order on July 8 with a requested ship date of July 12. Promising returns a scheduled ship date of July 24, a scheduled arrival date of July 27, and recommends a purchase order. Your supplier promises to deliver the item on July 21 to your warehouse. Add 2 days for post-processing and 1 day for pick-pack, and you're ready to ship on July 24:
Requested Ship Date | Supply Date (PO Promised Delivery Date) | Post-Processing Lead Time | Pick-Pack Lead Time | Scheduled Ship Date | Scheduled Arrival Date |
---|---|---|---|---|---|
July 12 | July 21 | 2 | 1 | July 24 | July 27 |
Your customer requests an earlier delivery. You negotiate with the supplier and the supplier agrees to make the item available 7 days earlier than promised. The revised purchase order's delivery date is July 14. If you use this feature, then the order line will have the revised scheduled ship date and scheduled arrival date:
Requested Ship Date | Supply Date (PO Promised Delivery Date) | Post-Processing Lead Time | Pick-Pack Lead Time | Scheduled Ship Date | Scheduled Arrival Date |
---|---|---|---|---|---|
July 12 | July 14 | 2 | 1 | July 17 | July 20 |
Keep the Override Schedule's Original Value
You can also use the new Keep Override Schedule's Original Value order management parameter to specify how to set the order line's Override Schedule attribute after Order Management updates the scheduling attributes.
Various sources can result in updates on your scheduling attributes:
- Order Promising work area
- Oracle Backlog Management
- Update Scheduling Attributes REST API
- Changes in the supply date
Order Management sets the order line's Override Schedule attribute to Yes and processes the request every time it receives an update from one of these sources. This makes sure that Global Order Promising accepts the change on the scheduling attributes without rescheduling the entire order line.
However, the Override Schedule attribute remains as Yes and that might affect a subsequent revision. For example, if you revise the sales order and modify the quantity or the requested date, then Global Order Promising won't reschedule but will keep the same scheduled dates or warehouse without considering changes in demand.
If you set the Keep Override Schedule's Original Value parameter to Yes, then the Override Schedule attribute will revert to its original value after Order Management updates the scheduling attribute. If Override Schedule's original value was No, then Order Management will revert it back to No after it updates the scheduling attributes. If you then revise the quantity or requested date, then Promising will include that revision when it reschedules the order line. The parameter comes predefined as No, which preserves the current behavior of always setting the Override Schedule attribute to Yes after Order Management updates the scheduling attributes.
Assume you leave the parameter at its default No. The value of the Override Schedule attribute will remain as Yes after you update a scheduling attribute. Assume your order line has these values:
Scheduled Ship Date | Scheduled Arrival Date | Override Schedule |
---|---|---|
June 20 | June 25 | No |
The supplier moves the purchase order's promised delivery date to June 22. Order Management processes the update and sets the new scheduled dates:
Scheduled Ship Date | Scheduled Arrival Date | Override Schedule |
---|---|---|
June 22 | June 27 | Yes |
Order Management also sets the Override Schedule attribute to Yes while it does this update. Promising will return the same scheduled dates for any subsequent revision that you make even if you change the quantity or requested date, and even if those changes might have resulted in a new scheduled date.
Assume your supplier changes the supply date. If you set the Keep Override Schedule's Original Value parameter to Yes, then Order Management will reset the Override Schedule attribute to its original value of No after it processes the update. If you then revise the quantity or date, then Promising will consider that revision, and the order line will have these values:
Scheduled Ship Date | Scheduled Arrival Date | Override Schedule |
---|---|---|
June 22 | June 27 | No |
If you set Keep Override Schedule's Original Value to No, then Order Management will leave the Override Schedule attribute as Yes after it updates the scheduling attribute.
Steps to Enable
Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.
Offering: Order Management
If necessary, you can use the Manage Order Management Parameters task in the Setup and Maintenance work area to change the value of the Keep Override Schedule's Original Value parameter.
Tips And Considerations
- You can use this feature only with your back-to-back flows. You can't use it with drop shipments.
- Assess how recalculated scheduled dates will affect your downstream operations. You might need to modify your shipping to manage earlier shipments and warehouses and to manage reduced inventory.
- Recalculated scheduled dates don't consider the earliest acceptable date or latest acceptable date. If your customer insists on an earliest date, then you might not want to ship early.
- If you expect frequent changes in demand, then consider setting the Keep Override Schedule's Original Value parameter to Yes. For example, the order quantity frequently changes, you change the requested ship or requested arrival date, or you get frequent updates from Backlog Management or from your supplier.
- You must collect data regularly so Promising has the latest demand. This is particularly important for a pick-to-order configured item, kit, or order line that's part of a shipment set. Collect each time after you change the supply date for an order line that has a shipment set.
Key Resources
- Implementing Order Management
- Using Order Management
- Using Order Promising
- Using Supply Chain Orchestration
Access Requirements
No new access privileges have been introduced as part of this feature.