<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/wh/onlinemanual/ue0200" xml:lang="en">
   <Header>
      <Title>Master Data for Unit Effectivity</Title>
      <Keyword type="header" order="d1e2591569">
         <Level1>Master Data</Level1>
         <Level2>unit effectivity</Level2>
      </Keyword>
      <Keyword type="header" order="d1e2591574">
         <Level1>Unit effectivity</Level1>
         <Level2>master data</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <SectionTitle>Unit effective item</SectionTitle>
      <Paragraph>An effectivity unit exists only in combination with an item and
		does not exist independently. The items for which units are generated are
		called <GUIRef href="" role="manual">unit effective items</GUIRef>. Usually, the unit effective item
		is the top-level item of a multi-level structure for which a sales order is
		created. However, end items do not have to be unit effective. If, for example,
		you create a sales order or production order for an item, you can enter an
		effectivity unit even if the item is not unit effective, or even if the unit
		belongs to a different unit effective item. In this way, selling spare parts or
		subassemblies for a specific configuration is supported.</Paragraph>
      <Paragraph>If multiple unit effective end items exist, you can use the
		connection between unit and end item to trace easily for which top-level item
		an activity is performed upstream in the production process.</Paragraph>
      <Paragraph>Suppose that in the example of Chapter 1, "Unit Effectivity
		Concept," the conveyor belt is a unit effective end item, and unit 15 is
		defined for the conveyor. In that situation, a user can trace back lower level
		purchase orders and production orders to that specific conveyor. Refer to the
		following figure:</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="500" width="700"
                   SRC="../images/tr_chart_ue_2_unit_effective_item_1.png"
                   alt="[...]"/>
      </Figure>
      <Paragraph>To define an item as unit effective in the Item - General
		(tcibd0501m000) details session, on the Unit Effectivity tab, select the <GUIRef href="" role="manual">Unit Effective End Item</GUIRef> check box.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Effectivity series</SectionTitle>
      <Paragraph>Units are unique numbers generated by LN.
		These numbers do not make any sense to users. Instead, users want to have codes
		that make sense to them. Therefore, before the unit is generated, users can
		enter an identification code for each occurrence of an item. This code consists
		of a series code and a sequence number. To define multiple sequence numbers
		simultaneously, you can simply enter the first sequence number and the last
		sequence number that you want to define. For every sequence number in
		combination with the series code, LN generates a unique unit code.</Paragraph>
      <Paragraph>For example, you could generate 20 sequence numbers for the AGR
		(agricultural) series. You can perform this process in the Items - Effectivity
		Series (tcuef0101m000) session.</Paragraph>
      <GeneralSection>
         <SectionTitle>Units</SectionTitle>
         <Paragraph>After you define the first and the last sequence number of the
		  series, LN generates the units for every sequence number of the series. Start the
		  Items ‑ Effectivity Series (tcuef0101m000) session, and on the <GUIRef href="" role="manual">Specific</GUIRef> menu, click <GUIRef href="" role="manual">Generate Effectivity Units</GUIRef>.</Paragraph>
         <Paragraph>LN generates a unit for every sequence number.</Paragraph>
      </GeneralSection>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Standard configuration and exceptions</SectionTitle>
      <Paragraph>For many entities in LN, you
		can determine whether the entities belong to the standard configuration, or
		whether the entities are only valid for a specific unit.</Paragraph>
      <Paragraph>You must define on the entity, for example, the BOM line,
		whether the entity belongs to the standard configuration or to a specific unit.
		A so-called <GUIRef href="" role="manual">exception</GUIRef>, which is related to the entity, is used
		to define whether that entity is valid or not for a specific unit. LN uses
		the following logic to verify if an entity is valid, that is effective or
		selected, for a specific entity:</Paragraph>
      <List>
         <ListIntro>If one of the following statements is true, an entity is <GUIRef href="" role="manual">valid</GUIRef> for a unit:</ListIntro>
         <ListItem>The entity belongs to the standard configuration</ListItem>
         <ListItem>The entity does not belong to the standard configuration, but
		  the entity is valid for the specified unit</ListItem>
      </List>
      <List>
         <ListIntro>If one of the following is true, an entity is <GUIRef href="" role="manual">invalid</GUIRef> for a unit:</ListIntro>
         <ListItem>The entity does not belong to the standard configuration</ListItem>
         <ListItem>The entity belongs to the standard configuration but the entity
		  is invalid for the specified unit</ListItem>
      </List>
      <Paragraph>In other words, if an entity belongs to the standard
		configuration, the entity is valid for all units unless an exception specifies
		that the entity is invalid for a unit. If an entity does not belong to the
		standard configuration, the entity is invalid for a all units, unless an
		exception specifies that the entity is valid for a specific unit.</Paragraph>
      <Paragraph>For example, you can define that two BOM lines of the conveyor,
		BELT LONG and BELT THICK, belong to specific units. Those BOM lines do not
		belong to the standard configuration. The other BOM lines of the conveyor
		belong to the standard configuration.</Paragraph>
      <Paragraph>Exceptions enable you to specify whether entities are valid or
		invalid for specific units. To define exceptions, you must use the Exceptions
		(tcuef0105m000) session, which you can start from the sessions in which unit
		effective entities are defined, for example, the Bill of Material
		(tibom1110m000) session and the Routing Operations (tirou1102m000)
		session.</Paragraph>
      <Paragraph>In the example, the conveyor component BELT LONG is valid for
		unit 9584. You specify this in an exception for that BOM line. To start the
		Exceptions (tcuef0105m000) session, click <GUIRef href="" role="manual">Exceptions</GUIRef> in the
		Bill of Material (tibom1110m000) session.</Paragraph>
      <Paragraph>The Exceptions (tcuef0105m000) session already contains the BOM
		line data. You must only specify for which unit the BOM line is valid or
		invalid. In the example, you specify that the BOM is valid for unit
		9584:</Paragraph>
      <Paragraph>After you define exceptions for a unit effective entity, you can
		exclude the entity, in this case, the BOM line, from the standard configuration
		by clearing the <GUIRef href="" role="manual">Standard Configuration</GUIRef> check box in the Bill
		of Material (tibom1110m000) session.</Paragraph>
      <Paragraph>If the entity does not have any exceptions, you cannot specify
		whether or not an entity belongs to the standard configuration. If no
		exceptions are linked, and you can clear the <GUIRef href="" role="manual">Standard Configuration</GUIRef> check box, the entity is valid neither for the standard
		configuration nor for an effectivity unit</Paragraph>
      <Paragraph>For example, if BELT STANDARD is part of the standard
		configuration, but that item must be invalid for unit 9584 and 9585, you can
		specify this by exceptions.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Requirements</SectionTitle>
      <Paragraph>Previously in this document, you can read how to define the
		validity of entities at requirement level. In the exceptions, you can define
		for which requirement an entity is valid or invalid.</Paragraph>
      <Paragraph>You define requirements in the Requirements (tcuef0106m000)
		session.</Paragraph>
      <Paragraph>For every requirement, you define the related effectivity units
		in the Requirement – Effectivity Units (tcuef0107m000) session. The following
		figure shows that units 9584 and 9587 consist of a long belt:</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="200" width="822"
                   SRC="../images/tr_chart_ue_2_requirements_tcuef0107m000.png"
                   alt="[...]"/>
      </Figure>
      <Paragraph>Linking effectivity units to requirements is useful if you want
		to define an exception for multiple effectivity units simultaneously. If, for
		example, an exception is required in the BOM of item conveyor, you can define
		the exception for a specific requirement, after which the exception is valid
		for all effectivity units linked to the requirement. In this way, you do not
		need to define the exception for every effectivity unit separately.</Paragraph>
      <Paragraph>In the example, the long belt, a BOM component of the conveyor,
		is valid for requirement LB. If you define this in an exception, the BOM line
		is automatically valid for unit 9584 and 9587:</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="167" width="582"
                   SRC="../images/tr_chart_ue_2_requirements_tcuef0105m000.png"
                   alt="[...]"/>
      </Figure>
      <Paragraph>You cannot refer both to a requirement and a unit in one
		exception. You can define an exception at requirement level or at unit level.</Paragraph>
      <GeneralSection>
         <SectionTitle>Group requirements</SectionTitle>
         <List>
            <ListIntro>In the Item – Requirements (tcuef0108m000) session, you can
			 group requirements by linking them to a specific entity or entity combination.
			 The following entities can be used to group requirements:</ListIntro>
            <ListItem>Sold-to business partner</ListItem>
            <ListItem>Ship-to country</ListItem>
            <ListItem>Ship-from warehouse</ListItem>
            <ListItem>End item</ListItem>
         </List>
         <Paragraph>You can use grouped requirements during sales order entry. If
		  you enter a sales order for a specific sold-to business partner, ship-to
		  country, ship-from warehouse, end item, or combination of entities, you can
		  start the Item – Requirements (tcuef0108m000) session from the Effectivity Unit
		  (tcuef0102m000) session to find the applicable requirements. If required,
		  however, you can still select requirements that are not defined in the Item –
		  Requirements (tcuef0108m000) session.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Default requirements</SectionTitle>
         <Paragraph>In the Item – Requirements (tcuef0108m000) session, you can
		  also define requirements as defaults. If you enter a sales order, and multiple
		  sets of requirements apply to the sales order, LN retrieves only the default requirements.</Paragraph>
         <Paragraph>For example, you define a number of requirements for a
		  specific end item, of which some of the requirements are defaults. You also
		  define some default requirements for a specific sold-to business partner. If
		  you create a sales order for this specific end item and sold-to business
		  partner, LN retrieves only the default requirements.</Paragraph>
      </GeneralSection>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Set up interchangeability</SectionTitle>
      <Paragraph>Chapter 1, "Unit Effectivity Concept," explains that various
		units can be interchangeable.</Paragraph>
      <List>
         <ListIntro>You can set up interchangeability at various
		  levels:</ListIntro>
         <ListItem>Company level</ListItem>
         <ListItem>Item level</ListItem>
         <ListItem>Series level</ListItem>
      </List>
      <GeneralSection>
         <SectionTitle>Company level</SectionTitle>
         <Paragraph>If the <GUIRef href="" role="manual">All Effectivity Units Are Interchangeable</GUIRef> check box is selected in the Unit Effectivity
		  Parameters (tcuef0100s000) session, all units in a specific company are
		  interchangeable. This setting overrules all other interchangeability settings
		  at lower levels.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Item level</SectionTitle>
         <Paragraph>If the <GUIRef href="" role="manual">Effectivity Units Are Interchangeable</GUIRef> check box is selected in the Item – General (tcibd0501m000) details session,
		  all units of a specific item are interchangeable. This setting overrules
		  interchangeability settings at series level.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Series level</SectionTitle>
         <List>
            <ListIntro>The most detailed level at which you can define
			 interchangeability is the series level. At series level, you can select the
			 following check boxes:</ListIntro>
            <ListItem> 
               <GUIRef href="" role="manual">Interchangeable in Series</GUIRef> If this check box
			 is selected, all units in the series specified in the <GUIRef href="" role="manual">Unit Series Code</GUIRef> field are interchangeable.</ListItem>
            <ListItem> 
               <GUIRef href="" role="manual">Interchangeable with other Interchangeable Series</GUIRef> If this check box is selected, the units of the series
			 specified in the <GUIRef href="" role="manual">Unit Series Code</GUIRef> field are interchangeable
			 with the units of any other series of the same item for which the <GUIRef href="" role="manual">Interchangeable with other Interchangeable Series</GUIRef> check box is
			 selected.</ListItem>
            <ListItem> 
               <GUIRef href="" role="manual">Interchangeable with Standard Configuration and vice versa</GUIRef> If this check box is selected, the units of the series that is
			 specified in the <GUIRef href="" role="manual">Unit Series Code</GUIRef> field are interchangeable
			 with the standard configuration. Technically speaking, the standard
			 configuration is unit 0 (zero).</ListItem>
         </List>
         <Paragraph>The <GUIRef href="" role="manual">All Effectivity Units are Interchangeable</GUIRef> check box and the <GUIRef href="" role="manual">End Item is Interchangeable</GUIRef> check box in the
		  Items – Effectivity Series (tcuef0101m000) session displays the settings you
		  made on company level or item level. If one of those check boxes is selected,
		  you cannot select the other check boxes.</Paragraph>
      </GeneralSection>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Configure units</SectionTitle>
      <List>
         <ListIntro>You can configure units in the Effectivity Unit
		  (tcuef0102m000) session. In this session, you can carry out the following
		  processes:</ListIntro>
         <ListItem>Link requirements</ListItem>
         <ListItem>Calculate cost prices by unit</ListItem>
         <ListItem>Link sales characteristics</ListItem>
         <ListItem>Define process variables</ListItem>
      </List>
      <Paragraph>You usually configure units on sales order lines. For more
		information, refer to Chapter 4, "Units in Sales." You can, however, configure
		every unit in LN.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Sales prices</SectionTitle>
      <Paragraph>You can specify an upgrade price for every requirement. Based on
		the selected requirements for an effectivity unit, LN adds
		the upgrade prices to the sales price, which can result in a different sales
		price for every effectivity unit. The final sales price that is displayed on
		the sales order line includes the requirements’ upgrade prices.</Paragraph>
      <Paragraph>You must define unit upgrade prices in the Requirements
		(tcuef0106m000) session.</Paragraph>
   </GeneralSection>
</ManualTopic>