<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/cp/rpd/cprpd7410m000" xml:lang="en">
   <Header>
      <Title>Print Sourcing Strategy (cprpd7410m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to print
        a report of the sourcing strategy data for the <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link> that correspond to the specified range and the
        selection criteria that you define for them in this session.</Paragraph>
      </AimSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="plnc.f">
         <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="plnc.t">
         <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="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="plvl.t">
         <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="clus.f">
         <Header>
            <Title>Cluster</Title>
         </Header>
         <FuncDesc>A group of entities that are not necessarily related to one
		financial company or logistic company.</FuncDesc>
         <SimpleSection>
            <Paragraph>In <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, clusters are used for groups of warehouses, connected by
		  supplying relationships.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="clus.t">
         <Header>
            <Title>Cluster</Title>
         </Header>
         <FuncDesc>A group of entities that are not necessarily related to one
		financial company or logistic company.</FuncDesc>
         <SimpleSection>
            <Paragraph>In <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, clusters are used for groups of warehouses, connected by
		  supplying relationships.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="citg.f">
         <Header>
            <Title>Item Group</Title>
         </Header>
         <FuncDesc>Group of items with similar characteristics. Each item belongs
		to a particular item group. The item group is used in combination with the item
		type to set up item defaults.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="citg.t">
         <Header>
            <Title>Item Group</Title>
         </Header>
         <FuncDesc>Group of items with similar characteristics. Each item belongs
		to a particular item group. The item group is used in combination with the item
		type to set up item defaults.</FuncDesc>
      </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="unit.config">
         <Header>
            <Title>Configuration</Title>
         </Header>
         <FuncDesc>Select one of the three possible settings from the pull-down
        menu to specify the type of report that you want to print for the sourcing
        strategies.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Select:</ListIntro>
               <ListItem> 
                  <Emphasis>All</Emphasis>, to print data of all the sourcing strategies. That
            is, the sourcing strategies data if LN uses the standard configuration, as
            well as the data for plan items for which you specified exceptions.</ListItem>
               <ListItem> 
                  <Emphasis>Standard</Emphasis>, to print a report of the sourcing strategy data
            if LN uses the standard configuration, that is, you did no specify
            exceptions.</ListItem>
               <ListItem> 
                  <Emphasis>Specific</Emphasis>, to print a report of the sourcing strategy data
            for plan items for which you specified exceptions. In this case, you must
            specify a range of exceptions in the <GUIRef href="/baanerp/cp/rpd/cprpd7410m000#unit.f" role="manual">From Unit</GUIRef> and <GUIRef href="/baanerp/cp/rpd/cprpd7410m000#unit.t" role="manual">To Unit</GUIRef> field.</ListItem>
            </List>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/cp/glossary/glossary#000104" role="glossary">sourcing strategy</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/tc/glossary/glossary#000306" role="glossary">unit effectivity</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="unit.f">
         <Header>
            <Title>From Unit</Title>
         </Header>
         <FuncDesc>Select an <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity unit</Link> to specify
        as the first in the range of effectivity units, if you selected <Emphasis>Specific</Emphasis> in the <GUIRef href="/baanerp/cp/rpd/cprpd7410m000#unit.config" role="manual">Configuration</GUIRef> field.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="unit.t">
         <Header>
            <Title>To Unit</Title>
         </Header>
         <FuncDesc>Select an <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity unit</Link> to specify
        as the last in the range of effectivity units, if you selected <Emphasis>Specific</Emphasis> in the <GUIRef href="/baanerp/cp/rpd/cprpd7410m000#unit.config" role="manual">Configuration</GUIRef> field.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="print.sourcing.strategy">
         <Header>
            <Title>Print</Title>
         </Header>
         <FuncDesc>Starts printing.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>