| Items - Planning Defaults (cprpd1110m000) |  |
| Use this session to define defaults for combinations of item type and item group to make it easier to define new plan items. This information is used when you enter a new item in the Items - Planning (cprpd1100m000) session.
Fields | Description
Item Group | Group of items with similar characteristics. Each item belongs to a particular item group. The item group is used in combination with the item type to set up item defaults.
Item Type | A classification of items used to identify if the item is, for example, a purchased item, a manufactured item, or an equipment item. Depending on the item's type, certain functions will only apply to that item.
Plan Level | The level within a hierarchical planning structure. When you plan on a higher plan level, plans are general and less detailed. Example Plan level 1 is the highest plan level; the higher the number, the lower the plan level. Related topics Plan levels and product families
Planner | The employee or department responsible for planning the production, purchase and distribution of items. The planner takes into account the inventory levels, availability of materials, and capacities of resources, and reacts on signals such as rescheduling messages that ERP LN generates. If this field is empty, no planner in particular is responsible for this plan item.
Default Warehouse | The warehouse from and to which the item is normally delivered. Allowed values For a non-clustered item this must be a warehouse in the item's logistical site. The warehouse of a clustered item must belong to the item's cluster.
Default Supply Source | In this field, you must select one of the following options from the pull-down menu to specify the Default Supply Source.
Time Fence | The date until which an item's supply plan and planned orders are frozen. The time fence is expressed as a number of working days or working hours from the date you carry out the simulation. As a rule, Enterprise Planning does not regenerate the supply plan or the planned orders within the time fence. However, you can overrule this behaviour when you run a master-plan simulation or order simulation. The time fence is meant to prevent: Disturbance of orders that have already started (at the shop-floor level). Generation of planned orders with start dates in the past (that is, orders that are late). Usually, the lead time of an item's production process is a reasonable value for the time fence. Related topics Horizons and time fences Simulated time period (RRP run)
Time Fence | Select Hours or Days as the time unit in which you want to express the time fence. If you select Hours, ERP LN sets the time fence by taking into account the workable hours, starting from the time point on which ERP LN generates the order planning, and by adding up the value you define in the Time Fence field. Suppose you set the time fence to 7 hours, and the working hours for every day of the week are from 8:00 am to 17:00 pm. If ERP LN generates the order planning on Wednesday, 13:00 pm, it sets the time fence to Thursday, 11:00 am.
Forecast Time Fence | The date up until which Enterprise Planning ignores the demand forecast when generating master plans and planned orders. In the first few days after the current date, ERP LN expects to receive no more sales orders than the actual sales orders that you already received. This field contains the default value for the Forecast Time Fence field in the Items - Planning (cprpd1100m000) session. Related topics Forecast Consumption with an Item Master Plan
Order Horizon | The time period for which Enterprise Planning uses order-based planning to plan supply. The order horizon is expressed as a number of working days from the date you carry out the simulation. If the order horizon is zero, Enterprise Planning does not use order-based planning for the item involved. To calculate the order horizon, ERP LN uses the calendar that you specified for the enterprise unit of the default warehouse to which the plan item belongs. If you did not specify an enterprise unit for the default warehouse of the plan item, Enterprise Planning uses the company calendar to calculate the order horizon. Note ERP LN moves the order horizon towards the end of the plan period) in which it falls, because Enterprise Planning must know whether a plan period falls within the order horizon. Related topics Horizons and time fences
Fixed Delivery | The fixed-delivery code for the plan item involved. Note If this field is empty, fixed delivery is not used for the plan item involved.
Planning Horizon | The time period for which ERP LN maintains planning data for an item. The planning horizon is expressed as a number of working days from the date you carry out the simulation. Enterprise Planning does not generate supply plans or planned orders beyond an item's planning horizon. To calculate the planning horizon, Enterprise Planning uses the calendar that you specified for the enterprise unit of the default warehouse to which the plan item belongs. Note Enterprise Planning moves the planning horizon to the end of the plan period in which it falls. Related topics Horizons and time fences
Safety Time | The safety time defined in the Items - Ordering (tcibd2500m000) details session. The safety time is expressed in days or in hours.
Order Lead Time | The plan item's default supply source is Production/Purchase. Depending on the Effectivity Date of the item, the Actual Source can be Production or Purchase. If the plan item's Actual Source is Production, then the order lead time defined in the Items - Production (tiipd0101m000) session is displayed in this field. This lead time is used for planned production orders within the fixed lead-time horizon. If the plan item's Actual Source is Purchase, then the supply time defined in the Items - Purchase (tdipu0101m000) session is displayed in this field. This lead time is used for planned purchase orders for which no particular supplier can be found. The order lead time is expressed in days or in hours.
Maintain Master Plan | If this check box is selected, an item master plan is maintained for the item. Note If this check box is selected, you can use master planning next to order planning to plan supply. If this check box is cleared, master-plan functionality is not available. In this case, order planning is the only available planning system for this item. Only maintain a master plan for an item if you need specific master-plan functionality, because it can decrease system performance. Related topics To use master plans
Dependent Demand Forecast | If this check box is selected, the calculation of the demand forecast is based on the historical demand data of both the dependent demand and the independent demand. If this check box is cleared, the calculation and consumption of the demand forecast is based on the independent demand only. If the calculation of the demand forecast takes the dependent demand into account, the forecast is also consumed by the dependent demand. Related topics To compute the demand forecast Forecast Consumption with an Item Master Plan
Priority | Specify the appropriate level of priority if you selected the Constraint check box. Enterprise Planning takes into account the priority of a plan item if you use the workload control as master-planning engine, and you selected Yes or Only in the Consider Item Priority field of the Work Load Control Parameters (cpwlc2101m000) session. Related topics Workload control, to compute planning priorities
Extra Lead Time | Time reserved for extra activities that are necessary to fully complete a planned order. Enterprise Planning treats the extra lead time in the same way as the safety time: the order must be delivered earlier based on the extra lead time. The extra lead time is expressed in days or in hours.
Extra Lead Time | Select Hours or Days from the pull-down menu as the default quantity to specify the Extra Lead Time.
Start of Fixed Lead-Time Horizon | The time period for which Enterprise Planning uses a fixed lead time to plan orders. Planning with a fixed lead time is faster than planning on the basis of routing data, but the results are less precise. The start date of the fixed lead-time horizon is defined in the plan-item settings. The end date coincides with the end of the order horizon. Before the fixed lead-time horizon, Enterprise Planning plans on the basis of routing data. Within the fixed lead-time horizon, Enterprise Planning plans using a fixed lead time. The fixed lead time is the sum of: order lead time extra lead time The fixed lead-time horizon is defined in working days. Related topics Order planning, an overview
Central Multi Site Planning | If this check box is selected, the item can be planned in a central multisite planning run. If you clear the Multisite Planning check box in the EP Parameters (cprpd0100m000) session, this check box is not available. Related topics Multisite planning
Production Plan | Select one of the following update options from the pull-down list.
Constraint | If this check box is selected, the availability of the plan item is a constraint in the planning. This field is only used in the Workload Control master planning method. Note You can also select the Constraint check box for clustered items to plan them with the Workload Control master planning method. Note that if the plan item involved is present in more than one cluster, you can only have a production plan in one cluster, because the warehouse specified in the BOM/BCM determines from which warehouse ERP Enterprise Planning retrieves the components for the plan item involved. For a production plan for item X in cluster 1 and a production plan for item X in cluster 2, ERP LN uses the same BCM warehouse: either in cluster 1 or in cluster 2. Related topics Workload control Workload control, to plan against constraints
Purchase Plan | Select one of the following update options on the pull-down menu.
Inventory Plan | Select one of the following update options on the pull-down menu.
Demand Forecast | Select one of the following update options from the pull-down list.
Forecast-Based Generation Method | If this check box is selected, the inventory plan is generated on the basis of the expected demand of the plan item during a certain forecast horizon. If this check box is cleared, the inventory plan is generated on the basis of the safety stock level and the seasonal pattern. Related topics Inventory planning in Enterprise Planning
Forecast Horizon | The number of days into the future on which the calculation of the inventory plan is based. The forecast horizon is expressed as a number of calendar days. The forecast-based calculation of the inventory plan is based on the following principle: The inventory plan must be equal to the expected demand during a certain forecast horizon. Example If the forecast horizon is 10 days, ERP LN aims at an inventory level for each plan period that is sufficient to cover the demand for the next 10 days. You can only access this field if the Forecast-Based Generation Method check box is selected. Related topics Inventory planning in Enterprise Planning
Master Plan Unit | The plan unit for master planning. With a master plan unit, you can choose a master planning engine for an item. Note You do not have to enter a plan unit in this field in the following cases: The item is planned with the infinite planning (not taken any constraints into account). The item does not have a master plan (the Maintain Master Plan check box is cleared). All supply is planned by order planning (the order horizon has the same length as the planning horizon). No production plan is generated (in other words, the Production Plan field has the value (Dis)aggregate Related topics Plan units in Enterprise Planning Rules for defining plan units
Critical in CTP | A plan item that is critical in CTP must be checked during a component CTP check for a higher level item in the bill of critical materials. A resource that is critical in CTP must be checked during a capacity CTP check for a plan item, if this resource is included in the plan item's bill of critical capacities. Note The performance (speed) of the component CTP check is greatly influenced by the number of components that are checked. The best approach is to have only the most important components checked. Related topics Capable-to-promise, an overview Component CTP
Online ATP Update | If this check box is selected, ERP LN updates the ATP for a plan item online if a planned or actual inventory transaction is recorded for the plan item. ERP LN updates the ATP over the entire planning horizon, but only in the actual scenario. Note Online ATP updates require processing power and therefore performance. You must only use online ATP updates for: Items for which the CTP is checked online Items for which the CTP is used during distribution planning Business processes that require up-to-date ATP figures You can select this check box only if the Maintain Master Plan check box is selected. Note If you use ATP functionality for an item that has no master plan, no online ATP updates are necessary. In this case, the ATP is always computed online. Related topics Online ATP update CTP Checking Procedure
Component CTP | If this check box is selected, a component CTP check will be carried out for this item, if the CTP of this item is checked, and the requested quantity of the item cannot be covered by the available inventory. Related topics Capable-to-promise, an overview Component CTP
Channel ATP | If this check box is selected, a channel ATP check is carried out in addition to other CTP checks. Related topics Channel ATP Capable-to-promise, an overview
Capacity CTP | If this check box is selected, a capacity CTP check will be carried out for this item, if the CTP of this item is checked and the requested quantity of the item cannot be covered by the available inventory. Related topics Capable-to-promise, an overview Component CTP
CTP Horizon | The number of working days from the current moment, during which ERP LN does not perform CTP checks. The CTP time fence must be smaller than the ATP/CTP horizon. During the period of the CTP time fence, CTP is considered to be zero. Related topics Capable-to-promise, an overview Horizons and time fences
Family CTP | If this check box is selected, a family CTP check is carried out for this item, if the CTP of this item is checked. Related topics Capable-to-promise, an overview Family CTP
Family Site | The logistic company in which an item family has been defined. The family site makes it possible to redirect CTP checks to a central logistic company. When a customer order is received, the CTP is checked at the family level in the central site. Example A large manufacturer of sports articles produces baseball bats in several states. A central master plan is maintained at headquarters (the central site). Each site has the bat defined as an item, and aggregation relationships have been set up to a product family of baseball bats at the central site. Allowed values The site must have been defined in the current company. Related topics Capable-to-promise, an overview
Family Item | The family item denotes the item to which the CTP check can be redirected. Allowed values The item must have been defined in the family site. The family item can be an item that you defined in another logistical site. Related topics Capable-to-promise, an overview Family CTP
Start of Family CTP Horizon | The time period for which ERP LN performs the capable-to-promise (CTP) check for an item on a higher product-family level, instead of the level of the item itself. The start date of the family CTP horizon is defined in the plan-item settings. The end date coincides with the CTP time fence. The application of family CTP depends on the plan period in which the delivery date of a customer order falls: If the plan period falls before the family CTP horizon, ERP LN checks the CTP of the item itself. If the plan period falls within the family CTP horizon, ERP LN checks the CTP on a higher product-family level. Related topics Capable-to-promise, an overview Family CTP
Use Time Fence | Select or clear the Use Time Fence check box to indicate whether or not you want to use the specified time fence to plan an individual item. If this check box is selected, Enterprise Planning uses the time fence according to the setting of the Generate Within Time Fence in the Generate Order Planning (cprrp1210m000) session to plan orders for an individual item. For example, when you select zero as time fence and you have a sales demand for yesterday, the planned finish date of the planned order is today, because Enterprise Planning cannot plan in the past. If this check box is cleared, Enterprise Planning ignores the time fence you defined for the current scenario. In this way you can overrule the setting of the Generate Within Time Fence check box in the Generate Order Planning (cprrp1210m000) session. If you clear the Generate Within Time Fence check box in the Generate Order Planning (cprrp1210m000) session, Enterprise Planning plans from the time fence for those plan items for which you select the Use Time Fence check box, and within the time fence for items for which the Use Time Fence check box is cleared. In the last case, Enterprise Planning can plan in the past (no time fence). For example, you have a sales demand for yesterday and you disable the time fence field. Enterprise Planning plans the finish date of the planned order for yesterday, because Enterprise Planning can plan in the past in that situation.