<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/cp/rrp/cprrp1105m000" xml:lang="en">
   <Header>
      <Title>Planned Order Distribution (cprrp1105m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view the distribution of
		  planned orders over different <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity units</Link>.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tc/onlinemanual/000300" role="manual">Overview of unit effectivity</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="cprrp105.plnc" OtherIDs="e.scenario.desc">
         <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>
      </FieldHelp>
      <FieldHelp ID="e.actual">
         <Header>
            <Title>Scenario</Title>
         </Header>
         <FuncDesc>If the scenario is the <Link href="/baanerp/cp/glossary/glossary#000093" role="glossary">actual scenario</Link>, this field indicates that fact.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp105.koor">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>The type of order ( <GUIRef href="/baanerp/tc/domains/koor#cp.sfc" role="option">Planned Production Order</GUIRef>, <GUIRef href="/baanerp/tc/domains/koor#cp.pur" role="option">Planned Purchase Order</GUIRef>, or <GUIRef href="/baanerp/tc/domains/koor#cp.ipl" role="option">Planned Distribution Order</GUIRef>).</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp105.orno">
         <Header>
            <Title>Planned Order</Title>
         </Header>
         <FuncDesc>A supply order in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> that is created for planning
		purposes, but which is not an actual order yet.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro> 
                  <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> works with planned orders of the following types:</ListIntro>
               <ListItem>Planned production order</ListItem>
               <ListItem>Planned purchase order</ListItem>
               <ListItem>Planned distribution order</ListItem>
            </List>
            <Paragraph>Planned orders are generated in the context of a particular
		  scenario. The planned orders of the actual scenario can be transferred to the
		  execution level, where they become actual supply orders.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cprrp105.lpon">
         <Header>
            <Title>Line Position Number</Title>
         </Header>
         <FuncDesc>The number used to identify the position of the order line on
		  the planned order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprrp105.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="cprrp105.oqan">
         <Header>
            <Title>Order Quantity</Title>
         </Header>
         <FuncDesc>The quantity of the order that belongs to a particular
		  effectivity unit.</FuncDesc>
      </FieldHelp>
      <FieldGroup>
         <Title>Specification</Title>
         <FieldHelp ID="cprrp001.albp">
            <Header>
               <Title>Allocated to BP</Title>
            </Header>
            <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary">sold-to business partner</Link> to which the <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link> 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="cprrp001.albt">
            <Header>
               <Title>Allocated to Business Object Type</Title>
            </Header>
            <FuncDesc>The type of order to which the <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link> 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>
            <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/cprrp1105m000#cprrp001.albt" role="manual">Allocated to Business Object Type</GUIRef>
                  </ListItem>
                  <ListItem>
                     <GUIRef href="/baanerp/cp/rrp/cprrp1105m000#cprrp001.albo" role="manual">Allocated to Business Object</GUIRef>
                  </ListItem>
                  <ListItem>
                     <GUIRef href="/baanerp/cp/rrp/cprrp1105m000#cprrp001.abor" role="manual">Allocated to 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="cprrp001.albo" OtherIDs="cprrp001.abor">
            <Header>
               <Title>Allocated to Business Object</Title>
            </Header>
            <FuncDesc>The <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>, or order line, to which the <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link> 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/cprrp1105m000#cprrp001.albt" role="manual">Allocated to Business Object Type</GUIRef>
                  </ListItem>
                  <ListItem>
                     <GUIRef href="/baanerp/cp/rrp/cprrp1105m000#cprrp001.albo" role="manual">Allocated to Business Object</GUIRef>
                  </ListItem>
                  <ListItem>
                     <GUIRef href="/baanerp/cp/rrp/cprrp1105m000#cprrp001.abor" role="manual">Allocated to 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="cprrp001.alrf">
            <Header>
               <Title>Allocated to Reference</Title>
            </Header>
            <FuncDesc>A reference code to which the <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link> was <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link>.</FuncDesc>
            <SimpleSection>
               <Paragraph>LN uses this characteristic to find a matching supply for this demand.</Paragraph>
               <Paragraph>LN uses the <GUIRef href="/baanerp/cp/rrp/cprrp1105m000#cprrp001.alrf" role="manual">Allocated 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">Allocation and hard pegging overview</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="cprrp001.uuai">
            <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>
   </Fields>
   <FormCommands>
      <CommandHelp ID="cprrp0501m000">
         <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>