| # Items - Planning (cprpd1100m000) To define plan items, use the Items - Planning (cprpd1100m000) session. The following fields in the Items - Planning (cprpd1100m000) session are relevant for the order planning.
Item planning data
Field | Description
--- | ---
Plan Item | The plan item code consists of first, the cluster code, then the project code, then the item code
Description | The description of the plan item is defined in the general item data.
Plan Item Type | The plan item type can be item or family. This type indicates the role the item plays in planning. For more information, refer to the next field.
Plan Level | 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.
Default Supply Source | Extends the item type as defined in the Items - General (tcibd0501m000)) session. The item type just distinguishes manufactured and purchased parts, while this source adds distribution to the scope of sources.
Actual Supply Source (display-only field) | This field determines the kind of supply order to be generated – planned purchase, planned production or planned distribution orders. If the default supply source is ‘Production/Purchase’, the item type from the General Item Data or the date-effective item type determines whether the source is Production or Purchase. The sourcing strategy can overrule the value of this field.
Default Warehouse | The warehouse where the planned orders are generated for. The default value for this field is retrieved from the general item data. You can specify one of the warehouses that belong to the same cluster as the item. You can find a warehouse’s cluster under Cluster Details in the Warehouses (tcemm1112m000) session.
Calendar of Default EU (display-only field) | If no specific work center calendar is found, LN uses the calendar of the warehouse’s enterprise unit to determine the correct calendar for the lead time calculations and determination of start and finish date of the order. This is only needed when no calendar can be found.
Planner | 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. The Planner field makes this responsibility visible to all the users. Planners can run the planning run (order generation) for their own items, view their own signals (exception messages and warnings) and set the tolerances. The Planner field is not used for authorization, it is just a selection mechanism.
Fixed Delivery Type |
Maintain Master Plan | 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. The following functionality is available if you select the Maintain Master Plan check box: Aggregation and disaggregation of data Inventory plan – to differentiate the required inventory level by plan period Forecast generation based on historic demand Record extra demand by plan period
Safety Stock (display-only field) | 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.
Time fence (on the Horizons tab) | 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.
Use Time Fence |
Forecast Time Fence |
Order Horizon | Determines the time frame in which planned orders are generated. The order horizon is expressed in working days and calculated from the current date.
Planning Horizon | 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.
Safety Time (display-only field) | A buffer between finish date of the planned order and the requirement date (for example, date of sales order). Either the plan item’s default warehouse in combination with the plan item or the plan item itself determines the safety time.
Order Lead Time (display-only field) | 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.
Extra Lead Time | Models a processing step outside the normal processing time (thus on purpose not between the start and finish date of the planned order). Time unit is working days.
Start of Fixed Lead Time Horizon |
Cumulative Order Lead Time (display-only field) |
Non-Critical COLT (display-only field) |
Online ATP Update (CTP tab) | Together with the Online ATP Update in EP check box in the Planning Parameters (cprpd0100m000) session, this field determines whether changes in goods flow (inventory, planned transactions) directly update the item master plan.