<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tp/ppc/tpppc2575m000" xml:lang="en">
   <Header>
      <Title>Subcontracting Cost History (tpppc2575m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to list the costs that are
		  posted to the project history for different projects for the cost type <GUIRef href="/baanerp/tp/domains/pdm.cotp#subcontracting" role="option">Subcontracting</GUIRef>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <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>
               <ListItem>Postings of type <GUIRef href="/baanerp/tp/domains/ppc.tetb#value.corr" role="option">Price Variance</GUIRef> do not reflect financial data, such as delivery company, from <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> because these
				transactions are now handled as normal integration transactions and not as
				'invoice specific'. Invoice number is only important for real invoice related
				transactions. Price variance can also arise due to a change in receipt price in <GUIRef href="/baanerp/procurement" role="package">Procurement</GUIRef>. The
				invoice data is not present for this price variance either.</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>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tpppc275.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>The project code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.cspa">
         <Header>
            <Title>Element</Title>
         </Header>
         <FuncDesc>The element code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.cact">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>The activity's code.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tp/glossary/glossary#000005" role="glossary">activity</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tpppc275.sern">
         <Header>
            <Title>Seq. No.</Title>
         </Header>
         <FuncDesc>The sequence number code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.csub">
         <Header>
            <Title>Subcontracting</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000073" role="glossary">subcontracting</Link> code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.ccco">
         <Header>
            <Title>Cost Comp.</Title>
         </Header>
         <FuncDesc>The cost object code.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tp/glossary/glossary#000003" role="glossary">cost object</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tpppc275.cstl">
         <Header>
            <Title>Extension</Title>
         </Header>
         <FuncDesc>The extension code.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tp/glossary/glossary#000017" role="glossary">extension</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tpppc275.snec">
         <Header>
            <Title>Comm Seq.</Title>
         </Header>
         <FuncDesc>The sequence number of the corresponding commitment for which a
		  reverse entry must be made in the <GUIRef href="/baanerp/tp/ppc/tpppc2110s000" role="session">Commitments (Material) (tpppc2110s000)</GUIRef> session. This is only true for manually
		  entered commitments via the same session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="txta.yeno">
         <Header>
            <Title>Text</Title>
         </Header>
         <FuncDesc> If this check box is selected, a text is present.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.quan">
         <Header>
            <Title>Quantity</Title>
         </Header>
         <FuncDesc>The quantity of the cost object.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.cuni">
         <Header>
            <Title>Unit</Title>
         </Header>
         <FuncDesc>The code of the <Link href="/baanerp/tp/glossary/glossary#000080" role="glossary">unit</Link> in which you specify the quantity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.curc">
         <Header>
            <Title>Cur</Title>
         </Header>
         <FuncDesc>A generally accepted medium of exchange (such as: coins,
		treasury notes, and banknotes).</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>LN distinguishes two currency types:</ListIntro>
               <ListItem>Home currency, used internally by companies for example, to
			 calculate costs, to record budgets, and to register tax amounts</ListItem>
               <ListItem>Transaction currency, used in transactions with business
			 partners, such as orders and invoices</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc275.amoc">
         <Header>
            <Title>Cost Amount</Title>
         </Header>
         <FuncDesc>Total costs.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.rtcc">
         <Header>
            <Title>Currency Rate/Rate Factor</Title>
         </Header>
         <FuncDesc>The currency rate.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.rtfc">
         <Header>
            <Title>Rate Factor Costs</Title>
         </Header>
         <FuncDesc>The rate factor.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="currency">
         <Header>
            <Title>Cur.</Title>
         </Header>
         <FuncDesc>You can express the cost amount in a home currency. In a
		  dependent and an independent currency system, you can use the Rotate Currency
		  option &lt;CTRL-R&gt; to rotate between the home currencies.</FuncDesc>
         <SimpleSection>
            <ProcedureList>
               <ListIntro>The following sequence is applicable:</ListIntro>
               <ListItem>Local currency</ListItem>
               <ListItem>Reporting currency 1</ListItem>
               <ListItem>Reporting currency 2</ListItem>
            </ProcedureList>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="home.amoc">
         <Header>
            <Title>Cost Amount</Title>
         </Header>
         <FuncDesc>The cost amount in the home currency.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.curs">
         <Header>
            <Title>Cur</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000036" role="glossary">project currency</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.amos">
         <Header>
            <Title>Sales Amount</Title>
         </Header>
         <FuncDesc>The total sales amount.</FuncDesc>
         <SimpleSection>
            <Paragraph>If you change the automatically generated sales amount, the
			 value of the <GUIRef href="/baanerp/tp/ppc/tpppc2515m000#tpppc215.rtcs" role="manual">Currency Rate/Rate Factor</GUIRef> field is automatically
			 adjusted, as follows:</Paragraph>
            <Formula space-and-orientation="indented-estimated">
               <Paragraph>Sales rate = sales amount / number of hours </Paragraph>
            </Formula>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc275.rtcs">
         <Header>
            <Title>Currency Rate/Rate Factor</Title>
         </Header>
         <FuncDesc>The currency <Link href="/baanerp/tc/glossary/glossary#Rate_tc" role="glossary">rate</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.rtfs">
         <Header>
            <Title>Rate Factor Sales</Title>
         </Header>
         <FuncDesc>The currency <Link href="/baanerp/tc/glossary/glossary#RateFactor_tc" role="glossary">rate factor</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="home.amos">
         <Header>
            <Title>Sales Amount</Title>
         </Header>
         <FuncDesc>The sales amount in the home currency.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.cdoc">
         <Header>
            <Title>Document Number</Title>
         </Header>
         <FuncDesc>The document code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.tetg">
         <Header>
            <Title>Posting Type</Title>
         </Header>
         <FuncDesc>Indicates both the origin of the transaction and the accounts,
		  based on which the transaction is posted to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.serb">
         <Header>
            <Title>Proces. Run</Title>
         </Header>
         <FuncDesc>The number of the processing run by which the transaction is
		  processed in the project history and possibly in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.sttl">
         <Header>
            <Title>Stl Org</Title>
         </Header>
         <FuncDesc>If this check box is selected, the transaction is
		  posted as the outcome of a fluctuation settlement. This transaction cannot be
		  included in cost control.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.drun">
         <Header>
            <Title>Run Date</Title>
         </Header>
         <FuncDesc>The date on which the transaction is processed to the project
		  history and possibly to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> using the <GUIRef href="/baanerp/tp/ppc/tpppc4802m000" role="session">Process Transactions (tpppc4802m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.comf">
         <Header>
            <Title>Reported Cpl (Finance)</Title>
         </Header>
         <FuncDesc>If this check box is selected, the financial result of
		  the transaction is processed in <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> by using the <GUIRef href="/baanerp/tp/ppc/tpppc4802m000" role="session">Process Transactions (tpppc4802m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.cdru">
         <Header>
            <Title>Run Date</Title>
         </Header>
         <FuncDesc>The date on which the transaction is processed to the project
		  history and possibly to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> using the <GUIRef href="/baanerp/tp/ppc/tpppc4802m000" role="session">Process Transactions (tpppc4802m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.cser">
         <Header>
            <Title>Run (Rep Completed)</Title>
         </Header>
         <FuncDesc>The number of the processing run by which the financial result
		  of the transaction is processed in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> in the <GUIRef href="/baanerp/tp/ppc/tpppc4802m000" role="session">Process Transactions (tpppc4802m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.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 the module <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef>, when a
		  purchase invoice is processed on the basis of the corresponding purchase order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.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 the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module,
		  when a purchase invoice is processed on the basis of the corresponding purchase
		  order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.srnb">
         <Header>
            <Title>Rec No</Title>
         </Header>
         <FuncDesc>The receipt number of the delivery for a purchase order is
		  assigned when a delivery is entered and assigned from the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module
		  when a purchase invoice is processed on the basis of the corresponding purchase
		  order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.otbp">
         <Header>
            <Title>B.From BP</Title>
         </Header>
         <FuncDesc>The buy-from business partner code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.ifbp">
         <Header>
            <Title>Invoice from</Title>
         </Header>
         <FuncDesc>The business partner that sends invoices to your organization.
		This usually represents a supplier's accounts receivable department. The
		definition includes the default currency and exchange rate, invoicing method
		and frequency, information about your organization's credit limit, the terms
		and method of payment, and the related pay-to business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.blbl">
         <Header>
            <Title>Billable</Title>
         </Header>
         <FuncDesc>If this check box is selected, the transaction has been
		  allowed to be invoiced to the customer. If this check box is cleared, the
		  transaction has not been allowed to be invoiced to the customer.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.invo">
         <Header>
            <Title>Tb Inv</Title>
         </Header>
         <FuncDesc>If this check box is selected, cost transaction must be
		  included when invoices are generated in the <GUIRef href="/baanerp/tp/pin/tppin4200m000" role="session">Transfer Project Data to Central Invoicing (tppin4200m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.srni">
         <Header>
            <Title>Batch Number</Title>
         </Header>
         <FuncDesc>If a purchase invoice is processed on the basis of the
		  corresponding purchase-order line, LN assigns the invoice sequence number from the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.trsl">
         <Header>
            <Title>trf Inv</Title>
         </Header>
         <FuncDesc>If this check box is selected, the transaction is
		  transferred to sales invoicing.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.hbyn">
         <Header>
            <Title>Use Holdback</Title>
         </Header>
         <FuncDesc>If this check box is selected, holdback applies to this
		  transaction.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.hbnr">
         <Header>
            <Title>Hb Nr</Title>
         </Header>
         <FuncDesc>The holdback serial-number, if holdback is applied to this
		  transaction.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.fcmp">
         <Header>
            <Title>Financial Company</Title>
         </Header>
         <FuncDesc>The financial company code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.ityp">
         <Header>
            <Title>Transaction Type</Title>
         </Header>
         <FuncDesc>The value of this field is part of the financial document
		  number that is used for revenues for which sales invoices are created in <GUIRef href="/baanerp/ci" role="package">Invoicing</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.idoc">
         <Header>
            <Title>Invoice Document</Title>
         </Header>
         <FuncDesc>The document code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.ocmp">
         <Header>
            <Title>Receiving Company</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Company_tc" role="glossary">company</Link> that receives
		  the transaction. When the transaction is processed, this field is automatically
		  filled with the company number, which is recorded for the project in the <GUIRef href="/baanerp/tp/pdm/tppdm6100m000" role="session">Project (tppdm6100m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="deliv.comp">
         <Header>
            <Title>Delivering Company</Title>
         </Header>
         <FuncDesc>The source company of the cost transaction. If the delivering
		  company is different from the receiving company it is an intercompany
		  transaction. However, if the posting type of the cost transaction is <GUIRef href="/baanerp/tp/domains/ppc.tetd#stock" role="option">Inventory</GUIRef>, the financial company of the project is used
		  for the financial transactions. The intercompany booking related to this
		  inventory transaction does not result in a project cost transaction because it
		  is already booked.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.entu">
         <Header>
            <Title>Enterprise Unit</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#000011" role="glossary">enterprise unit</Link> (EU) that is responsible for the delivery, which is specified on
		  the transaction line.</FuncDesc>
         <SimpleSection>
            <Paragraph>If you post the costs to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, you need to know
			 which EU is linked to the cost record. The EU can differ from the EU to which
			 the project is linked because of the possibility of inter-company transactions.</Paragraph>
            <Paragraph>If you enter costs manually, you can supply a value for the
			 EU. When zooming from <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, the EU is imported.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc275.cptc">
         <Header>
            <Title>CstPer Code</Title>
         </Header>
         <FuncDesc>The cost-control period code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.year">
         <Header>
            <Title>Cost Year</Title>
         </Header>
         <FuncDesc>The year in which the transaction must be posted to the project
		  history for cost control. The default value of this field is the year of the
		  date of input's cost-control period.</FuncDesc>
         <SimpleSection>
            <Paragraph>If the <Link href="/baanerp/tp/ppc/tpppc0100s000#tpppc000.pfpp" role="formfield">Fiscal Period</Link> check box in the <GUIRef href="/baanerp/tp/ppc/tpppc0100s000" role="session">PPC Parameters (tpppc0100s000)</GUIRef> session is selected, the current fiscal year is the
			 default value for this field.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc275.peri">
         <Header>
            <Title>Cost Per</Title>
         </Header>
         <FuncDesc>The period in which the transaction must be posted to the
		  project history for cost control.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.cptf">
         <Header>
            <Title>FinPer Code</Title>
         </Header>
         <FuncDesc>The period in which the transaction is posted to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.fyea">
         <Header>
            <Title>Fin Year</Title>
         </Header>
         <FuncDesc>The fiscal year in which the transaction is posted to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.fper">
         <Header>
            <Title>Fin Per.</Title>
         </Header>
         <FuncDesc>The period in which the transaction is posted to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.ltdt">
         <Header>
            <Title>Transaction Time</Title>
         </Header>
         <FuncDesc>The transaction's date of input.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.rgdt">
         <Header>
            <Title>Registr Date</Title>
         </Header>
         <FuncDesc>Date of input for the forecast deviation of costs.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.ncmp">
         <Header>
            <Title>Financial Document</Title>
         </Header>
         <FuncDesc>The value of this field is part of the financial document
		  number that is used for the purchase order invoice that matches in the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module
		  in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> or it is part
		  of the financial document number that is used for manually-entered invoices in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> that are posted
		  to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.ftty">
         <Header>
            <Title>Financial Document</Title>
         </Header>
         <FuncDesc>The value of this field is part of the financial document
		  number that is used for the purchase order invoice that matches in the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module
		  in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> or it is part
		  of the financial document number that is used for manually-entered invoices in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> that are posted
		  to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.fdoc">
         <Header>
            <Title>Financial Document</Title>
         </Header>
         <FuncDesc>The value of this field is part of the financial document
		  number that is used for the purchase order invoice that matches in the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module
		  in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> or it is part
		  of the financial document number that is used for manually-entered invoices in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> that are posted
		  to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.flin">
         <Header>
            <Title>Financial Document</Title>
         </Header>
         <FuncDesc>The value of this field is part of the financial document
		  number that is used for the purchase order invoice that matches in the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module
		  in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> or it is part
		  of the financial document number that is used for manually-entered invoices in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> that are posted
		  to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.fsrl">
         <Header>
            <Title>Financial Document</Title>
         </Header>
         <FuncDesc>The value of this field is part of the financial document
		  number that is used for the purchase order invoice that matches in the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module
		  in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> or it is part
		  of the financial document number that is used for manually-entered invoices in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> that are posted
		  to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc275.ftln">
         <Header>
            <Title>Financial Document</Title>
         </Header>
         <FuncDesc>The value of this field is part of the financial document
		  number that is used for the purchase order invoice that matches in the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module
		  in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> or it is part
		  of the financial document number that is used for manually-entered invoices in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> that are posted
		  to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="tpppc2414m000">
         <Header>
            <Title>Print History</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/tp/ppc/tpppc2414m000" role="session">Print History (tpppc2414m000)</GUIRef> session which prints history information in relation
		  to costs, commitments, revenues, and additional revenues.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>