<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/cp/onlinemanual/000200" xml:lang="en">
   <Header>
      <Title>Generic items in Enterprise Planning</Title>
      <Keyword type="header" order="d1e195932">
         <Level1>Generic items</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>A generic item represents
		an item structure that is configured according to a customer's preferences.
		This configuration takes place in the <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> module.</Paragraph>
      <List>
         <ListIntro>When an actual sales order is closed for a generic item, LN generates a project structure, and the demand is recorded for the
		  corresponding project item. This means that for the generic item itself, no
		  actual demand exists. Only the following types of demand can exist for a
		  generic item:</ListIntro>
         <ListItem>Forecast demand</ListItem>
         <ListItem>Dependent demand
		  resulting from forecast demand at a higher BOM or BCM level</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Master-based planning</SectionTitle>
      <Paragraph>Master-based planning
		for a generic item is similar to master-based planning for a normal item. You
		can maintain an item master plan for a generic item, and use BCMs and BCCs to
		explode critical requirements.</Paragraph>
      <List>
         <ListIntro>As long as the configured (project) items involved are
		  derived from the generic item (see the <GUIRef href="/baanerp/tc/ibd/tcibd0101s000#tcibd001.dfit" role="manual">Derived-from Item</GUIRef> field in the <GUIRef href="/baanerp/tc/ibd/tcibd0101s000" role="session">Item - General (tcibd0101s000)</GUIRef> session), you can:</ListIntro>
         <ListItem>Maintain one item master
		  plan that includes both the generic item and its configured items</ListItem>
         <ListItem>Apply forecast
		  consumption to the forecast of the generic item</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Order-based planning</SectionTitle>
      <List>
         <ListIntro>Order-based planning for a generic item differs from normal
		  order-based planning in that it uses:</ListIntro>
         <ListItem>A generic BOM instead of
		  a normal BOM.</ListItem>
         <ListItem>A generic routing
		  instead of a normal routing.</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Generic BOM</SectionTitle>
      <List>
         <ListIntro>The following fields in the <GUIRef href="/baanerp/ti/pcf/tipcf3110m000" role="session">Generic BOMs (tipcf3110m000)</GUIRef> session are relevant for planning in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>:</ListIntro>
         <ListItem> 
            <GUIRef href="/baanerp/ti/pcf/tipcf3110m000#tipcf310.pqan" role="manual">Planning Quantity</GUIRef>
         </ListItem>
         <ListItem> 
            <GUIRef href="/baanerp/ti/pcf/tipcf3120m000#tipcf320.pper" role="manual">Planning Perc.</GUIRef>
         </ListItem>
         <ListItem> 
            <GUIRef href="/baanerp/ti/pcf/tipcf3120m000#tipcf320.ltmo" role="manual">Lead Tm Offset</GUIRef>
         </ListItem>
      </List>
      <List>
         <ListIntro>The planning percentage roughly indicates how often this
		  particular material is actually used for a configured item. The required
		  quantity for planning is computed as follows: The requirement date of a
		  material in a generic BOM is determined as follows:</ListIntro>
         <ListItem>Start from the planned
		  finish date of the planned order involved</ListItem>
         <ListItem>Plan backward the
		  lead-time offset from the generic BOM</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Generic routing</SectionTitle>
      <Paragraph>The operations in a
		generic routing are not planned with regular backward planning, but each
		operation involved is planned with its own lead-time offset.</Paragraph>
      <List>
         <ListIntro>The following fields in the <GUIRef href="/baanerp/ti/pcf/tipcf3120m000" role="session">Generic Routing (tipcf3120m000)</GUIRef> session are relevant for planning in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>:</ListIntro>
         <ListItem> 
            <GUIRef href="/baanerp/ti/pcf/tipcf3120m000#tipcf320.pptm" role="manual">Planned Prod. Time</GUIRef>
         </ListItem>
         <ListItem> 
            <GUIRef href="/baanerp/ti/pcf/tipcf3120m000#tipcf320.pper" role="manual">Planning Perc.</GUIRef>
         </ListItem>
         <ListItem> 
            <GUIRef href="/baanerp/ti/pcf/tipcf3120m000#tipcf320.ltmo" role="manual">Lead Tm Offset</GUIRef>
         </ListItem>
      </List>
      <Paragraph>The planned production
		time is used to plan the operation involved.</Paragraph>
      <List>
         <ListIntro>The planning percentage roughly indicates how often this
		  particular operation is actually used for a configured item. The capacity use
		  of the operation is computed as follows: The start date and finish date of an
		  operation in a generic routing are determined as follows:</ListIntro>
         <ListItem>Start from the planned
		  finish date of the planned order involved</ListItem>
         <ListItem>Plan backward the
		  following offset to determine the operation's finish date:</ListItem>
      </List>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/cp/onlinemanual/000088" role="manual">Project items in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>
         </Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/cp/onlinemanual/000334" role="manual">Phantoms of generic items</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>