Editing of demand plans at aggregate levels uses the demand plan values to help calculate the distribution through the defined hierarchy. When demand plan values are 0, the system does not have a means to calculate the distribution. The current, and most accurate, means to overcome this is by going to each PCL that is 0 and entering a value to serve as the distribution basis.

We have had numerous requests by customers to allow editing of 0 demand plan values at aggregate levels easier. In light of these many requests, we have added this capability with the following rules:

• When entering a demand plan value at the aggregate level, if all PCL have 0 demand plans the edit will be distributed equally among the PCL's. For example, if the demand plan is 0 and a value of 1000 is entered in the period with one or more PCL's, each PCL will receive the same quantity plan each.
• The distribution to weeks will follow a time frame based distribution based on the number of days in the month.

Below, an entry of 1000 is entered in November.

Each node within the level and period being edited receives the same quantity of 333.33 as a monthly plan value.

The weekly bucketed view will have the 333.33 distributed based on the number of days per week within the month. In the example below, the last week of the month has a different quantity allocated because the week is split between two calendar months thus it has a proportional share of each months demand plan.

Distribution also takes into account discontinue dates of SKU's and applies the distribution in a manner that ensures the aggregate edits are distributed to accommodate the discontinue date while maintaining the overall edited value. In this case, of the two of the three nodes will receive a greater quantity of the edited value.

A new setting has been added to allow users to break their daily (or weekly) order requirements into smaller order increments.

The new setting is named "Order by batches." The setting is defaulted to "No." Changing to "Yes" breaks the periodic order requirement into multiple orders by the set batch size.

In the example below, the setting breaks the requirement of 6,000 units due on August 27 into 6 orders of 1,000 each.

This is also reflected in the planner action with each batch as its own order line.

The level loading logic has been enhanced to better support lock periods and has also been extended to dependent demand SKU's. Previously, level loading was only applied against independent demand SKU's.

As can be seen below, due to a lock period, there is a spike requirement on week of October 25th.

As a reminder, the level loading logic looks to maintain inventory at or above safety stock while not over driving inventory levels. At times there will be small spikes and dips within weeks as adjustments are auto-applied to replenishment quantities.

With the new logic, the order spike is removed and leveled with the preceding requirements.