Items - Planning (cprpd1100m000)

This level is intended for the planning of product families. Example: a manufacturer of bicycles has a family ‘bicycles’ on level 1, on level 2 he models the sub-families Woman’s bikes, Men’s bikes and Children’s bikes. On level 3 the real items are defined.

Enterprise Planning cannot handle BOM explosion for items that are defined on different levels. You are advised to model the plan items of plan item type Item on the lowest plan level.

This field determines the kind of supply order to be generated – planned purchase, planned production or planned distribution orders.

The warehouse where the planned orders are generated for. The default value for this field is retrieved from the general item data.

In many sessions, you can use the planner ID to make selections of items, orders, and signals. In many business cases, the planners are responsible for specific items or groups of items.

If this check box is selected, you can maintain a master plan for the item. An item’s master plan is central to the master-based planning method. However, a master plan is also useful for the order-based planning method, although not required.

This field displays the sum of the item’s safety stock for all warehouses in the cluster. You define the safety stock for each warehouse in the Warehouse - Item (whwmd2510m000) session.

If the Use Item Ordering Data check box is selected in the Warehouse - Item (whwmd2510m000) session, LN retrieves the safety stock value from the ordering data in the Items - Ordering (tcibd2500m000) session. If multiple warehouses refer to ordering data, LN adds this central safety stock only once to the safety stock of the cluster.

The time fence defines the horizon where Enterprise Planning is not allowed to generate new supply orders. The time fence is meant to freeze the planning on the short term to prevent from creating nervousness in the planning schedule and the production schedule on the shop floor. It is recommended to make the time fence equal to the lead time of the item.

Usually, orders that are due in the near future – before the time fence – have already been released to the execution level, because the start date for processing has been reached.

The released orders are probably also scheduled already on the shop floor, so stability of the plan within this time fence is important. You can express the time fence in working days or working hours. The time fence is calculated from the current date. Note that a value of 0 also has effect. That time fence will prevent Enterprise Planning to plan orders in the past.

Determines how far Enterprise Planning looks forward in time when planning supply and demand. The planning horizon applies to both order planning and master planning.

Master planning can only be executed after the order planning horizon.

Therefore, when the planning horizon is equal to the order planning, no plan but only orders can be generated. After the planning horizon, nothing exists from a planning perspective. No transactions are considered and no plans or orders are generated.

The time between the order’s start time and finish time.

LN uses the order lead time for order generation in order to determine the planned order start date outside the fixed lead time horizon.

If the order’s source is purchase, Enterprise Planning retrieves the lead time for purchase orders. The purchase order lead time is the supply time defined in item purchase data.

If the order’s source is production, Enterprise Planning retrieves the lead time for production orders. The order lead time of orders for distribution plan items is zero.

The production order lead time is retrieved from the item production data.