Example of How Preventing An Order's Improvement Impacts Planning Results

Let's say you're planning three orders for the same item, sourced from the same organization. Let's chart out the sales order attributes that are relevant before and after planning. We will review two planning scenarios: in the first, the Pull-in Enabled value is Yes for all three orders, and in the second, we prevent one order from being considered for improvement.

This table depicts the attribute values relevant for planning.

Order Number	Requested Date	Requested Quantity	Scheduled Date	Pull-in Enabled
Order 1	01/04/2020	10	01/15/2020	Yes
Order 2	01/06/2020	4	01/15/2020	Yes
Order 3	01/12/2020	6	01/15/2020	Yes

Supply Availability Information

• 10 units on 01/11/2020

• 10 units on 01/15/2020

Key Settings for the Plan Run

• We select a simple demand priority rule REQDATE, which prioritizes demands by just by their requested date. It gives highest priority to the order with the earliest requested date.

• The Pull-in Enabled value is Yes for all three orders.

Planning Results When All Orders Are Considered for Improvement

The plan was run. Our table now also includes calculated priority values and planned dates.

Order Number	Calculated Priority	Requested Date	Requested Quantity	Scheduled Date	Planned Date	Pull-in Enabled
Order 1	10	01/04/2020	10	01/15/2020	01/11/2020	Yes
Order 2	20	01/06/2020	4	01/15/2020	01/15/2020	Yes
Order 3	30	01/12/2020	6	01/15/2020	01/15/2020	Yes

Orders are prioritized based on their requested date. You infer Order 1 has been improved beyond its scheduled date. This is because 10 units of supply were available on 01/11 to satisfy the request from Order 1. Another 10 units of supply were available on 01/15, of which 4 units can be allocated to Order 2 and 6 units to Order 3, as requested.

Now let's see what happens when the Pull-in Enabled value of Order 1 is changed to No.

Planning Results When One Order Isn't Considered for Improvement

The plan was run and Order 1 wasn't considered for improvement. Our table now displays new planned dates.

Order Number	Calculated Priority	Requested Date	Requested Quantity	Scheduled Date	Planned Date	Pull-in Enabled
Order 1	10	01/04/2020	10	01/15/2020	01/15/2020	No
Order 2	20	01/06/2020	4	01/15/2020	01/11/2020	Yes
Order 3	30	01/12/2020	6	01/15/2020	01/12/2020	Yes

You infer that the planned date of Order 1 is the same as its scheduled date. This is because it wasn't considered for improvement. The supply of 10 units available on 01/11 can now be used to fulfill the demand of Orders 2 and 3, for which 4 and 6 units were requested, and so their planned dates improve beyond their scheduled date. The 10 units of supply are available on 01/15, and this supply is used to fulfill Order 1.

Planning Results When Order Lines are Planned Earlier than Requested Date

Let’s say you have an arrival type order of 50 units with a request date of 01/11/2030 and another arrival type order of 50 units with a request date of 01/13/2030. As per the customer’s receiving calendar, customer works only on Thursdays.

Key Settings for the Plan Run

• We select a simple demand priority rule REQDATE, which prioritizes demands just by their requested date. It gives highest priority to the order with the earliest requested date.
• Transit time from ship-from organization to customer is 0.
• The Pull-in Enabled value is Yes for both orders.

The plan was run, the table displays new planned dates.

Order Number	Calculated Priority	Requested Date	Requested Quantity	Scheduled Date	Planned Date	Planned Arrival Date
Order 1	10	01/11/2030	50	01/17/2030	01/10/2030	01/10/2030
Order 2	20	01/13/2030	50	01/17/2030	01/10/2030	01/10/2030

You can see the planned date has been scheduled to the nearest Thursday (01/10/2030) to respect the customer’s receiving calendar and to avoid delay in fulfillment.

Here are few things to consider when Oracle Backlog Management schedules the planned date before the requested date:

• Planned ship date or planned arrival date can be overridden and rescheduled to a date before the requested date even if the earliest acceptable date isn't specified on the Backlog Analysis page.
• Backlog Management reschedules order closer to the requested date and doesn't expedite the orders closer to the earliest acceptable date when the earliest acceptable date is much earlier than the requested date.
• Earliest acceptable date won't be treated as a requested date, so orders won't be expedited and planned early as per the earliest acceptable date.
• On the Backlog Analysis page, a planned date may be on or before the requested date but will be as close as possible to the requested date, subject to constraints and the earliest acceptable date.
• There's no limit to how early the planned date can be relative to the requested date when an earliest acceptable date isn't specified. However, this doesn't mean that the Backlog Management will plan the order as early as possible.