<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/pcs/tipcs4120m000" xml:lang="en">
   <Header>
      <Title>Module Planning (tipcs4120m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>In the overview session
		  you can list the modules by project.</Paragraph>
      </AimSection>
      <GeneralSection>
         <List>
            <ListIntro>In the details session you can:</ListIntro>
            <ListItem>Maintain the <Link href="/baanerp/ti/glossary/glossary#000085" role="glossary">module</Link> planning by <Link href="/baanerp/ti/glossary/glossary#000023" role="glossary">project</Link>.</ListItem>
            <ListItem>Record rough material
			 requirements for the project.</ListItem>
            <ListItem>Record (final)
			 assembly scheduling for the project.</ListItem>
            <ListItem>Link modules to
			 activities for activity-controlled material planning per project.</ListItem>
         </List>
         <Paragraph>Module planning is the
		  relation between activities of the network planning and the modules. Modules
		  can be materials that can jeopardize the finish date of the project because of
		  their long delivery times. These materials are also referred to as critical
		  materials. A module can also be an assembled part.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Module planning is
			 created by manual input or by running the <GUIRef href="/baanerp/ti/pcs/tipcs2210m000" role="session">Copy Project (tipcs2210m000)</GUIRef> session.</Paragraph>
         </Note>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tipcs420.cprj">
         <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="tipcs420.mdul">
         <Header>
            <Title>Module</Title>
         </Header>
         <FuncDesc>A planning unit for a customized, manufactured, or purchased
		part, for which the logistical planning is related directly to the project
		network planning. A module may be a more or less complex compound part or a
		single part, such as a long delivery time part.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs420.item">
         <Header>
            <Title>Customized 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>
      </FieldHelp>
      <FieldHelp ID="tipcs420.effn">
         <Header>
            <Title>Effectivity Unit</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity unit</Link> on which
		  the generation of the requirements planning is based. The requirements planning
		  is based on item/effectivity unit combination. The unit which is connected to
		  the item is always the unit of the top-item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs420.clus" OtherIDs="tcemm135.desc">
         <Header>
            <Title>Cluster</Title>
         </Header>
         <FuncDesc>In <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, a grouping of warehouses connected to each other by
		supplying relationships.</FuncDesc>
         <SimpleSection>
            <Paragraph>A cluster represents a geographical location that consists of
		  one or more warehouses. <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> considers these warehouses as one unit for planning purposes.</Paragraph>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>
               <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> uses the this field to determine the location of the material
			 demand for this module.</Paragraph>
            <Paragraph>
               <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> retrieves the cluster <Link href="/baanerp/tc/glossary/glossary#000069" role="glossary">segment</Link> of the code of the <Link href="/baanerp/ti/glossary/glossary#PlanItems_ti" role="glossary">plan item</Link> from this field.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs420.cact">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>The activity related to the module.</FuncDesc>
         <SimpleSection>
            <Paragraph>The activity, which
			 is part of the activity network for the project, controls the logistical
			 planning for the relevant module.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs420.sftm">
         <Header>
            <Title>Safety Time (Perc)</Title>
         </Header>
         <FuncDesc>The safety time, expressed as a percentage of the activity's
		  duration, indicates when the relevant module should be completed. It is
		  calculated from the planned finish date for the activity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs420.fixq">
         <Header>
            <Title>Fixed Plan Quantity</Title>
         </Header>
         <FuncDesc>The fixed plan quantity indicates whether it is entered by hand
		  or whether it is automatically determined on the basis of the actual material
		  requirements by using the RRP calculation.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs420.plnq">
         <Header>
            <Title>Plan Quantity</Title>
         </Header>
         <FuncDesc>This is the manually entered plan quantity that must be planned
		  during the RRP calculation.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>When transferring
			 planned RRP purchase orders or RRP production orders, the fixed plan quantity
			 is automatically reduced by the order quantity, so that the remaining plan
			 quantity can be replanned during a following RRP calculation.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tcibd001.cuni">
         <Header>
            <Title>Inventory Unit</Title>
         </Header>
         <FuncDesc>The unit of measure in which the inventory of an item is
		recorded, such as piece, kilogram, box of 12, or meter.</FuncDesc>
         <SimpleSection>
            <Paragraph>The inventory unit is also used as the base unit in measure
		  conversions, especially for conversions that concern the order unit and the
		  price unit on a purchase order or a sales order. These conversions always use
		  the inventory unit as the base unit. An inventory unit therefore applies to all
		  item types, also to item types that cannot be kept in stock.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cprj.status">
         <Header>
            <Title>Status</Title>
         </Header>
         <FuncDesc>Indicates the current progress of the project.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>