<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/cp/rpd/cprpd1100m000" xml:lang="en">
   <Header>
      <Title>Items - Planning</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to list <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan items</Link>, and to maintain and modify the related
		  settings.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>Click the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd1110m000" role="command" Update="No">Planning Defaults</GUIRef> option on the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu to zoom to
		  the <GUIRef href="/baanerp/cp/rpd/cprpd1110m000" role="session">Items - Planning Defaults (cprpd1110m000)</GUIRef> session.</Paragraph>
         <Paragraph>LN automatically starts this session when you define an item in the <GUIRef href="/baanerp/tc/ibd/tcibd0501m000" role="session">Items - General (tcibd0501m000)</GUIRef> session, set the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000#tcibd200.osys" role="manual">Order System</GUIRef> field
		  in the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000" role="session">Item - Ordering (tcibd2100s000)</GUIRef> session to Planned, and save the
		  item.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If you have started this session by zooming, you can only
			 find and select a record.</Paragraph>
         </Note>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Performance aspects</SectionTitle>
         <Paragraph>The settings in this session could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/cp/P000020_number_of_plan_items" role="manual">Number of plan items</Link>.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000017" role="manual">Plan items in Enterprise Planning</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000012" role="manual">Item definition in Enterprise Planning</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldGroup>
         <Title>Plan Item</Title>
         <FieldHelp ID="cprpd100.plni" OtherIDs="tcibd001.dsca">
            <Header>
               <Title>Plan Item</Title>
            </Header>
            <FuncDesc>An item with the order system <GUIRef href="/baanerp/tc/domains/osys#mps" role="option">Planned</GUIRef>.</FuncDesc>
            <SimpleSection>
               <Paragraph>The production, distribution, or purchase of these items is
		  planned in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> based on the forecast or the actual demand.</Paragraph>
               <List>
                  <ListIntro>You can plan these items by means of the following:</ListIntro>
                  <ListItem>Master-based planning, which is similar to master production
			 scheduling techniques.</ListItem>
                  <ListItem>Order-based planning, which is similar to
			 material-requirements planning techniques.</ListItem>
                  <ListItem>A combination of master-based planning and order-based
			 planning.</ListItem>
               </List>
               <List>
                  <ListIntro>Plan items can be one of the following:</ListIntro>
                  <ListItem>An actual manufactured or purchased item.</ListItem>
                  <ListItem>A product family.</ListItem>
                  <ListItem>A basic model, that is, a defined product variant of a
			 generic item.</ListItem>
               </List>
               <Paragraph>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.</Paragraph>
            </SimpleSection>
            <SimpleSection>
               <Paragraph>The plan items must be unique for all <Link href="/baanerp/ti/glossary/glossary#PlanLevel_ti" role="glossary">plan levels</Link>.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000017" role="manual">Plan items in Enterprise Planning</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>General</Title>
         <FieldGroup>
            <Title>General Data</Title>
            <FieldHelp ID="cprpd100.plit">
               <Header>
                  <Title>Plan Item Type</Title>
               </Header>
               <FuncDesc>The type of plan item.</FuncDesc>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>All plan items must first be defined as an item in <GUIRef href="/baanerp/tc" role="package">Common</GUIRef>, even if it
				  concerns a plan item of type <GUIRef href="/baanerp/cp/domains/rpd.plit#productfamily" role="option">Family</GUIRef>.</Paragraph>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000149" role="manual">Plan levels and product families</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000050" role="manual">To update goods-flow data</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.plvl">
               <Header>
                  <Title>Plan Level</Title>
               </Header>
               <FuncDesc>The level within a hierarchical planning structure.</FuncDesc>
               <SimpleSection>
                  <Paragraph>When you plan on a higher plan level, plans are general and
		  less detailed.</Paragraph>
               </SimpleSection>
               <ExampleSection>
                  <SectionTitle>Example</SectionTitle>
                  <Figure space-and-orientation="indented-estimated">
                     <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" width="390" height="231"
                               SRC="../images/tr_graph_tiglossary_01.gif"
                               alt="[...]"/>
                  </Figure>
                  <Paragraph>Plan level 1 is the highest plan level; the higher the
		  number, the lower the plan level.</Paragraph>
               </ExampleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000149" role="manual">Plan levels and product families</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.sour">
               <Header>
                  <Title>Default Supply Source</Title>
               </Header>
               <FuncDesc>The default supply source of a plan item, which can be <GUIRef href="/baanerp/cp/domains/rpd.sour#manpur" role="option">Production/Purchase</GUIRef> or <GUIRef href="/baanerp/cp/domains/rpd.sour#distribution" role="option">Distribution</GUIRef>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>LN uses the value of the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.sour" role="manual">Default Supply Source</GUIRef> field if it can find no valid <Link href="/baanerp/cp/glossary/glossary#000104" role="glossary">sourcing strategy</Link> for the
				  plan item.</Paragraph>
                  <Paragraph>If you set the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.sour" role="manual">Default Supply Source</GUIRef> field to <GUIRef href="/baanerp/cp/domains/rpd.sour#manpur" role="option">Production/Purchase</GUIRef>, LN takes into account the
				  date effective item type that you defined in the <GUIRef href="/baanerp/tc/ibd/tcibd0510m000" role="session">Date-Effective Item Data (tcibd0510m000)</GUIRef> session.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000410" role="manual">Sources of supply: production, purchase, or distribution</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="actual.sour">
               <Header>
                  <Title>Actual Source</Title>
               </Header>
               <FuncDesc>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 <GUIRef href="/baanerp/tc/ibd/tcibd0510m000" role="session">Date-Effective Item Data (tcibd0510m000)</GUIRef> session.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/tc/onlinemanual/000322" role="manual">Date-effective item data</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.cwar" OtherIDs="tcmcs003.dsca">
               <Header>
                  <Title>Default Warehouse</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> from and to which the item is normally
				delivered.</FuncDesc>
               <AllowedValues>
                  <SectionTitle>Allowed values</SectionTitle>
                  <Paragraph>For a <Link href="/baanerp/cp/glossary/glossary#000055" role="glossary">non-clustered item</Link> this must
				  be a warehouse in the item's logistical site.</Paragraph>
                  <Paragraph>The warehouse of a <Link href="/baanerp/cp/glossary/glossary#000054" role="glossary">clustered item</Link> must belong
				  to the item's cluster.</Paragraph>
               </AllowedValues>
            </FieldHelp>
            <FieldHelp ID="item.cdeu" OtherIDs="item.cdeu.dsca">
               <Header>
                  <Title>Calendar of Default EU</Title>
               </Header>
               <FuncDesc>The calendar of the <Link href="/baanerp/tc/glossary/glossary#000011" role="glossary">enterprise unit</Link> that you
				specified in the session for the default warehouse.</FuncDesc>
               <SimpleSection>
                  <Paragraph>LN uses the enterprise unit calendar for several planning aspects
				  that are not related to a particular <Link href="/baanerp/cp/glossary/glossary#000008" role="glossary">resource</Link>, <Link href="/baanerp/tc/glossary/glossary#BusinePartne_tc" role="glossary">business partner</Link>, or <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link>.</Paragraph>
                  <Paragraph>LN uses the enterprise unit calendar when a more specific calendar is not
				  available.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000034" role="manual">Calendars in Enterprise Planning</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.plid">
               <Header>
                  <Title>Planner</Title>
               </Header>
               <FuncDesc>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.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If this field is empty, no planner in particular is
				  responsible for this plan item.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="planner.nama">
               <Header>
                  <Title>Planner</Title>
               </Header>
               <FuncDesc>The name of the planner that belongs to the code in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.plid" role="manual">Planner</GUIRef> field.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cprpd100.fide" OtherIDs="cprpd210.dsca">
               <Header>
                  <Title>Fixed Delivery Type</Title>
               </Header>
               <FuncDesc>The fixed-delivery code for this plan item.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If the actual source corresponds with the supply source
				  for which the <Link href="/baanerp/cp/glossary/glossary#000306" role="glossary">fixed delivery code</Link> is valid, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> generates <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned orders</Link> for the item. In this case, the finish
				  date equals a fixed-delivery date.</Paragraph>
                  <Paragraph>You can link a fixed-delivery types to a <Link href="/baanerp/td/glossary/glossary#000030" role="glossary">pattern</Link> in the <GUIRef href="/baanerp/cp/rpd/cprpd2110m000" role="session">Fixed Delivery Codes (cprpd2110m000)</GUIRef> session.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>If this field is empty, fixed delivery is not used for
				  this item.</Paragraph>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/tc/onlinemanual/000375" role="manual">To define patterns</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.vmir">
               <Header>
                  <Title>VMI Role</Title>
               </Header>
               <FuncDesc>The function of this plan item in a <Link href="/baanerp/wh/glossary/glossary#000469" role="glossary">vendor managed inventory (VMI)</Link> setup.</FuncDesc>
               <SimpleSection>
                  <Paragraph>This field determines what VMI-related actions LN must perform during
				  an <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order-based planning</Link> run.</Paragraph>
               </SimpleSection>
               <SimpleSection>
                  <List>
                     <ListIntro>This field can have the following values:</ListIntro>
                     <ListItemHead>
                        <GUIRef href="/baanerp/cp/domains/vmi.role#customer" role="option">Customer</GUIRef>
                     </ListItemHead>
                     <ListItem>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 <Link href="/baanerp/cp/glossary/glossary#000456" role="glossary">forecast</Link> that you send to the <Link href="/baanerp/cp/glossary/glossary#000466" role="glossary">VMI supplier</Link>.</ListItem>
                     <ListItemHead>
                        <GUIRef href="/baanerp/cp/domains/vmi.role#supplier" role="option">Supplier</GUIRef>
                     </ListItemHead>
                     <ListItem>You are the <Link href="/baanerp/cp/glossary/glossary#000466" role="glossary">VMI supplier</Link> 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.</ListItem>
                     <ListItemHead>
                        <GUIRef href="/baanerp/cp/domains/vmi.role#not.applicable" role="option">Not Applicable</GUIRef>
                     </ListItemHead>
                     <ListItem>This item is not involved in vendor-managed inventory
					 that is planned by a supplier.</ListItem>
                  </List>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>Every time you run <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order-based planning</Link>, LN reevaluates the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.vmir" role="manual">VMI Role</GUIRef> field. LN takes the entire period between current date and the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link> into account. If at any time in that
				  period an applicable <Link href="/baanerp/tc/glossary/glossary#000500" role="glossary">terms and conditions agreement</Link> is found, the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.vmir" role="manual">VMI Role</GUIRef> field is set to <GUIRef href="/baanerp/cp/domains/vmi.role#customer" role="option">Customer</GUIRef> or <GUIRef href="/baanerp/cp/domains/vmi.role#supplier" role="option">Supplier</GUIRef>, even if this terms and conditions agreement is
				  not effective at the current date. In this way, LN makes sure that the <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order-based planning</Link> run executes the VMI-functionality
				  if it is needed.</Paragraph>
               </Note>
               <SimpleSection>
                  <Paragraph>For information on the method LN uses to evaluate
				  this field, refer to <Link href="/baanerp/cp/onlinemanual/000481" role="manual">To determine the VMI role</Link>.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000470" role="manual">Supply planning by supplier</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000481" role="manual">To determine the VMI role</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title>General Parameters</Title>
            <FieldHelp ID="cprpd100.osys">
               <Header>
                  <Title>Maintain Master Plans</Title>
               </Header>
               <FuncDesc>If this check box is selected, Enterprise Planning
				maintains an <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary">item master plan</Link> for the
				item.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If this check box is selected, Enterprise Planning also
				  maintains a <Link href="/baanerp/cp/glossary/glossary#000020" role="glossary">channel master plan</Link> for
				  every channel that you linked to the specified plan item in the <GUIRef href="/baanerp/cp/dsp/cpdsp5100m000" role="session">Plan Item - Channels (cpdsp5100m000)</GUIRef> session.</Paragraph>
                  <Paragraph>A master plan allows the use of various functions, see: <Link href="/baanerp/cp/onlinemanual/000022" role="manual">To use master plans</Link>.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <List>
                     <ListItem>If an item master plan is maintained, you can still
					 also use <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order-based planning</Link>.</ListItem>
                     <ListItem>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.</ListItem>
                     <ListItem>You must only maintain a master plan for an item if you
					 need the described functionality, because it can decrease LN's performance.</ListItem>
                     <ListItem>If the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.vmir" role="manual">VMI Role</GUIRef> field is <GUIRef href="/baanerp/cp/domains/vmi.role#customer" role="option">Customer</GUIRef> or <GUIRef href="/baanerp/cp/domains/vmi.role#supplier" role="option">Supplier</GUIRef>, you cannot maintain an item master plan for this
					 item.</ListItem>
                  </List>
               </Note>
               <SimpleSection>
                  <SectionTitle>Performance aspects</SectionTitle>
                  <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/cp/P000014_maintain_master_plan" role="manual">Maintain master plan</Link>.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000022" role="manual">To use master plans</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.depd">
               <Header>
                  <Title>Dependent Demand Forecast</Title>
               </Header>
               <FuncDesc>If this check box is selected, the calculation of the
				demand forecast is based on the historical demand data of both the <Link href="/baanerp/cp/glossary/glossary#000074" role="glossary">dependent demand</Link> and the <Link href="/baanerp/cp/glossary/glossary#000075" role="glossary">independent demand</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If this check box is cleared, the calculation and
				  consumption of the demand forecast is based on the independent demand only.</Paragraph>
                  <Paragraph>If the calculation of the demand forecast takes the
				  dependent demand into account, the forecast is also consumed by dependent
				  demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000107" role="manual">To compute the demand forecast</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000133" role="manual">Forecast Consumption with an Item Master Plan</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.mult">
               <Header>
                  <Title>Central Multi Site Planning</Title>
               </Header>
               <FuncDesc>If this check box is selected, the item can be planned
				in a central multisite planning run.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If you clear the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000#cprpd000.imul" role="manual">Multisite Planning</GUIRef> check box in the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000" role="session">EP Parameters (cprpd0100m000)</GUIRef> session, this check box is not available.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000148" role="manual">Multisite planning</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.efpg">
               <Header>
                  <Title>Exclude from Pegging</Title>
               </Header>
               <FuncDesc>If this check box is selected, LN generates no <Link href="/baanerp/cp/glossary/glossary#000452" role="glossary">pegging information</Link> for this plan item.</FuncDesc>
               <SimpleSection>
                  <Paragraph>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.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000076" role="manual">Pegging for planned orders</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title>Inventory</Title>
            <FieldHelp ID="inventory">
               <Header>
                  <Title>Inventory on Hand</Title>
               </Header>
               <FuncDesc>The physical quantity of goods in one or more warehouses
		(including the inventory on hold).</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/wh/glossary/glossary#000331" role="glossary">inventory on hold</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="inv.cuni">
               <Header>
                  <Title>Inventory on Hand</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Units_tc" role="glossary">unit</Link> in which LN manages physical
				quantities of the item.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tcibd.sfst">
               <Header>
                  <Title>Safety Stock</Title>
               </Header>
               <FuncDesc>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.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000332" role="manual">To compute cumulative ATP</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="sfst.cuni">
               <Header>
                  <Title>Safety Stock</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Units_tc" role="glossary">unit</Link> in which LN manages physical
				quantities of the item.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldHelp ID="display.text">
            <Header>
               <Title>Plan Item Text</Title>
            </Header>
            <FuncDesc> If this check box is selected, a text is present.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>Horizons</Title>
         <FieldGroup>
            <Title>Time Fences</Title>
            <FieldHelp ID="cprpd100.tmfc">
               <Header>
                  <Title>Time Fence</Title>
               </Header>
               <FuncDesc>The date until which an item's supply plan and planned orders
		are frozen.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The time fence is expressed as a number of working days or
		  working hours from the date you carry out the simulation.</Paragraph>
                  <Paragraph>As a rule, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> 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.</Paragraph>
                  <List>
                     <ListIntro>The time fence is meant to prevent:</ListIntro>
                     <ListItem>Disturbance of orders that have already started (at the
			 shop-floor level).</ListItem>
                     <ListItem>Generation of planned orders with start dates in the past
			 (that is, orders that are late).</ListItem>
                  </List>
                  <Paragraph>Usually, the lead time of an item's production process is a
		  reasonable value for the time fence.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>You can override the time fence for master-based
				  planning by selecting the <GUIRef href="/baanerp/cp/rmp/cprmp1202m000#sim.in.fence" role="manual">Generate Within Time Fence</GUIRef> check box in the <GUIRef href="/baanerp/cp/rmp/cprmp1202m000" role="session">Generate Master Planning (cprmp1202m000)</GUIRef> session.</Paragraph>
               </Note>
               <SimpleSection>
                  <Paragraph>You can override the time fence for order-based
				  planning by selecting the <GUIRef href="/baanerp/cp/rmp/cprmp1202m000#sim.in.fence" role="manual">Generate Within Time Fence</GUIRef> check box in the <GUIRef href="/baanerp/cp/rrp/cprrp1210m000" role="session">Generate Order Planning (cprrp1210m000)</GUIRef> session.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>Although you can define a time fence for purchase
				  schedule items, LN does
				  not take into account the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.tmfc" role="manual">Time Fence</GUIRef> field. For the firm part of purchase
				  schedules, LN uses a <Link href="/baanerp/td/glossary/glossary#000346" role="glossary">frozen period</Link>. For more information about purchase
				  schedules and time fences, see <Link href="/baanerp/cp/onlinemanual/000078" role="manual">Purchase schedules and Enterprise Planning</Link>.</Paragraph>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000023" role="manual">Horizons and time fences</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000015" role="manual">Simulated time period (RRP run)</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000411" role="manual">Time fences in order planning and in master planning</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000078" role="manual">Purchase schedules and Enterprise Planning</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.tmfu">
               <Header>
                  <Title>Time Fence</Title>
               </Header>
               <FuncDesc>Select <GUIRef href="/baanerp/tc/domains/tope#hours" role="option">Hours</GUIRef> or <GUIRef href="/baanerp/tc/domains/tope#days" role="option">Days</GUIRef> as time
				unit for the <Link href="/baanerp/cp/glossary/glossary#000063" role="glossary">time fence</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If you select <GUIRef href="/baanerp/tc/domains/tope#hours" role="option">Hours</GUIRef>, 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 <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.tmfc" role="manual">Time Fence</GUIRef> field.</Paragraph>
                  <Paragraph>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.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tmfc.dt">
               <Header>
                  <Title>Time Fence</Title>
               </Header>
               <FuncDesc>The date on which LN sets the <Link href="/baanerp/cp/glossary/glossary#000063" role="glossary">time fence</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>To find the correct date, LN starts from the
				  current date, and stops after the number of <Link href="/baanerp/cp/glossary/glossary#000064" role="glossary">workdays</Link> that you defined in
				  the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.tmfc" role="manual">Time Fence</GUIRef> field.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="cprpd100.utmf">
               <Header>
                  <Title>Use Time Fence</Title>
               </Header>
               <FuncDesc>Select or clear the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.utmf" role="manual">Use Time Fence</GUIRef> check box to indicate whether or not you want to use the
				specified <Link href="/baanerp/cp/glossary/glossary#000063" role="glossary">time fence</Link> to plan an
				individual item.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If this check box is selected, Enterprise Planning uses
				  the time fence according to the setting of the <GUIRef href="/baanerp/cp/rrp/cprrp1210m000#f.sim.in.fence" role="manual">Generate Within Time Fence</GUIRef> in the <GUIRef href="/baanerp/cp/rrp/cprrp1210m000" role="session">Generate Order Planning (cprrp1210m000)</GUIRef> session to plan orders for an individual
				  item.</Paragraph>
                  <Paragraph>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.</Paragraph>
                  <Paragraph>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 <GUIRef href="/baanerp/cp/rrp/cprrp1210m000#f.sim.in.fence" role="manual">Generate Within Time Fence</GUIRef> check box in the <GUIRef href="/baanerp/cp/rrp/cprrp1210m000" role="session">Generate Order Planning (cprrp1210m000)</GUIRef> session.</Paragraph>
                  <Paragraph>If you clear the <GUIRef href="/baanerp/cp/rrp/cprrp1210m000#f.sim.in.fence" role="manual">Generate Within Time Fence</GUIRef> check box in the <GUIRef href="/baanerp/cp/rrp/cprrp1210m000" role="session">Generate Order Planning (cprrp1210m000)</GUIRef> session, Enterprise Planning plans from the
				  time fence for those plan items for which you select the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.utmf" role="manual">Use Time Fence</GUIRef> check box, and within the time fence for items for which
				  the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.utmf" role="manual">Use Time Fence</GUIRef> check box is cleared. In the last case, Enterprise Planning can plan in the
				  past (no time fence).</Paragraph>
                  <Paragraph>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.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000023" role="manual">Horizons and time fences</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000411" role="manual">Time fences in order planning and in master planning</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.fctf">
               <Header>
                  <Title>Forecast Time Fence</Title>
               </Header>
               <FuncDesc>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.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The forecast time fence is expressed as a number of
				  working days from the date you carry out the planning.</Paragraph>
                  <Paragraph>Before the forecast time fence, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> only
				  considers actual customer orders. Beyond the forecast time fence, total demand
				  is a combination of actual orders and forecasts.</Paragraph>
                  <Paragraph>A reasonable value for the forecast time fence is the
				  minimum time period between the receipt of customer orders and the requested
				  delivery dates.</Paragraph>
                  <Paragraph>To calculate the forecast time fence, LN uses the calendar
				  that you specified for the <Link href="/baanerp/tc/glossary/glossary#000011" role="glossary">enterprise unit</Link> of the plan item's default warehouse.</Paragraph>
                  <Paragraph>If you did not specify an enterprise unit for the
				  default warehouse of the plan item, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses the company calendar to
				  calculate the forecast time fence.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>In <Link href="/baanerp/cp/glossary/glossary#000059" role="glossary">master planning</Link>, LN ignores the demand
				  forecast up to the end of the <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan period</Link> in which the time fence falls.</Paragraph>
                  <Paragraph>In <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order-based planning</Link>, 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 <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order-based planning</Link>, the demand forecast consists of <Link href="/baanerp/cp/glossary/glossary#000017" role="glossary">special demand</Link>.</Paragraph>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000133" role="manual">Forecast Consumption with an Item Master Plan</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000411" role="manual">Time fences in order planning and in master planning</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="fctf.dt">
               <Header>
                  <Title>Date</Title>
               </Header>
               <FuncDesc>The date on which LN sets the <Link href="/baanerp/cp/glossary/glossary#000067" role="glossary">forecast time fence</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>To find the correct date, LN starts from the
				  current date, and stops after the number of <Link href="/baanerp/cp/glossary/glossary#000064" role="glossary">workdays</Link> that you defined in
				  the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.fctf" role="manual">Forecast Time Fence</GUIRef> field.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="cprpd100.otmf">
               <Header>
                  <Title>Order Horizon</Title>
               </Header>
               <FuncDesc>The time period for which <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses
		order-based planning to plan supply.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The order horizon is expressed as a number of working days
		  from the date you carry out the simulation.</Paragraph>
                  <Paragraph>If the order horizon is zero, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> does not
		  use order-based planning for the item involved.</Paragraph>
                  <Paragraph>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.</Paragraph>
                  <Paragraph>If you did not specify an <Link href="/baanerp/tc/glossary/glossary#000011" role="glossary">enterprise unit</Link> for the default <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> of the plan
		  item, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses the company calendar to calculate the order horizon.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>LN moves
		  the order horizon towards the end of the <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan</Link> period) in which it falls, because <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> must know whether a <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan period</Link> falls within the order horizon.</Paragraph>
               </Note>
               <SimpleSection>
                  <List>
                     <ListIntro>LN automatically updates the order horizon when
					 you run the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session, if the following conditions are
					 met:</ListIntro>
                     <ListItem>The <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.upho" role="manual">Automate Update Horizons</GUIRef> check box is selected.</ListItem>
                     <ListItem>The <GUIRef href="/baanerp/cp/rpd/cprpd1200m000#f.upd.method" role="manual">Update Method</GUIRef> in the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session is set to <GUIRef href="/baanerp/cp/domains/rpd.upd.meth#small" role="option">COLT + Horizons When Too Small</GUIRef>, or to <GUIRef href="/baanerp/cp/domains/rpd.upd.meth#all" role="option">COLT + All Horizons</GUIRef>.</ListItem>
                  </List>
                  <Paragraph>If you set the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000#f.upd.method" role="manual">Update Method</GUIRef> field
				  in the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session to <GUIRef href="/baanerp/cp/domains/rpd.upd.meth#small" role="option">COLT + Horizons When Too Small</GUIRef>, LN corrects the <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">order horizon</Link> when it is too
				  short to correctly create planned orders.</Paragraph>
                  <Paragraph>If you set the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000#f.upd.method" role="manual">Update Method</GUIRef> field
				  in the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session to <GUIRef href="/baanerp/cp/domains/rpd.upd.meth#all" role="option">COLT + All Horizons</GUIRef>, LN corrects the order horizon, regardless of the value in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#min.otmf" role="manual">Minimum Order Horizon</GUIRef> field.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000023" role="manual">Horizons and time fences</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000317" role="manual">Cumulative order lead times and horizons</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="otmf.dt">
               <Header>
                  <Title>Date</Title>
               </Header>
               <FuncDesc>The date on which LN sets the <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">order horizon</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>To find the correct date, LN starts from the
				  current date, and stops after the number of <Link href="/baanerp/cp/glossary/glossary#000064" role="glossary">workdays</Link> that you defined in
				  the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.otmf" role="manual">Order Horizon</GUIRef> field.</Paragraph>
                  <Paragraph>LN takes into account the actual calendar for the <Link href="/baanerp/tc/glossary/glossary#000011" role="glossary">enterprise unit</Link> calendar of
				  the item's warehouse and the default <Link href="/baanerp/tc/glossary/glossary#ResoActiType_tc" role="glossary">availability type</Link> that you
				  defined in the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000" role="session">EP Parameters (cprpd0100m000)</GUIRef> session.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="cprpd100.ptmf">
               <Header>
                  <Title>Planning Horizon</Title>
               </Header>
               <FuncDesc>The time period for which LN maintains planning
		data for an item.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The planning horizon is expressed as a number of working days
		  from the date you carry out the simulation.</Paragraph>
                  <Paragraph> 
                     <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> does not generate supply plans or planned orders beyond an
		  item's planning horizon.</Paragraph>
                  <Paragraph>To calculate the planning horizon, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses the
		  calendar that you specified for the enterprise unit of the default warehouse to
		  which the plan item belongs.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>
                     <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> moves the planning horizon to the end of the plan period in
		  which it falls.</Paragraph>
               </Note>
               <SimpleSection>
                  <List>
                     <ListIntro>LN automatically updates the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link> when you
					 run the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session, if the following conditions are met:</ListIntro>
                     <ListItem>The <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.upho" role="manual">Automate Update Horizons</GUIRef> check box is selected.</ListItem>
                     <ListItem>The <GUIRef href="/baanerp/cp/rpd/cprpd1200m000#f.upd.method" role="manual">Update Method</GUIRef> field
					 in the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session is set to <GUIRef href="/baanerp/cp/domains/rpd.upd.meth#small" role="option">COLT + Horizons When Too Small</GUIRef>, or to <GUIRef href="/baanerp/cp/domains/rpd.upd.meth#all" role="option">COLT + All Horizons</GUIRef>.</ListItem>
                  </List>
                  <List>
                     <ListIntro>If you set the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000#f.upd.method" role="manual">Update Method</GUIRef> field
					 in the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session to <GUIRef href="/baanerp/cp/domains/rpd.upd.meth#small" role="option">COLT + Horizons When Too Small</GUIRef>, corrects the planning horizon when it is too
					 short to correctly create an order plan.</ListIntro>
                     <ListItem>LN</ListItem>
                  </List>
                  <Paragraph>If you set the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000#f.upd.method" role="manual">Update Method</GUIRef> field
				  in the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session to <GUIRef href="/baanerp/cp/domains/rpd.upd.meth#all" role="option">COLT + All Horizons</GUIRef>, LN corrects the planning horizon, regardless of the value in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#min.ptmf" role="manual">Minimum Planning Horizon</GUIRef> field.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000023" role="manual">Horizons and time fences</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000317" role="manual">Cumulative order lead times and horizons</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="ptmf.dt">
               <Header>
                  <Title>Date</Title>
               </Header>
               <FuncDesc>The date on which LN sets the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>To find the correct date, LN starts from the
				  current date, and stops after the number of <Link href="/baanerp/cp/glossary/glossary#000064" role="glossary">workdays</Link> that you defined in
				  the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.ptmf" role="manual">Planning Horizon</GUIRef> field, which is comparable to the way that LN finds the correct date
				  of the <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">order horizon</Link>.</Paragraph>
               </SimpleSection>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title>Order Lead Times</Title>
            <FieldHelp ID="tcibd.sftm" OtherIDs="tcibd.sftu">
               <Header>
                  <Title>Safety Time</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/td/glossary/glossary#000041" role="glossary">safety time</Link> defined in the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000" role="session">Item - Ordering (tcibd2100s000)</GUIRef> session.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The safety time is expressed in hours or in
				  days.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tiipd.oltm" OtherIDs="tiipd.oltu">
               <Header>
                  <Title>Order Lead Time</Title>
               </Header>
               <FuncDesc>The plan item's default supply source is <GUIRef href="/baanerp/cp/domains/rpd.sour#manpur" role="option">Production/Purchase</GUIRef>.
				Depending on the Effectivity Date of the item, the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#actual.sour" role="manual">Actual Source</GUIRef> can be
				Production or Purchase.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If the plan item's <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#actual.sour" role="manual">Actual Source</GUIRef> is <GUIRef href="/baanerp/cp/domains/rpd.act.sour#manufacture" role="option">Production</GUIRef>, then
				  the <Link href="/baanerp/tc/glossary/glossary#000010" role="glossary">order lead time</Link> defined in
				  the <GUIRef href="/baanerp/ti/ipd/tiipd0101m000" role="session">Items - Production (tiipd0101m000)</GUIRef> session is displayed in this field. This
				  lead time is used for planned production orders within the <Link href="/baanerp/cp/glossary/glossary#000058" role="glossary">fixed lead-time horizon</Link>.</Paragraph>
                  <Paragraph>If the plan item's <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#actual.sour" role="manual">Actual Source</GUIRef> is <GUIRef href="/baanerp/cp/domains/rpd.act.sour#purchase" role="option">Purchase</GUIRef>, then the <Link href="/baanerp/td/glossary/glossary#000011" role="glossary">supply time</Link> defined in the <GUIRef href="/baanerp/td/ipu/tdipu0101m000" role="session">Items - Purchase (tdipu0101m000)</GUIRef> session is displayed in this field. This lead time is
				  used for planned purchase orders for which no particular supplier can be found.</Paragraph>
                  <Paragraph>The order lead time is expressed in days or in
				  hours.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="cprpd100.eltm">
               <Header>
                  <Title>Extra Lead Time</Title>
               </Header>
               <FuncDesc>Time reserved for extra activities that are necessary to fully
		complete a planned order.</FuncDesc>
               <SimpleSection>
                  <Paragraph> 
                     <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> 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.</Paragraph>
                  <Paragraph>The extra lead time is expressed in days or in hours.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="cprpd100.eltu">
               <Header>
                  <Title>Extra Lead Time</Title>
               </Header>
               <FuncDesc>The time unit in which this lead time is expressed.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cprpd100.fltm">
               <Header>
                  <Title>Start of Fixed Lead-Time Horizon (SFC)</Title>
               </Header>
               <FuncDesc>The number of workdays after which the <Link href="/baanerp/cp/glossary/glossary#000058" role="glossary">fixed lead-time horizon</Link> starts.</FuncDesc>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>The start of the fixed lead-time horizon is rounded to
				  the end of a <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan period</Link>. Effectively,
				  this means that the fixed lead-time horizon starts at the next plan period.</Paragraph>
               </Note>
               <SimpleSection>
                  <Paragraph>If the value of this field is greater than the <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">order horizon</Link>, this
				  effectively means that no fixed lead-time horizon is used.</Paragraph>
               </SimpleSection>
               <Important>
                  <SectionTitle>Important!</SectionTitle>
                  <Paragraph>If the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.fltm" role="field">Start of Fixed Lead-Time Horizon (SFC)</GUIRef> field is zero, you cannot transfer
				  the generated planned orders to the <Link href="/baanerp/cp/glossary/glossary#000027" role="glossary">execution level</Link>, because <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> links no
				  routing operations to the planned order. You can use this setting only for
				  simulations.</Paragraph>
               </Important>
               <SimpleSection>
                  <SectionTitle>Performance aspects</SectionTitle>
                  <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/cp/P000010_start_of_fixed_lead-time_horizon"
                           role="manual">Start of fixed lead-time horizon</Link>.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000314" role="manual">Production lead-time calculation in Enterprise Planning</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000021" role="manual">Order planning, an overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="fltm.dt">
               <Header>
                  <Title>Date</Title>
               </Header>
               <FuncDesc>The date on which LN sets the start of the <Link href="/baanerp/cp/glossary/glossary#000058" role="glossary">fixed lead-time horizon</Link>.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title>COLT</Title>
            <FieldHelp ID="cprpd100.colt">
               <Header>
                  <Title>Cumulative Order Lead Time</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#413" role="glossary">cumulative order lead time (COLT)</Link> for this plan item.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListItem>When calculating the purchase item lead time, the <Link href="/baanerp/td/ipu/tdipu0110m000#tdipu010.suti" role="formfield">Supply Time</Link> from the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session is taken into account.</ListItem>
                     <ListItem>When you run the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session, LN automatically updates this field.</ListItem>
                  </List>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000317" role="manual">Cumulative order lead times and horizons</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/td/onlinemanual/000324" role="manual">To calculate purchase item lead time</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000316" role="manual">Lead times and horizons</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.nclt">
               <Header>
                  <Title>Non-Critical COLT</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#414" role="glossary">non-critical cumulative order lead time (non-critical COLT)</Link> for this plan item.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListItem>When calculating the purchase item lead time, the <Link href="/baanerp/td/ipu/tdipu0110m000#tdipu010.suti" role="formfield">Supply Time</Link> from the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session is taken into account.</ListItem>
                     <ListItem>When you run the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session, LN automatically updates this field.</ListItem>
                  </List>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000317" role="manual">Cumulative order lead times and horizons</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/td/onlinemanual/000324" role="manual">To calculate purchase item lead time</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000316" role="manual">Lead times and horizons</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.fclt">
               <Header>
                  <Title>Full Cumulative Order Lead Time</Title>
               </Header>
               <FuncDesc>The full <Link href="/baanerp/cp/glossary/glossary#413" role="glossary">cumulative order lead time (COLT)</Link> for this plan item if it must be produced or purchased
				outside the forecast.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListItem>This field is only visible if the <GUIRef href="/baanerp/td/pur/tdpur0100m000#tdpur000.fstu" role="manual">Use Full Supply Time</GUIRef> check box is selected in the <GUIRef href="/baanerp/td/pur/tdpur0100m000" role="session">Purchase Parameters (tdpur0100m000)</GUIRef> session.</ListItem>
                     <ListItem>When calculating the purchase item lead time, the <Link href="/baanerp/td/ipu/tdipu0110m000#tdipu010.fsti" role="formfield">Full Supply Time</Link> from the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session is taken into account.</ListItem>
                     <ListItem>When you run the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session, LN automatically updates this field.</ListItem>
                  </List>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000317" role="manual">Cumulative order lead times and horizons</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/td/onlinemanual/000324" role="manual">To calculate purchase item lead time</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.fnct">
               <Header>
                  <Title>Full Non-Critical COLT</Title>
               </Header>
               <FuncDesc>The full <Link href="/baanerp/cp/glossary/glossary#414" role="glossary">non-critical cumulative order lead time (non-critical COLT)</Link> for this plan item if it
				must be produced or purchased outside the forecast.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListItem>This field is only visible if the <GUIRef href="/baanerp/td/pur/tdpur0100m000#tdpur000.fstu" role="manual">Use Full Supply Time</GUIRef> check box is selected in the <GUIRef href="/baanerp/td/pur/tdpur0100m000" role="session">Purchase Parameters (tdpur0100m000)</GUIRef> session.</ListItem>
                     <ListItem>When calculating the purchase item lead time, the <Link href="/baanerp/td/ipu/tdipu0110m000#tdipu010.fsti" role="formfield">Full Supply Time</Link> from the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session is taken into account.</ListItem>
                     <ListItem>When you run the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session, LN automatically updates this field.</ListItem>
                  </List>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000317" role="manual">Cumulative order lead times and horizons</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/td/onlinemanual/000324" role="manual">To calculate purchase item lead time</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="min.otmf">
               <Header>
                  <Title>Minimum Order Horizon</Title>
               </Header>
               <FuncDesc>The time period for which <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses
		order-based planning to plan supply.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The order horizon is expressed as a number of working days
		  from the date you carry out the simulation.</Paragraph>
                  <Paragraph>If the order horizon is zero, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> does not
		  use order-based planning for the item involved.</Paragraph>
                  <Paragraph>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.</Paragraph>
                  <Paragraph>If you did not specify an <Link href="/baanerp/tc/glossary/glossary#000011" role="glossary">enterprise unit</Link> for the default <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> of the plan
		  item, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses the company calendar to calculate the order horizon.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>LN moves
		  the order horizon towards the end of the <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan</Link> period) in which it falls, because <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> must know whether a <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan period</Link> falls within the order horizon.</Paragraph>
               </Note>
               <SimpleSection>
                  <Paragraph>LN automatically updates the value of the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#min.otmf" role="manual">Minimum Order Horizon</GUIRef> field when you run the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session, if you selected the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.upho" role="manual">Automate Update Horizons</GUIRef> check box.</Paragraph>
               </SimpleSection>
               <SimpleSection>
                  <SectionTitle>Performance aspects</SectionTitle>
                  <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/cp/P000011_order_horizon" role="manual">Order horizon</Link>.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000023" role="manual">Horizons and time fences</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000317" role="manual">Cumulative order lead times and horizons</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="min.ptmf">
               <Header>
                  <Title>Minimum Planning Horizon</Title>
               </Header>
               <FuncDesc>The time period for which LN maintains planning
		data for an item.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The planning horizon is expressed as a number of working days
		  from the date you carry out the simulation.</Paragraph>
                  <Paragraph> 
                     <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> does not generate supply plans or planned orders beyond an
		  item's planning horizon.</Paragraph>
                  <Paragraph>To calculate the planning horizon, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses the
		  calendar that you specified for the enterprise unit of the default warehouse to
		  which the plan item belongs.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>
                     <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> moves the planning horizon to the end of the plan period in
		  which it falls.</Paragraph>
               </Note>
               <SimpleSection>
                  <Paragraph>LN automatically updates the value of the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#min.ptmf" role="manual">Minimum Planning Horizon</GUIRef> field when you run the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session, if you selected the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.upho" role="manual">Automate Update Horizons</GUIRef> check box.</Paragraph>
               </SimpleSection>
               <SimpleSection>
                  <SectionTitle>Performance aspects</SectionTitle>
                  <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/cp/P000012_planning_horizon" role="manual">Planning horizon</Link>.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000023" role="manual">Horizons and time fences</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000317" role="manual">Cumulative order lead times and horizons</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.upho">
               <Header>
                  <Title>Automate Update Horizons</Title>
               </Header>
               <FuncDesc>If this check box is selected, LN automatically updates the <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">order horizon</Link> and/or the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link> when you
				run the <GUIRef href="/baanerp/cp/rpd/cprpd1200m000" role="session">Check Horizons (cprpd1200m000)</GUIRef> session.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000316" role="manual">Lead times and horizons</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title>Master Plan</Title>
         <FieldGroup>
            <Title>Automatic Update</Title>
            <FieldHelp ID="cprpd100.aupr">
               <Header>
                  <Title>Production Plan</Title>
               </Header>
               <FuncDesc>Select one of the four update modes.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/domains/rpd.auto" role="domain">Possible Values</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.aupu">
               <Header>
                  <Title>Purchase Plan</Title>
               </Header>
               <FuncDesc>Select one of the four update modes.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/domains/rpd.auto" role="domain">Possible Values</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.auiv">
               <Header>
                  <Title>Inventory Plan</Title>
               </Header>
               <FuncDesc>Select one of the four update modes.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/domains/rpd.auto" role="domain">Possible Values</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.audf">
               <Header>
                  <Title>Demand Forecast</Title>
               </Header>
               <FuncDesc>Select one of the four update modes.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/domains/rpd.auto" role="domain">Possible Values</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title>Planning</Title>
            <FieldHelp ID="cprpd100.info">
               <Header>
                  <Title>Forecast-Based Generation Method</Title>
               </Header>
               <FuncDesc>If this check box is selected, the <Link href="/baanerp/cp/glossary/glossary#000011" role="glossary">inventory plan</Link> is generated
				on the basis of the expected demand of the plan item during a certain <Link href="/baanerp/cp/glossary/glossary#000068" role="glossary">forecast horizon</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If this check box is cleared, the inventory plan is
				  generated on the basis of the safety stock level and the seasonal pattern.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000114" role="manual">Inventory planning in Enterprise Planning</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.inho">
               <Header>
                  <Title>Forecast Horizon</Title>
               </Header>
               <FuncDesc>If this check box is selected, the <Link href="/baanerp/cp/glossary/glossary#000011" role="glossary">inventory plan</Link> is generated
				on the basis of the expected demand of the plan item during a certain <Link href="/baanerp/cp/glossary/glossary#000068" role="glossary">forecast horizon</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If this check box is cleared, the inventory plan is
				  generated on the basis of the safety stock level and the seasonal pattern.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000114" role="manual">Inventory planning in Enterprise Planning</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="inho.dt">
               <Header>
                  <Title>Date</Title>
               </Header>
               <FuncDesc>The date to which LN sets the <Link href="/baanerp/cp/glossary/glossary#000068" role="glossary">forecast horizon</Link>.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title>Work Load Control</Title>
            <FieldHelp ID="cprpd100.fica">
               <Header>
                  <Title>Constraint</Title>
               </Header>
               <FuncDesc>If this check box is selected, the availability of the
				plan item is a constraint in the planning.</FuncDesc>
               <SimpleSection>
                  <Paragraph>This field is only used in the <GUIRef href="/baanerp/cp/domains/rpd.plme#workloadcontrol" role="option">Workload Control</GUIRef> master planning method.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>You can also select the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.fica" role="manual">Constraint</GUIRef> check box for clustered items to plan them
				  with the <GUIRef href="/baanerp/cp/domains/rpd.plme#workloadcontrol" role="option">Workload Control</GUIRef> 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, LN uses the
				  same BCM warehouse: either in cluster 1 or in cluster 2.</Paragraph>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000003" role="manual">Workload control</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000027" role="manual">Workload control, to plan against constraints</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.mrpu" OtherIDs="cprpd600.dsca">
               <Header>
                  <Title>Master Plan Unit</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000004" role="glossary">plan unit</Link> for <Link href="/baanerp/cp/glossary/glossary#000059" role="glossary">master planning</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>With a master plan unit you can choose a master
				  planning engine for an item.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <List>
                     <ListIntro>You do not have to enter a plan unit in this field in
					 the following cases:</ListIntro>
                     <ListItem>The item is planned with infinite planning (not taking
					 any constraints into account).</ListItem>
                     <ListItem>The item does not have a <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary">master plan</Link> (the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.osys" role="manual">Maintain Master Plans</GUIRef> check box is cleared).</ListItem>
                     <ListItem>All supply is planned by <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order planning</Link> (the order
					 horizon has the same length as the planning horizon).</ListItem>
                     <ListItem>No production plan is generated, in other words, the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.aupr" role="manual">Production Plan</GUIRef> field has the value <GUIRef href="/baanerp/cp/domains/rpd.auto#no" role="option">No Update</GUIRef> or <GUIRef href="/baanerp/cp/domains/rpd.auto#aggregate" role="option">(Dis)aggregate</GUIRef>.</ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000025" role="manual">Plan units in Enterprise Planning</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000157" role="manual">Rules for defining plan units</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.prio">
               <Header>
                  <Title>Priority</Title>
               </Header>
               <FuncDesc>Specify the appropriate level of priority if you selected
				the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.fica" role="manual">Constraint</GUIRef> check box.</FuncDesc>
               <SimpleSection>
                  <Paragraph>Enterprise Planning takes into account the priority of a
				  plan item if you use the workload control as master-planning engine, and you
				  selected <GUIRef href="/baanerp/cp/domains/com.ynon#yes" role="option">Yes</GUIRef> or <GUIRef href="/baanerp/cp/domains/com.ynon#only" role="option">Only</GUIRef> in
				  the <GUIRef href="/baanerp/cp/wlc/cpwlc2101m000#cpwlc200.prio" role="manual">Consider Item Priority</GUIRef> field of the <GUIRef href="/baanerp/cp/wlc/cpwlc2101m000" role="session">Work Load Control Parameters (cpwlc2101m000)</GUIRef> session.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000004" role="manual">Workload control, to compute planning priorities</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title>CTP</Title>
         <FieldGroup>
            <Title>CTP Parameters</Title>
            <FieldHelp ID="cprpd100.onat">
               <Header>
                  <Title>Online ATP Update</Title>
               </Header>
               <FuncDesc>If this check box is selected, LN updates the <Link href="/baanerp/cp/glossary/glossary#000030" role="glossary">ATP</Link> for a plan item online
				if a planned or actual inventory transaction is recorded for the plan item.</FuncDesc>
               <SimpleSection>
                  <Paragraph>LN updates the ATP over the entire <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>, but only in the <Link href="/baanerp/cp/glossary/glossary#000093" role="glossary">actual scenario</Link>.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>Online ATP updates require processing power and,
				  therefore, performance. You must only use online ATP updates for:</Paragraph>
                  <List>
                     <ListItem>Items for which the CTP is checked online</ListItem>
                     <ListItem>Items for which the CTP is used during distribution
					 planning</ListItem>
                     <ListItem>Business processes that require up-to-date ATP figures</ListItem>
                  </List>
               </Note>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>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.</Paragraph>
               </Note>
               <SimpleSection>
                  <SectionTitle>Performance aspects</SectionTitle>
                  <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/cp/P000022_online_atp_update" role="manual">Online ATP update</Link>.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000039" role="manual">Online ATP update</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000116" role="manual">CTP Checking Procedure</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.cria">
               <Header>
                  <Title>Critical in CTP</Title>
               </Header>
               <FuncDesc>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.</FuncDesc>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>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.</Paragraph>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000115" role="manual">Capable-to-promise, an overview</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000123" role="manual">Component CTP</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000116" role="manual">CTP Checking Procedure</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.coat">
               <Header>
                  <Title>Component CTP</Title>
               </Header>
               <FuncDesc>If this check box is selected, LN can carry out <Link href="/baanerp/cp/glossary/glossary#000035" role="glossary">component CTP checks</Link> for
				this item.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000123" role="manual">Component CTP</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000116" role="manual">CTP Checking Procedure</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000115" role="manual">Capable-to-promise, an overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.catp">
               <Header>
                  <Title>Capacity CTP</Title>
               </Header>
               <FuncDesc>If this check box is selected, LN can carry out <Link href="/baanerp/cp/glossary/glossary#000034" role="glossary">capacity CTP checks</Link> for this item.</FuncDesc>
               <SimpleSection>
                  <Paragraph>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 <GUIRef href="/baanerp/td/sls/tdsls4899m000" role="session">ATP Handling (tdsls4899m000)</GUIRef> session is higher than the item's ATP in the <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary">item master plan</Link>, and the
				  required quantity cannot be fulfilled by the ATP alone.</Paragraph>
                  <List>
                     <ListIntro>The choice of resource to check depends partly on the <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">order horizon</Link>:</ListIntro>
                     <ListItem>If the requirement date is beyond the <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">order horizon</Link>, LN carries out the capacity CTP check using the
					 item's <Link href="/baanerp/ti/glossary/glossary#BillOfCritic_ti" role="glossary">Bill of Critical Capacities</Link>.</ListItem>
                     <ListItem>If the requirement date is before the <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">order horizon</Link>, LN carries out the capacity CTP check using the
					 item's <Link href="/baanerp/ti/glossary/glossary#Routing_ti" role="glossary">routing</Link>.</ListItem>
                  </List>
                  <Paragraph>LN checks the capacity of only the resources for which you selected the <GUIRef href="/baanerp/cp/rpd/cprpd2100m000#cprpd200.cria" role="manual">Critical in CTP</GUIRef> check box in the <GUIRef href="/baanerp/cp/rpd/cprpd2100m000" role="session">Resource (cprpd2100m000)</GUIRef> session.</Paragraph>
                  <Paragraph>LN cannot carry out capacity CTP checks if the resource has no <Link href="/baanerp/cp/glossary/glossary#000132" role="glossary">resource master plan</Link>.</Paragraph>
                  <Paragraph>If LN checked a sales order for capacity CTP, and
				  accepts and records the sales order in the Sales (SLS) module of Order
				  Management, LN carries
				  out a <Link href="/baanerp/cp/glossary/glossary#000041" role="glossary">capacity CTP reservation</Link> on the critical resources so
				  that the resource capacity cannot be given away again.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000121" role="manual">Capacity CTP</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000312" role="manual">Capacity CTP reservations</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000119" role="manual">To compute capacity CTP</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000115" role="manual">Capable-to-promise, an overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.chat">
               <Header>
                  <Title>Channel ATP</Title>
               </Header>
               <FuncDesc>If this check box is selected, LN can carry out <Link href="/baanerp/cp/glossary/glossary#000076" role="glossary">channel ATP checks</Link> for this item.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000125" role="manual">Channel ATP</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000085" role="manual">Channel ATP periods</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000115" role="manual">Capable-to-promise, an overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.tfat">
               <Header>
                  <Title>CTP Time Fence</Title>
               </Header>
               <FuncDesc>The number of working days from the current moment, during
		which LN does not
		perform CTP checks.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The CTP time fence must be smaller than the ATP/CTP
		  horizon.</Paragraph>
                  <Paragraph>During the period of the CTP time fence, CTP is considered to
		  be zero.</Paragraph>
               </SimpleSection>
               <SimpleSection>
                  <Paragraph>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.</Paragraph>
                  <Paragraph>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.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000115" role="manual">Capable-to-promise, an overview</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000023" role="manual">Horizons and time fences</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.hoat">
               <Header>
                  <Title>CTP Horizon</Title>
               </Header>
               <FuncDesc>The date until which LN performs ATP and CTP checks.</FuncDesc>
               <SimpleSection>
                  <Paragraph>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.</Paragraph>
                  <Paragraph/>
               </SimpleSection>
               <SimpleSection>
                  <Paragraph>After the ATP/CTP horizon, LN assumes that capacity
				  and components are infinite.</Paragraph>
               </SimpleSection>
               <Important>
                  <SectionTitle>Important!</SectionTitle>
                  <Paragraph>If you defined this plan item as a <Link href="/baanerp/ti/glossary/glossary#000376" role="glossary">alternative material</Link>, the value of this field must be
				  greater than the <GUIRef href="/baanerp/cp/rpd/cprpd4100m000#cprpd400.almh" role="manual">Alternative Materials Horizon</GUIRef> in the <GUIRef href="/baanerp/cp/rpd/cprpd4100m000" role="session">Scenarios (cprpd4100m000)</GUIRef> session. Otherwise, LN erroneously assumes
				  that the alternative material is infinitely available to cover for shortages of
				  the standard material.</Paragraph>
               </Important>
               <SimpleSection>
                  <SectionTitle>Performance aspects</SectionTitle>
                  <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/cp/P000013_ctp_horizon" role="manual">CTP horizon</Link>.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000116" role="manual">CTP Checking Procedure</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000454" role="manual">Use-up materials and alternative materials in Enterprise Planning</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title>Family CTP Parameters</Title>
            <FieldHelp ID="cprpd100.fatp">
               <Header>
                  <Title>Family CTP</Title>
               </Header>
               <FuncDesc>If this check box is selected, LN can carry out <Link href="/baanerp/cp/glossary/glossary#000032" role="glossary">family CTP checks</Link> for this item.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000115" role="manual">Capable-to-promise, an overview</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000120" role="manual">Family CTP</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.fasi" OtherIDs="company.dsca">
               <Header>
                  <Title>Family Site</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000077" role="glossary">family site</Link> in which you
				defined the family item that LN takes into account to perform a family ctp
				check.</FuncDesc>
               <AllowedValues>
                  <SectionTitle>Allowed values</SectionTitle>
                  <Paragraph>The <Link href="/baanerp/tc/glossary/glossary#000046" role="glossary">site</Link> must have been defined
				  in the current company.</Paragraph>
               </AllowedValues>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000115" role="manual">Capable-to-promise, an overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.fite">
               <Header>
                  <Title>Family Item</Title>
               </Header>
               <FuncDesc>The family item denotes the item to which the CTP check can
				be redirected.</FuncDesc>
               <AllowedValues>
                  <SectionTitle>Allowed values</SectionTitle>
                  <Paragraph>The item must have been defined in the family site.</Paragraph>
               </AllowedValues>
               <SimpleSection>
                  <Paragraph>The family item can be an item that you defined in
				  another logistical site.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000115" role="manual">Capable-to-promise, an overview</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000120" role="manual">Family CTP</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.atho">
               <Header>
                  <Title>Start of Family CTP Horizon</Title>
               </Header>
               <FuncDesc>The number of workdays after which the <Link href="/baanerp/cp/glossary/glossary#000033" role="glossary">family CTP horizon</Link> starts.</FuncDesc>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>The start of the family CTP horizon is rounded to the
				  end of a <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan period</Link>. As a result,
				  the family CTP horizon effectively starts at the next plan period.</Paragraph>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000115" role="manual">Capable-to-promise, an overview</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000120" role="manual">Family CTP</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title>Net Change</Title>
         <FieldGroup>
            <Title>Phase Numbers</Title>
            <FieldHelp ID="cprpd100.phnu">
               <Header>
                  <Title>Master Phase Number</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000045" role="glossary">phase number</Link> for <Link href="/baanerp/cp/glossary/glossary#000059" role="glossary">master planning</Link>.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000156" role="manual">Planning sequence and phase numbers</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.mrph">
               <Header>
                  <Title>Order Phase Number</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000045" role="glossary">phase number</Link> for <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order planning</Link>.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000156" role="manual">Planning sequence and phase numbers</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.sphc">
               <Header>
                  <Title>Master Phase Number Parent</Title>
               </Header>
               <FuncDesc>This field contains the maximum master <Link href="/baanerp/cp/glossary/glossary#000045" role="glossary">phase number</Link> of any of the
				parents of the item in one of the following relationships: <Link href="/baanerp/ti/glossary/glossary#000081" role="glossary">BCM</Link> or <Link href="/baanerp/cp/glossary/glossary#000005" role="glossary">Supplying relationships</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If the value of the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.phnu" role="manual">Master Phase Number</GUIRef> field is smaller or equal to the value of the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.sphc" role="manual">Master Phase Number Parent</GUIRef> field, the master phase number must be recomputed.</Paragraph>
                  <Paragraph>You can recompute phase numbers by means of the <GUIRef href="/baanerp/cp/rpd/cprpd6200m000" role="session">Compute Phase Numbers (cprpd6200m000)</GUIRef> session.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000156" role="manual">Planning sequence and phase numbers</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000055" role="manual">Net-change phase number computation</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.phch">
               <Header>
                  <Title>Order Phase Number Parent</Title>
               </Header>
               <FuncDesc>This field contains the maximum order <Link href="/baanerp/cp/glossary/glossary#000045" role="glossary">phase number</Link> of any of the
				parents of the item in one of the following relationships: <Link href="/baanerp/ti/glossary/glossary#BillOfMateri_ti" role="glossary">BOM</Link> or <Link href="/baanerp/cp/glossary/glossary#000005" role="glossary">supplying relationships</Link>.</FuncDesc>
               <DefaultValue>
                  <SectionTitle>Default value</SectionTitle>
                  <Paragraph>The default value is -1.</Paragraph>
               </DefaultValue>
               <SimpleSection>
                  <Paragraph>If the value of the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.mrph" role="manual">Order Phase Number</GUIRef> field is smaller or equal to the value of the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.phch" role="manual">Order Phase Number Parent</GUIRef> field, the phase number must be recomputed.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000156" role="manual">Planning sequence and phase numbers</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000055" role="manual">Net-change phase number computation</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title>Net Change</Title>
            <FieldHelp ID="cprpd100.netc">
               <Header>
                  <Title>Net Change</Title>
               </Header>
               <FuncDesc>If this check box is selected, a change occurred that
				affects one or both of the following plans:</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListItem>The <Link href="/baanerp/cp/glossary/glossary#000059" role="glossary">master planning</Link> of the item
					 (for example, a change in the <Link href="/baanerp/ti/glossary/glossary#BillOfMateri_ti" role="glossary">bill of material (BOM)</Link>.</ListItem>
                     <ListItem>The <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order planning</Link> of the item
					 (for example, a change in the BOM, or the acceptance of a customer order).</ListItem>
                  </List>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000026" role="manual">Net-change simulations</Link>
                  </RelTopic>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000015" role="manual">Simulated time period (RRP run)</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cprpd100.netd">
               <Header>
                  <Title>Net Change Date</Title>
               </Header>
               <FuncDesc>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.</FuncDesc>
               <SimpleSection>
                  <Paragraph>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.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="cprpd100.pnet">
               <Header>
                  <Title>Pegging Net Change</Title>
               </Header>
               <FuncDesc>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.</FuncDesc>
               <SimpleSection>
                  <Paragraph>For more information, refer to the <Link href="/baanerp/cp/onlinemanual/000076#net.change" role="manual">Net-change pegging update</Link> section in <Link href="/baanerp/cp/onlinemanual/000076" role="manual">Pegging for planned orders</Link>.</Paragraph>
               </SimpleSection>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
   </Fields>
   <FormCommands>
      <CommandHelp ID="view.tree">
         <Header>
            <Title>View Family Structure</Title>
         </Header>
         <FuncDesc>Displays a <Link href="/baanerp/cp/glossary/glossary#000371" role="glossary">exception message</Link> overview in a tree format.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>