<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/pcs/tipcs2220m000" xml:lang="en">
   <Header>
      <Title>Generate (Project) Structure for Product Variant (tipcs2220m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to generate a <Link href="/baanerp/ti/glossary/glossary#000074" role="glossary">product structure</Link> from a <Link href="/baanerp/ti/glossary/glossary#GeneriItem_ti" role="glossary">generic item</Link>, or to
		  regenerate a <Link href="/baanerp/td/glossary/glossary#ProducVarian_td" role="glossary">product variant</Link> structure of
		  an existing project.</Paragraph>
      </AimSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>This session can only
		  be used for generic items. Product variant structures are always customized.</Paragraph>
      </Note>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="regenerate">
         <Header>
            <Title>Regenerate Existing Product Variant</Title>
         </Header>
         <FuncDesc>If this check box is selected, the existing product variant structure is
		  deleted and a new product variant structure is generated. This action can
		  update existing sales order lines and sales quotation lines.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is cleared, a new product variant structure is generated.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cust.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>An item produced on a customer specification for a specific
		project. A customized item can have a customized BOM and/or a customized
		routing and is normally not available as a standard item. A customized item
		can, however, be derived from a standard item or a generic item.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tc/glossary/glossary#ItemCode_tc" role="glossary">item code</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="product.variant">
         <Header>
            <Title>Product Variant</Title>
         </Header>
         <FuncDesc>In this field you can select a product variant.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="generic.item">
         <Header>
            <Title>Generic Item</Title>
         </Header>
         <FuncDesc>An item that exists in multiple product variants. Before any
		manufacturing activities are performed on a generic item, the item must be
		configured to determine the desired product variant.</FuncDesc>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <Paragraph>Generic item: electric drill</Paragraph>
            <List>
               <ListIntro>Options:</ListIntro>
               <ListItem>3 power sources (batteries, 12 V or 220 V)</ListItem>
               <ListItem>2 colors (blue, gray).</ListItem>
            </List>
            <Paragraph>A total of 6 product variants can be produced with these
		  options.</Paragraph>
         </ExampleSection>
      </FieldHelp>
      <FieldHelp ID="project.code">
         <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>
      </FieldHelp>
      <FieldHelp ID="ref.date">
         <Header>
            <Title>Reference date</Title>
         </Header>
         <FuncDesc>The date on which the BOM and the routing operations are
		  exploded when a customized product structure is generated. If you use the <Link href="/baanerp/ti/pcs/tipcs2220m000" role="session">Generate (Project) Structure for Product Variant (tipcs2220m000)</Link> session to generate a customized product structure, this <GUIRef href="/baanerp/ti/pcs/tipcs2220m000#ref.date" role="manual">Reference date</GUIRef> fills the <Link href="/baanerp/ti/pcf/tipcf5101s000#tipcf500.pcfd" role="formfield">Product Configuration Date</Link> field in the <GUIRef href="/baanerp/ti/pcf/tipcf5101s000" role="session">Product Variants (tipcf5101s000)</GUIRef> session.</FuncDesc>
         <SimpleSection>
            <Paragraph>Note that in a customized product structure, the date in
			 this field (the <GUIRef href="/baanerp/ti/pcs/tipcs2220m000#ref.date" role="manual">Reference date</GUIRef>) can differ from the <GUIRef href="/baanerp/ti/pcf/tipcf5101s000#tipcf500.pcfd" role="manual">Product Configuration Date</GUIRef> in the <GUIRef href="/baanerp/ti/pcf/tipcf5101s000" role="session">Product Variants (tipcf5101s000)</GUIRef> session. The <GUIRef href="/baanerp/ti/pcs/tipcs2220m000#ref.date" role="manual">Reference date</GUIRef> does not affect existing product
			 variants. However, if an existing product variant is initialized, the <GUIRef href="/baanerp/ti/pcf/tipcf5101s000#tipcf500.pcfd" role="manual">Product Configuration Date</GUIRef> field of the product variant
			 will be filled with the <GUIRef href="/baanerp/ti/pcs/tipcs2220m000#ref.date" role="manual">Reference date</GUIRef>.</Paragraph>
            <Paragraph>If an existing product variant structure is regenerated, the <GUIRef href="/baanerp/ti/pcs/tipcs2220m000#ref.date" role="manual">Reference date</GUIRef> field is filled with the <GUIRef href="/baanerp/ti/pcf/tipcf5101s000#tipcf500.pcfd" role="manual">Product Configuration Date</GUIRef> of the product variant structure
			 to be regenerated.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="update.ref.date">
         <Header>
            <Title>Update Project Reference Date</Title>
         </Header>
         <FuncDesc>If this check box is selected, the project's reference date is updated by the
		  reference date in this session.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is cleared, the project's reference date is <Emphasis>not</Emphasis> updated by the reference date in this
			 session.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="gener.pol">
         <Header>
            <Title>Generation Method</Title>
         </Header>
         <FuncDesc>This field allows you to specify the method used to generate
		  the project structure. You can select the following methods:</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <List>
               <ListItemHead>
                  <GUIRef href="/baanerp/tc/domains/cpge#eto" role="option">Engineer-to-Order</GUIRef>
               </ListItemHead>
               <ListItem>ERP Enterprise generates a product structure for the item including customized items,
				customized BOMs and customized routings.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/tc/domains/cpge#sto" role="option">Standard-to-Order</GUIRef>
               </ListItemHead>
               <ListItem>ERP Enterprise creates a PCS project for the item but no customized BOM and routing. The PCS
				project is mainly used for pegging purposes, for example, to track down the
				costs for the customized item. Note that in case of a generic item, ERP Enterprise creates a PCS
				project, customized BOM, and customized routing for the generic part of the
				item structure. However, for (lower level) parts of the item structure with a
				production BOM, the items become customized, but no customized BOM and routing
				are generated.</ListItem>
            </List>
         </AllowedValues>
      </FieldHelp>
      <FieldHelp ID="check.stock">
         <Header>
            <Title>Check Standard Item Inventory</Title>
         </Header>
         <FuncDesc>If this check box is selected, the inventory level for the standard items is
		  checked. If sufficient inventory of a standard item is available, no customized
		  item is generated. If no inventory, or insufficient inventory is available, the
		  customized item is generated.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="upd.quot.price">
         <Header>
            <Title>Update Prices Quotation Lines</Title>
         </Header>
         <FuncDesc>If this check box is selected, prices in existing quotation lines are
		  updated.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="upd.sales.price">
         <Header>
            <Title>Update Prices Sales Order Lines</Title>
         </Header>
         <FuncDesc>If this check box is selected, prices in existing sales order lines are
		  updated.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="print.warnings">
         <Header>
            <Title>Print Warnings</Title>
         </Header>
         <FuncDesc>If you select this checkbox, any warnings during the execution
		  of the session will be printed.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>