<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ff/common/common_ff_calendars" xml:lang="it">
   <Header>
      <Title> Calendari e periodi</Title>
      <Keyword type="header" order="d1e368723">
         <Level1>Functions and features</Level1>
         <Level2>Calendari e periodi</Level2>
      </Keyword>
      <Keyword type="header" order="d1e368729">
         <Level1>Calendari e periodi</Level1>
         <Level2>functions and features</Level2>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>Calendars define the working hours for resources in the company
		such as work centers, employees, warehouses, purchase offices and sales
		offices. The calendars are used to determine lead times and start/end dates for
		activities carried out in a company, such as production, purchasing,
		warehousing, service and maintenance, and project activities.</Paragraph>
   </AimSection>
   <GeneralSection>
      <List>
         <ListItemHead>
            <Link href="/baanerp/tc/onlinemanual/tcccp" role="manual">
               <GUIRef href="/baanerp/tc/ccp" role="module">Calendari e periodi</GUIRef>
            </Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>Can be defined on both a higher level such as enterprise
			 unit and company level as on a detailed level such as when planning a resource.
			 If a calendar is not found on the level of the resource itself, the calendar on
			 a higher level will be used such as on company level.</Paragraph>
         </ListItem>
         <ListItemHead>
            <Link href="/baanerp/tc/onlinemanual/000300" role="manual">Panoramica degli identificatori di configurazione</Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>Multiple occurrences or called units for one item can be
			 defined with unit effectivity functionality without having to define multiple
			 item codes. Usually, a unit identifies an exception to one standard
			 configuration. A great deal of item-related data can be included or excluded in
			 a unit, which is managed by exceptions.</Paragraph>
            <Paragraph>A unit is a system-generated number and consist of a
			 user-defined series and sequence number.</Paragraph>
         </ListItem>
         <ListItemHead>Unit effective data</ListItemHead>
         <ListItem>
            <List>
               <ListIntro>Exceptions can be linked to the data described in the
				following list. Therefore, this data is unit effective. Depending on the unit
				of the end item, the data that is effective for that unit will be
				used.</ListIntro>
               <ListItem>Engineering BOM lines: a unit of an end item can be linked
				to E-BOM lines at multiple lower levels.</ListItem>
               <ListItem>Bill of Material: also multilevel unit
				effectivity.</ListItem>
               <ListItem>Routings</ListItem>
               <ListItem>Routing operations</ListItem>
               <ListItem>Sourcing strategies</ListItem>
               <ListItem>Item purchased business partners</ListItem>
               <ListItem>Operation assignments</ListItem>
               <ListItem>Generic Bill of Material</ListItem>
               <ListItem>Flattened Assembly Parts and Operations</ListItem>
            </List>
         </ListItem>
         <ListItemHead>Requirements</ListItemHead>
         <ListItem>
            <Paragraph>Multiple units can be grouped together in to a requirement.
			 This can then be linked to unit-effective data such as a BOM line or routing.
			 This way multiple units can be assigned simultaneously.</Paragraph>
         </ListItem>
         <ListItemHead>Units and sales order entry</ListItemHead>
         <ListItem>
            <Paragraph>During sales order entry an existing unit can be selected.
			 New units can also be configured, during this process requirements are assigned
			 to a new unit code.</Paragraph>
         </ListItem>
         <ListItemHead>Units in inventory</ListItemHead>
         <ListItem>
            <Paragraph>Items selected for a specific unit can keep the unit
			 information during storage in inventory. This unit code is linked to a lot
			 number that is linked to the inventory information of the item.</Paragraph>
         </ListItem>
         <ListItemHead>Pegging</ListItemHead>
         <ListItem>
            <Paragraph>If a unique unit is configured for every sales order it can
			 be used as a peg for that sales order.</Paragraph>
         </ListItem>
         <ListItemHead>Cost price calculation</ListItemHead>
         <ListItem>
            <Paragraph>The standard cost price is based on the standard
			 configuration of the unit effective product. Estimated cost price calculations
			 can be performed. If the inventory valuation method is lot price and actual
			 costing is used, the actual costs can also be calculated per unit.</Paragraph>
         </ListItem>
      </List>
   </GeneralSection>
</ManualTopic>