<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tc/onlinemanual/000304" xml:lang="en">
   <Header>
      <Title>Overview of serialized items</Title>
      <Keyword type="header" order="d1e1154661">
         <Level1>serialized items</Level1>
      </Keyword>
      <Keyword type="header" order="d1e1154664">
         <Level1>item</Level1>
         <Level2>serialized</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1154669">
         <Level1>masks</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>A serialized item is a physical occurrence of a standard item
		that is given a unique lifetime serial number. This enables you to track the
		individual item throughout its lifetime, for example, through the design,
		production, testing, distribution, and maintenance phases. A serialized item
		can consist of other serialized components.</Paragraph>
      <Paragraph>Some business examples of the use of serialized items
		are:</Paragraph>
      <List>
         <ListItem>The vehicle identification number (VIN) that is used in the
		  car industry</ListItem>
         <ListItem>The tail numbers that are used in the Aerospace and Defense
		  industry</ListItem>
         <ListItem>The serial numbers that are used in the electronics industry</ListItem>
      </List>
      <Paragraph>A serialized item is identified by the item code in combination
		with the serial number.</Paragraph>
   </AimSection>
   <GeneralSection>
      <Paragraph>In LN, you can
		define every type of item as a <Link href="/baanerp/tc/glossary/glossary#000302" role="glossary">serialized item</Link>.</Paragraph>
      <Paragraph>Note that a serialized
		item is not the same as a <Link href="/baanerp/tc/glossary/glossary#000312" role="glossary">unit effective item</Link>. A serialized item has a serial
		number that is used to identify and track individual items, whereas a unit
		effectivity item has an effectivity unit that provides some information about
		the item's configuration. However, an item can be both serialized and unit
		effective.</Paragraph>
      <Paragraph>You can allocate serial numbers to serialized items during
		specific stages of an item's life cycle in the following LN packages:</Paragraph>
      <List>
         <ListItem>
            <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>
         </ListItem>
         <ListItem>
            <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>
         </ListItem>
         <ListItem>
            <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>
         </ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Manufacturing</SectionTitle>
      <Paragraph>In <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>, shop floor operators can enter serial
		numbers for new manufactured items during various stages of the production
		process. They can enter a serial number manually, or they can generate a serial
		number based on a specific mask.</Paragraph>
      <Paragraph>Serial numbers are entered in as-built structures. An as-built
		structure reflects the configuration of a product. The product has a serialized
		number; the component items in the as-built structure can be serialized or
		non-serialized. If the component items are serialized, serial numbers are
		either allocated to the components when they are issued from the warehouse, or
		the shop floor operators allocate the serial numbers when they add the
		components to the as-built structure.</Paragraph>
      <Paragraph>You can use the serial numbers assigned to manufactured items
		for tracking through warehousing, sales, and service processes.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Warehousing</SectionTitle>
      <Paragraph>The need to track items by means of serial numbers arises from
		the items' cost. The more expensive the item, the more closely you want to
		monitor the item during its life cycle. In general, expensive items are
		produced and handled in relatively small quantities, whereas the goods flow of
		less expensive items involves larger quantities. In LN, this concept is
		modeled in the following scenarios:</Paragraph>
      <List>
         <ListItemHead>Low volume</ListItemHead>
         <ListItem>This scenario is used for expensive items produced and handled
		  in relatively small quantities that require intensive tracking throughout the
		  warehouse flow. When received in the warehouse or issued from the warehouse, a
		  serial number is allocated, either manually or automatically, to each
		  serialized item. Upon receipt, each item/serial number combination is
		  individually stored in inventory. For each inventory transaction, such as a
		  receipt, transfer, or an issue, the inventory records of the serialized items
		  are updated.</ListItem>
         <ListItemHead>High volume</ListItemHead>
         <ListItem>The high volume scenario is used for relatively less expensive
		  items produced and handled in large quantities that require less intensive
		  tracking. In this scenario, serialized items are not stored in inventory.
		  Consequently, no inventory records exist that show updates on inventory
		  transactions. However, for each item-by-warehouse you can specify whether
		  serial numbers must be registered for receipts, transfers, and/or issues. This
		  helps you obtain an overview of the whereabouts of particular serialized items
		  through warehousing but also enables you to skip scrutinizing serials where you
		  do not need it.</ListItem>
      </List>
      <Paragraph>
         <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> also enables you to track the orders that initiated the
		receipt, transfer, or issue of serialized items, such as production orders,
		purchase orders, or sales orders. This option is available for both the high
		volume and the low volume scenario.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Service</SectionTitle>
      <Paragraph>To obtain product information and to register item replacements
		for service and maintenance purposes, you can copy as-built structures created
		in <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef> to product
		structures called <Link href="/baanerp/ts/glossary/glossary#000310" role="glossary">physical breakdowns</Link> in <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>.</Paragraph>
      <Paragraph>You can define an item as serialized to be able to track the
		item in all transactions that take place within <GUIRef href="/baanerp/ts" role="package">Service</GUIRef>. To interact with
		other areas such as production or warehousing, you must define the item as
		serialized in <GUIRef href="/baanerp/tc" role="package">Common</GUIRef> as
		well.</Paragraph>
      <Paragraph>The <GUIRef href="/baanerp/ts/msc" role="module">Maintenance Sales Control</GUIRef> and <GUIRef href="/baanerp/ts/wcs" role="module">Work Control System</GUIRef> modules deal with service and maintenance activities
		performed at your own company. The <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef> module deals with service and
		maintenance activities performed at customer sites. Both scenarios involve the
		sale and delivery of (spare part) items, the sale of repair and maintenance
		activities, the receipt of returned items, and replacement of
		items.</Paragraph>
      <List>
         <ListItemHead>
            <GUIRef href="/baanerp/ts/msc" role="module">Maintenance Sales Control</GUIRef>
         </ListItemHead>
         <ListItem>All sales activities involved in service and maintenance and
		  all repair and maintenance jobs on customer-owned items performed at your own
		  company are handled by means of <Link href="/baanerp/ts/glossary/glossary#000414" role="glossary">maintenance sales orders</Link>. For each type of activity, you
		  must add the appropriate type of order line to the <GUIRef href="/baanerp/wh/domains/ltc.tord#maint.sales" role="option">Maintenance Sales</GUIRef> order header. Selecting a particular order line triggers the
		  procedure that performs the activity, such as creating receipt lines and/or
		  outbound order lines, and so on. For more information, refer to <Link href="/baanerp/ts/domains/msc.lpro" role="domain">Line Procedure</Link>
         </ListItem>
         <ListItemHead>
            <GUIRef href="/baanerp/ts/wcs" role="module">Work Control System</GUIRef>
         </ListItemHead>
         <ListItem>All repair and maintenance activities performed at your own
		  site are handled by means of <Link href="/baanerp/ts/glossary/glossary#000385" role="glossary">work orders</Link>. These activities can include maintenance or
		  repair jobs on both customer-owned items and items owned by your own company.
		  Work orders for customer-owned items can be triggered by a <GUIRef href="/baanerp/wh/domains/ltc.tord#maint.sales" role="option">Maintenance Sales</GUIRef> order, which is described in the previous list item.</ListItem>
         <ListItemHead>
            <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>
         </ListItemHead>
         <ListItem>After you release a <Link href="/baanerp/ts/glossary/glossary#ServicOrder_ts" role="glossary">service order</Link>, LN issues the serialized component items required to
		  carry out the activities described on the service order by means of outbound
		  order lines of the <GUIRef href="/baanerp/wh/domains/ltc.tord#service" role="option">Service</GUIRef> origin.</ListItem>
      </List>
      <Paragraph>When the item and the components are issued for work orders or
		service orders, the serial numbers are, either automatically or manually,
		registered for the issued items.</Paragraph>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/ti/onlinemanual/000360" role="manual">Serialized items in <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>
         </Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/wh/onlinemanual/000382" role="manual">Serialized items in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>
         </Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/wh/onlinemanual/000375" role="manual">To set up serialized items</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/ti/onlinemanual/000431" role="manual">Rework order procedure for serialized items</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/ts/onlinemanual/000307" role="manual">To create a physical breakdown from an as-built structure</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>