<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/cp/onlinemanual/at000340" xml:lang="en">
   <Header>
      <Title>Component CTP reservations</Title>
      <Keyword type="header" order="d1e171641">
         <Level1>CTP reservations</Level1>
         <Level2>component</Level2>
      </Keyword>
      <Keyword type="header" order="d1e171646">
         <Level1>Component</Level1>
         <Level2>CTP reservations</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <Figure space-and-orientation="indented-estimated">
         <FigIntro>Assume the following multi-level bill of material for end item
		  JOSUEF11:</FigIntro>
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" width="899" height="341"
                   SRC="../images/tr_graph_at_component_ctp_reservations.png"
                   alt="[...]"/>
         <FigCaption>Component CTP reservations</FigCaption>
      </Figure>
      <Paragraph>If you enter and save an order for JOSUEF11, CTP reservations
		are placed on the components based on the same logic as used for the CTP check.
		The CTP reservation is stored in the CTP reservations session, and aggregated
		to the item master plan in case the component has one.</Paragraph>
      <Paragraph>The timing of the component reservations is based on the
		lead-time offset logic that is also used during the CTP check; in other words,
		in the order horizon by means the LTO on the BOM line and the inbound and
		outbound lead-time, and the safety time and extra lead-time. The timing of the
		planned issue that is created after running the order planning can, therefore,
		differ slightly from the CTP reservation, because timing of the planned issue
		is determined on a more detailed backward planning logic.</Paragraph>
      <List>
         <ListIntro>The meaning of the quantity fields is:</ListIntro>
         <ListItem>
            <GUIRef href="/baanerp/cp/rrp/cprrp0111m000#cprrp011.aqua" role="manual">Allocated Quantity</GUIRef>: ATP quantity of the component that is allocated by means of
		  the CTP reservation to fulfill all or part of the demand.</ListItem>
         <ListItem>
            <GUIRef href="/baanerp/cp/rrp/cprrp0111m000#cprrp011.nqua" role="manual">Needed Quantity</GUIRef>: required quantity passed from the parent of this
		  component.</ListItem>
         <ListItem>
            <GUIRef href="/baanerp/cp/rrp/cprrp0111m000#cprrp011.cqua" role="manual">CTP Quantity</GUIRef>: quantity passed to the child of this component.</ListItem>
      </List>
      <Paragraph>Formula:</Paragraph>
      <Formula space-and-orientation="indented-estimated">
         <Paragraph>Needed quantity - allocated quantity = CTP quantity</Paragraph>
      </Formula>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Sales order demand for JOSUEF11 = 100 pieces. The following
		  CTP reservations are created for the right-side branch of the BOM. The ATP
		  column states the ATP quantities that are available during the CTP
		  check.</Paragraph>
         <Paragraph>If you save the sales order line, the other columns are
		  updated in the CTP reservations session.</Paragraph>
         <TABLE width="100%" border="1" borderstyle="default"
                space-and-orientation="indented-estimated">
            <TBODY noTR="6">
               <TR no="1" isLast="false">
                  <TH colspan="5" rowspan="1">CTP reservations</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TH rowspan="1" colspan="1">Item</TH>
                  <TH rowspan="1" colspan="1">ATP</TH>
                  <TH rowspan="1" colspan="1">Allocated</TH>
                  <TH rowspan="1" colspan="1">Needed</TH>
                  <TH rowspan="1" colspan="1">CTP</TH>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">JOSUEF11</TD>
                  <TD rowspan="1" colspan="1">40</TD>
                  <TD rowspan="1" colspan="1">0</TD>
                  <TD rowspan="1" colspan="1">60</TD>
                  <TD rowspan="1" colspan="1">60</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD rowspan="1" colspan="1">JOSUEF15</TD>
                  <TD rowspan="1" colspan="1">0</TD>
                  <TD rowspan="1" colspan="1">0</TD>
                  <TD rowspan="1" colspan="1">60</TD>
                  <TD rowspan="1" colspan="1">60</TD>
               </TR>
               <TR no="5" isLast="false">
                  <TD rowspan="1" colspan="1">JOSUEF16</TD>
                  <TD rowspan="1" colspan="1">20</TD>
                  <TD rowspan="1" colspan="1">20</TD>
                  <TD rowspan="1" colspan="1">60</TD>
                  <TD rowspan="1" colspan="1">40</TD>
               </TR>
               <TR no="6" isLast="true">
                  <TD rowspan="1" colspan="1">JOSUEF17</TD>
                  <TD rowspan="1" colspan="1">40</TD>
                  <TD rowspan="1" colspan="1">40</TD>
                  <TD rowspan="1" colspan="1">40</TD>
                  <TD rowspan="1" colspan="1">0</TD>
               </TR>
            </TBODY>
         </TABLE>
         <List>
            <ListIntro>The calculation proceeds:</ListIntro>
            <ListItem>No allocation of the ATP is made on this level, because the
			 sales order for JOSUEF11 already created a planned issue for this item. A total
			 of 60 pieces is required (100 – 40).</ListItem>
            <ListItem>JOSUEF15 has no availability, therefore, the same quantities
			 again pass to the next component level.</ListItem>
            <ListItem>JOSUEF16 has an ATP of 20, so this quantity is allocated to
			 fulfill part of the needed quantity. Still to build are 40 pieces, therefore,
			 CTP quantity changes to 40.</ListItem>
            <ListItem>JOSUEF17 has ATP of 40, so this quantity is allocated to
			 fulfill the remaining needed quantity.</ListItem>
            <ListItem>To build is changed to zero, because the entire demand is
			 fulfilled.</ListItem>
         </List>
      </ExampleSection>
      <Note>
         <SectionTitle> Note</SectionTitle>
         <Paragraph>Even if for the JOSUEF15 and JOSUEF16 items the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000#cprpd100.cria" role="manual">Critical in CTP</GUIRef> check box is cleared, records are
		  created in the CTP reservations sessions.</Paragraph>
         <Paragraph>This step is required to pass the needed quantity and CTP
		  quantity through the BOM. However, the allocated quantity will always be zero
		  for non-critical items, even if ATP is present for this type of
		  item.</Paragraph>
      </Note>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Pegged order number field and originating plan item
		field</SectionTitle>
      <Paragraph>In the previous example, the CTP reservation of the component
		JOSUEF17 is made for the sales order for end item JOSUEF11.</Paragraph>
      <Paragraph>However, the originating plan item is the direct parent,
		JOSUEF16.</Paragraph>
      <Paragraph>The reason for this is because the quantities that you see in
		the figure are passed by means of this item, as described
		previously.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Capacity CTP reservations</SectionTitle>
      <Paragraph>As described, capacity CTP depends on the presence of a resource
		master plan. Therefore, capacity CTP is plan-period based.</Paragraph>
      <Paragraph>The CTP reservation is stored in both the resource master plan
		and the capacity CTP reservations session.</Paragraph>
      <Paragraph>CTP reservations are only created for resources that are
		critical in CTP and have a resource master plan.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>CTP time fence</SectionTitle>
      <Paragraph>A CTP time fence for component and capacity CTP can be defined
		in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef> session.</Paragraph>
      <Paragraph>In the CTP time fence, the availability of components and
		capacities will not be checked. This concept is introduced to prevent
		situations in which deliveries to customers are promised although this is not
		realistic because no time is available anymore to build extra quantities.</Paragraph>
      <Paragraph>In fact, the CTP time fence usually equals the item’s production
		time fence (frozen period for planning). The production time fence, also
		defined in the Item-Planning sessions, is used during order
		planning.</Paragraph>
      <Paragraph>The planned production order will be placed outside this time
		fence, although the demand may originate from within the time fence. This will
		create lateness.</Paragraph>
      <Paragraph>To assure that demand is not promised too early, only ATP can be
		promised inside the CTP time fence and not CTP. To give the user flexibility
		and to make it more explicit, a separate CTP time fence is introduced instead
		of using the production time fence.</Paragraph>
   </GeneralSection>
</ManualTopic>