Net-change simulations

A planning run or simulation in Enterprise Planning can be carried out in two modes:

  • Regenerative
  • Net change

This applies to master planning as well as order planning.

Regenerative planning run

In a regenerative simulation, the planned supply of each plan item is recomputed, regardless of whether the planning data has changed since the last run or not.

A regenerative simulation can take many hours.

Net-change planning run

In a net-change planning run, the master plan or planned orders are only regenerated for plan items for which the planning data has changed since the previous calculation, and for plan items that are affected by such changes.

In general, a net-change run takes less time than a regenerative run.

LN takes two types of changes into account:

  • Changes in the item structure of an item, such as the bill of material (BOM).
  • Changes in the inventory transactions recorded for an item, such as inventory movements related to sales orders and purchase orders.
Net-change date

The Net Change check box in the Items - Planning (cprpd1100m000) session indicates whether a plan item changed after the previous planning run. LN records the earliest of these changes, the net-change date, in the Net Change Date field.

During a simulation, LN resets the plan item's net-change status.

Note

LN maintains a single net-change date for both master planning and order planning.

Net-change and clustered items

If a particular change is related to a particular cluster by means of the warehouse, LN marks the related clustered item as changed.

If a change is not related to a cluster, LN marks all plan items for the item as changed.

Example

Suppose the following events occurred:

  • On May 1, you perform a full regenerative planning run.

    LN resets the net-change indicators of all planned items.

  • On May 2, you define a change in the BOM of item X. The BOM change is effective on June 15.

    LN marks item X as changed for all clusters and sets the net-change date to June 15.

  • On May 3, you receive a new sales order for 500 piece of item X, to be delivered on June 20.

    Item X's net-change date remains June 15, because the BOM change is effective earlier than the sales order.

  • On May 4, a sales order for item X is cancelled. The planned delivery date for that sales order was May 30. The sales order was to be delivered from a warehouse in cluster JP.

    LN sets plan item JP X's net-change date to May 30. Item X in other clusters does not change.

To perform a net-change planning run

You can perform net-change planning in a master-planning run and in an order-planning run:

  • Master planning
    To perform a net-change master-planning run, select the Net Change Run check box in the Generate Master Planning (cprmp1202m000) session.
  • Order planning
    To perform a net-change order-planning run, select the Run a Net Change Planning check box in the Generate Order Planning (cprrp1210m000) session or the Generate Order Planning (Item) (cprrp1220m000) session. The setting of the Reset Net Change in Time Fence check box influences the planning algorithm within the time fence. For more information, refer to Net-change date before time fence.
Note
  • You can perform a net-change run only in the actual scenario.
  • When the planning data is changed at the scenario level (for example, the plan-period definition), you must perform a regenerative planning run.
Pegging net change

Between two regenerative or net-change planning runs, you can perform multiple net-change updates of the pegging information. For more information, refer to Pegging for planned orders.

Related topics