<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ts/onlinemanual/000468" xml:lang="en">
   <Header>
      <Title>To create a physical breakdown from a Bill of Materials</Title>
      <Keyword type="header" order="d1e2782812">
         <Level1>Configuration Management</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>You can use the Create Physical Breakdown Structure
		(tscfg2210m000) session to create the physical breakdown from a <Link href="/baanerp/ti/glossary/glossary#BillOfMateri_ti" role="glossary">bill of material (BOM)</Link>.</Paragraph>
   </AimSection>
   <GeneralSection>
      <Paragraph>If you create a <Link href="/baanerp/ts/glossary/glossary#000310" role="glossary">physical breakdown</Link> from a bill of material, this results
		in a direct copy of effective items present in the <Link href="/baanerp/ti/bom/tibom1110m000" role="session">Bill of Material (tibom1110m000)</Link> session of ERP Enterprise Manufacturing to
		the Serialized Items (tscfg2100m000) session of ERP Enterprise Service. If no item
		service data is present, ERP Enterprise uses the item service defaults maintained for item type and item
		group to create items in Service.</Paragraph>
      <GeneralSection>
         <SectionTitle>To create a physical breakdown from a Bill of
		  Materials</SectionTitle>
         <Paragraph>Start the Create Physical Breakdown Structure (tscfg2210m000)
		  session.</Paragraph>
         <Paragraph>In the <GUIRef href="" role="manual">Source</GUIRef> field, select <GUIRef href="" role="manual">Bill of Material</GUIRef>.</Paragraph>
         <Paragraph>
            <GUIRef href="" role="manual">Sales Deliveries:</GUIRef> Use this option to create a
		  physical breakdown from Sales (after sales). The end item of the sales order, <Link href="/baanerp/ti/glossary/glossary#ProducBom_ti" role="glossary">production BOM</Link>, is copied to a physical breakdown. If
		  this check box is selected, you can use the fields in the <GUIRef href="" role="manual">Selection Range</GUIRef> group box to create a physical breakdown from a range of <Link href="/baanerp/ts/glossary/glossary#000306" role="glossary">installation group</Link>, <Link href="/baanerp/ts/glossary/glossary#000075" role="glossary">item</Link>, or <Link href="/baanerp/ts/glossary/glossary#Objects_ts" role="glossary">serialized item</Link>. For this selection range, a physical
		  breakdown is created.</Paragraph>
         <Paragraph>
            <GUIRef href="" role="manual">Item Effectiveness:</GUIRef> If this check box is
		  selected, the items' validity is checked before the items are copied to <Link href="/baanerp/ts/glossary/glossary#000310" role="glossary">physical breakdown</Link>.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>ERP Enterprise validates the following:</SectionTitle>
         <Paragraph>If the item is revision controlled and derived from sales
		  deliveries, ERP Enterprise checks
		  for revision from the sales order line. ERP Enterprise checks for the
		  effective date from engineering items for the given item and
		  revision.</Paragraph>
         <Paragraph>If the item is not revision controlled and derived from sales
		  deliveries, then ERP Enterprise checks for the effective date from sales based on Configuration Date in sales
		  parameter.</Paragraph>
         <Paragraph>If the item is not from sales deliveries then, ERP Enterprise takes the effective
		  date given as input.</Paragraph>
         <Paragraph>
            <GUIRef href="" role="manual">Unit Effectivity:</GUIRef> When ERP Enterprise creates the
		  physical breakdown structure from <Link href="/baanerp/ti/glossary/glossary#BillOfMateri_ti" role="glossary">bill of material (BOM)</Link>, unit effectivity
		  is considered as a validation. The items belongs to the unit effectivity are
		  only created in service. Unit effectivity is checked from <Link href="/baanerp/ts/glossary/glossary#Objects_ts" role="glossary">serialized item</Link>. If unit effectivity is not present in
		  the serialized item then, ERP Enterprise checks the unit effectivity from a sales order line if the item
		  originates from sales.</Paragraph>
         <Paragraph>
            <GUIRef href="" role="manual">Fall Back on BOM if source is not found:</GUIRef> If
		  this check box is selected when the <Link href="/baanerp/ts/glossary/glossary#000310" role="glossary">physical breakdown</Link> structure is created from an <Link href="/baanerp/ts/glossary/glossary#000311" role="glossary">as-built structure</Link> or <Link href="/baanerp/ts/glossary/glossary#000300" role="glossary">item breakdown</Link> and no source item is found, ERP Enterprise copies the bill of
		  material of that item to the physical breakdown structure.</Paragraph>
         <Paragraph>
            <GUIRef href="" role="manual">Consistency checks:</GUIRef> If the physical breakdown
		  is generated directly from a <Link href="/baanerp/ti/glossary/glossary#ProducBom_ti" role="glossary">production BOM</Link>, ERP Enterprise performs a consistency check, both at ERP Enterprise <GUIRef href="" role="manual">Manufacturing</GUIRef> and ERP Enterprise <GUIRef href="" role="manual">Service</GUIRef>, to ensure the
		  structure is defined without any mismatch. The items in such a structure must
		  be defined in ERP Enterprise Service with appropriate <Link href="/baanerp/ts/glossary/glossary#ServicItemDa_ts" role="glossary">service-item data</Link> with related
		  configuration control, and checked for consistency.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>ERP Enterprise performs the following consistency checks:</SectionTitle>
         <Paragraph>To distinguish between the items relevant and not relevant to
		  service, ERP Enterprise copies the
		  items that are configuration controlled, namely serialized or anonymous items,
		  into <Link href="/baanerp/ts/glossary/glossary#000310" role="glossary">physical breakdown</Link>. If no <Link href="/baanerp/ts/glossary/glossary#ServicItemDa_ts" role="glossary">service-item data</Link> is available for an <Link href="/baanerp/ts/glossary/glossary#000075" role="glossary">item</Link>, based on service defaults, the item data will be
		  created in <GUIRef href="" role="manual">items-service</GUIRef> and copied to <GUIRef href="" role="manual">physical breakdown</GUIRef>.</Paragraph>
      </GeneralSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>You must create service item data for all the items copied
		  from a production bill of material to the physical breakdown
		  structure.</Paragraph>
      </Note>
      <Paragraph>ERP Enterprise checks for consistency with respect to the structure formation. A serialized
		item must always be situated above an anonymous item, so that the structure
		remains consistent with the item definition. ERP Enterprise begins to copy when
		inconsistency is detected in the structure formation and an error report is
		generated.</Paragraph>
      <Paragraph>ERP Enterprise prints an error report if a serialized item is present under an anonymous item,
		as illustrated in the following example:</Paragraph>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="9">
               <TR no="1" isLast="false">
                  <TD width="62" rowspan="1" colspan="1">
                     <GUIRef href="" role="manual">Level</GUIRef>
                  </TD>
                  <TD width="52" rowspan="1" colspan="1">
                     <GUIRef href="" role="manual">Item</GUIRef>
                  </TD>
                  <TD width="112" rowspan="1" colspan="1">
                     <GUIRef href="" role="manual">Conf.cont</GUIRef>
                  </TD>
                  <TD width="136" rowspan="1" colspan="1">
                     <GUIRef href="" role="manual">Item Service Data Present</GUIRef>
                  </TD>
               </TR>
               <TR no="2" isLast="false">
                  <TD width="62" rowspan="1" colspan="1">0</TD>
                  <TD width="52" rowspan="1" colspan="1">X</TD>
                  <TD width="112" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="136" rowspan="1" colspan="1">Yes</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD width="62" rowspan="1" colspan="1">1</TD>
                  <TD width="52" rowspan="1" colspan="1">Y</TD>
                  <TD width="112" rowspan="1" colspan="1">Anonymous</TD>
                  <TD width="136" rowspan="1" colspan="1">Yes</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD width="62" rowspan="1" colspan="1">2</TD>
                  <TD width="52" rowspan="1" colspan="1">A</TD>
                  <TD width="112" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="136" rowspan="1" colspan="1">Yes
				  ------- Problem 1</TD>
               </TR>
               <TR no="5" isLast="false">
                  <TD width="62" rowspan="1" colspan="1">2</TD>
                  <TD width="52" rowspan="1" colspan="1">B</TD>
                  <TD width="112" rowspan="1" colspan="1">None</TD>
                  <TD width="136" rowspan="1" colspan="1">No</TD>
               </TR>
               <TR no="6" isLast="false">
                  <TD width="62" rowspan="1" colspan="1">1</TD>
                  <TD width="52" rowspan="1" colspan="1">Z</TD>
                  <TD width="112" rowspan="1" colspan="1">Anonymous</TD>
                  <TD width="136" rowspan="1" colspan="1">Yes</TD>
               </TR>
               <TR no="7" isLast="false">
                  <TD width="62" rowspan="1" colspan="1">2</TD>
                  <TD width="52" rowspan="1" colspan="1">A</TD>
                  <TD width="112" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="136" rowspan="1" colspan="1">Yes ------- Problem
				  2</TD>
               </TR>
               <TR no="8" isLast="false">
                  <TD width="62" rowspan="1" colspan="1">3</TD>
                  <TD width="52" rowspan="1" colspan="1">B</TD>
                  <TD width="112" rowspan="1" colspan="1">None</TD>
                  <TD width="136" rowspan="1" colspan="1">No</TD>
               </TR>
               <TR no="9" isLast="true">
                  <TD width="62" rowspan="1" colspan="1">4</TD>
                  <TD width="52" rowspan="1" colspan="1">C</TD>
                  <TD width="112" rowspan="1" colspan="1">Anonymous</TD>
                  <TD width="136" rowspan="1" colspan="1">Yes -------
				  Problem 3</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Paragraph>All three problems are caused by serialized items present
		  under anonymous items.</Paragraph>
         <Paragraph>ERP Enterprise prints the following error report:</Paragraph>
         <List>
            <ListIntro>For item X, no PBD could be generated,
			 reason(s):</ListIntro>
            <ListItem>Parent item (Y-anonymous) has a lower configuration control
			 setup than Child item (A-serialized).</ListItem>
            <ListItem>Parent item (Z-anonymous) has a lower configuration control
			 setup than Child item (A-serialized).</ListItem>
            <ListItem>Parent item (B-none) has a lower configuration control setup
			 than Child item (C-anonymous).</ListItem>
         </List>
      </ExampleSection>
      <Paragraph>ERP Enterprise checks for consistency with respect to the loops in the <Link href="/baanerp/ti/glossary/glossary#BillOfMateri_ti" role="glossary">bill of material (BOM)</Link>. If two anonymous
		items occur in an opposite fashion, with respect to an existing structure
		definition, the anonymous items can subsequently end up in a loop.</Paragraph>
      <Paragraph>ERP Enterprise prints an error report if it detects a loop in a bill of material, as
		illustrated in the following example:</Paragraph>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="9">
               <TR no="1" isLast="false">
                  <TD width="58" rowspan="1" colspan="1"> 
                     <GUIRef href="" role="manual">Level</GUIRef>
                  </TD>
                  <TD width="42" rowspan="1" colspan="1">
                     <GUIRef href="" role="manual">Item</GUIRef>
                  </TD>
                  <TD width="74" rowspan="1" colspan="1">
                     <GUIRef href="" role="manual">Conf.cont</GUIRef>
                  </TD>
                  <TD width="161" rowspan="1" colspan="1">
                     <GUIRef href="" role="manual">Item Service Data Present</GUIRef>
                  </TD>
               </TR>
               <TR no="2" isLast="false">
                  <TD width="58" rowspan="1" colspan="1">0</TD>
                  <TD width="42" rowspan="1" colspan="1">X</TD>
                  <TD width="74" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="161" rowspan="1" colspan="1">Yes</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD width="58" rowspan="1" colspan="1">1</TD>
                  <TD width="42" rowspan="1" colspan="1">Y</TD>
                  <TD width="74" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="161" rowspan="1" colspan="1">Yes</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD width="58" rowspan="1" colspan="1">2</TD>
                  <TD width="42" rowspan="1" colspan="1">A</TD>
                  <TD width="74" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="161" rowspan="1" colspan="1">Yes</TD>
               </TR>
               <TR no="5" isLast="false">
                  <TD width="58" rowspan="1" colspan="1">2</TD>
                  <TD width="42" rowspan="1" colspan="1">B</TD>
                  <TD width="74" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="161" rowspan="1" colspan="1">Yes</TD>
               </TR>
               <TR no="6" isLast="false">
                  <TD width="58" rowspan="1" colspan="1">1</TD>
                  <TD width="42" rowspan="1" colspan="1">Z</TD>
                  <TD width="74" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="161" rowspan="1" colspan="1">Yes</TD>
               </TR>
               <TR no="7" isLast="false">
                  <TD width="58" rowspan="1" colspan="1">2</TD>
                  <TD width="42" rowspan="1" colspan="1">A</TD>
                  <TD width="74" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="161" rowspan="1" colspan="1">Yes</TD>
               </TR>
               <TR no="8" isLast="false">
                  <TD width="58" rowspan="1" colspan="1">3</TD>
                  <TD width="42" rowspan="1" colspan="1">B</TD>
                  <TD width="74" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="161" rowspan="1" colspan="1">Yes</TD>
               </TR>
               <TR no="9" isLast="true">
                  <TD width="58" rowspan="1" colspan="1">4</TD>
                  <TD width="42" rowspan="1" colspan="1">X</TD>
                  <TD width="74" rowspan="1" colspan="1">Serialized</TD>
                  <TD width="161" rowspan="1" colspan="1">Yes ------- Problem
				  1</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Paragraph>ERP Enterprise prints the following error report:</Paragraph>
         <Paragraph>For item X, no PBD could be generated for the following
		  reason(s):</Paragraph>
         <List>
            <ListItem>Cycle detected in BOM.</ListItem>
         </List>
      </ExampleSection>
   </GeneralSection>
</ManualTopic>