<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/cp/rpd/cprpd3120m000" xml:lang="en">
   <Header>
      <Title>Bill of Critical Materials (cprpd3120m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to define a <Link href="/baanerp/ti/glossary/glossary#000081" role="glossary">bill of critical material (BCM)</Link>. A BCM indicates the components that are regarded as critical
		  during the production process of an item. The BCM is a kind of summary of the
		  production <Link href="/baanerp/ti/glossary/glossary#BillOfMateri_ti" role="glossary">bill of material (BOM)</Link> that
		  contains only the important components, that is, the relationships between a <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link> and its critical items.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000135" role="manual">To generate critical material requirements</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/ti/onlinemanual/000182" role="manual">Critical items</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000020" role="manual">Master planning, an overview</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000149" role="manual">Plan levels and product families</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/cp/onlinemanual/000406" role="manual">Warehouse on the BCM line</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="cprpd320.plni">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link> for which you want to generate a bill of
		  critical material.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprpd320.sern">
         <Header>
            <Title>Sequence Number</Title>
         </Header>
         <FuncDesc>The number that identifies the unique relationship between the
		  plan item and critical item shown on this line. The number is the critical BOM
		  equivalent of a production BOM position number. LN automatically
		  generates this number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprpd320.citm">
         <Header>
            <Title>Critical Item</Title>
         </Header>
         <FuncDesc>Enter the <Link href="/baanerp/ti/onlinemanual/000182" role="manual">Critical items</Link> that you want to relate to a <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link>.</FuncDesc>
         <SimpleSection>
            <Paragraph>The critical item
			 and plan item must be on the same <Link href="/baanerp/ti/glossary/glossary#PlanLevel_ti" role="glossary">plan level</Link> in the <Link href="/baanerp/cp/glossary/glossary#000402" role="glossary">aggregation relationship</Link>.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The critical item
			 must itself be a plan item, and must have the order system <GUIRef href="/baanerp/tc/domains/osys#mps" role="option">Planned</GUIRef>.</Paragraph>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000182" role="manual">Critical items</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="cprpd320.indt">
         <Header>
            <Title>Effectivity Date</Title>
         </Header>
         <FuncDesc>The date from which the relationship between the plan item and
		  the critical item is valid.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprpd320.exdt">
         <Header>
            <Title>Expiry Date</Title>
         </Header>
         <FuncDesc>The date after which the relationship between the critical item
		  and the plan item is no longer valid. If no date is given, the relationship is
		  valid on any date after the effective date.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprpd320.rqan">
         <Header>
            <Title>Quantity Required</Title>
         </Header>
         <FuncDesc>Enter the quantity of the required critical item to produce the <Link href="/baanerp/ti/glossary/glossary#MainItem_ti" role="glossary">main item</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprpd320.ltmo">
         <Header>
            <Title>Lead-Time Offset</Title>
         </Header>
         <FuncDesc>Enter the lead-time offset for the critical item.</FuncDesc>
         <SimpleSection>
            <Paragraph>The lead-time offset
			 is the total number of working days of the production process. It is calculated
			 from the stage in which the relevant critical material is needed, to the final
			 stage of the production process.</Paragraph>
            <Paragraph>The lead-time offset
			 can be considered as the difference between the requirement date and the moment
			 of time at which the material is needed.</Paragraph>
         </SimpleSection>
         <SimpleSection>
            <SectionTitle>Offsetting logic bill of critical
			 materials</SectionTitle>
            <Paragraph>LN takes into account the parent/child relation
			 when it generates <Link href="/baanerp/cp/glossary/glossary#000074" role="glossary">dependent demand</Link> for
			 critical components. When you carry out the <GUIRef href="/baanerp/cp/rmp/cprmp1202m000" role="session">Generate Master Planning (cprmp1202m000)</GUIRef> session, Enterprise Planning performs the following
			 steps to compute dependent demand for critical components:</Paragraph>
            <ProcedureList>
               <ListItem>LN offsets the <Link href="/baanerp/ti/glossary/glossary#LeadTime_ti" role="glossary">lead time</Link> of the parent item
				to the <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan periods</Link>, and divides the forecasted demand to the plan
				periods.</ListItem>
               <ListItem>LN rounds the forecasted quantities that it found in step one according to the <Link href="/baanerp/tc/glossary/glossary#UnitSet_tc" role="glossary">unit set</Link> that you defined
				for the item in the <GUIRef href="/baanerp/tc/ibd/tcibd0501m000" role="session">Items - General (tcibd0501m000)</GUIRef> session.</ListItem>
               <ListItem>During the next step, LN multiplies each BCM
				quantity by the total of the parent item for each plan period.</ListItem>
               <ListItem>LN rounds the critical components to the unit set that you defined for them in the <GUIRef href="/baanerp/tc/ibd/tcibd0501m000" role="session">Items - General (tcibd0501m000)</GUIRef> session.</ListItem>
            </ProcedureList>
            <Paragraph>The major advantage
			 of this offsetting method is that LN always plans a multiple of the BCM quantity
			 for each plan period, so that you do not have to wait to produce the parent
			 item until the <Link href="/baanerp/cp/glossary/glossary#000018" role="glossary">production plan</Link> for all the
			 periods over which the dependent demand is spread, is executed.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>LN takes the network routing (routing for
			 phantom items) into account when it calculates the lead-time offset.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="cprpd320.qtdp">
         <Header>
            <Title>Quantity Dependent</Title>
         </Header>
         <FuncDesc>If this check box is selected, LN takes quantities into account when it
		  explodes the <Link href="/baanerp/ti/glossary/glossary#000081" role="glossary">bill of critical materials</Link>.
		  The quantity that results from the dependent demand explosion is the product of
		  the forecasted amount of parent items and the value that you specified in the
		  Quantity Required field.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is cleared, LN treats the quantity as
			 a fixed quantity in each explosion. The quantity that results from the
			 dependent demand explosion is the quantity that you defined in the <GUIRef href="/baanerp/cp/rpd/cprpd3120m000#cprpd320.rqan" role="manual">Quantity Required</GUIRef> field.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cprpd320.cwar">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>The warehouse from which the critical item is delivered.</FuncDesc>
         <SimpleSection>
            <Paragraph>The warehouse you
			 specify determines whether the dependent demand of the plan item is transferred
			 to a clustered item.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/cp/onlinemanual/000406" role="manual">Warehouse on the BCM line</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="inv.unit">
         <Header>
            <Title>Quantity Required</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/wh/glossary/glossary#000337" role="glossary">inventory unit</Link> to express
		  the required quantity.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>