The ID of the plan item.
Items - Planning (cprpd1100m000)Use this session to list plan items, and to maintain and modify related settings. Click the Planning Defaults option on the appropriate menu to zoom to the Items - Planning Defaults (cprpd1110m000) session. LN automatically starts this session when you define an item in the Items (tcibd0501m000) session, set the Order System field in the Items - Ordering (tcibd2100m000) 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.
Plan Item Plan Item Type The type of plan item. Allowed values General General 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 ![[...]](../images/tr_graph_tiglossary_01.gif) Plan level 1 is the highest plan level; the higher the number, the lower the plan level. Supply Source The default supply source of a plan item, which can be Item Source or Distribution. Note
Allowed values 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 Supply Source (tcibd0510m000) session. Default Warehouse The warehouse from and to which the item is normally
delivered. Allowed values
Calendar of Default EU The calendar of the enterprise unit that you
specified in the session for the default warehouse. Note
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 LN generates. If this field is empty, no particular planner is responsible for this plan item. Fixed Delivery 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. VMI Relation The function of this plan item in a vendor managed inventory (VMI) setup. This field
determines what VMI-related actions LN must perform during an order-based planning run. Note Every time you run order-based planning, LN reevaluates the VMI Relation field. 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 Relation field is set to Create Supplier Forecast or Receive Customer Forecast, even if this terms and conditions agreement is not effective at the current date. In this way, LN makes sure that the order-based planning run executes the VMI-functionality if it is needed. For information on the method LN uses to evaluate this field, refer to To determine the VMI Relation. Allowed values General Parameters 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
This check must be cleared when using Mandatory Project Peg in Items (tcibd0501m000) Performance aspects The setting of this field could affect system performance and database growth. For more information, refer to Maintain master plan. 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. 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 Planning Parameters (cprpd0100m000) session, this check box is not available. Exclude from Pegging If this check box is selected, 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. Note This checkbox is disabled if the plan item is a project pegged item. Plan Item Text If this check box is selected, a text is present. 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:
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, LN does not take into account the Time Fence field. For the firm part of purchase schedules, LN uses a frozen period. For more information about purchase schedules and time fences, see Purchase schedules and Enterprise Planning. Time Fence Select Hours or Days as time
unit for the time fence. If you select Hours, LN sets the time fence by taking into account the workable hours, starting from the time point on which 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 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 LN sets the time fence. To find the correct date, 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 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 check box in the Generate Order Planning (cprrp1210m000) session. Dependent on the settings of both the Generate within check box and the Use Time Fence check box, three situation exist:
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. 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, 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, 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, LN ignores the demand forecast up to the end of the plan period in which the time fence falls. In order-based planning, 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. Date The date on which LN sets the forecast time fence. To find the correct date, 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, 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 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. LN automatically updates the order horizon when you run the Check Horizons (cprpd1200m000) session, if the following conditions are met:
If you set the Update Method field in the Check Horizons (cprpd1200m000) session to COLT + Horizons When Too Small, 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, LN corrects the order horizon, regardless of the value in the Minimum Order Horizon field. Date The date on which LN sets the order horizon. To find the correct date, LN starts from the current date, and stops after the number of workdays that you defined in the Order Horizon field. 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 Planning Parameters (cprpd0100m000) session. Planning Horizon The time period for which 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 that are after the 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 a plan period. LN automatically updates the planning horizon when you run the Check Horizons (cprpd1200m000) session, if the following conditions are met:
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.
If you set the Update Method field in the Check Horizons (cprpd1200m000) session to COLT + All Horizons, LN corrects the planning horizon, regardless of the value in the Minimum Planning field. Date The date on which LN sets the planning horizon. To find the correct date, 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 LN finds the correct date of the order horizon. Production Schedules The time period for which Enterprise Planning uses
planned production schedules to plan the supply. The production schedule horizon is expressed as the number of working days from the date you execute the simulation. If the value is zero, Enterprise Planning does not use planned production schedules to plan supply. To calculate this value, LN uses the calendar specified for the enterprise unit of the default warehouse of the plan item. Note This field is applicable only if the Repetitive Production Schedules check box is selected in the Repetitive Manufacturing Parameters (tirpt0100m000)) session. Lead Times Safety The time that you can add to the normal lead time to protect
delivery of goods against fluctuations in the lead time so that an order can be
completed before the order's real need date. If the Use Item Ordering Data check box in the Item Data by Warehouse (whwmd2110s000) session is selected, the safety time is retrieved from this session. If the check box is cleared, the safety time is retrieved from the Items - Ordering (tcibd2100m000) session. The safety time is expressed in hours or in days. Planned Order Depending on the Actual Source the
order lead time for the planned item is determined as follows. If the plan item's Actual Source is Job Shop, the order lead time specified 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:
Note To view the breakdown of the components for the selected lead time you can zoom to the Lead-Time Analysis (cprrp1150m000) session. The order lead time is expressed in days or in hours. Inbound The time interval between the arrival of the items and the
actual storage in the warehouse. Outbound The time interval between taking the items out of the warehouse
and the departure of the carrier on which the items are placed. 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. If the lead - time is set to 0 it will not taken in to account during order planning. Operations Time Fence 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 Operations Time Fence 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. Date The date on which LN sets the start of the fixed lead-time horizon. Available to Transfer Use Available to Transfer Lead Time If this check box is selected, non-excess cost pegged supply may be
transferred to a demand with a higher priority. New supply is raised to fulfill
the demand of the original cost peg. Note Non-excess transfer is for inventory and scheduled supply. If a multiplier is applied to the minimum planning horizon you can determine the actual planning horizon. COLT COLT The cumulative order lead time (COLT) for this plan item.
Non-Critical COLT The non-critical cumulative order lead time (non-critical COLT) for this plan item.
Full Cumulative Order Lead Time The full cumulative order lead time (COLT) for this plan item if it must be produced or purchased
outside the forecast.
Full Non-Critical COLT The full non-critical cumulative order lead time (non-critical COLT) for this plan item if it
must be produced or purchased outside the forecast.
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, 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 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. 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. Minimum Planning The time period for which 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 that are after the 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 a plan period. LN automatically updates the value of the Minimum Planning 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. Automate Update Horizons If this check box is selected, LN automatically updates the order horizon and/or the planning horizon when you
run the Check Horizons (cprpd1200m000) session. Master Plan Automatic Update Production Plan Select one of the four update modes. Purchase Plan Select one of the four update modes. Inventory Plan Select one of the four update modes. Demand Forecast Select one of the four update modes. 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. 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. Days The date to which 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
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:
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. CTP CTP Parameters Online ATP Update If this check box is selected, LN updates the ATP for a plan item online
if a planned or actual inventory transaction is recorded for the plan item. 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:
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. 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. Component CTP If this check box is selected, LN can carry out component CTP checks for
this item. Capacity CTP If this check box is selected, LN can carry out capacity CTP checks for this item. During an ATP check, LN can check the availability of critical resource capacity for additional production. LN only performs a CTP check if the sales order quantity or the quantity you entered in the ATP Handling (cprrp4800m000) 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:
LN checks the capacity of only the resources for which you selected the Critical in CTP check box in the Resources (cprpd2100m000) session. LN cannot carry out capacity CTP checks if the resource has no resource master plan. If LN checked a sales order for capacity CTP, and accepts and records the sales order in Sales Control, LN carries out a capacity CTP reservation on the critical resources so that the resource capacity cannot be given away again. Channel ATP If this check box is selected, LN can carry out channel ATP checks for this item. CTP Time Fence The number of working days from the current moment, during
which 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. LN performs CTP checks between the end of the CTP time fence and the end of the ATP/CTP horizon. After the CTP horizon, LN assumes that capacity and components are infinite. However, 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. CTP Horizon The date until which LN performs ATP and CTP checks. The ATP horizon is expressed as a number of working days during which LN can carry out ATP and CTP checks. Beyond the ATP/CTP horizon, LN does not check ATP or CTP: all customer orders are accepted. After the ATP/CTP horizon, 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, 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. Family CTP Parameters Family CTP If this check box is selected, LN can carry out family CTP checks for this item. Family Site The family site in which you
defined the family item that LN takes into account to perform a family ctp
check. Allowed values The site must have been defined in the current company. 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. CTP Time Fence 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. Net Change Phase Numbers Master Phase Number The phase number for master planning. Order Phase Number The phase number for order planning. 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. 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. Net Change Net Change If this check box is selected, a change occurred that
affects one or both of the following plans:
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. Cluster A group of entities that are not necessarily related to one
financial company or logistic company. In Enterprise Planning, clusters are used for groups of warehouses, connected by supplying relationships.
View Family Structure Displays a exception message overview in a tree format.
| |||