<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tp/ppc/tpppc2511m000" xml:lang="en">
   <Header>
      <Title>Material Costs (tpppc2511m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to display material costs
		  for a project. This session shows the cost transactions which are not yet
		  processed to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>If costs are the result of actions in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef> or <GUIRef href="/baanerp/procurement" role="package">Procurement</GUIRef>, these
		  transactions are automatically created. The cost of goods for which a purchase
		  invoice is received are automatically transferred to this session. In addition,
		  cost transactions that are entered manually are shown.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>If this session is started from the <GUIRef href="/baanerp/tp/ppc/tpppc2811m000" role="session">Costs (tpppc2811m000)</GUIRef> session, financial data cannot be maintained for
				transactions entered in this session.</ListItem>
               <ListItem>Transaction lines with the <GUIRef href="/baanerp/tp/domains/ppc.tetb#order.invoice" role="option">Invoice (Purchase Order)</GUIRef> posting type that were approved by <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> and unapproved
				again later can be recognized, because for the unapproved transactions the
				purchase order related fields are set to zero.</ListItem>
            </List>
         </Note>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tp/onlinemanual/000096" role="manual">To register costs and commitments</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tp/onlinemanual/000322" role="manual">To use posting types</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tpppc211.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>The project code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc211.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>The item's code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc211.sern">
         <Header>
            <Title>Seq</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#SequenNumber_tc" role="glossary">sequence number</Link> code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc211.phit">
         <Header>
            <Title>Phantom Item</Title>
         </Header>
         <FuncDesc>A <Link href="/baanerp/ti/glossary/glossary#Phantom_ti" role="glossary">phantom</Link> item that includes a <Link href="/baanerp/tp/glossary/glossary#000323" role="glossary">bill of material</Link>.</FuncDesc>
         <SimpleSection>
            <Paragraph>The value of this field is retrieved from the <GUIRef href="/baanerp/tp/pss/tppss6116m000" role="session">Warehouse order - Phantom item Link (tppss6116m000)</GUIRef> session.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc211.cspa">
         <Header>
            <Title>Element</Title>
         </Header>
         <FuncDesc>The smallest part of an element structure. An element is used
		to define the (structure of the) work of the project, so that you can carry it
		out.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc211.cact">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>The smallest part of the activity structure used for a
		time-scaled budget. An entity that is used to represent a part of a project in
		an activity structure.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>LN distinguishes the following activity types:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#wbsel" role="option">WBS Element</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#cosac" role="option">Project Cost Account</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#worpa" role="option">Work Package</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#plapa" role="option">Planning Package</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#milst" role="option">Milestone</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc211.cstl">
         <Header>
            <Title>Extension</Title>
         </Header>
         <FuncDesc>The specific agreements within or in addition to the initial
		contract. An extension falls outside the initial contract with the sold-to
		business partner. Extensions can be assigned to the bottom-up
		budget.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>LN distinguishes four extension types:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#additional.work" role="option">Scope Change</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#provision.entry" role="option">Provisional Amount</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#risc.settl" role="option">Fluctuation Settlement</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#quan.settl" role="option">Quantities to be Settled</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc211.quan">
         <Header>
            <Title>Quantity</Title>
         </Header>
         <FuncDesc>The cost object's quantity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc211.cuni">
         <Header>
            <Title>Un.</Title>
         </Header>
         <FuncDesc>The unit of measure for the cost object. This unit can affect
		how budget line quantities are calculated.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc211.curc">
         <Header>
            <Title>Cur</Title>
         </Header>
         <FuncDesc>The currency used in the transaction document.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc211.amoc">
         <Header>
            <Title>Cost Amount</Title>
         </Header>
         <FuncDesc>The quantity times the price of the cost object.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc211.orno">
         <Header>
            <Title>Order Number</Title>
         </Header>
         <FuncDesc>The purchase order number that is assigned when an order or
		  delivery is entered and assigned from <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, in case a
		  purchase invoice is processed on the basis of the corresponding purchase
		  order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc211.pono">
         <Header>
            <Title>Posn no</Title>
         </Header>
         <FuncDesc>The purchase order line number that is assigned when an order
		  or delivery is entered and assigned from <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> package, in case
		  a purchase invoice is processed on the basis of the corresponding purchase
		  order.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>