<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tp/ptc/tpptc1255m000" xml:lang="en">
   <Header>
      <Title>Customize Items in Budget (tpptc1255m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to customize a range of
		  material budget lines. This is only relevant for standard items of type
		  Manufactured that have a to-order policy or for generic items that are
		  configured in <GUIRef href="/baanerp/ti/pcf" role="module">Product Configuration</GUIRef> or in the <GUIRef href="/baanerp/cf" role="package">Configurator</GUIRef> templates. The project status and the
		  budget status must be Free or Active. The budget line is updated with the
		  customized item. If the budget line quantity is zero, it is updated to one. You
		  can create one or more new PCS projects, or use an existing one.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If you copied a project or a budget, you must run this
			 session to customize the items on the budget lines of the new project. The
			 copied items are no longer customized, as the link with a PCS project is
			 project-specific.</Paragraph>
         </Note>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="cprj.f">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>Enter the project for which the items must be customized.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprj.t">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cpla.f">
         <Header>
            <Title>Plan</Title>
         </Header>
         <FuncDesc>This is the plan of the project that is displayed if the
		  project has an activity budget. If a leading plan is defined, this field is
		  automatically filled. If no leading plan is defined, the field remains empty
		  and you can enter a plan manually.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cpla.t">
         <Header>
            <Title>Plan</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cact.f">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>The From and To fields define a range of: <Link href="/baanerp/tp/glossary/glossary#000005" role="glossary">activity.</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cact.t">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>The From and To fields define a range of: <Link href="/baanerp/tp/glossary/glossary#000005" role="glossary">activity</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cspa.f">
         <Header>
            <Title>Element</Title>
         </Header>
         <FuncDesc>The From and To fields define a range of: <Link href="/baanerp/tp/glossary/glossary#Element_tp" role="glossary">element</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cspa.t">
         <Header>
            <Title>Element</Title>
         </Header>
         <FuncDesc>The From and To fields define a range of: <Link href="/baanerp/tp/glossary/glossary#Element_tp" role="glossary">element</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="item.f">
         <Header>
            <Title>From Item</Title>
         </Header>
         <FuncDesc>The From and To fields define a range of: <Link href="/baanerp/tc/glossary/glossary#000001" role="glossary">item</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="item.t">
         <Header>
            <Title>To Item</Title>
         </Header>
         <FuncDesc>The From and To fields define a range of: <Link href="/baanerp/tc/glossary/glossary#000001" role="glossary">item</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="new.proj">
         <Header>
            <Title>New PCS Project for each budget line</Title>
         </Header>
         <FuncDesc>If this check box is selected, a new PCS project is
		  created for each budget line item that needs to be customized. Note that this
		  option results in a number of PCS projects, and this can generate in a great
		  deal of administrative work.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="one.proj">
         <Header>
            <Title>One new PCS Project for all budget lines</Title>
         </Header>
         <FuncDesc>If this check box is selected, a new PCS project is
		  created for the first item to be customized. This same PCS project is used for
		  all the other items to be customized.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="exist.proj">
         <Header>
            <Title>Existing PCS Project for all budget lines</Title>
         </Header>
         <FuncDesc>If this check box is selected, you must enter a PCS
		  project in the PCS Project field. This PCS project is used for all budget lines
		  that require customization.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The existing PCS project must meet the following
				conditions:</ListIntro>
               <ListItem>The PCS project status must be Free, Active, or Simulated.</ListItem>
               <ListItem>The PCS project type cannot be Budget.</ListItem>
               <ListItem>The <GUIRef href="" role="manual">Engineering Allowed</GUIRef> check box in the <GUIRef href="" role="manual">Projects (tipcs2101m000)</GUIRef> session must be selected.</ListItem>
               <ListItem>The PCS project is not linked to another LN Project.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="without.proj">
         <Header>
            <Title>Without PCS Project (Only for Generic, Anonymous Items)</Title>
         </Header>
         <FuncDesc>If this check box is selected, LN creates a
		  new standard item, with no PCS project defined. The standard item is created
		  from the generic item, based on the product variant defined in the budget
		  lines.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The generic item must have the <GUIRef href="" role="manual">Order Policy</GUIRef> set to <GUIRef href="" role="manual">Anonymous</GUIRef>.</Paragraph>
         </Note>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The new standard item has the <GUIRef href="" role="manual">Order Policy</GUIRef> set to <GUIRef href="" role="manual">To Order</GUIRef>.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="pcs.proj">
         <Header>
            <Title>PCS Project</Title>
         </Header>
         <FuncDesc>Enter an existing PCS project for customization.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cost.calc">
         <Header>
            <Title>Cost Price Calculation</Title>
         </Header>
         <FuncDesc>If this check box is selected, the cost price is
		  calculated for the customized item, but the cost price of the item on the
		  budget line remains the same. You can also calculate the cost price with the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="update.price">
         <Header>
            <Title>Update Cost Price of Budget Line</Title>
         </Header>
         <FuncDesc>If this check box is selected, the cost price is
		  calculated and updated in the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session and entered in the Cost
		  Price field of the items in the budget. If you leave this check box unselected,
		  your original budget cost price is retained.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>