<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/cp/rrp/cprrp1240m000" xml:lang="en">
   <Header>
      <Title>Copy Planned Orders to Scenarios (cprrp1240m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to copy <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned orders</Link> from one <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link> to another.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>You can choose and
		  combine various selection criteria.</Paragraph>
         <Paragraph>Moreover, you can
		  indicate that existing planned orders in the target scenario with a particular <Link href="/baanerp/cp/glossary/glossary#000051" role="glossary">order status</Link> must be
		  deleted.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>After the planned
			 orders have been copied, the order numbers in the target scenario and the order
			 numbers in the source scenario do not necessarily match.</Paragraph>
         </Note>
      </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/000326" role="manual">Planned orders in Enterprise Planning</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="plnc.f">
         <Header>
            <Title>Scenario</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link> from which the
		  planned orders are copied.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="plvl.f">
         <Header>
            <Title>Plan Level</Title>
         </Header>
         <FuncDesc>The level within a hierarchical planning structure.</FuncDesc>
         <SimpleSection>
            <Paragraph>When you plan on a higher plan level, plans are general and
		  less detailed.</Paragraph>
         </SimpleSection>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <Figure space-and-orientation="indented-estimated">
               <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" width="390" height="231"
                         SRC="../images/tr_graph_tiglossary_01.gif"
                         alt="[...]"/>
            </Figure>
            <Paragraph>Plan level 1 is the highest plan level; the higher the
		  number, the lower the plan level.</Paragraph>
         </ExampleSection>
      </FieldHelp>
      <FieldHelp ID="plid.f">
         <Header>
            <Title>Planner</Title>
         </Header>
         <FuncDesc>The employee or department responsible for planning the
		production, purchase and distribution of items. The planner takes into account
		the inventory levels, availability of materials, and capacities of resources,
		and reacts on signals such as rescheduling messages that LN generates.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="date.f">
         <Header>
            <Title>Date</Title>
         </Header>
         <FuncDesc>Specify the earliest order start date of the planned orders
		  that you want to copy from the source <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link> to the target scenario.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="date.t">
         <Header>
            <Title>Date</Title>
         </Header>
         <FuncDesc>Specify the latest order start date of the planned orders that
		  you want to copy from the source <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link> to the target scenario.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cwar.f">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>A place for storing goods. For each warehouse, you can enter
		address data and data relating to its type.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="orno.f">
         <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="koor.f">
         <Header>
            <Title>From Order Type</Title>
         </Header>
         <FuncDesc>Select the type of <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned orders</Link> that you want to copy to the target <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The available options are:</ListIntro>
               <ListItem> 
                  <Link href="/baanerp/cp/glossary/glossary#000047" role="glossary">planned production order</Link>
               </ListItem>
               <ListItem> 
                  <Link href="/baanerp/cp/glossary/glossary#000048" role="glossary">planned purchase order</Link>
               </ListItem>
               <ListItem> 
                  <Link href="/baanerp/cp/glossary/glossary#000049" role="glossary">planned distribution order</Link>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="koor.t">
         <Header>
            <Title>To Order Type</Title>
         </Header>
         <FuncDesc>Select the type of <Link href="/baanerp/cp/glossary/glossary#000050" role="glossary">planned order</Link> that you want to copy to the target <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link>.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The available options are:</ListIntro>
               <ListItem>
                  <Link href="/baanerp/cp/glossary/glossary#000047" role="glossary">planned production order</Link>
               </ListItem>
               <ListItem> 
                  <Link href="/baanerp/cp/glossary/glossary#000048" role="glossary">planned purchase order</Link>
               </ListItem>
               <ListItem> 
                  <Link href="/baanerp/cp/glossary/glossary#000049" role="glossary">planned distribution order</Link>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="item.f">
         <Header>
            <Title>From 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="item.t">
         <Header>
            <Title>To 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="plnc.t">
         <Header>
            <Title>Scenario</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link> to which you want
		  to copy the planned orders.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="del.planned">
         <Header>
            <Title>Delete Current Planned Orders</Title>
         </Header>
         <FuncDesc>If this check box is selected, LN deletes all planned orders in the target
		  scenario that match the selection criteria and which have the <GUIRef href="/baanerp/cp/domains/rrp.osta#planned" role="option">Planned</GUIRef> order status.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="del.firmplanned">
         <Header>
            <Title>Delete Current Firm-Planned Orders</Title>
         </Header>
         <FuncDesc>If this check box is selected, LN deletes all planned orders in the target
		  scenario that match the selection criteria and which have the <GUIRef href="/baanerp/cp/domains/rrp.osta#firmplanned" role="option">Firm Planned</GUIRef> order status.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="del.confirmed">
         <Header>
            <Title>Delete Current Confirmed Orders</Title>
         </Header>
         <FuncDesc>If this check box is selected, LN deletes all planned orders in the target
		  scenario that match the selection criteria and which have the <GUIRef href="/baanerp/cp/domains/rrp.osta#confirmed" role="option">Confirmed</GUIRef> order
		  status.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="exec.cont.process">
         <Header>
            <Title>Copy</Title>
         </Header>
         <FuncDesc>Starts the copying process.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>