<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tp/ppc/tpppc2555m000" xml:lang="en">
   <Header>
      <Title>Equipment Cost History (tpppc2555m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to list the costs that are
		  posted to the project history for different projects of the cost type <GUIRef href="/baanerp/tp/domains/pdm.cotp#equipment" role="option">Equipment</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>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tpppc255.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>The project code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.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="tpppc255.cact">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>Activity equipment is posted.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.sern">
         <Header>
            <Title>Seq. No.</Title>
         </Header>
         <FuncDesc>The sequence number code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.cequ">
         <Header>
            <Title>Equipment</Title>
         </Header>
         <FuncDesc>The equipment's code.</FuncDesc>
         <SimpleSection>
            <Paragraph>This is the equipment on which the costs are posted.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc255.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.ccco">
         <Header>
            <Title>Cost Component</Title>
         </Header>
         <FuncDesc>A cost component is a collection of cost objects with a certain
		characteristic. A cost component does not depend on the cost type, therefore,
		for example, a project can be monitored from another dimension. For example,
		all the costs that refer to electrical work, for example, cable and
		installation work, are visible if the applicable cost objects are linked to the
		cost component Electrical work.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.cstl">
         <Header>
            <Title>Extension</Title>
         </Header>
         <FuncDesc>The status of the selected extension cannot be <GUIRef href="/baanerp/tp/domains/est.stat#free" role="option">Free</GUIRef> and the extension type must be <GUIRef href="/baanerp/tp/domains/ptc.stlt#risc.settl" role="option">Fluctuation Settlement</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.snec">
         <Header>
            <Title>Comm Seq.</Title>
         </Header>
         <FuncDesc>The sequence number of the corresponding commitment for which a
		  reverse entry is to 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 in 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="tpppc255.quan">
         <Header>
            <Title>Quantity</Title>
         </Header>
         <FuncDesc>The cost object's quantity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.time">
         <Header>
            <Title>Amount of Time</Title>
         </Header>
         <FuncDesc>The number of time units. For instance, the numbers of days
		  that a crane has been employed for a project.</FuncDesc>
         <SimpleSection>
            <Formula space-and-orientation="indented-estimated">
               <Paragraph> Total quantity of transaction = amount of time * quantity (rounded to two decimals).</Paragraph>
            </Formula>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc255.cuti">
         <Header>
            <Title>Time Unit</Title>
         </Header>
         <FuncDesc>The unit code.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tp/glossary/glossary#000080" role="glossary">unit of measure</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tpppc255.curc">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>The currency.</FuncDesc>
         <SimpleSection>
            <Paragraph>This is the currency in which the cost is posted. For
			 example, the <Link href="/baanerp/tp/glossary/glossary#000036" role="glossary">project currency</Link> is the
			 default.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc255.amoc">
         <Header>
            <Title>Cost Amount</Title>
         </Header>
         <FuncDesc>The total costs. If you change the automatically generated cost
		  amount, the unit-cost rate is automatically adjusted.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.rtcc">
         <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="tpppc255.rtfc">
         <Header>
            <Title>Rate Factor Costs</Title>
         </Header>
         <FuncDesc>The factor by which the amount in the transaction currency or
		the invoice currency is divided before ERP Enterprise converts it to a
		home currency. A rate factor is often used for currencies that have a
		relatively low price, for example, Korean Won.</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="tpppc255.curs">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>The currency.</FuncDesc>
         <SimpleSection>
            <Paragraph>This is the currency in which the cost is posted. For
			 example, the <Link href="/baanerp/tp/glossary/glossary#000036" role="glossary">project currency</Link> is the
			 default.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc255.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="tpppc255.rtcs">
         <Header>
            <Title>Currency Rate/Rate Factor</Title>
         </Header>
         <FuncDesc>The rate.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.rtfs">
         <Header>
            <Title>Rate Factor Sales</Title>
         </Header>
         <FuncDesc>The factor by which the amount in the transaction currency or
		the invoice currency is divided before ERP Enterprise converts it to a
		home currency. A rate factor is often used for currencies that have a
		relatively low price, for example, Korean Won.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="home.amos">
         <Header>
            <Title>Sales Amount</Title>
         </Header>
         <FuncDesc>The sales amount in the home currency.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.cdoc">
         <Header>
            <Title>Document Number</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 Accounts
		  Payable (ACP) module in Finance or it is part of the financial document number
		  that is used for manually-entered invoices in Finance that are posted to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.tetn">
         <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="tpppc255.serb">
         <Header>
            <Title>Run Number</Title>
         </Header>
         <FuncDesc>The number of the processing run by which the transaction is
		  processed in the project history.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.drun">
         <Header>
            <Title>Run Date</Title>
         </Header>
         <FuncDesc>The date on which the financial result of the transaction is
		  processed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.sttl">
         <Header>
            <Title>Stl Org</Title>
         </Header>
         <FuncDesc>Indicates whether the transaction is posted as the outcome of a
		  fluctuation settlement. If so, this transaction cannot be included in cost
		  control.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.comf">
         <Header>
            <Title>Reported Cpl (Finance)</Title>
         </Header>
         <FuncDesc>This indicates whether the financial result of the transaction
		  is processed in <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> using the <GUIRef href="/baanerp/tp/ppc/tpppc4802m000" role="session">Process Transactions (tpppc4802m000)</GUIRef> session when closing the project.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.cdru">
         <Header>
            <Title>Run Date</Title>
         </Header>
         <FuncDesc>The date on which the financial result of the transaction is
		  processed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.cser">
         <Header>
            <Title>Run (Rep Completed)</Title>
         </Header>
         <FuncDesc>The date on which the financial result of the transaction is
		  processed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.orno">
         <Header>
            <Title>Order Number</Title>
         </Header>
         <FuncDesc>The purchase order number that is assigned in <GUIRef href="/baanerp/procurement" role="package">Procurement</GUIRef>, when
		  an order or delivery is entered and assigned from the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module,
		  and when a purchase invoice is processed on the basis of the corresponding
		  purchase order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.pono">
         <Header>
            <Title>Posn no</Title>
         </Header>
         <FuncDesc>The order line number is automatically 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 line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.srnb">
         <Header>
            <Title>Rec No</Title>
         </Header>
         <FuncDesc>The sequence number code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.otbp">
         <Header>
            <Title>B.From BP</Title>
         </Header>
         <FuncDesc>The order-to business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.ifbp">
         <Header>
            <Title>Invoice from</Title>
         </Header>
         <FuncDesc>Invoice from business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.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="tpppc255.invo">
         <Header>
            <Title>Tb Inv</Title>
         </Header>
         <FuncDesc>Indicates whether the cost transaction must be included when
		  invoices are generated.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is selected, the transaction has been
			 released for invoicing.</Paragraph>
            <Paragraph>If this check box is cleared, the transaction has not
			 been released for invoicing in the <GUIRef href="/baanerp/tp/pin" role="module">Project Invoicing</GUIRef>.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tpppc255.srni">
         <Header>
            <Title>Bat No.</Title>
         </Header>
         <FuncDesc>The invoice sequence number is assigned by ERP Enterprise 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 line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.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="tpppc255.hbyn">
         <Header>
            <Title>Use Holdback</Title>
         </Header>
         <FuncDesc>If this check box is selected, holdback applies to this
		  transaction.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.hbnr">
         <Header>
            <Title>Hb Nr</Title>
         </Header>
         <FuncDesc>The serial number of the holdback given in <GUIRef href="/baanerp/tp/pin/tppin4140m000" role="session">Holdback (tppin4140m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.fcmp">
         <Header>
            <Title>Financial Company</Title>
         </Header>
         <FuncDesc>A company that is used for posting financial data in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. You can link one
		or more enterprise units from multiple logistic companies to one financial
		company.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.ityp">
         <Header>
            <Title>Transaction Type</Title>
         </Header>
         <FuncDesc>Invoice type from <GUIRef href="/baanerp/ci/sli" role="module">Invoicing</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.idoc">
         <Header>
            <Title>Invoice Document</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="tpppc255.ocmp">
         <Header>
            <Title>Receiving Company</Title>
         </Header>
         <FuncDesc>The company that receives the transaction. When the transaction
		  is processed with the <GUIRef href="/baanerp/tp/ppc/tpppc4802m000" role="session">Process Transactions (tpppc4802m000)</GUIRef> session, this field is filled with the
		  company number, that is recorded for the project in the <GUIRef href="/baanerp/tp/pdm/tppdm6100m000" role="session">Projects (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="tpppc255.entu">
         <Header>
            <Title>Enterprise Unit</Title>
         </Header>
         <FuncDesc>The enterprise unit.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.cptc">
         <Header>
            <Title>CstPer Code</Title>
         </Header>
         <FuncDesc>Cost period table for cost control.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.year">
         <Header>
            <Title>Cost Year</Title>
         </Header>
         <FuncDesc>The year in which the transaction must be posted to the project
		  history for cost control.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.peri">
         <Header>
            <Title>Cst Per</Title>
         </Header>
         <FuncDesc>The period in which the transaction must be posted to the
		  project history for cost control.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.cptf">
         <Header>
            <Title>FinPer Code</Title>
         </Header>
         <FuncDesc>Cost period table for cost control.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.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="tpppc255.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="tpppc255.ltdt">
         <Header>
            <Title>Transaction Time</Title>
         </Header>
         <FuncDesc>The transaction's date of input.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.rgdt">
         <Header>
            <Title>Registr. Date</Title>
         </Header>
         <FuncDesc>Date of input for the forecast deviation of costs.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpppc255.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="tpppc255.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="tpppc255.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="tpppc255.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="tpppc255.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="tpppc255.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>