<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/cp/rrp/cprrp0511m000" xml:lang="en">
   <Header>
      <Title>Planned Order - Inventory Movements (cprrp0511m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to list the simulated
		  movements of planned items resulting from a <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>Depending on the order
		  type, the following planned inventory movements are listed for an order:</Paragraph>
         <List>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/koor#cp.sfc" role="option">Planned Production Order</GUIRef> The planned inventory movements for all estimated materials are
			 displayed per planned item. The first displayed line represents the planned
			 receipt of the original ordered item.</ListItem>
         </List>
         <List>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/koor#cp.pur" role="option">Planned Purchase Order</GUIRef> A planned receipt of the ordered item is displayed.</ListItem>
         </List>
         <List>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/koor#cp.ipl" role="option">Planned Distribution Order</GUIRef> If the order involves distribution within one company, a planned
			 receipt and a planned issue for the ordered item are displayed. If the order
			 involves distribution between companies, a planned receipt of the ordered item
			 is displayed in your company. (A planned issue for the item is displayed in the
			 supplying company.)</ListItem>
         </List>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>The data in the <GUIRef href="/baanerp/cp/rrp/cprrp0511m000" role="session">Planned Order - Inventory Movements (cprrp0511m000)</GUIRef> session is updated by an RRP run,
				which can be carried out in the <GUIRef href="/baanerp/cp/rrp/cprrp1210m000" role="session">Generate Order Planning (cprrp1210m000)</GUIRef> session.</ListItem>
               <ListItem>The <GUIRef href="/baanerp/cp/rrp/cprrp0511m000" role="session">Planned Order - Inventory Movements (cprrp0511m000)</GUIRef> session does not display inventory
				movements for items that have not been configured with planning information
				from the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef> session.</ListItem>
            </List>
         </Note>
         <Paragraph>If you have started
		  this session by zooming, you can only find and select a record.</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/cp/onlinemanual/000162" role="manual">RRP run, an overview</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000164" role="manual">RRP run, basic calculation for one item</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="cprrp010.plnc" OtherIDs="cprpd400.dsca">
         <Header>
            <Title>Scenario</Title>
         </Header>
         <FuncDesc>The identification of an overall planning solution.</FuncDesc>
         <SimpleSection>
            <Paragraph>Each scenario represents one overall planning solution, and
		  involves particular settings for the planning of items and resources. You can
		  use scenarios to analyze and compare various planning options and to find the
		  best planning solution. For example, you can vary demand forecasts or sourcing
		  strategies.</Paragraph>
            <Paragraph>One of the scenarios is the actual scenario, which
		  corresponds with the actual planning situation. You can only transfer planned
		  orders and production plans from the actual scenario to the execution level of LN.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/cp/onlinemanual/000044" role="manual">Scenarios in Enterprise Planning</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="cprrp010.resi">
         <Header>
            <Title>Receiving Site</Title>
         </Header>
         <FuncDesc>The site (plant) on a receiving point of the supply chain.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The receiving site
			 is only relevant if the order type is <GUIRef href="/baanerp/tc/domains/koor#cp.ipl" role="option">Planned Distribution Order</GUIRef>.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="cprrp010.koor">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>The order type of the related <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.orno">
         <Header>
            <Title>Planned Order</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link> that causes
		  the inventory movements.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.lpon">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc>The number used to identify the position of the order line on
		  the planned order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.pono">
         <Header>
            <Title>Position</Title>
         </Header>
         <FuncDesc>The number that identifies the different transactions that take
		  place as a result of the <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.kotr">
         <Header>
            <Title>Transaction Type</Title>
         </Header>
         <FuncDesc>In this field you can see if the transaction is a receipt or an
		  issue.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.opno">
         <Header>
            <Title>Operation</Title>
         </Header>
         <FuncDesc>The planned <Link href="/baanerp/ti/glossary/glossary#000000000000052" role="glossary">operation</Link> to which the
		  inventory transaction is related.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.date">
         <Header>
            <Title>Date</Title>
         </Header>
         <FuncDesc>The date on which the inventory movement of the item will take
		  place.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.code">
         <Header>
            <Title>Code</Title>
         </Header>
         <FuncDesc>The code used to provide information about the item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprpd120.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="cprrp010.qana">
         <Header>
            <Title>Quantity</Title>
         </Header>
         <FuncDesc>The quantity of planned items that is included in the planned
		  receipt or planned issue.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.effn">
         <Header>
            <Title>Unit Effectivity Number</Title>
         </Header>
         <FuncDesc>A reference number on a sales order line or a sales quotation
		line that is used to model deviations for a unit effective item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.qana">
         <Header>
            <Title>Quantity</Title>
         </Header>
         <FuncDesc>The quantity of a component or material that is theoretically
		required to make a certain quantity of a product.</FuncDesc>
         <SimpleSection>
            <Paragraph>This quantity is referred to as the net quantity because in
		  practice you may need more than this quantity to make up for certain losses of
		  the material or the product.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cprrp010.sitm">
         <Header>
            <Title>Plan Item</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link> that the planned order uses as component.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.mitm">
         <Header>
            <Title>Main Item</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link> that the planned order produces.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.cpon">
         <Header>
            <Title>Position Number</Title>
         </Header>
         <FuncDesc>The position of the material in the estimated materials.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.seqn">
         <Header>
            <Title>Sequence Number</Title>
         </Header>
         <FuncDesc>Identification of the material record.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.hpon">
         <Header>
            <Title>Highest Position Number</Title>
         </Header>
         <FuncDesc>No Help available</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.levl">
         <Header>
            <Title>BOM Level</Title>
         </Header>
         <FuncDesc>When a product is manufactured, components are assembled into
		subassemblies, and those subassemblies are in turn assembled into the final
		product. The components that go together at each stage are described in a bill
		of material. Each stage is one level in the bill of material.</FuncDesc>
         <SimpleSection>
            <Paragraph>The listing of the wheel components is one level in the bill
		  of material. The listing of the subassemblies of the bicycle is the highest
		  level, and is frequently referred to as level zero.</Paragraph>
         </SimpleSection>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <Paragraph>A bicycle has one frame and two wheels. The frame is made of
		  three tubes. The wheels are each made of one rim, one hub, and 35 spokes.</Paragraph>
         </ExampleSection>
      </FieldHelp>
      <FieldHelp ID="cprrp010.cwar">
         <Header>
            <Title>Default Warehouse</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> where the material is usually stored.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.lsel">
         <Header>
            <Title>Lot Selection</Title>
         </Header>
         <FuncDesc>The specific conditions that can be established for lot items
		on order lines.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>These conditions are:</ListIntro>
               <ListItemHead>
                  <GUIRef href="/baanerp/tc/domains/lsel#any" role="option">Any</GUIRef>
               </ListItemHead>
               <ListItem>The goods to be received or shipped are not subject to
			 specific lot conditions. You can use more than one lot.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/tc/domains/lsel#same" role="option">Same</GUIRef>
               </ListItemHead>
               <ListItem>You can select any lot for receipt or shipment, but the
			 entire receipt or shipment must have the same lot.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/tc/domains/lsel#specific" role="option">Specific</GUIRef>
               </ListItemHead>
               <ListItem>You can receive or ship only one, specific lot.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cprrp010.pdoc">
         <Header>
            <Title>Print on Order Document</Title>
         </Header>
         <FuncDesc>The value of the <Link href="/baanerp/ti/bom/tibom1110m000#tibom010.pdoc" role="formfield">
               <GUIRef href="/baanerp/ti/bom/tibom1110m000#tibom010.pdoc" role="manual">Print on Order Document</GUIRef>
            </Link> field in the <GUIRef href="/baanerp/ti/bom/tibom1110m000" role="session">Bill of Material (tibom1110m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.leng">
         <Header>
            <Title>Length</Title>
         </Header>
         <FuncDesc>
            <Link href="/baanerp/ti/cst/ticst0101m000#ticst001.leng" role="formfield">Length</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.widt">
         <Header>
            <Title>Width</Title>
         </Header>
         <FuncDesc>
            <Link href="/baanerp/ti/cst/ticst0101m000#ticst001.widt" role="formfield">Width</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.noun">
         <Header>
            <Title>Number of Units</Title>
         </Header>
         <FuncDesc>The required quantity of the material, expressed as the number
		  of units of specified length and width.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp010.scpf">
         <Header>
            <Title>Scrap Factor</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#Scrap_ti" role="glossary">scrap factor</Link> by which the
		  net quantity must be increased to compensate for material losses.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000018" role="manual">Scrap</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="cprrp010.scpq">
         <Header>
            <Title>Scrap Quantity</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#Scrap_ti" role="glossary">scrap quantity</Link> by which the
		  net quantity must be increased to compensate for material losses.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000018" role="manual">Scrap</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="cprrp010.preq">
         <Header>
            <Title>Percentage Required</Title>
         </Header>
         <FuncDesc>The percentage of raw material that must be available before
		  the operation can be started.</FuncDesc>
      </FieldHelp>
      <FieldGroup>
         <Title>Specification</Title>
         <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/cprrp0511m000#cprrp0101s000" role="manual">Specification</GUIRef>.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="e.effectivity.unt">
            <Header>
               <Title>Unit Effectivity Number</Title>
            </Header>
            <FuncDesc>A reference number on a sales order line or a sales quotation
		line that is used to model deviations for a unit effective item.</FuncDesc>
         </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">Allocation and hard pegging overview</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldGroup>
            <Title>Hard Pegged To</Title>
            <FieldHelp ID="e.alloc.to.bp" OtherIDs="e.allo.to.bp.desc">
               <Header>
                  <Title>Business Partner</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary">sold-to business partner</Link> 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>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>LN uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bot">
               <Header>
                  <Title>Business Object Type</Title>
               </Header>
               <FuncDesc>The type of order to which the inventory was allocated or
				the supply object was hard pegged, 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>.</FuncDesc>
               <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/cprrp0511m000#e.alloc.to.bot" role="manual">Business Object Type</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0511m000#e.alloc.to.bo" role="manual">Business Object</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0511m000#e.alloc.to.bor" role="manual">Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <AllowedValues>
                  <SectionTitle>Allowed values</SectionTitle>
                  <Paragraph>
                     <Link href="/baanerp/tc/domains/albt" role="domain">Allocated to Business Object Type</Link>
                  </Paragraph>
               </AllowedValues>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.bo" OtherIDs="e.alloc.to.bor">
               <Header>
                  <Title>Business Object</Title>
               </Header>
               <FuncDesc>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>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>LN 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/cprrp0511m000#e.alloc.to.bot" role="manual">Business Object Type</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0511m000#e.alloc.to.bo" role="manual">Business Object</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/cp/rrp/cprrp0511m000#e.alloc.to.bor" role="manual">Business Object Reference</GUIRef>
                     </ListItem>
                  </List>
               </Note>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="e.alloc.to.ref">
               <Header>
                  <Title>Reference</Title>
               </Header>
               <FuncDesc>A 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>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>LN uses this characteristic to match supply and demand.</Paragraph>
               </SimpleSection>
               <SimpleSection>
                  <List>
                     <ListIntro>LN can use this field in two ways:</ListIntro>
                     <ListItem>If the <GUIRef href="/baanerp/cp/rrp/cprrp0511m000#e.alloc.to.bp" role="manual">Business Partner</GUIRef> field is filled, LN uses the <GUIRef href="/baanerp/cp/rrp/cprrp0511m000#e.alloc.to.ref" role="manual">Reference</GUIRef> field to record a reference code defined by
					 a customer.</ListItem>
                     <ListItem>If the <GUIRef href="/baanerp/cp/rrp/cprrp0511m000#e.alloc.to.bp" role="manual">Business Partner</GUIRef> field is empty, LN uses the <GUIRef href="/baanerp/cp/rrp/cprrp0511m000#e.alloc.to.ref" role="manual">Reference</GUIRef> field to record an internal
					 reference.</ListItem>
                  </List>
               </SimpleSection>
               <SimpleSection>
                  <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 <Link href="/baanerp/td/glossary/glossary#Subcontracto_td" role="glossary">subcontractor</Link> to be returned later.</Paragraph>
               </SimpleSection>
               <RelatedTopics>
                  <SectionTitle>Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
   </Fields>
   <FormCommands>
      <CommandHelp ID="start.planned.orders">
         <Header>
            <Title>Planned Orders</Title>
         </Header>
         <FuncDesc>No Help available</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="cprrp0410m000">
         <Header>
            <Title>Print Planned Inventory Movements</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/cp/rrp/cprrp0410m000" role="session">Print Planned Inventory Movements (cprrp0410m000)</GUIRef> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="cprrp0101s000">
         <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>