<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tc/onlinemanual/000300" xml:lang="en">
   <Header>
      <Title>Overview of unit effectivity</Title>
      <Keyword type="header" order="d1e1434413">
         <Level1>Unit effectivity</Level1>
      </Keyword>
      <Keyword type="header" order="d1e1434416">
         <Level1>Effectivity units</Level1>
      </Keyword>
   </Header>
   <AimSection ID="aim_uniteffectivity_main_tasks">
      <Paragraph>Unit effectivity is a method to control the validity of
		variations on an end item. You can use unit effectivity for pegging purposes,
		or to model exceptions from a standard end item so that you can make variations
		without having to define separate item codes. As a result, you do not need to
		maintain separate BOMs for every combination of variations. End items can be,
		for example, airplanes or touring cars.</Paragraph>
      <Paragraph>The deviations consist of relatively small variations of the end
		item. For example, fitting red seats instead of blue ones, or a special type of
		radar or air-conditioning, in an otherwise standard type of
		airplane.</Paragraph>
      <List>
         <ListIntro>You can use unit effectivity to apply changes if:</ListIntro>
         <ListItem>Few changes are made.</ListItem>
         <ListItem>The changes apply to relatively small subsets of the end item.</ListItem>
         <ListItem>The changes result from customer requests, engineering, or
		  production.</ListItem>
      </List>
   </AimSection>
   <GeneralSection>
      <SectionTitle>Main concepts in unit effectivity</SectionTitle>
      <List>
         <ListIntro>In unit effectivity, a number of concepts can be
		  distinguished:</ListIntro>
         <ListItem>Effectivity unit</ListItem>
         <ListItem>Requirement</ListItem>
         <ListItem>Exception</ListItem>
      </List>
      <GeneralSection>
         <SectionTitle>Effectivity unit</SectionTitle>
         <Paragraph>An effectivity unit is a code that is linked to an end item
		  for identification, and which can represent the deviation(s) from the standard
		  end item. You can link an effectivity unit to manufactured items and purchased
		  items. For more information, refer to <Link href="/baanerp/tc/onlinemanual/000354" role="manual">Effectivity units</Link>.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Requirement</SectionTitle>
         <Paragraph>A requirement in unit effectivity is a business reason that
		  you define to describe the modifications and the variations for an item (the
		  exceptions). The requirement is expressed by exceptions, as follows.</Paragraph>
         <List>
            <ListIntro>Requirements can indicate, for example,
			 regulations:</ListIntro>
            <ListItem>USA: USA regulations</ListItem>
            <ListItem>EUR: European regulations</ListItem>
            <ListItem>ASIA: Asian regulations</ListItem>
         </List>
         <List>
            <ListIntro>Requirements can also, for example, concern an item’s
			 model:</ListIntro>
            <ListItem>LIGHT: Model with limited features</ListItem>
            <ListItem>NORMAL: Model with the normal features</ListItem>
            <ListItem>ADVANCED: Model with advanced features</ListItem>
         </List>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Exception</SectionTitle>
         <Paragraph>An exception in unit effectivity is the definition of a
		  deviation that applies to a unit effective item. An exception indicates, for
		  example, whether a specific BOM line or a specific routing operation is used
		  for an effectivity unit. Exceptions are often created as a result of customer
		  requirements, or technology upgrades. For more information, refer to <Link href="/baanerp/tc/onlinemanual/000355" role="manual">Exceptions in unit effectivity</Link>.</Paragraph>
      </GeneralSection>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>How to use unit effectivity</SectionTitle>
      <List>
         <ListIntro>You can use unit effectivity in the following three
		  ways:</ListIntro>
         <ListItem>To configure effectivity units</ListItem>
         <ListItem>As a lean configurator in <GUIRef href="/baanerp/sales" role="package">Sales</GUIRef>
         </ListItem>
         <ListItem>For pegging</ListItem>
      </List>
      <GeneralSection>
         <SectionTitle>Configuring effectivity units</SectionTitle>
         <Paragraph>Use effectivity units to define exceptions for an item’s
		  series, or series’ subset. You can use this approach in low-volume production
		  of complex products, for example, in aerospace and defence industries. Series
		  are defined for a specific end item, for example, for an airplane. Exceptions
		  are then defined, for example, for numbers 50-100 of an item’s series. This
		  method is the way in which unit effectivity was used in former releases. For an
		  example of this approach, refer to <Link href="/baanerp/tc/onlinemanual/000311" role="manual">To configure effectivity units</Link>.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Lean configurator</SectionTitle>
         <Paragraph>Use effectivity units to configure items on individual sales
		  order lines. You can use this approach in high-volume industries, such as
		  electronics industries. Unit effectivity is then used as ‘lean configurator’.
		  For an example of this approach, refer to <Link href="/baanerp/tc/onlinemanual/000358" role="manual">Unit effectivity as a lean configurator in Sales</Link>.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Pegging</SectionTitle>
         <Paragraph>Except for deviation modelling, you can use unit effectivity
		  for pegging purposes. If an effectivity unit is specified for the item on a
		  sales quotation line, a sales order line, or a sales contract line, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> provides <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>, <GUIRef href="/baanerp/procurement" role="package">Procurement</GUIRef>, and <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> with
		  that effectivity unit. In this way, you can trace the specific unit effective
		  item through the production process.</Paragraph>
         <Paragraph>The pegging process is multilevel. The effectivity unit linked
		  to the item on the sales order line is also linked to all (manufactured and
		  purchased) components of the item’s product structure. Therefore, material
		  purchased by purchase orders and used in production orders, on all levels of
		  the production structure, can be traced to the sales order line, the sales
		  quotation line, or the sales contract line.</Paragraph>
      </GeneralSection>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000301" role="manual">To set up unit effectivity</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000354" role="manual">Effectivity units</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000355" role="manual">Exceptions in unit effectivity</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000311" role="manual">To configure effectivity units</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000358" role="manual">Unit effectivity as a lean configurator in Sales</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000306" role="manual">Example of unit effectivity</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000360" role="manual">Unit effectivity and production order completion</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000303" role="manual">Interchangeability of effectivity units</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000357" role="manual">Identical configurations of effectivity units</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000359" role="manual">To define user-specific constraints in unit effectivity</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/ti/onlinemanual/000430" role="manual">Rework order procedure for effectivity units</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000356" role="manual">Unit effectivity in PCS</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/ti/onlinemanual/000311" role="manual">Unit effectivity in EDM</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/cp/onlinemanual/000308" role="manual" Update="No">Unit effectivity in Enterprise Planning</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tc/onlinemanual/000304" role="manual">Overview of serialized items</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>