<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/mfc/timfc0110m000" xml:lang="en">
   <Header>
      <Title>Serial End Item - As-Built Headers (timfc0110m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to maintain and display the <Link href="/baanerp/tc/glossary/glossary#000302" role="glossary">serialized end items</Link> built in the <Link href="/baanerp/ti/onlinemanual/tiasc" role="manual">Assembly Control (ASC)</Link> module or the <Link href="/baanerp/ti/onlinemanual/tisfc" role="manual">Shop Floor Control (SFC)</Link> module.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>For every individual
		  serialized item of an assembly order or a production order a line is present in
		  this session. For example, for an ordered quantity of six items, six lines are
		  present in this session, each line having a serial number that is a unique
		  identification of a single physical item. An example of a serial number is the
		  Vehicle Identification Number (VIN) of a car.</Paragraph>
         <Paragraph>If you select an item
		  in this session, and you click <GUIRef href="/baanerp/ti/mfc/timfc0110m000#as.built.components" role="command">As-Built Components</GUIRef> from the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu, the
		  serialized components of each serialized end item are displayed in the <Link href="/baanerp/ti/mfc/timfc0111m000" role="session">Serial End Item - As-Built Components (timfc0111m000)</Link> session. The serialized
		  end item and its serialized components form together the as-built structure,
		  which enables you to track order data, and to investigate which components are
		  in each individual end item.</Paragraph>
         <GeneralSection>
            <SectionTitle>Shop Floor Control (SFC)</SectionTitle>
            <Paragraph>The moment you can
			 display the as-built structure of a serialized item produced in <GUIRef href="/baanerp/ti/sfc" role="module">Shop Floor Control</GUIRef> depends on the <GUIRef href="/baanerp/ti/sfc/tisfc0100s000#tisfc000.serg" role="manual">Serial Generation Moment</GUIRef> field in the <GUIRef href="/baanerp/ti/sfc/tisfc0100s000" role="session">Shop Floor Control Parameters (tisfc0100s000)</GUIRef> session. At various moments, you can enable LN to generate serial
			 numbers based on a <Link href="/baanerp/tc/glossary/glossary#000300" role="glossary">mask</Link>. If the mask is not present, you must insert serial
			 numbers manually.</Paragraph>
         </GeneralSection>
         <GeneralSection>
            <SectionTitle>Assembly Control (ASC)</SectionTitle>
            <Paragraph>Serial numbers can
			 be generated when you have confirmed the line sequence in <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef>. You can
			 then display the as-built structure of the item.</Paragraph>
         </GeneralSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>You can only delete
			 an as-built serial item if the serial status is <GUIRef href="/baanerp/ti/domains/mfc.stat#created" role="option">Created</GUIRef>.</Paragraph>
         </Note>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tc/onlinemanual/000304" role="manual">Overview of serialized items</Link>
         </RelTopic>
         <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/tc/onlinemanual/000305" role="manual">To define a mask</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="timfc010.pdno">
         <Header>
            <Title>Production / Assembly Order</Title>
         </Header>
         <FuncDesc>The production order or the assembly order for which the
		  serialized item is produced.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="timfc010.mitm">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>The parent item for which the <Link href="/baanerp/tc/glossary/glossary#000302" role="glossary">serialized item</Link> is
		  derived.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcibd001.kitm">
         <Header>
            <Title>Item Type</Title>
         </Header>
         <FuncDesc>A classification of items used to identify if the item is, for
		example, a purchased item, a manufactured item, or an equipment item. Depending
		on the item's type, certain functions will only apply to that item.</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/tc/domains/kitm" role="domain">Item Type (a.k.a. kind of item)</Link>
            </Paragraph>
         </AllowedValues>
      </FieldHelp>
      <FieldHelp ID="tisfc001.qrdr">
         <Header>
            <Title>Quantity Ordered</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#000041" role="glossary">order quantity</Link> to be
		  produced. The estimates of materials and hours are based on this
		  quantity.</FuncDesc>
         <SimpleSection>
            <Paragraph>If no routing or
			 date has been entered yet, the calendar is based on the default routing and
			 100% utilization.</Paragraph>
            <Paragraph>If you are using <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity units</Link> when you
			 alter the value of the current field, the value of the <GUIRef href="/baanerp/ti/cst/ticst0101m000#order.quantity" role="manual">Quantity Ordered</GUIRef> field in the <GUIRef href="/baanerp/ti/cst/ticst0101m000" role="session">Estimated Materials (ticst0101m000)</GUIRef> session for each of the effectivity units will be
			 altered so that their total is the same as the value of the current field, and
			 the quantity is evenly distributed between each of the effectivity
			 units.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro>You can reduce the order quantity for released orders,
				for example, from 10 to 7. However, you cannot change the order quantity to a
				value less than the quantity that is reported as complete on an operation. If
				you want to enter a ordered quantity that is less than the quantity on an
				operation, you must reduce the quantity on the operation first. To do this, you
				must take the following into account:</ListIntro>
               <ListItem>If the operation
				status is <GUIRef href="/baanerp/ti/domains/sfc.opst#completed" role="option">Completed</GUIRef>, you must
				reset the operation status to <GUIRef href="/baanerp/ti/domains/sfc.opst#active" role="option">Active</GUIRef>.</ListItem>
               <ListItem>If a count point is
				used on the operation, you must first remove the count point before you can
				complete the order with a lower quantity.</ListItem>
            </List>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000157" role="manual">Order quantity dependent routings</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/tc/onlinemanual/000300" role="manual">Overview of unit effectivity</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000211" role="manual">Specify material to be issued</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="timfc010.mser">
         <Header>
            <Title>Serial Number</Title>
         </Header>
         <FuncDesc>The unique identification of a single physical item. LN uses a mask to
		generate the serial number. The serial number can consist of multiple data
		segments that represent, for example, a date, model and color information,
		sequence number, and so on.</FuncDesc>
         <SimpleSection>
            <Paragraph>Serial numbers can be generated for items and for tools.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="lot.code">
         <Header>
            <Title>Lot Code</Title>
         </Header>
         <FuncDesc>A number of items produced and stored together that are
		identified by a (lot) code. Lots identify goods.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="timfc010.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>A collection of manufacturing and purchasing actions that are
		performed especially for a particular customer order. A project is initiated by
		a customer order for items having a <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> order policy. The purpose of a project is to plan and coordinate the production
		of these items.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For a standard-to-order production, the project is only
			 used to link the item with the customer order. Otherwise, a project can
			 include:</ListIntro>
               <ListItem>Customized item data (BOMs and routings)</ListItem>
               <ListItem>Project planning (activity planning)</ListItem>
            </List>
            <Paragraph>A budget is a special type of project. A budget is used to
		  plan and estimate, not to carry out production.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000175" role="manual">Project types</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="timfc010.cspa">
         <Header>
            <Title>Element</Title>
         </Header>
         <FuncDesc>
            <Link href="/baanerp/cp/rrp/cprrp0101s000#cprrp001.cspa" role="formfield">Element</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="timfc010.cact">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>
            <Link href="/baanerp/cp/rrp/cprrp0101s000#cprrp001.cact" role="formfield">Activity</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="timfc010.effn">
         <Header>
            <Title>Item Effectivity Unit</Title>
         </Header>
         <FuncDesc>The item's <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity unit</Link>.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>When project pegging is implemented, only zero or one
			 effectivity unit is allowed on the distribution lines of one production
			 order.</Paragraph>
            <Paragraph/>
         </Note>
      </FieldHelp>
      <FieldHelp ID="timfc010.stat">
         <Header>
            <Title>Serial Status</Title>
         </Header>
         <FuncDesc>The status of the end item's serial number.</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/ti/domains/mfc.stat" role="domain">Serial Number Status</Link>
            </Paragraph>
         </AllowedValues>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000361" role="manual">Working with serialized items in <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>
               </Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="timfc010.vali">
         <Header>
            <Title>Valid</Title>
         </Header>
         <FuncDesc>If this check box is selected, the as-built structure is complete. An
		  as-built structure is complete when serial numbers are present for serialized
		  components, and lot numbers for lot-controlled (serialized) items. LN automatically
		  checks the completeness of the as-built structure when the serial status
		  changes (manually or automatically) from <GUIRef href="/baanerp/ti/domains/mfc.stat#created" role="option">Created</GUIRef> or <GUIRef href="/baanerp/ti/domains/mfc.stat#rejected" role="option">Rejected</GUIRef> to <GUIRef href="/baanerp/ti/domains/mfc.stat#assigned" role="option">Assigned</GUIRef>.</FuncDesc>
         <SimpleSection>
            <Paragraph>If an as-built structure is not valid, you cannot copy the
			 as-built structure to an as-maintained structure in the <Link href="/baanerp/ts/cfg/tscfg2210m000" role="session">Create Physical Breakdown Structure (tscfg2210m000)</Link> session. Furthermore, if
			 the <Link href="/baanerp/wh/inh/whinh0100m000#whinh000.chms" role="formfield">Check as-built serials</Link> field in the <GUIRef href="/baanerp/wh/inh/whinh0100m000" role="session">Inventory Handling Parameters (whinh0100m000)</GUIRef> session is <GUIRef href="/baanerp/tc/domains/hstp#warn" role="option">Warn</GUIRef> or <GUIRef href="/baanerp/tc/domains/hstp#block" role="option">Block</GUIRef>, the
			 item cannot be shipped.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000361" role="manual">Working with serialized items in <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef>
               </Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="timfc010.rwko">
         <Header>
            <Title>Rework Order</Title>
         </Header>
         <FuncDesc>If rework exists for the serialized item, this field displays
		  the rework order number.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000005" role="manual">Rework orders</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldGroup>
         <Title>Initial Hidden</Title>
         <FieldHelp ID="timfc010.cprj" OtherIDs="project.dsca">
            <Header>
               <Title>Project</Title>
            </Header>
            <FuncDesc>A collection of manufacturing and purchasing actions that are
		performed especially for a particular customer order. A project is initiated by
		a customer order for items having a <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> order policy. The purpose of a project is to plan and coordinate the production
		of these items.</FuncDesc>
            <SimpleSection>
               <List>
                  <ListIntro>For a standard-to-order production, the project is only
			 used to link the item with the customer order. Otherwise, a project can
			 include:</ListIntro>
                  <ListItem>Customized item data (BOMs and routings)</ListItem>
                  <ListItem>Project planning (activity planning)</ListItem>
               </List>
               <Paragraph>A budget is a special type of project. A budget is used to
		  plan and estimate, not to carry out production.</Paragraph>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/ti/onlinemanual/000175" role="manual">Project types</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="timfc010.cspa" OtherIDs="element.dsca">
            <Header>
               <Title>Element</Title>
            </Header>
            <FuncDesc>
               <Link href="/baanerp/cp/rrp/cprrp0101s000#cprrp001.cspa" role="formfield">Element</Link>
            </FuncDesc>
         </FieldHelp>
         <FieldHelp ID="timfc010.cact" OtherIDs="activity.dsca">
            <Header>
               <Title>Activity</Title>
            </Header>
            <FuncDesc>
               <Link href="/baanerp/cp/rrp/cprrp0101s000#cprrp001.cact" role="formfield">Activity</Link>
            </FuncDesc>
         </FieldHelp>
      </FieldGroup>
   </Fields>
   <FormCommands>
      <CommandHelp ID="as.built.components">
         <Header>
            <Title>As-Built Components</Title>
         </Header>
         <FuncDesc>LN starts
		  the <GUIRef href="/baanerp/ti/mfc/timfc0111m000" role="session">Serial End Item - As-Built Components (timfc0111m000)</GUIRef> session. In this session you can
		  display the components of the <Link href="/baanerp/tc/glossary/glossary#000302" role="glossary">serialized item</Link>.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="generate.serials">
         <Header>
            <Title>Generate Serial Numbers</Title>
         </Header>
         <FuncDesc>If you click this button, LN generates serial
		  numbers for the items produced for the assembly order.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="validate.as.built">
         <Header>
            <Title>Validate</Title>
         </Header>
         <FuncDesc>Click to check whether the as-built structure is complete. An
		  as-built structure is complete when serial numbers are present for serialized
		  components, and lot numbers for lot-controlled (serialized) items. An as-built
		  structure is incomplete when serial numbers and/or lot numbers are
		  missing.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>