<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ff/planning/planning_ff_epmd" xml:lang="it">
   <Header>
      <Title>Pianificazione aziendale Master Data</Title>
      <Keyword type="header" order="d1e366754">
         <Level1>Functions and features</Level1>
         <Level2>Pianificazione aziendale</Level2>
      </Keyword>
      <Keyword type="header" order="d1e366760">
         <Level1>Pianificazione aziendale</Level1>
         <Level2>functions and features</Level2>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>You set up the planning structure in master data. The structure
		consists of simulation scenarios, plan items, capacity resources and plan
		units. Additionally the rules for supplier and distribution sources can be set
		up and for lot size values.</Paragraph>
   </AimSection>
   <GeneralSection>
      <List>
         <ListItemHead>
            <Link href="/baanerp/cp/onlinemanual/000044" role="manual">Scenari in Enterprise Planning</Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>Scenarios are used to simulate planning runs for various
			 business situations. Only one scenario can be the actual scenario, representing
			 the actual plan that is transferred to production, purchase and
			 warehousing.</Paragraph>
            <Paragraph>The scenario-planning horizon can be divided in to plan
			 periods of various lengths. This allows forecasting and planning in small
			 periods on the short-term and in longer periods in the longer-term. The
			 scenario can be defined as rolling, which will periodically redivide the
			 scenario-planning horizon in plan periods starting with the current date. This
			 offers a consistent period division for the planner as time passes.</Paragraph>
            <Paragraph>Static data such as supplying and sourcing strategies and
			 dynamic data such as planned orders can be copied between scenarios.
			 Relationships between a central scenario and local scenarios in a multisite
			 environment can be defined, this allows a central planning run that triggers
			 the local planning runs. Data, such as forecast and orders, can be aggregated
			 and disaggregated between the local scenarios and central scenario.</Paragraph>
         </ListItem>
         <ListItemHead>
            <Link href="/baanerp/tc/onlinemanual/000329" role="manual">Dati articolo</Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>The planning settings for an item is defined in Item
			 Planning Data, which is an aggregate of multiple plan items. Another important
			 setting is the default source, which determines if the item is supplied by
			 production, purchase or distribution. When selecting the default source
			 production/purchase the actual source is determined by the Date-Effective Item
			 Data session. The horizons to generate planned orders and plans for each plan
			 item can be defined. Additionally it can be defined whether or not a plan item
			 has an item master plan and the types of capable-to-promise that are used for
			 promising the item to customers.</Paragraph>
         </ListItem>
         <ListItemHead>
            <Link href="/baanerp/cp/onlinemanual/000032" role="manual">Risorse in Enterprise Planning</Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>In <GUIRef href="/baanerp/cp" role="package">Pianificazione aziendale</GUIRef>, production facilities are referred to as <Link href="/baanerp/cp/glossary/glossary#000008" role="glossary" Update="No">resources</Link>. A resource in <GUIRef href="/baanerp/cp" role="package">Pianificazione aziendale</GUIRef> corresponds to a work center in <GUIRef href="/baanerp/ti" role="package">Produzione</GUIRef>. Every work center in <GUIRef href="/baanerp/ti" role="package">Produzione</GUIRef> is defined as
			 resource in <GUIRef href="/baanerp/cp" role="package">Pianificazione aziendale</GUIRef>. Resources are used to provide information about available
			 capacity, capacity utilization, the resulting free capacity and capacity
			 capable to promise.</Paragraph>
         </ListItem>
         <ListItemHead>
            <Link href="/baanerp/cp/onlinemanual/000025" role="manual">Unità del piano in Enterprise Planning</Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>Plan units are used to manage interdependencies that exist
			 in constraint-based production planning. A plan unit groups plan items that
			 must be planned together because of capacity or material constraints. Plan
			 units are only necessary for workload control.</Paragraph>
         </ListItem>
         <ListItemHead>
            <Link href="/baanerp/cp/onlinemanual/000410" role="manual">Validità della data nel tipo di articolo</Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>Sourcing is the method to determine the source of supply for
			 a plan item to satisfy demand.</Paragraph>
            <List>
               <ListIntro>Sourcing can be defined on two levels:</ListIntro>
               <ListItemHead>Source strategy</ListItemHead>
               <ListItem>This strategy determines if the item is produced, purchased
				or distributed. Defining a sourcing strategy is not a requirement, if the
				sourcing strategy is not defined the default source from the Item-Planning data
				is taken.</ListItem>
               <ListItemHead>Supply strategy</ListItemHead>
               <ListItem>This strategy determines the rules that specify which
				suppliers and warehouses must be selected for purchasing and distribution. For
				production, no second level applies in the sourcing business object. The supply
				strategy is optional. If a supply strategy is not defined the suppliers are
				selected based on the priorities in the Item Purchase Business Partner session.
				The warehouses are then selected based on the priorities in the supplying
				relationship session.</ListItem>
            </List>
            <Paragraph>The supplying relationships between clusters can be defined.
			 A cluster is a group of entities without the restriction that the entities are
			 all of the same type and belong to the same financial company or logistic
			 company. These relationships represent the possible supplies between
			 warehouses. <GUIRef href="/baanerp/cp" role="package">Pianificazione aziendale</GUIRef> always translates the cluster to the default warehouse in
			 that cluster. The supplying relationships are selected based on the supply
			 strategy. If no supplying strategy is applicable, they are based on the
			 priorities in the supplying relationships.</Paragraph>
         </ListItem>
         <ListItemHead>Project Pegging</ListItemHead>
         <ListItem>
            <Paragraph>To facilitate cost accountability for selected finished
			 goods within projects it is now possible to indicate that certain goods are
			 project pegged. By using the pegging policy for these items it is possible to
			 track costs at the project, element, and activity level through the complete
			 product life-cycle.</Paragraph>
         </ListItem>
         <ListItemHead>Planning Groups</ListItemHead>
         <ListItem>
            <Paragraph>Commingling and cost transfer rules are defined at the
			 planning group level to control supply planning of project pegged items within
			 one or several planning groups. When excess inventory occurs in a project, the
			 inventory can be consumed by other projects when not limited by commingling
			 rules defined for the planning group or project with the excess.</Paragraph>
            <Paragraph>A cost transfer is a project cost account change and not a
			 physical transfer of items. Cost transfer rules determine in which conditions
			 excess inventory on projects is made available for transfer to other projects
			 or to allowed to receive excess inventory from other projects or to allow
			 receiving of inventory from other projects.</Paragraph>
            <Paragraph>Commingling of project requirements for project pegged items
			 is possible across project planning groups or be restricted to a single
			 planning group. It is also possible to exclude project cost accounts from
			 commingling.</Paragraph>
         </ListItem>
      </List>
   </GeneralSection>
</ManualTopic>