| Items - Planning |  |
| Use this session to list plan items, and to maintain and modify the related settings. Click the Planning Defaults option on the Specific menu to zoom to the Items - Planning Defaults (cprpd1110m000) session. ERP LN automatically starts this session when you define an item in the Items - General (tcibd0501m000) session, set the Order System field in the Item - Ordering (tcibd2100s000) session to Planned, and save the item. Note If you have started this session by zooming, you can only find and select a record. Performance aspects The settings in this session could affect system performance and database growth. For more information, refer to Number of plan items. Related topics Plan items in Enterprise Planning Item definition in Enterprise Planning To use an overview session
Fields | Description
Plan Item
Plan Item | An item with the order system Planned. The production, distribution, or purchase of these items is planned in Enterprise Planning based on the forecast or the actual demand. You can plan these items by means of the following: Master-based planning, which is similar to master production scheduling techniques. Order-based planning, which is similar to material-requirements planning techniques. A combination of master-based planning and order-based planning. Plan items can be one of the following: An actual manufactured or purchased item. A product family. A basic model, that is, a defined product variant of a generic item. A group of similar plan items or families is called a product family. The items are aggregated to give a more general plan than the one devised for individual items. A code displayed by the item code's cluster segment shows that the plan item is a clustered item that is used for distribution planning. The plan items must be unique for all plan levels. Related topics Plan items in Enterprise Planning
General
Plan Item Text | If this check box is selected, a text is present.
General Data
Plan Item Type | The type of plan item. Note All plan items must first be defined as an item in Common, even if it concerns a plan item of type Family. Related topics Plan levels and product families To update goods-flow data
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
Default Supply Source | The default supply source of a plan item, which can be Production/Purchase or Distribution. ERP LN uses the value of the Default Supply Source field if it can find no valid sourcing strategy for the plan item. If you set the Default Supply Source field to Production/Purchase, ERP LN takes into account the date effective item type that you defined in the Date-Effective Item Data (tcibd0510m000) session. Related topics Sources of supply: production, purchase, or distribution
Actual Supply Source | The time-dependent supply source. The actual value depends on the date effectivity line of the current moment of the item type that you defined in the Date-Effective Item Data (tcibd0510m000) session. Related topics Date-effective item data
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.
Calendar of Default EU | The calendar of the enterprise unit that you specified in the session for the default warehouse. ERP LN uses the enterprise unit calendar for several planning aspects that are not related to a particular resource, business partner, or warehouse. ERP LN uses the enterprise unit calendar when a more specific calendar is not available. Related topics Calendars in Enterprise Planning
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.
Planner | The name of the planner that belongs to the code in the Planner field.
Fixed Delivery Type | The fixed-delivery code for this plan item. If the actual source corresponds with the supply source for which the fixed delivery code is valid, Enterprise Planning generates planned orders for the item. In this case, the finish date equals a fixed-delivery date. You can link a fixed-delivery types to a pattern in the Fixed Delivery Codes (cprpd2110m000) session. Note If this field is empty, fixed delivery is not used for this item. Related topics To define patterns
VMI Role | The function of this plan item in a vendor managed inventory (VMI) setup. This field determines what VMI-related actions ERP LN must perform during an order-based planning run. This field can have the following values: Customer You are the customer in a VMI-relationship. The supplier of this plan item also takes care of the supply planning. The order-based planning run can create a forecast that you send to the VMI supplier. Supplier You are the VMI supplier for the plan item. You perform the supply planning for this item on behalf of your customer. Possibly, the customer sends you a forecast of the item demand. Not Applicable This item is not involved in vendor-managed inventory that is planned by a supplier. Note Every time you run order-based planning, ERP LN reevaluates the VMI Role field. ERP LN takes the entire period between current date and the planning horizon into account. If at any time in that period an applicable terms and conditions agreement is found, the VMI Role field is set to Customer or Supplier, even if this terms and conditions agreement is not effective at the current date. In this way, ERP LN makes sure that the order-based planning run executes the VMI-functionality if it is needed. For information on the method ERP LN uses to evaluate this field, refer to To determine the VMI role. Related topics Supply planning by supplier To determine the VMI role
General Parameters
Maintain Master Plan | If this check box is selected, Enterprise Planning maintains an item master plan for the item. If this check box is selected, Enterprise Planning also maintains a channel master plan for every channel that you linked to the specified plan item in the Plan Item - Channels (cpdsp5100m000) session. A master plan allows the use of various functions, see: To use master plans. Note If an item master plan is maintained, you can still also use order-based planning. If this check box is cleared, the above-mentioned functions are not available. Order-based planning is the only available planning system for this item. You must only maintain a master plan for an item if you need the described functionality, because it can decrease ERP LN's performance. If the VMI Role field is Customer or Supplier, you cannot maintain an item master plan for this item. Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Maintain master plan. 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 dependent demand. Related topics To compute the demand forecast Forecast Consumption with an Item Master Plan
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
Exclude from Pegging | If this check box is selected, ERP LN generates no pegging information for this plan item. The generation of pegging information can have a negative effect on performance. Select this check box unless you really want to have the pegging information. Related topics Pegging for planned orders
Inventory
Inventory on Hand | The physical quantity of goods in one or more warehouses (including the inventory on hold). Related topics inventory on hold
Inventory on Hand | The unit in which ERP LN manages physical quantities of the item.
Safety Stock | The buffer inventory necessary to meet fluctuations in demand and delivery lead time. In general, safety stock is a quantity of inventory planned to be in inventory to protect against fluctuations in demand or supply. In the context of master production scheduling, safety stock is the additional inventory and capacity planned as protection against forecast errors and short-term changes in the backlog. Related topics To compute cumulative ATP
Safety Stock | The unit in which ERP LN manages physical quantities of the item.
Horizons
Time Fences
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 behavior 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. Note You can override the time fence for master-based planning by selecting the Generate Within Time Fence check box in the Generate Master Planning (cprmp1202m000) session. You can override the time fence for order-based planning by selecting the Generate Within Time Fence check box in the Generate Order Planning (cprrp1210m000) session. Note Although you can define a time fence for purchase schedule items, ERP LN does not take into account the Time Fence field. For the firm part of purchase schedules, ERP LN uses a frozen period. For more information about purchase schedules and time fences, see Purchase schedules and Enterprise Planning. Related topics Horizons and time fences Simulated time period (RRP run) Time fences in order planning and in master planning Purchase schedules and Enterprise Planning
Time Fence | Select Hours or Days as time unit for 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.
Time Fence | The date on which ERP LN sets the time fence. To find the correct date, ERP LN starts from the current date, and stops after the number of workdays that you defined in the Time Fence field.
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. Related topics Horizons and time fences Time fences in order planning and in master planning
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. The forecast time fence is expressed as a number of working days from the date you carry out the planning. Before the forecast time fence, Enterprise Planning only considers actual customer orders. Beyond the forecast time fence, total demand is a combination of actual orders and forecasts. A reasonable value for the forecast time fence is the minimum time period between the receipt of customer orders and the requested delivery dates. To calculate the forecast time fence, ERP LN uses the calendar that you specified for the enterprise unit of the plan item's default warehouse. 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 forecast time fence. Note In master planning, ERP LN ignores the demand forecast up to the end of the plan period in which the time fence falls. In order-based planning, ERP LN ignores the demand forecast up to the end of the day in which the time fence falls. The demand forecast is taken into account starting 0:00 hours (midnight) of the next day. In order-based planning, the demand forecast consists of special demand. Related topics Forecast Consumption with an Item Master Plan Time fences in order planning and in master planning
Date | The date on which ERP LN sets the forecast time fence. To find the correct date, ERP LN starts from the current date, and stops after the number of workdays that you defined in the Forecast Time Fence field.
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. ERP LN automatically updates the order horizon when you run the Check Horizons (cprpd1200m000) session, if the following conditions are met: The Automate Update Horizons check box is selected. The Update Method in the Check Horizons (cprpd1200m000) session is set to COLT + Horizons When Too Small, or to COLT + All Horizons. If you set the Update Method field in the Check Horizons (cprpd1200m000) session to COLT + Horizons When Too Small, ERP LN corrects the order horizon when it is too short to correctly create planned orders. If you set the Update Method field in the Check Horizons (cprpd1200m000) session to COLT + All Horizons, ERP LN corrects the order horizon, regardless of the value in the Minimum Order Horizon field. Related topics Horizons and time fences Cumulative order lead times and horizons
Date | The date on which ERP LN sets the order horizon. To find the correct date, ERP LN starts from the current date, and stops after the number of workdays that you defined in the Order Horizon field. ERP LN takes into account the actual calendar for the enterprise unit calendar of the item's warehouse and the default availability type that you defined in the EP Parameters (cprpd0100m000) session.
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. ERP LN automatically updates the planning horizon when you run the Check Horizons (cprpd1200m000) session, if the following conditions are met: The Automate Update Horizons check box is selected. The Update Method field in the Check Horizons (cprpd1200m000) session is set to COLT + Horizons When Too Small, or to COLT + All Horizons. If you set the Update Method field in the Check Horizons (cprpd1200m000) session to COLT + Horizons When Too Small, corrects the planning horizon when it is too short to correctly create an order plan. ERP LN If you set the Update Method field in the Check Horizons (cprpd1200m000) session to COLT + All Horizons, ERP LN corrects the planning horizon, regardless of the value in the Minimum Planning Horizon field. Related topics Horizons and time fences Cumulative order lead times and horizons
Date | The date on which ERP LN sets the planning horizon. To find the correct date, ERP LN starts from the current date, and stops after the number of workdays that you defined in the Planning Horizon field, which is comparable to the way that ERP LN finds the correct date of the order horizon.
Order Lead Times
Safety Time | The safety time defined in the Item - Ordering (tcibd2100s000) session. The safety time is expressed in hours or in days.
Order Lead Time | The plan item's default supply source is Production/Purchase. Depending on the Effectivity Date of the item, the Actual Supply Source can be Production or Purchase. If the plan item's Actual Supply 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 Supply 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.
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 | The time unit in which this lead time is expressed.
Start of Fixed Lead-Time Horizon (SFC) | The number of workdays after which the fixed lead-time horizon starts. Note The start of the fixed lead-time horizon is rounded to the end of a plan period. Effectively, this means that the fixed lead-time horizon starts at the next plan period. If the value of this field is greater than the order horizon, this effectively means that no fixed lead-time horizon is used. Important! If the Start of Fixed Lead-Time Horizon (SFC) field is zero, you cannot transfer the generated planned orders to the execution level, because Enterprise Planning links no routing operations to the planned order. You can use this setting only for simulations. Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Start of fixed lead-time horizon. Related topics Production lead-time calculation in Enterprise Planning Order planning, an overview
Date | The date on which ERP LN sets the start of the fixed lead-time horizon.
COLT
Cumulative Order Lead Time | The cumulative order lead time (COLT) for this plan item. ERP LN automatically updates the value of the Cumulative Order Lead Time field when you run the Check Horizons (cprpd1200m000) session, if you selected the Automate Update Horizons check box. Related topics Cumulative order lead times and horizons Lead times and horizons
Non-Critical COLT | The noncritical cumulative order lead time (noncritical COLT) for this plan item. ERP LN automatically updates the value of the Non-Critical COLT field when you run the Check Horizons (cprpd1200m000) session, if you selected the Automate Update Horizons check box. Related topics Cumulative order lead times and horizons Lead times and horizons
Minimum 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. ERP LN automatically updates the value of the Minimum Order Horizon field when you run the Check Horizons (cprpd1200m000) session, if you selected the Automate Update Horizons check box. Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Order horizon. Related topics Horizons and time fences Cumulative order lead times and horizons
Minimum 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. ERP LN automatically updates the value of the Minimum Planning Horizon field when you run the Check Horizons (cprpd1200m000) session, if you selected the Automate Update Horizons check box. Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Planning horizon. Related topics Horizons and time fences Cumulative order lead times and horizons
Automate Update Horizons | If this check box is selected, ERP LN automatically updates the order horizon and/or the planning horizon when you run the Check Horizons (cprpd1200m000) session. Related topics Lead times and horizons
Master Plan
Automatic Update
Production Plan | Select one of the four update modes. Related topics Possible Values
Purchase Plan | Select one of the four update modes. Related topics Possible Values
Inventory Plan | Select one of the four update modes. Related topics Possible Values
Demand Forecast | Select one of the four update modes. Related topics Possible Values
Planning
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 | 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
Date | The date to which ERP LN sets the forecast horizon.
Work Load Control
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 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
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 infinite planning (not taking 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 No Update or (Dis)aggregate. Related topics Plan units in Enterprise Planning Rules for defining plan units
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
CTP
CTP Parameters
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 Note If you use ATP functionality for an item that has no master plan, no online ATP updates are required. In this case, the ATP is always computed online. Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Online ATP update. Related topics Online ATP update CTP Checking Procedure
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, specifically the 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 CTP Checking Procedure
Component CTP | If this check box is selected, ERP LN can carry out component CTP checks for this item. Related topics Component CTP CTP Checking Procedure Capable-to-promise, an overview
Capacity CTP | If this check box is selected, ERP LN can carry out capacity CTP checks for this item. During an ATP check, ERP LN can check the availability of critical resource capacity for additional production. ERP LN only performs a CTP check if the sales order quantity or the quantity you entered in the ATP Handling (tdsls4899m000) session is higher than the item's ATP in the item master plan, and the required quantity cannot be fulfilled by the ATP alone. The choice of resource to check depends partly on the order horizon: If the requirement date is beyond the order horizon, ERP LN carries out the capacity CTP check using the item's Bill of Critical Capacities. If the requirement date is before the order horizon, ERP LN carries out the capacity CTP check using the item's routing. ERP LN checks the capacity of only the resources for which you selected the Critical in CTP check box in the Resource (cprpd2100m000) session. ERP LN cannot carry out capacity CTP checks if the resource has no resource master plan. If ERP LN checked a sales order for capacity CTP, and accepts and records the sales order in the Sales (SLS) module of Order Management, ERP LN carries out a capacity CTP reservation on the critical resources so that the resource capacity cannot be given away again. Related topics Capacity CTP Capacity CTP reservations To compute capacity CTP Capable-to-promise, an overview
Channel ATP | If this check box is selected, ERP LN can carry out channel ATP checks for this item. Related topics Channel ATP Channel ATP periods Capable-to-promise, an overview
CTP Time Fence | 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. ERP LN performs CTP checks between the end of the CTP time fence and the end of the ATP/CTP horizon. After the CTP horizon, ERP LN assumes that capacity and components are infinite. However, ERP LN does perform ATP checks between the current moment and the end of the CTP time fence and the end of the ATP/CTP horizon. Related topics Capable-to-promise, an overview Horizons and time fences
CTP Horizon | The date until which ERP LN performs ATP and CTP checks. The ATP horizon is expressed as a number of working days during which ERP LN can carry out ATP and CTP checks. Beyond the ATP/CTP horizon, ERP LN does not check ATP or CTP: all customer orders are accepted. After the ATP/CTP horizon, ERP LN assumes that capacity and components are infinite. Important! If you defined this plan item as a alternative material, the value of this field must be greater than the Alternative Materials Horizon in the Scenarios (cprpd4100m000) session. Otherwise, ERP LN erroneously assumes that the alternative material is infinitely available to cover for shortages of the standard material. Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to CTP horizon. Related topics CTP Checking Procedure Use-up materials and alternative materials in Enterprise Planning
Family CTP Parameters
Family Item CTP | If this check box is selected, ERP LN can carry out family CTP checks for this item. Related topics Capable-to-promise, an overview Family CTP
Family Site | The family site in which you defined the family item that ERP LN takes into account to perform a family ctp check. 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 number of workdays after which the family CTP horizon starts. Note The start of the family CTP horizon is rounded to the end of a plan period. As a result, the family CTP horizon effectively starts at the next plan period. Related topics Capable-to-promise, an overview Family CTP
Net Change
Phase Numbers
Master Phase Number | The phase number for master planning. Related topics Planning sequence and phase numbers
Order Phase Number | The phase number for order planning. Related topics Planning sequence and phase numbers
Master Phase Number Parent | This field contains the maximum master phase number of any of the parents of the item in one of the following relationships: BCM or Supplying relationships. If the value of the Master Phase Number field is smaller or equal to the value of the Master Phase Number Parent field, the master phase number must be recomputed. You can recompute phase numbers by means of the Compute Phase Numbers (cprpd6200m000) session. Related topics Planning sequence and phase numbers Net-change phase number computation
Order Phase Number Parent | This field contains the maximum order phase number of any of the parents of the item in one of the following relationships: BOM or supplying relationships. Default value The default value is -1. If the value of the Order Phase Number field is smaller or equal to the value of the Order Phase Number Parent field, the phase number must be recomputed. Related topics Planning sequence and phase numbers Net-change phase number computation
Net Change
Net Change | If this check box is selected, a change occurred that affects one or both of the following plans: The master planning of the item (for example, a change in the bill of material (BOM). The order planning of the item (for example, a change in the BOM, or the acceptance of a customer order). Related topics Net-change simulations Simulated time period (RRP run)
Net Change Date | The date on which something changes that affects the current master plan or the current planned orders. For example, a higher demand or a change in a BOM. When a net-change simulation is performed, then items are selected based on the net-change date and flag. For example, when the flag is set and the date is outside the order horizon, then the item is skipped.
Pegging Net Change | If this check box is selected, this plan item must be included in the next net-change pegging update, because the plan item has changed since the previous pegging update. For more information, refer to the Net-change pegging update section in Pegging for planned orders.
Commands | Description
View Family Structure | Displays a signal overview in a tree format.