<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/cp/rrp/cprrp0520m000" xml:lang="en">
   <Header>
      <Title>Item Order Plan (cprrp0520m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to get a time-phased
		  overview of your order planning, which lists overview values for demand and
		  forecast on the one hand, and scheduled receipts (actual orders) and planned
		  supply (planned orders) on the other. Click the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#sim.input" role="manual">Simulate</GUIRef> field to
		  change the above values and see what the results are for the <Link href="/baanerp/cp/glossary/glossary#000046" role="glossary">projected inventory</Link>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>The order quantities
		  of the orders that fall in one period are added up. Click the Find button to
		  choose one of a set of predefined period lengths. Instead of selecting a time
		  period, you can also choose to display a detailed overview in which each order
		  is listed separately.</Paragraph>
         <Paragraph>You can click Change
		  Company on the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu, to zoom to the <GUIRef href="/baanerp/cp/com/cpcom1200s000" role="session">Change Company (cpcom1200s000)</GUIRef> session. Here you can switch to a different logistical
		  company.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>The Group commands
				are disabled in this session, because the displayed data is not read directly
				from a database, but is computed (aggregated) online. If you want to view other
				data, click Find.</ListItem>
               <ListItem>If you have started
				this session by zooming, you can only find and select a record.</ListItem>
            </List>
         </Note>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The horizon of the <Link href="/baanerp/cp/glossary/glossary#000370" role="glossary">item order plan</Link> is equal to the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>, because
			 you must be able to see an order when it is moved from the <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary">item master plan</Link> to a
			 planned order before you release it.</Paragraph>
         </Note>
         <Paragraph>If you move the <Link href="/baanerp/cp/glossary/glossary#000018" role="glossary">production plan</Link> or the <Link href="/baanerp/cp/glossary/glossary#000023" role="glossary">purchase plan</Link> to planned
		  orders with the <GUIRef href="/baanerp/cp/rmp/cprmp2240m000" role="session">Convert Master Plan to Planned Orders (cprmp2240m000)</GUIRef> session, the resulting orders have the order type
		  Production Plan and Purchase Plan in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000" role="session">Item Order Plan (cprrp0520m000)</GUIRef> session.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Customized items derived from this item</SectionTitle>
         <Paragraph>To view all transactions for an item and the <Link href="/baanerp/ti/glossary/glossary#CustomItem_ti" role="glossary">customized items</Link> derived from the item, click the <Link href="/baanerp/cp/rrp/cprrp0520m000#toggle.item.overview" role="command">Toggle Item View</Link> button.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000021" role="manual">Order planning, an overview</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/basictasks/000001" role="manual">To use an overview session</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000020" role="manual">Master planning, an overview</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000086" role="manual">To maintain an item master plan</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000049" role="manual">To update master-plan data</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000084" role="manual">To maintain a resource master plan</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000329" role="manual">Forecast Consumption without an Item Master Plan</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="e.scenario">
         <Header>
            <Title>Scenario</Title>
         </Header>
         <FuncDesc>This code indicates that ERP Enterprise displays the <Link href="/baanerp/cp/glossary/glossary#000370" role="glossary">item order plan</Link> for the <Link href="/baanerp/cp/glossary/glossary#000093" role="glossary">actual scenario</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="f.plan.item" OtherIDs="e.plan.item.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>
      </FieldHelp>
      <FieldGroup>
         <Title>Horizons</Title>
         <FieldHelp ID="tmfc.dt">
            <Header>
               <Title>Time Fence</Title>
            </Header>
            <FuncDesc>The date to which the <Link href="/baanerp/cp/glossary/glossary#000063" role="glossary">time fence</Link> extends.</FuncDesc>
            <SimpleSection>
               <Paragraph>You can specify
				the time fence in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef> session.</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="fctf.dt">
            <Header>
               <Title>Forecast Time Fence</Title>
            </Header>
            <FuncDesc>The date to which the <Link href="/baanerp/cp/glossary/glossary#000067" role="glossary">forecast time fence</Link> extends.</FuncDesc>
            <SimpleSection>
               <Paragraph>You can specify
				the forecast time fence in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef> session.</Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>The forecast time
				fence is only used if the item has an <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary">item master plan</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/000411" role="manual">Time fences in order planning and in master planning</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="otmf.dt">
            <Header>
               <Title>Order Horizon</Title>
            </Header>
            <FuncDesc>The date to which the <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">order horizon</Link> extends.</FuncDesc>
            <SimpleSection>
               <Paragraph>You can specify
				the order horizon in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef> session.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000023" role="manual">Horizons and time fences</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="ptmf.dt">
            <Header>
               <Title>Planning Horizon</Title>
            </Header>
            <FuncDesc>The date to which the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link> extends.</FuncDesc>
            <SimpleSection>
               <Paragraph>You can specify
				the planning horizon in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef> session.</Paragraph>
               <Paragraph>Whenever you move
				a plan to planned orders, you must be able to see the orders before you
				transfer them to execution level. This is why the <Link href="/baanerp/cp/glossary/glossary#000370" role="glossary">item order plan</Link> uses the planning horizon. If the item does not have an <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary">item master plan</Link>, the
				planning horizon is equal to the <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">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>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="hoat.dt">
            <Header>
               <Title>ATP Horizon</Title>
            </Header>
            <FuncDesc>
               <Link href="/baanerp/cp/rpd/cprpd1110m000#cprpd101.hoat" role="formfield">CTP Horizon</Link>
            </FuncDesc>
         </FieldHelp>
         <FieldHelp ID="netchangedate">
            <Header>
               <Title>Net Change Date</Title>
            </Header>
            <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000079" role="glossary">net change date</Link> for order
			 planning (see the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef> session).</FuncDesc>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000026" role="manual">Net-change simulations</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>General</Title>
         <FieldHelp ID="cprpd100.plid" OtherIDs="planner.nama">
            <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 ERP Enterprise generates.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="cost.price">
            <Header>
               <Title>Cost Price</Title>
            </Header>
            <FuncDesc>The cost incurred by manufacturing or purchasing a single item
		(inventory valuation).</FuncDesc>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>ERP Enterprise retrieves the value of the
				current field from the <GUIRef href="/baanerp/ti/cpr/ticpr0107m000#ticpr007.acpr" role="manual">Cost Price</GUIRef> field in
				the <GUIRef href="/baanerp/ti/cpr/ticpr0107m000" role="session">Items - Costing (ticpr0107m000)</GUIRef> session.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="actual.sour">
            <Header>
               <Title>Actual Supply Source</Title>
            </Header>
            <FuncDesc>The actual supply source of the item.</FuncDesc>
            <SimpleSection>
               <Paragraph>If you define a
				date effectivity line in the <GUIRef href="/baanerp/tc/ibd/tcibd0510m000" role="session">Date-Effective Item Data (tcibd0510m000)</GUIRef> session, the actual source can be time-dependent.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="total.demand">
            <Header>
               <Title>Total Demand</Title>
            </Header>
            <FuncDesc>The total (forecast and actual) demand displayed in this
			 session.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="item.stock" OtherIDs="inventory.unit">
            <Header>
               <Title>Inventory on Hand</Title>
            </Header>
            <FuncDesc>The physical quantity of goods in one or more warehouses
		(including the inventory on hold).</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>Project Peg</Title>
         <FieldHelp ID="rrp0521.project">
            <Header>
               <Title>Project</Title>
            </Header>
            <FuncDesc>
               <Link href="/baanerp/tp/pdm/tppdm6100m000#tppdm600.cprj" role="formfield">Project</Link>
            </FuncDesc>
         </FieldHelp>
         <FieldHelp ID="rrp0521.element">
            <Header>
               <Title>Element</Title>
            </Header>
            <FuncDesc>
               <Link href="/baanerp/cp/rrp/cprrp0101s000#cprrp001.cspa" role="formfield">Element</Link>
            </FuncDesc>
         </FieldHelp>
         <FieldHelp ID="rrp0521.activity">
            <Header>
               <Title>Activity</Title>
            </Header>
            <FuncDesc>
               <Link href="/baanerp/cp/rrp/cprrp0101s000#cprrp001.cact" role="formfield">Activity</Link>
            </FuncDesc>
         </FieldHelp>
      </FieldGroup>
   </Fields>
   <Fields>
      <FieldGroup>
         <Title>Overview</Title>
         <FieldHelp ID="end.date">
            <Header>
               <Title>Date</Title>
            </Header>
            <FuncDesc>The end date and time of the period.</FuncDesc>
            <SimpleSection>
               <Paragraph>The displayed
				periods are defined by the period length (specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field) and
				the start date of the <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>. The first
				displayed period starts on the start date of the scenario. The last displayed
				period is determined by the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>. The period
				in which the planning horizon falls is the last displayed period.</Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>If you chose the <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef> option in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field, the
				last displayed line is the last order that occurs in the order horizon.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="sim.input">
            <Header>
               <Title>Simulate</Title>
            </Header>
            <FuncDesc>You can use this field to enter additional demand or an
			 additional supply of the <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>.</FuncDesc>
            <SimpleSection>
               <Paragraph>You can simulate
				an additional demand by entering a negative quantity. You can simulate an
				additional scheduled receipt or an additional planned supply by entering a
				positive quantity.</Paragraph>
               <Paragraph>If you want to see
				the results of the simulation, click the Update icon.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="koor">
            <Header>
               <Title>Order Type</Title>
            </Header>
            <FuncDesc>The order type of the order involved.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="orno">
            <Header>
               <Title>Order Number</Title>
            </Header>
            <FuncDesc>This field is filled when you choose a detailed overview, or
			 the period of the planned inventory movements contains only one order. This
			 field contains the order number.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="order.plni">
            <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>
         </FieldHelp>
         <FieldHelp ID="order.status">
            <Header>
               <Title>Order Status</Title>
            </Header>
            <FuncDesc>The status assigned to a planned order in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</FuncDesc>
            <SimpleSection>
               <List>
                  <ListIntro>The order status can either be:</ListIntro>
                  <ListItem> 
                     <GUIRef href="/baanerp/cp/domains/rrp.osta#planned" role="option">Planned</GUIRef>
                  </ListItem>
                  <ListItem> 
                     <GUIRef href="/baanerp/cp/domains/rrp.osta#firmplanned" role="option">Firm Planned</GUIRef>
                  </ListItem>
                  <ListItem> 
                     <GUIRef href="/baanerp/cp/domains/rrp.osta#confirmed" role="option">Confirmed</GUIRef>
                  </ListItem>
               </List>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="demand">
            <Header>
               <Title>Demand</Title>
            </Header>
            <FuncDesc>The demand for the <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link> expressed in the number of items.</FuncDesc>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>If the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field has
				the value <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef>, you can see where
				the demand originates in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#orno" role="manual">Order Number</GUIRef> field and the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#koor" role="manual">Order Type</GUIRef> field on the <GUIRef href="" role="manual">Detail</GUIRef> tab.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="supply.quantity">
            <Header>
               <Title>Supply</Title>
            </Header>
            <FuncDesc>The sum of the scheduled receipts and the <Link href="/baanerp/wh/glossary/glossary#000366" role="glossary">planned receipt</Link>.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="pl.available">
            <Header>
               <Title>Planned Available</Title>
            </Header>
            <FuncDesc>The expected inventory level at the end of a plan
		period.</FuncDesc>
            <SimpleSection>
               <Paragraph>Note that the projected inventory of plan periods that are
		  entirely in the past equals the inventory on hand.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="atp">
            <Header>
               <Title>ATP</Title>
            </Header>
            <FuncDesc>The item quantity that is still available to be promised to a
		customer.</FuncDesc>
            <SimpleSection>
               <Paragraph>In ERP Enterprise,
		  available-to-promise (ATP) is part of a more extended framework of order
		  promising techniques called capable-to-promise (CTP). If an item's ATP is
		  insufficient, CTP goes beyond ATP in that it also considers the possibility of
		  producing more than was initially planned.</Paragraph>
               <Paragraph>In addition to the standard ATP functionality, ERP Enterprise also uses channel ATP.
		  This term refers to the availability of an item for a certain sales channel,
		  taking into account the sales limits for that channel.</Paragraph>
               <Paragraph>For all other types of order promising functionality used in ERP Enterprise, the term CTP is used.</Paragraph>
               <Paragraph>Acronym:</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000311" role="manual">Item ATP</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="safety.stock">
            <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>
         </FieldHelp>
         <FieldHelp ID="effn">
            <Header>
               <Title>Effectivity Unit</Title>
            </Header>
            <FuncDesc>The number of the effectivity unit involved in this
			 transaction.</FuncDesc>
            <SimpleSection>
               <Paragraph>You can define <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity units</Link> in the <GUIRef href="/baanerp/tc/uef/tcuef0502m000" role="session">Effectivity Units (tcuef0502m000)</GUIRef> session.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/tc/glossary/glossary#000306" role="glossary">unit effectivity</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="e.spec.present">
            <Header>
               <Title>Specification</Title>
            </Header>
            <FuncDesc>If this check box is selected, a <Link href="/baanerp/cp/glossary/glossary#000455" role="glossary">specification</Link> is present.</FuncDesc>
            <SimpleSection>
               <Paragraph>To display the specification, in the <GUIRef href="" role="manual" Update="No">appropriate</GUIRef> menu, click <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#start.specification" role="manual">Specification</GUIRef>.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldGroup>
            <Title>Initial Hidden</Title>
            <FieldHelp ID="end.date">
               <Header>
                  <Title>Date</Title>
               </Header>
               <FuncDesc>The end date and time of the period.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The displayed
				  periods are defined by the period length (specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field) and
				  the start date of the <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>. The first
				  displayed period starts on the start date of the scenario. The last displayed
				  period is determined by the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>. The period
				  in which the planning horizon falls is the last displayed period.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>If you chose the <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef> option in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field, the
				  last displayed line is the last order that occurs in the order horizon.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="position">
               <Header>
                  <Title>Line Position Number</Title>
               </Header>
               <FuncDesc>Dependent on the order type, ERP Enterprise displays the number of
				the <Link href="/baanerp/fm/glossary/glossary#000010" role="glossary">order line</Link>.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="order.plni" OtherIDs="plni.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>
            </FieldHelp>
            <FieldHelp ID="pl.order.due">
               <Header>
                  <Title>Planned Supply</Title>
               </Header>
               <FuncDesc>The number of plan items that you expect to receive
				according to the <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order(s)</Link>.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>The number of items is displayed either:</ListIntro>
                     <ListItem>By period, if a
					 period is specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field.</ListItem>
                     <ListItem>By planned
					 order, if the value of the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field is <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef>.</ListItem>
                  </List>
                  <Paragraph>You can change
				  the planned orders for which a number of items is displayed in the current
				  field.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>ERP Enterprise retrieves the planned supply
				  data from the <GUIRef href="/baanerp/cp/rrp/cprrp1100m000" role="session">Planned Orders (cprrp1100m000)</GUIRef> session.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="sched.rec">
               <Header>
                  <Title>Scheduled Receipts</Title>
               </Header>
               <FuncDesc>The number of items that you expect to receive according
				to the orders that are transferred to the <Link href="/baanerp/cp/glossary/glossary#000027" role="glossary">execution level</Link>.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>Transferred orders are, for example:</ListIntro>
                     <ListItem> 
                        <Link href="/baanerp/ti/glossary/glossary#000022" role="glossary">production order</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/td/glossary/glossary#PurchaOrders_td" role="glossary">purchase order</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/wh/glossary/glossary#000388" role="glossary">warehousing order</Link>
                     </ListItem>
                  </List>
                  <List>
                     <ListIntro>The number of items is displayed either:</ListIntro>
                     <ListItem>By period, if a
					 period is specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field.</ListItem>
                     <ListItem>By order, if the
					 value of the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field is <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef>.</ListItem>
                  </List>
                  <Paragraph>You cannot
				  change the transferred orders in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>ERP Enterprise retrieves the scheduled receipt
				  data from the <GUIRef href="/baanerp/wh/inp/whinp1500m000" role="session">Planned Inventory Transactions (whinp1500m000)</GUIRef> session.</Paragraph>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000010" role="manual">To transfer orders to the execution level</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="depd.comp">
               <Header>
                  <Title>Receiving Site</Title>
               </Header>
               <FuncDesc>
                  <Link href="/baanerp/cp/rrp/cprrp0511m000#cprrp010.resi" role="formfield">Receiving Site</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="depending.item" OtherIDs="receiv.item.dsca">
               <Header>
                  <Title>Receiving Item</Title>
               </Header>
               <FuncDesc>The receiving <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="dest.cwar" OtherIDs="dest.cwar.desc">
               <Header>
                  <Title>Warehouse</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> in which the items are received, or from which
				the items are issued.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="supplier">
               <Header>
                  <Title>Business Partner</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#ShipfrBusine_tc" role="glossary">ship-from business partner</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If no ship-from
				  business partner is known, the <Link href="/baanerp/tc/glossary/glossary#BuyfroBusine_tc" role="glossary">buy-from business partner</Link> is
				  displayed instead.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="supl.comp">
               <Header>
                  <Title>Supplying Site</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000115" role="glossary">supplying site</Link>.</FuncDesc>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>This field always contains a value. In case of <Link href="/baanerp/cp/glossary/glossary#000047" role="glossary">planned production order</Link> or <Link href="/baanerp/cp/glossary/glossary#000048" role="glossary">planned purchase order</Link> the value is set to the current
				  company.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="supplying.item">
               <Header>
                  <Title>Supplying Item</Title>
               </Header>
               <FuncDesc>The supplying <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="org.pldt">
               <Header>
                  <Title>Ordered Date</Title>
               </Header>
               <FuncDesc>
                  <Link href="/baanerp/cp/rrp/cprrp0520m000#org.pldt" role="formfield">Ordered Date</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="org.qana">
               <Header>
                  <Title>Ordered Quantity</Title>
               </Header>
               <FuncDesc>The quantity of item ordered.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cur.date">
               <Header>
                  <Title>Order Confirm Date</Title>
               </Header>
               <FuncDesc>The date on which the order is confirmed.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cur.qana">
               <Header>
                  <Title>Confirmed Quantity</Title>
               </Header>
               <FuncDesc>The total confirmed quantity of the item ordered.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="effn">
               <Header>
                  <Title>Effectivity Unit</Title>
               </Header>
               <FuncDesc>A reference number, for example a sales order line or a project
		deliverable line, that is used to model deviations for a unit effective item.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bp">
               <Header>
                  <Title>Demand Pegged to BP</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary">sold-to business partner</Link> to which this
				supply was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>. If this record involves a demand, this field
				indicates the sold-to business partner to which the supply that can fill this
				demand must have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bot">
               <Header>
                  <Title>Demand Pegged to Business Object Type</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the
				type of order to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>, such as, <GUIRef href="/baanerp/tc/domains/albt#sales" role="option">Sales Order</GUIRef>,
				or <GUIRef href="/baanerp/tc/domains/albt#service" role="option">Service Order</GUIRef>. If this record involves a demand, this field indicates the type
				of order to which the supply that can fill this demand must have been allocated
				or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <List>
                     <ListIntro>The following fields are always used in combination;
					 together, they identify the relevant order or order line:</ListIntro>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bot" role="manual">Demand Pegged to Business Object Type</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bo" role="manual">Demand Pegged to Business Object</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bor" role="manual">Demand Pegged to Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bo" OtherIDs="e.alloc.to.bor">
               <Header>
                  <Title>Demand Pegged to Business Object</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>, or order line, to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>, such as, <GUIRef href="/baanerp/tc/domains/albt#sales" role="option">Sales Order</GUIRef>,
				or <GUIRef href="/baanerp/tc/domains/albt#service" role="option">Service Order</GUIRef>. If this record involves a demand, this field indicates the <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>, or order line, to which the supply that can fill
				this demand must have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <List>
                     <ListIntro>The following fields are always used in combination;
					 together, they identify the relevant order or order line:</ListIntro>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bot" role="manual">Demand Pegged to Business Object Type</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bo" role="manual">Demand Pegged to Business Object</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bor" role="manual">Demand Pegged to Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.ref">
               <Header>
                  <Title>Demand Pegged to Reference</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the
				reference code to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>. If this record involves a demand, this field
				indicates the reference code to which the supply that can fill this demand must
				have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to find a matching supply for this
				  demand.</Paragraph>
                  <Paragraph>ERP Enterprise uses the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.ref" role="manual">Demand Pegged to Reference</GUIRef> field to record an internal
				  reference.</Paragraph>
                  <Paragraph>You can use a reference code to keep a collection of
				  parts linked together, even if they follow different routings, for example, if
				  some of the parts are transported to a subcontractor to be returned later.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.use.unalloc.inv">
               <Header>
                  <Title>Use Unallocated Inventory</Title>
               </Header>
               <FuncDesc>If this check box is selected, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> can use
				unallocated inventory to supply the demand. <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses
				allocated inventory first. If there is not enough allocated inventory, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> also
				uses unallocated inventory.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If this check box is cleared, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> can use
				  only allocated inventory to fill the demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.option.list.id">
               <Header>
                  <Title>Option List ID</Title>
               </Header>
               <FuncDesc>
                  <Link href="/baanerp/cp/rrp/cprrp0520m000#e.option.list.id" role="formfield">Option List ID</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.ppeg.poject">
               <Header>
                  <Title>Project</Title>
               </Header>
               <FuncDesc>View the project peg the order belongs to.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.ppeg.pl.group">
               <Header>
                  <Title>Planning Group</Title>
               </Header>
               <FuncDesc>
                  <Link href="/baanerp/cp/rrp/cprrp1210m000#plgr.f" role="formfield">Planning Group</Link>
               </FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title>Demand</Title>
         <FieldHelp ID="end.date">
            <Header>
               <Title>Date</Title>
            </Header>
            <FuncDesc>The end date and time of the period.</FuncDesc>
            <SimpleSection>
               <Paragraph>The displayed
				periods are defined by the period length (specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field) and
				the start date of the <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>. The first
				displayed period starts on the start date of the scenario. The last displayed
				period is determined by the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>. The period
				in which the planning horizon falls is the last displayed period.</Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>If you chose the <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef> option in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field, the
				last displayed line is the last order that occurs in the order horizon.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="koor">
            <Header>
               <Title>Order Type</Title>
            </Header>
            <FuncDesc>The order type of the order involved.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="orno">
            <Header>
               <Title>Order Number</Title>
            </Header>
            <FuncDesc>This field is filled when you choose a detailed overview, or
			 the period of the planned inventory movements contains only one order. This
			 field contains the order number.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="position">
            <Header>
               <Title>Line Position Number</Title>
            </Header>
            <FuncDesc>Dependent on the order type, ERP Enterprise displays the number of
			 the <Link href="/baanerp/fm/glossary/glossary#000010" role="glossary">order line</Link>.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="demand">
            <Header>
               <Title>Demand</Title>
            </Header>
            <FuncDesc>The demand for the <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link> expressed in the number of items.</FuncDesc>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>If the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field has
				the value <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef>, you can see where
				the demand originates in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#orno" role="manual">Order Number</GUIRef> field and the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#koor" role="manual">Order Type</GUIRef> field on the <GUIRef href="" role="manual">Detail</GUIRef> tab.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="order.status">
            <Header>
               <Title>Order Status</Title>
            </Header>
            <FuncDesc>The status assigned to a planned order in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</FuncDesc>
            <SimpleSection>
               <List>
                  <ListIntro>The order status can either be:</ListIntro>
                  <ListItem> 
                     <GUIRef href="/baanerp/cp/domains/rrp.osta#planned" role="option">Planned</GUIRef>
                  </ListItem>
                  <ListItem> 
                     <GUIRef href="/baanerp/cp/domains/rrp.osta#firmplanned" role="option">Firm Planned</GUIRef>
                  </ListItem>
                  <ListItem> 
                     <GUIRef href="/baanerp/cp/domains/rrp.osta#confirmed" role="option">Confirmed</GUIRef>
                  </ListItem>
               </List>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="project">
            <Header>
               <Title>Project</Title>
            </Header>
            <FuncDesc>A collection of manufacturing and purchasing actions that are
		performed especially for a particular customer order. A project is initiated by
		a customer order for items having a <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> order policy. The purpose of a project is to plan and coordinate the production
		of these items.</FuncDesc>
            <SimpleSection>
               <List>
                  <ListIntro>For a standard-to-order production, the project is only
			 used to link the item with the customer order. Otherwise, a project can
			 include:</ListIntro>
                  <ListItem>Customized item data (BOMs and routings)</ListItem>
                  <ListItem>Project planning (activity planning)</ListItem>
               </List>
               <Paragraph>A budget is a special type of project. A budget is used to
		  plan and estimate, not to carry out production.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="order.plni">
            <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>
         </FieldHelp>
         <FieldHelp ID="dest.cwar" OtherIDs="dest.cwar.desc">
            <Header>
               <Title>Warehouse</Title>
            </Header>
            <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> in which the items are received, or from which
			 the items are issued.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="depd.comp">
            <Header>
               <Title>Receiving Site</Title>
            </Header>
            <FuncDesc>
               <Link href="/baanerp/cp/rrp/cprrp0511m000#cprrp010.resi" role="formfield">Receiving Site</Link>
            </FuncDesc>
         </FieldHelp>
         <FieldHelp ID="depending.item" OtherIDs="receiv.item.dsca">
            <Header>
               <Title>Receiving Item</Title>
            </Header>
            <FuncDesc>The receiving <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>
            </FuncDesc>
         </FieldHelp>
         <FieldHelp ID="effn">
            <Header>
               <Title>Effectivity Unit</Title>
            </Header>
            <FuncDesc>The number of the effectivity unit involved in this
			 transaction.</FuncDesc>
            <SimpleSection>
               <Paragraph>You can define <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity units</Link> in the <GUIRef href="/baanerp/tc/uef/tcuef0502m000" role="session">Effectivity Units (tcuef0502m000)</GUIRef> session.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/tc/glossary/glossary#000306" role="glossary">unit effectivity</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="e.spec.present">
            <Header>
               <Title>Specification</Title>
            </Header>
            <FuncDesc>If this check box is selected, a <Link href="/baanerp/cp/glossary/glossary#000455" role="glossary">specification</Link> is present.</FuncDesc>
            <SimpleSection>
               <Paragraph>To display the specification, in the <GUIRef href="" role="manual" Update="No">appropriate</GUIRef> menu, click <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#cprrp0501m000" role="command">Specification</GUIRef>.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldGroup>
            <Title>Initial Hidden</Title>
            <FieldHelp ID="end.date">
               <Header>
                  <Title>Date</Title>
               </Header>
               <FuncDesc>The end date and time of the period.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The displayed
				  periods are defined by the period length (specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field) and
				  the start date of the <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>. The first
				  displayed period starts on the start date of the scenario. The last displayed
				  period is determined by the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>. The period
				  in which the planning horizon falls is the last displayed period.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>If you chose the <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef> option in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field, the
				  last displayed line is the last order that occurs in the order horizon.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="pl.available">
               <Header>
                  <Title>Planned Available</Title>
               </Header>
               <FuncDesc>The expected inventory level at the end of a plan
		period.</FuncDesc>
               <SimpleSection>
                  <Paragraph>Note that the projected inventory of plan periods that are
		  entirely in the past equals the inventory on hand.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="atp">
               <Header>
                  <Title>ATP</Title>
               </Header>
               <FuncDesc>The item quantity that is still available to be promised to a
		customer.</FuncDesc>
               <SimpleSection>
                  <Paragraph>In ERP Enterprise,
		  available-to-promise (ATP) is part of a more extended framework of order
		  promising techniques called capable-to-promise (CTP). If an item's ATP is
		  insufficient, CTP goes beyond ATP in that it also considers the possibility of
		  producing more than was initially planned.</Paragraph>
                  <Paragraph>In addition to the standard ATP functionality, ERP Enterprise also uses channel ATP.
		  This term refers to the availability of an item for a certain sales channel,
		  taking into account the sales limits for that channel.</Paragraph>
                  <Paragraph>For all other types of order promising functionality used in ERP Enterprise, the term CTP is used.</Paragraph>
                  <Paragraph>Acronym:</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000311" role="manual">Item ATP</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="safety.stock">
               <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>
            </FieldHelp>
            <FieldHelp ID="order.plni" OtherIDs="plni.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>
            </FieldHelp>
            <FieldHelp ID="depending.item" OtherIDs="receiv.item.dsca">
               <Header>
                  <Title>Receiving Item</Title>
               </Header>
               <FuncDesc>The receiving <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="org.pldt">
               <Header>
                  <Title>Ordered Date</Title>
               </Header>
               <FuncDesc>The date on which the order is created.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="org.qana">
               <Header>
                  <Title>Ordered Quantity</Title>
               </Header>
               <FuncDesc>The quantity of item ordered.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cur.date">
               <Header>
                  <Title>Order Confirm Date</Title>
               </Header>
               <FuncDesc>The date on which the order is confirmed.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cur.qana">
               <Header>
                  <Title>Confirmed Quantity</Title>
               </Header>
               <FuncDesc>The total confirmed quantity of the item ordered.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cur.qana">
               <Header>
                  <Title>Confirmed Quantity</Title>
               </Header>
               <FuncDesc>The total confirmed quantity of the item ordered.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="effn">
               <Header>
                  <Title>Effectivity Unit</Title>
               </Header>
               <FuncDesc>A reference number, for example a sales order line or a project
		deliverable line, that is used to model deviations for a unit effective item.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bp">
               <Header>
                  <Title>Demand Pegged to BP</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary">sold-to business partner</Link> to which this
				supply was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>. If this record involves a demand, this field
				indicates the sold-to business partner to which the supply that can fill this
				demand must have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bot">
               <Header>
                  <Title>Demand Pegged to Business Object Type</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the
				type of order to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>, such as, <GUIRef href="/baanerp/tc/domains/albt#sales" role="option">Sales Order</GUIRef>,
				or <GUIRef href="/baanerp/tc/domains/albt#service" role="option">Service Order</GUIRef>. If this record involves a demand, this field indicates the type
				of order to which the supply that can fill this demand must have been allocated
				or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <List>
                     <ListIntro>The following fields are always used in combination;
					 together, they identify the relevant order or order line:</ListIntro>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bot" role="manual">Demand Pegged to Business Object Type</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bo" role="manual">Demand Pegged to Business Object</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bor" role="manual">Demand Pegged to Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bo" OtherIDs="e.alloc.to.bor">
               <Header>
                  <Title>Demand Pegged to Business Object</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>, or order line, to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>, such as, <GUIRef href="/baanerp/tc/domains/albt#sales" role="option">Sales Order</GUIRef>,
				or <GUIRef href="/baanerp/tc/domains/albt#service" role="option">Service Order</GUIRef>. If this record involves a demand, this field indicates the <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>, or order line, to which the supply that can fill
				this demand must have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <List>
                     <ListIntro>The following fields are always used in combination;
					 together, they identify the relevant order or order line:</ListIntro>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bot" role="manual">Demand Pegged to Business Object Type</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bo" role="manual">Demand Pegged to Business Object</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bor" role="manual">Demand Pegged to Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.ref">
               <Header>
                  <Title>Demand Pegged to Reference</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the
				reference code to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>. If this record involves a demand, this field
				indicates the reference code to which the supply that can fill this demand must
				have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to find a matching supply for this
				  demand.</Paragraph>
                  <Paragraph>ERP Enterprise uses the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.ref" role="manual">Demand Pegged to Reference</GUIRef> field to record an internal
				  reference.</Paragraph>
                  <Paragraph>You can use a reference code to keep a collection of
				  parts linked together, even if they follow different routings, for example, if
				  some of the parts are transported to a subcontractor to be returned later.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.use.unalloc.inv">
               <Header>
                  <Title>Use Unallocated Inventory</Title>
               </Header>
               <FuncDesc>If this check box is selected, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> can use
				unallocated inventory to supply the demand. <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses
				allocated inventory first. If there is not enough allocated inventory, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> also
				uses unallocated inventory.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If this check box is cleared, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> can use
				  only allocated inventory to fill the demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.option.list.id">
               <Header>
                  <Title>Option List ID</Title>
               </Header>
               <FuncDesc>
                  <Link href="/baanerp/cp/rrp/cprrp0520m000#e.option.list.id" role="formfield">Option List ID</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.ppeg.poject">
               <Header>
                  <Title>Project</Title>
               </Header>
               <FuncDesc>View the project peg the order belongs to.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.ppeg.pl.group">
               <Header>
                  <Title>Planning Group</Title>
               </Header>
               <FuncDesc>
                  <Link href="/baanerp/cp/rrp/cprrp0520m000#e.ppeg.pl.group" role="formfield">Planning Group</Link>
               </FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title>Supply</Title>
         <FieldHelp ID="end.date">
            <Header>
               <Title>Date</Title>
            </Header>
            <FuncDesc>The end date and time of the period.</FuncDesc>
            <SimpleSection>
               <Paragraph>The displayed
				periods are defined by the period length (specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field) and
				the start date of the <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>. The first
				displayed period starts on the start date of the scenario. The last displayed
				period is determined by the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>. The period
				in which the planning horizon falls is the last displayed period.</Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>If you chose the <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef> option in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field, the
				last displayed line is the last order that occurs in the order horizon.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="koor">
            <Header>
               <Title>Order Type</Title>
            </Header>
            <FuncDesc>The order type of the order involved.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="orno">
            <Header>
               <Title>Order Number</Title>
            </Header>
            <FuncDesc>This field is filled when you choose a detailed overview, or
			 the period of the planned inventory movements contains only one order. This
			 field contains the order number.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="position">
            <Header>
               <Title>Line Position Number</Title>
            </Header>
            <FuncDesc>Dependent on the order type, ERP Enterprise displays the number of
			 the <Link href="/baanerp/fm/glossary/glossary#000010" role="glossary">order line</Link>.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="sched.rec">
            <Header>
               <Title>Scheduled Receipts</Title>
            </Header>
            <FuncDesc>The number of items that you expect to receive according to
			 the orders that are transferred to the <Link href="/baanerp/cp/glossary/glossary#000027" role="glossary">execution level</Link>.</FuncDesc>
            <SimpleSection>
               <List>
                  <ListIntro>Transferred orders are, for example:</ListIntro>
                  <ListItem> 
                     <Link href="/baanerp/ti/glossary/glossary#000022" role="glossary">production order</Link>
                  </ListItem>
                  <ListItem> 
                     <Link href="/baanerp/td/glossary/glossary#PurchaOrders_td" role="glossary">purchase order</Link>
                  </ListItem>
                  <ListItem> 
                     <Link href="/baanerp/wh/glossary/glossary#000388" role="glossary">warehousing order</Link>
                  </ListItem>
               </List>
               <List>
                  <ListIntro>The number of items is displayed either:</ListIntro>
                  <ListItem>By period, if a
				  period is specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field.</ListItem>
                  <ListItem>By order, if the
				  value of the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field is <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef>.</ListItem>
               </List>
               <Paragraph>You cannot change
				the transferred orders in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>ERP Enterprise retrieves the scheduled receipt
				data from the <GUIRef href="/baanerp/wh/inp/whinp1500m000" role="session">Planned Inventory Transactions (whinp1500m000)</GUIRef> session.</Paragraph>
            </Note>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000010" role="manual">To transfer orders to the execution level</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="order.status">
            <Header>
               <Title>Order Status</Title>
            </Header>
            <FuncDesc>The status assigned to a planned order in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</FuncDesc>
            <SimpleSection>
               <List>
                  <ListIntro>The order status can either be:</ListIntro>
                  <ListItem> 
                     <GUIRef href="/baanerp/cp/domains/rrp.osta#planned" role="option">Planned</GUIRef>
                  </ListItem>
                  <ListItem> 
                     <GUIRef href="/baanerp/cp/domains/rrp.osta#firmplanned" role="option">Firm Planned</GUIRef>
                  </ListItem>
                  <ListItem> 
                     <GUIRef href="/baanerp/cp/domains/rrp.osta#confirmed" role="option">Confirmed</GUIRef>
                  </ListItem>
               </List>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="project">
            <Header>
               <Title>Project</Title>
            </Header>
            <FuncDesc> 
               <Link href="/baanerp/cp/rrp/cprrp0101s000#cprrp001.cprj" role="formfield">Project</Link> 
               <Link href="/baanerp/ti/glossary/glossary#000023" role="glossary">project</Link>
            </FuncDesc>
         </FieldHelp>
         <FieldHelp ID="order.plni">
            <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>
         </FieldHelp>
         <FieldHelp ID="dest.cwar" OtherIDs="dest.cwar.desc">
            <Header>
               <Title>Warehouse</Title>
            </Header>
            <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> in which the items are received, or from which
			 the items are issued.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="supplier">
            <Header>
               <Title>Business Partner</Title>
            </Header>
            <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#ShipfrBusine_tc" role="glossary">ship-from business partner</Link>.</FuncDesc>
            <SimpleSection>
               <Paragraph>If no ship-from
				business partner is known, the <Link href="/baanerp/tc/glossary/glossary#BuyfroBusine_tc" role="glossary">buy-from business partner</Link> is
				displayed instead.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="supl.comp">
            <Header>
               <Title>Supplying Site</Title>
            </Header>
            <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000115" role="glossary">supplying site</Link>.</FuncDesc>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>This field always contains a value. In case of <Link href="/baanerp/cp/glossary/glossary#000047" role="glossary">planned production order</Link> or <Link href="/baanerp/cp/glossary/glossary#000048" role="glossary">planned purchase order</Link> the value is set to the current
				company.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="supplying.item">
            <Header>
               <Title>Supplying Item</Title>
            </Header>
            <FuncDesc>The supplying <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="effn">
            <Header>
               <Title>Effectivity Unit</Title>
            </Header>
            <FuncDesc>The number of the effectivity unit involved in this
			 transaction.</FuncDesc>
            <SimpleSection>
               <Paragraph>You can define <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity units</Link> in the <GUIRef href="/baanerp/tc/uef/tcuef0502m000" role="session">Effectivity Units (tcuef0502m000)</GUIRef> session.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/tc/glossary/glossary#000306" role="glossary">unit effectivity</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="e.spec.present">
            <Header>
               <Title>Specification</Title>
            </Header>
            <FuncDesc>If this check box is selected, a <Link href="/baanerp/cp/glossary/glossary#000455" role="glossary">specification</Link> is present.</FuncDesc>
            <SimpleSection>
               <Paragraph>To display the specification, in the <GUIRef href="" role="manual" Update="No">appropriate</GUIRef> menu, click <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#cprrp0501m000" role="command">Specification</GUIRef>.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldGroup>
            <Title>Initial Hidden</Title>
            <FieldHelp ID="end.date">
               <Header>
                  <Title>Date</Title>
               </Header>
               <FuncDesc>The end date and time of the period.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The displayed
				  periods are defined by the period length (specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field) and
				  the start date of the <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>. The first
				  displayed period starts on the start date of the scenario. The last displayed
				  period is determined by the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>. The period
				  in which the planning horizon falls is the last displayed period.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>If you chose the <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef> option in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field, the
				  last displayed line is the last order that occurs in the order horizon.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="f.plan.item" OtherIDs="e.plan.item.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>
            </FieldHelp>
            <FieldHelp ID="atp">
               <Header>
                  <Title>ATP</Title>
               </Header>
               <FuncDesc>The item quantity that is still available to be promised to a
		customer.</FuncDesc>
               <SimpleSection>
                  <Paragraph>In ERP Enterprise,
		  available-to-promise (ATP) is part of a more extended framework of order
		  promising techniques called capable-to-promise (CTP). If an item's ATP is
		  insufficient, CTP goes beyond ATP in that it also considers the possibility of
		  producing more than was initially planned.</Paragraph>
                  <Paragraph>In addition to the standard ATP functionality, ERP Enterprise also uses channel ATP.
		  This term refers to the availability of an item for a certain sales channel,
		  taking into account the sales limits for that channel.</Paragraph>
                  <Paragraph>For all other types of order promising functionality used in ERP Enterprise, the term CTP is used.</Paragraph>
                  <Paragraph>Acronym:</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000311" role="manual">Item ATP</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="safety.stock">
               <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>
            </FieldHelp>
            <FieldHelp ID="org.pldt">
               <Header>
                  <Title>Ordered Date</Title>
               </Header>
               <FuncDesc>The date on which the order is created.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="org.qana">
               <Header>
                  <Title>Ordered Quantity</Title>
               </Header>
               <FuncDesc>The quantity of item ordered.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cur.date">
               <Header>
                  <Title>Order Confirm Date</Title>
               </Header>
               <FuncDesc>The date on which the order is confirmed.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cur.qana">
               <Header>
                  <Title>Confirmed Quantity</Title>
               </Header>
               <FuncDesc>The total confirmed quantity of the item ordered.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cur.qana">
               <Header>
                  <Title>Confirmed Quantity</Title>
               </Header>
               <FuncDesc>The total confirmed quantity of the item ordered.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="effn">
               <Header>
                  <Title>Effectivity Unit</Title>
               </Header>
               <FuncDesc>A reference number, for example a sales order line or a project
		deliverable line, that is used to model deviations for a unit effective item.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bp">
               <Header>
                  <Title>Demand Pegged to BP</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary">sold-to business partner</Link> to which this
				supply was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>. If this record involves a demand, this field
				indicates the sold-to business partner to which the supply that can fill this
				demand must have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bot">
               <Header>
                  <Title>Demand Pegged to Business Object Type</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the
				type of order to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>, such as, <GUIRef href="/baanerp/tc/domains/albt#sales" role="option">Sales Order</GUIRef>,
				or <GUIRef href="/baanerp/tc/domains/albt#service" role="option">Service Order</GUIRef>. If this record involves a demand, this field indicates the type
				of order to which the supply that can fill this demand must have been allocated
				or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <List>
                     <ListIntro>The following fields are always used in combination;
					 together, they identify the relevant order or order line:</ListIntro>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bot" role="manual">Demand Pegged to Business Object Type</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bo" role="manual">Demand Pegged to Business Object</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bor" role="manual">Demand Pegged to Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bo" OtherIDs="e.alloc.to.bor">
               <Header>
                  <Title>Demand Pegged to Business Object</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>, or order line, to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>, such as, <GUIRef href="/baanerp/tc/domains/albt#sales" role="option">Sales Order</GUIRef>,
				or <GUIRef href="/baanerp/tc/domains/albt#service" role="option">Service Order</GUIRef>. If this record involves a demand, this field indicates the <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>, or order line, to which the supply that can fill
				this demand must have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <List>
                     <ListIntro>The following fields are always used in combination;
					 together, they identify the relevant order or order line:</ListIntro>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bot" role="manual">Demand Pegged to Business Object Type</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bo" role="manual">Demand Pegged to Business Object</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bor" role="manual">Demand Pegged to Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.ref">
               <Header>
                  <Title>Demand Pegged to Reference</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the
				reference code to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>. If this record involves a demand, this field
				indicates the reference code to which the supply that can fill this demand must
				have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to find a matching supply for this
				  demand.</Paragraph>
                  <Paragraph>ERP Enterprise uses the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.ref" role="manual">Demand Pegged to Reference</GUIRef> field to record an internal
				  reference.</Paragraph>
                  <Paragraph>You can use a reference code to keep a collection of
				  parts linked together, even if they follow different routings, for example, if
				  some of the parts are transported to a subcontractor to be returned later.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.use.unalloc.inv">
               <Header>
                  <Title>Use Unallocated Inventory</Title>
               </Header>
               <FuncDesc>If this check box is selected, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> can use
				unallocated inventory to supply the demand. <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses
				allocated inventory first. If there is not enough allocated inventory, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> also
				uses unallocated inventory.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If this check box is cleared, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> can use
				  only allocated inventory to fill the demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.option.list.id">
               <Header>
                  <Title>Option List ID</Title>
               </Header>
               <FuncDesc>
                  <Link href="/baanerp/cp/rrp/cprrp0520m000#e.option.list.id" role="formfield">Option List ID</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.ppeg.poject">
               <Header>
                  <Title>Project</Title>
               </Header>
               <FuncDesc>View the project peg the order belongs to.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title>Confirmed Demand</Title>
         <FieldHelp ID="end.date">
            <Header>
               <Title>Date</Title>
            </Header>
            <FuncDesc>The end date and time of the period.</FuncDesc>
            <SimpleSection>
               <Paragraph>The displayed
				periods are defined by the period length (specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field) and
				the start date of the <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>. The first
				displayed period starts on the start date of the scenario. The last displayed
				period is determined by the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>. The period
				in which the planning horizon falls is the last displayed period.</Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>If you chose the <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef> option in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field, the
				last displayed line is the last order that occurs in the order horizon.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="koor">
            <Header>
               <Title>Order Type</Title>
            </Header>
            <FuncDesc>The order type of the order involved.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="orno">
            <Header>
               <Title>Order Number</Title>
            </Header>
            <FuncDesc>This field is filled when you choose a detailed overview, or
			 the period of the planned inventory movements contains only one order. This
			 field contains the order number.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="position">
            <Header>
               <Title>Line Position Number</Title>
            </Header>
            <FuncDesc>Dependent on the order type, ERP Enterprise displays the number of
			 the <Link href="/baanerp/fm/glossary/glossary#000010" role="glossary">order line</Link>.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="demand">
            <Header>
               <Title>Demand</Title>
            </Header>
            <FuncDesc>The demand for the <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link> expressed in the number of items.</FuncDesc>
            <Note>
               <SectionTitle>Note</SectionTitle>
               <Paragraph>If the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field has
				the value <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef>, you can see where
				the demand originates in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#orno" role="manual">Order Number</GUIRef> field and the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#koor" role="manual">Order Type</GUIRef> field on the <GUIRef href="" role="manual">Detail</GUIRef> tab.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="e.conf.demand">
            <Header>
               <Title>Confirmed Demand</Title>
            </Header>
            <FuncDesc>The confirmed demand for the plan item expressed in the
			 number of items.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="supply.quantity">
            <Header>
               <Title>Supply</Title>
            </Header>
            <FuncDesc>The sum of the scheduled receipts and the <Link href="/baanerp/wh/glossary/glossary#000366" role="glossary">planned receipt</Link>.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="org.qana">
            <Header>
               <Title>Ordered Quantity</Title>
            </Header>
            <FuncDesc>The quantity of item ordered.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="org.pldt">
            <Header>
               <Title>Ordered Date</Title>
            </Header>
            <FuncDesc>The date on which the order is created.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="cur.date">
            <Header>
               <Title>Order Confirm Date</Title>
            </Header>
            <FuncDesc>The date on which the order is confirmed.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="cur.qana">
            <Header>
               <Title>Confirmed Quantity</Title>
            </Header>
            <FuncDesc>The total confirmed quantity of the item ordered.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="pl.available">
            <Header>
               <Title>Planned Available</Title>
            </Header>
            <FuncDesc>The expected inventory level at the end of a plan
		period.</FuncDesc>
            <SimpleSection>
               <Paragraph>Note that the projected inventory of plan periods that are
		  entirely in the past equals the inventory on hand.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="e.spec.present">
            <Header>
               <Title>Specification</Title>
            </Header>
            <FuncDesc>If this check box is selected, a <Link href="/baanerp/cp/glossary/glossary#000455" role="glossary">specification</Link> is present.</FuncDesc>
            <SimpleSection>
               <Paragraph>To display the specification, in the <GUIRef href="" role="manual" Update="No">appropriate</GUIRef> menu, click <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#cprrp0501m000" role="command">Specification</GUIRef>.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="e.conf.pl.avail">
            <Header>
               <Title>Planned Available (Confirmed)</Title>
            </Header>
            <FuncDesc>View which op the planned available inventory is
			 confirmed.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="e.spec.present">
            <Header>
               <Title>Specification</Title>
            </Header>
            <FuncDesc>If this check box is selected, a <Link href="/baanerp/cp/glossary/glossary#000455" role="glossary">specification</Link> is present.</FuncDesc>
            <SimpleSection>
               <Paragraph>To display the specification, in the <GUIRef href="" role="manual" Update="No">appropriate</GUIRef> menu, click <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#cprrp0501m000" role="command">Specification</GUIRef>.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldGroup>
            <Title>Initial Hidden</Title>
            <FieldHelp ID="effn">
               <Header>
                  <Title>Effectivity Unit</Title>
               </Header>
               <FuncDesc>A reference number, for example a sales order line or a project
		deliverable line, that is used to model deviations for a unit effective item.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="order.status">
               <Header>
                  <Title>Order Status</Title>
               </Header>
               <FuncDesc>The status assigned to a planned order in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>The order status can either be:</ListIntro>
                     <ListItem> 
                        <GUIRef href="/baanerp/cp/domains/rrp.osta#planned" role="option">Planned</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/cp/domains/rrp.osta#firmplanned" role="option">Firm Planned</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/cp/domains/rrp.osta#confirmed" role="option">Confirmed</GUIRef>
                     </ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="project">
               <Header>
                  <Title>Project</Title>
               </Header>
               <FuncDesc>
                  <Link href="/baanerp/cp/rrp/cprrp0101s000#cprrp001.cprj" role="formfield">Project</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="order.plni" OtherIDs="e.plan.item.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>
            </FieldHelp>
            <FieldHelp ID="depd.comp">
               <Header>
                  <Title>Receiving Site</Title>
               </Header>
               <FuncDesc>
                  <Link href="/baanerp/cp/rrp/cprrp0511m000#cprrp010.resi" role="formfield">Receiving Site</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="depending.item" OtherIDs="receiv.item.dsca">
               <Header>
                  <Title>Receiving Item</Title>
               </Header>
               <FuncDesc>The receiving <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="dest.cwar" OtherIDs="dest.cwar.desc">
               <Header>
                  <Title>Warehouse</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> in which the items are received, or from which
				the items are issued.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="supplier">
               <Header>
                  <Title>Business Partner</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#ShipfrBusine_tc" role="glossary">ship-from business partner</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If no ship-from
				  business partner is known, the <Link href="/baanerp/tc/glossary/glossary#BuyfroBusine_tc" role="glossary">buy-from business partner</Link> is
				  displayed instead.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="e.dist.line">
               <Header>
                  <Title>Distribution Line</Title>
               </Header>
               <FuncDesc>The number of the distribution line the order belongs
				to.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="supl.comp">
               <Header>
                  <Title>Supplying Site</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000115" role="glossary">supplying site</Link>.</FuncDesc>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>This field always contains a value. In case of <Link href="/baanerp/cp/glossary/glossary#000047" role="glossary">planned production order</Link> or <Link href="/baanerp/cp/glossary/glossary#000048" role="glossary">planned purchase order</Link> the value is set to the current
				  company.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="supplying.item">
               <Header>
                  <Title>Supplying Item</Title>
               </Header>
               <FuncDesc>The supplying <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="end.date">
               <Header>
                  <Title>Date</Title>
               </Header>
               <FuncDesc>The end date and time of the period.</FuncDesc>
               <SimpleSection>
                  <Paragraph>The displayed
				  periods are defined by the period length (specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field) and
				  the start date of the <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>. The first
				  displayed period starts on the start date of the scenario. The last displayed
				  period is determined by the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>. The period
				  in which the planning horizon falls is the last displayed period.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>If you chose the <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef> option in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field, the
				  last displayed line is the last order that occurs in the order horizon.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="sim.input">
               <Header>
                  <Title>Simulate</Title>
               </Header>
               <FuncDesc>You can use this field to enter additional demand or an
				additional supply of the <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>You can simulate
				  an additional demand by entering a negative quantity. You can simulate an
				  additional scheduled receipt or an additional planned supply by entering a
				  positive quantity.</Paragraph>
                  <Paragraph>If you want to
				  see the results of the simulation, click the Update icon.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="sched.rec">
               <Header>
                  <Title>Scheduled Receipts</Title>
               </Header>
               <FuncDesc>The number of items that you expect to receive according
				to the orders that are transferred to the <Link href="/baanerp/cp/glossary/glossary#000027" role="glossary">execution level</Link>.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>Transferred orders are, for example:</ListIntro>
                     <ListItem> 
                        <Link href="/baanerp/ti/glossary/glossary#000022" role="glossary">production order</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/td/glossary/glossary#PurchaOrders_td" role="glossary">purchase order</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/wh/glossary/glossary#000388" role="glossary">warehousing order</Link>
                     </ListItem>
                  </List>
                  <List>
                     <ListIntro>The number of items is displayed either:</ListIntro>
                     <ListItem>By period, if a
					 period is specified in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field.</ListItem>
                     <ListItem>By order, if the
					 value of the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#period.length" role="manual">Scenario</GUIRef> field is <GUIRef href="/baanerp/cp/domains/rrp.perl#detail" role="option">Detail</GUIRef>.</ListItem>
                  </List>
                  <Paragraph>You cannot
				  change the transferred orders in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>ERP Enterprise retrieves the scheduled receipt
				  data from the <GUIRef href="/baanerp/wh/inp/whinp1500m000" role="session">Planned Inventory Transactions (whinp1500m000)</GUIRef> session.</Paragraph>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000010" role="manual">To transfer orders to the execution level</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="atp">
               <Header>
                  <Title>ATP</Title>
               </Header>
               <FuncDesc>The item quantity that is still available to be promised to a
		customer.</FuncDesc>
               <SimpleSection>
                  <Paragraph>In ERP Enterprise,
		  available-to-promise (ATP) is part of a more extended framework of order
		  promising techniques called capable-to-promise (CTP). If an item's ATP is
		  insufficient, CTP goes beyond ATP in that it also considers the possibility of
		  producing more than was initially planned.</Paragraph>
                  <Paragraph>In addition to the standard ATP functionality, ERP Enterprise also uses channel ATP.
		  This term refers to the availability of an item for a certain sales channel,
		  taking into account the sales limits for that channel.</Paragraph>
                  <Paragraph>For all other types of order promising functionality used in ERP Enterprise, the term CTP is used.</Paragraph>
                  <Paragraph>Acronym:</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000311" role="manual">Item ATP</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="safety.stock">
               <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>
            </FieldHelp>
            <FieldHelp ID="dest.cwar" OtherIDs="dest.cwar.desc">
               <Header>
                  <Title>Warehouse</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> in which the items are received, or from which
				the items are issued.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="order.plni" OtherIDs="e.plan.item.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>
            </FieldHelp>
            <FieldHelp ID="depending.item" OtherIDs="receiv.item.dsca">
               <Header>
                  <Title>Receiving Item</Title>
               </Header>
               <FuncDesc>The receiving <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.effectivity.unt">
               <Header>
                  <Title>Effectivity Unit</Title>
               </Header>
               <FuncDesc>A reference number, for example a sales order line or a project
		deliverable line, that is used to model deviations for a unit effective item.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bp">
               <Header>
                  <Title>Demand Pegged to BP</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary">sold-to business partner</Link> to which this
				supply was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>. If this record involves a demand, this field
				indicates the sold-to business partner to which the supply that can fill this
				demand must have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bot">
               <Header>
                  <Title>Demand Pegged to Business Object Type</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the
				type of order to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>, such as, <GUIRef href="/baanerp/tc/domains/albt#sales" role="option">Sales Order</GUIRef>,
				or <GUIRef href="/baanerp/tc/domains/albt#service" role="option">Service Order</GUIRef>. If this record involves a demand, this field indicates the type
				of order to which the supply that can fill this demand must have been allocated
				or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <List>
                     <ListIntro>The following fields are always used in combination;
					 together, they identify the relevant order or order line:</ListIntro>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bot" role="manual">Demand Pegged to Business Object Type</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bo" role="manual">Demand Pegged to Business Object</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bor" role="manual">Demand Pegged to Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bo" OtherIDs="e.alloc.to.bor">
               <Header>
                  <Title>Demand Pegged to Business Object</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>, or order line, to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>, such as, <GUIRef href="/baanerp/tc/domains/albt#sales" role="option">Sales Order</GUIRef>,
				or <GUIRef href="/baanerp/tc/domains/albt#service" role="option">Service Order</GUIRef>. If this record involves a demand, this field indicates the <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>, or order line, to which the supply that can fill
				this demand must have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <List>
                     <ListIntro>The following fields are always used in combination;
					 together, they identify the relevant order or order line:</ListIntro>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bot" role="manual">Demand Pegged to Business Object Type</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bo" role="manual">Demand Pegged to Business Object</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.bor" role="manual">Demand Pegged to Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.ref">
               <Header>
                  <Title>Demand Pegged to Reference</Title>
               </Header>
               <FuncDesc>If this record involves a supply, this field indicates the
				reference code to which the inventory was <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or the supply object was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>. If this record involves a demand, this field
				indicates the reference code to which the supply that can fill this demand must
				have been allocated or hard pegged.</FuncDesc>
               <SimpleSection>
                  <Paragraph>ERP Enterprise uses this characteristic to find a matching supply for this
				  demand.</Paragraph>
                  <Paragraph>ERP Enterprise uses the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#e.alloc.to.ref" role="manual">Demand Pegged to Reference</GUIRef> field to record an internal
				  reference.</Paragraph>
                  <Paragraph>You can use a reference code to keep a collection of
				  parts linked together, even if they follow different routings, for example, if
				  some of the parts are transported to a subcontractor to be returned later.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.use.unalloc.inv">
               <Header>
                  <Title>Use Unallocated Inventory</Title>
               </Header>
               <FuncDesc>If this check box is selected, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> can use
				unallocated inventory to supply the demand. <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses
				allocated inventory first. If there is not enough allocated inventory, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> also
				uses unallocated inventory.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If this check box is cleared, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> can use
				  only allocated inventory to fill the demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Demand pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.option.list.id">
               <Header>
                  <Title>Option List ID</Title>
               </Header>
               <FuncDesc>
                  <Link href="/baanerp/cp/rrp/cprrp0520m000#e.option.list.id" role="formfield">Option List ID</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.ppeg.poject">
               <Header>
                  <Title>Project</Title>
               </Header>
               <FuncDesc>View the project peg the order belongs to.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
   </Fields>
   <FormCommands>
      <CommandHelp ID="recompute">
         <Header>
            <Title>Update</Title>
         </Header>
         <FuncDesc>Click this button to let ERP Enterprise carry out an update,
		  when you entered additional demand or additional supply in the <GUIRef href="/baanerp/cp/rrp/cprrp0520m000#sim.input" role="manual">Simulate</GUIRef> field.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="consume.demand">
         <Header>
            <Title>Consume Forecast</Title>
         </Header>
         <FuncDesc>Carries out forecast consumption.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="start.general.item.data">
         <Header>
            <Title>General Data</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/tc/ibd/tcibd0101s000" role="session">Item - General (tcibd0101s000)</GUIRef> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="start.item.ordering.data">
         <Header>
            <Title>Ordering Data</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/tc/ibd/tcibd2100s000" role="session">Item - Ordering (tcibd2100s000)</GUIRef> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="start.item.supplier.data">
         <Header>
            <Title>Item Purchase BP</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="start.plan.item.data">
         <Header>
            <Title>Planning Data</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="cprmp3501m000">
         <Header>
            <Title>Resource Master Plan</Title>
         </Header>
         <FuncDesc>Click this button to zoom to the <GUIRef href="/baanerp/cp/rrp/cprrp2100m000" role="session">Capacity Use by Planned Order (cprrp2100m000)</GUIRef> session in which you can get a
		  period-based overview of the required capacity of a specific resource, or to
		  the <GUIRef href="/baanerp/cp/rmp/cprmp3501m000" role="session">Resource Master Plan (cprmp3501m000)</GUIRef> session in which you can analyze the capacity
		  planning of a specific resource.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="toggle.item.overview">
         <Header>
            <Title>Toggle Item View</Title>
         </Header>
         <FuncDesc>Click this button to switch from <GUIRef href="/baanerp/cp/messages/rpds0034" role="message">(Item only)</GUIRef> to <GUIRef href="/baanerp/cp/messages/rpds0035" role="message">(Item + derived items)</GUIRef> or vice versa.</FuncDesc>
         <SimpleSection>
            <List>
               <ListItemHead>
                  <GUIRef href="/baanerp/cp/messages/rpds0034" role="message">(Item only)</GUIRef>
               </ListItemHead>
               <ListItem>ERP Enterprise displays only the transactions of the item itself. The transactions displayed
				match the item's ATP.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/cp/messages/rpds0035" role="message">(Item + derived items)</GUIRef>
               </ListItemHead>
               <ListItem>ERP Enterprise displays the transactions of the item itself <Emphasis>and</Emphasis> the
				transactions including all customized items derived from this item.</ListItem>
            </List>
         </SimpleSection>
      </CommandHelp>
      <CommandHelp ID="start.specification">
         <Header>
            <Title>Specification</Title>
         </Header>
         <FuncDesc>Displays the selected record's <Link href="/baanerp/cp/glossary/glossary#000455" role="glossary">specification</Link>.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>