<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tp/pdm/tppdm6100s000" xml:lang="en">
   <Header>
      <Title>Project (tppdm6100s000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph> Use this session to maintain master project data for each project. The project data defines all
		  aspects of the project. Many fields depend on the parameter sessions for
		  defaults or input. So, if a field has incorrect data, please check the related
		  field in the parameter sessions.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>Use the Rotate Currency button to see amounts
		  in the different home currencies.</Paragraph>
         <Paragraph>The revenue recognition method and the cost of
		  goods sold method is defined at the project, extension. RR and COGS can also be
		  determined at the element and activity level depending on the method of RR and
		  COGS selected. The usage of element and activity depends on whether the project
		  is controlled by element or controlled by activity.</Paragraph>
         <Paragraph>On the project level and extension level, you
		  can set a lower and upper limit on the revenue to be recognized.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle> Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tp/onlinemanual/000001" role="manual">To use project data management</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tp/onlinemanual/000307" role="manual">To create a project</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tp/onlinemanual/000309" role="manual">To use a search path</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tp/onlinemanual/000301" role="manual">To use currencies in Project</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tp/onlinemanual/000302" role="manual">To use home currencies in Project</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tp/onlinemanual/000332" role="manual">To use the rate determiner</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tp/onlinemanual/000337" role="manual">Revenue Recognition (RR) and Cost of Goods Sold (COGS)</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldGroup>
         <Title> General</Title>
         <FieldHelp ID="tppdm600.cprj">
            <Header>
               <Title>Project</Title>
            </Header>
            <FuncDesc>Enter a new project code.</FuncDesc>
            <SimpleSection>
               <List>
                  <ListIntro>You can choose to create a project from:</ListIntro>
                  <ListItem>An existing not-used general project.</ListItem>
                  <ListItem>A new number attached to the project series.</ListItem>
                  <ListItem>A new number attached to the estimate series. The
				  estimate series is different from the project series. If you create an
				  estimating project, the numbering helps you recognize that the project started
				  as an estimate.</ListItem>
                  <ListItem>A first free number.</ListItem>
               </List>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tppdm600.psts">
            <Header>
               <Title>Status</Title>
            </Header>
            <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000087" role="glossary">status</Link> of the project. The project status is important for following the right course
			 throughout the project life cycle.</FuncDesc>
            <Note>
               <SectionTitle> Note</SectionTitle>
               <Paragraph>For projects of type Template, the project
				status does not hold any significance.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldGroup>
            <Title> General</Title>
            <FieldHelp ID="cprj.dsca">
               <Header>
                  <Title>Description</Title>
               </Header>
               <FuncDesc> The description or name of the code.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.seak">
               <Header>
                  <Title>Search Key</Title>
               </Header>
               <FuncDesc>An alternative form of a description used for convenience
		during searching. Typically, it is an abbreviation, an acronym, or a mnemonic
		alternative to a full description.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.padr">
               <Header>
                  <Title>Address Code Project</Title>
               </Header>
               <FuncDesc>The code that identifies the location where the
				deliverables for the project can be sent. In the US this address code is used
				for the tax provider.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.sadr">
               <Header>
                  <Title>Ship-from Address</Title>
               </Header>
               <FuncDesc>The address entered here will be used as the standard
				ship-from address for the project deliveries and services.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="ent.unit">
               <Header>
                  <Title>Enterprise Unit</Title>
               </Header>
               <FuncDesc>A financially independent part of your organization that
		consists of entities such as departments, work centers, warehouses, and
		projects. The enterprise unit's entities must all belong to the same logistic
		company, but a logistic company can contain multiple enterprise units. An
		enterprise unit is linked to a single financial company.</FuncDesc>
               <SimpleSection>
                  <Paragraph>When you carry out logistic transactions between enterprise
		  units, these are posted in the financial companies to which each enterprise
		  unit is linked. You can define the relationships between the enterprise units,
		  and thus the goods transfer that can take place between the enterprise units.
		  To use invoicing and pricing between enterprise units, you must link the
		  enterprise units to internal business partners.</Paragraph>
                  <Paragraph>You can use enterprise units to do separate financial
		  accounting for parts of your business. For example, you can define enterprise
		  units for separate parts of your organization that belong to one logistic
		  company, but that are located in different countries. The accounting of each
		  enterprise unit is performed in each country's national currency, and in the
		  financial company linked to the enterprise unit.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ncmp">
               <Header>
                  <Title>Financial Company</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tf/glossary/glossary#FinancCompan_tf" role="glossary">financial company</Link> to which the <Link href="/baanerp/tc/glossary/glossary#000011" role="glossary">enterprise unit</Link> is linked.
				If the financial company is not the same as the operational company, the
				currency system of the financial company will be used for <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/tc/onlinemanual/000028" role="manual">Currency systems</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Project Type</Title>
            <FieldHelp ID="tppdm600.intp">
               <Header>
                  <Title>Internal Project</Title>
               </Header>
               <FuncDesc> If this check box is selected, the project is an
				internal project. An internal project has no contractual obligations to a
				business partner and its costs will be booked to the profit and loss account.
				Next to the simple internal project there is also a possibility of making a
				capital project if you check the <GUIRef href="/baanerp/tp/pdm/tppdm6100s000#tppdm600.intp" role="manual">Internal Project</GUIRef> check box and the <GUIRef href="/baanerp/tp/pdm/tppdm6100s000#tppdm600.capp" role="manual">Capital Project</GUIRef> check box. A capital project is an
				internal project that will be capitalized on the balance sheet as a fixed asset
				after completion.</FuncDesc>
               <SimpleSection>
                  <SectionTitle> Example</SectionTitle>
                  <List>
                     <ListItem>A training program for the employees is a normal
					 internal project.</ListItem>
                     <ListItem>Constructing production facilities for a new product
					 line is a capital project.</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.capp">
               <Header>
                  <Title>Capital Project</Title>
               </Header>
               <FuncDesc>A project used for internal use in which deliverables can be
		booked as fixed assets but delivery of goods is not possible. In a capital
		project, you are the business partner.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>The check box cannot be selected if the
				  financial transactions have been processed for the project and the project has
				  already been made <GUIRef href="/baanerp/tp/domains/pdm.psts#construction" role="option">Active</GUIRef>.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.tmpl">
               <Header>
                  <Title>Template</Title>
               </Header>
               <FuncDesc> If this check box is selected, the project is of the type <Link href="/baanerp/tp/glossary/glossary#000308" role="glossary">template</Link> and cannot be used for actual projects. This
				project can be used only for copying projects.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>You can select the check box only if the
				  status of the project is <GUIRef href="/baanerp/tp/domains/pdm.psts#free" role="option">Free</GUIRef>.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.kopr">
               <Header>
                  <Title>Hierarchy Type</Title>
               </Header>
               <FuncDesc>A project must belong to one of the project types.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.mprj">
               <Header>
                  <Title>Main Project</Title>
               </Header>
               <FuncDesc>The main project to which the subproject belongs.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Organization Breakdown Structure</Title>
            <FieldHelp ID="tppdm600.uobs">
               <Header>
                  <Title>Use OBS</Title>
               </Header>
               <FuncDesc>This field indicates whether an <Link href="/baanerp/tp/glossary/glossary#OrganiBreakd_tp" role="glossary">organization breakdown structure</Link> (OBS) is used for the project.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.cobs">
               <Header>
                  <Title>OBS</Title>
               </Header>
               <FuncDesc>The code of the organization breakdown structure.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Contract</Title>
         <FieldGroup>
            <Title> Agreement Specification</Title>
            <FieldHelp ID="proj.customer">
               <Header>
                  <Title>Sold-to Business Partner</Title>
               </Header>
               <FuncDesc>Usually a customer's purchase department, the business partner
		who orders goods or services from your organization, that owns the
		configurations you maintain, or for whom you perform a project.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>Details of the agreement with the sold-to business partner
			 can include the following:</ListIntro>
                     <ListItem>Default price and discount agreements</ListItem>
                     <ListItem>Sales order defaults</ListItem>
                     <ListItem>Delivery terms</ListItem>
                     <ListItem>The related ship-to and invoice-to business partner</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.copr">
               <Header>
                  <Title>Contract Amount</Title>
               </Header>
               <FuncDesc>The total amount of the project contract.</FuncDesc>
               <SimpleSection>
                  <Paragraph>For a time-phased budget version, the contract amount is
		  expressed as follows:</Paragraph>
                  <Formula space-and-orientation="indented-estimated">
                     <Paragraph>contract amount = profit fee + management reserve + distributed budget + undistr. budget</Paragraph>
                  </Formula>
                  <Paragraph>The contract amount is used to determine the invoice limit.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rate">
               <Header>
                  <Title>Rate/Rate Factor</Title>
               </Header>
               <FuncDesc>A charge or payment fixed according to a standard scale, for
		example, the currency rate of the transaction.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ratf">
               <Header>
                  <Title>Rate/Rate Factor</Title>
               </Header>
               <FuncDesc>The factor by which the amount in the transaction currency or
		the invoice currency is divided before LN 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.ccur">
               <Header>
                  <Title>In Home Currency</Title>
               </Header>
               <FuncDesc>One of a company's base currencies in which LN registers and
		reports amounts.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>In a multicurrency system, up to three home currencies can
			 be defined:</ListIntro>
                     <ListItem>The <Link href="/baanerp/tc/glossary/glossary#000062" role="glossary">local currency</Link>
                     </ListItem>
                     <ListItem>Two <Link href="/baanerp/tc/glossary/glossary#000065" role="glossary" Update="No">reporting currencies</Link>
                     </ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="home.amnt">
               <Header>
                  <Title>In Home Currency</Title>
               </Header>
               <FuncDesc>The amount in the home currency.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.agty">
               <Header>
                  <Title>Contract Type</Title>
               </Header>
               <FuncDesc>This field determines how the project contract amount is
				calculated. This affects the invoicing in <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.coty">
               <Header>
                  <Title>Contract Execution</Title>
               </Header>
               <FuncDesc>The contract type indicates whether your company executes
				the project as main contractor or as a subcontractor.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.invm">
               <Header>
                  <Title>Invoice Type</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000095" role="glossary">invoice type</Link> you choose determines the way invoicing is handled in <GUIRef href="/baanerp/tp/pin" role="module">Project Invoicing</GUIRef>.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.hbpc">
               <Header>
                  <Title>Holdback Percentage</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000052" role="glossary">holdback</Link> percentage.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rfcu">
               <Header>
                  <Title>Customer Reference</Title>
               </Header>
               <FuncDesc>This field will only be printed for Progress Invoice
				invoices. As part of the procedure for progress invoices, progress invoice
				specifications are created, which will use the reference.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.fddt">
               <Header>
                  <Title>Substantial Completion Date</Title>
               </Header>
               <FuncDesc>The agreed date of the first completion of the project.
				This field only provides information.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Cost-Plus Markup</Title>
            <FieldHelp ID="tppdm600.pcit">
               <Header>
                  <Title>Material</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#Surcharges_tp" role="glossary">surcharge</Link> percentage
				used in the <Link href="/baanerp/tp/ppc/tpppc2111s000" role="session">Material Costs (tpppc2111s000)</Link> session to calculate the default value of the <Link href="/baanerp/tp/glossary/glossary#000012" role="glossary">sales price</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>This calculation is performed as
				  follows:</Paragraph>
                  <Formula space-and-orientation="indented-estimated">
                     <Paragraph>surcharge percentage sales price = cost price * (1 + (surcharge percentage / 100))</Paragraph>
                  </Formula>
               </SimpleSection>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>This is only relevant for <Link href="/baanerp/tp/glossary/glossary#CostPlusCont_tp" role="glossary">cost plus</Link> projects or <Link href="/baanerp/tp/glossary/glossary#000017" role="glossary">extensions</Link>.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pcts">
               <Header>
                  <Title>Labor</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#Surcharges_tp" role="glossary">surcharge</Link> percentage
				used in the <Link href="/baanerp/tp/ppc/tpppc2131s000" role="session">Labor Costs (tpppc2131s000)</Link> session to calculate the default value of the <Link href="/baanerp/tp/glossary/glossary#000012" role="glossary">sales rate</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>This calculation is performed as
				  follows:</Paragraph>
                  <Formula space-and-orientation="indented-estimated">
                     <Paragraph>sales rate = cost rate * (1 + (surcharge percentage / 100))</Paragraph>
                  </Formula>
               </SimpleSection>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>This is only relevant for <Link href="/baanerp/tp/glossary/glossary#CostPlusCont_tp" role="glossary">cost plus</Link> projects or <Link href="/baanerp/tp/glossary/glossary#000017" role="glossary">extensions</Link>.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pceq">
               <Header>
                  <Title>Equipment</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#Surcharges_tp" role="glossary">surcharge</Link> percentage
				used in the <Link href="/baanerp/tp/ppc/tpppc2151s000" role="session">Equipment Cost (tpppc2151s000)</Link> session to calculate the default value of the <Link href="/baanerp/tp/glossary/glossary#000012" role="glossary">sales rate</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>This calculation is performed as
				  follows:</Paragraph>
                  <Formula space-and-orientation="indented-estimated">
                     <Paragraph>sales rate = cost rate * (1 + (surcharge percentage / 100))</Paragraph>
                  </Formula>
               </SimpleSection>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>This is only relevant for <Link href="/baanerp/tp/glossary/glossary#CostPlusCont_tp" role="glossary">cost plus</Link> projects or <Link href="/baanerp/tp/glossary/glossary#000017" role="glossary">extensions</Link>.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pcsb">
               <Header>
                  <Title>Subcontracting</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#Surcharges_tp" role="glossary">surcharge</Link> percentage
				used in the <Link href="/baanerp/tp/ppc/tpppc2171s000" role="session">Subcontracting Costs (tpppc2171s000)</Link> session to calculate the default value of the <Link href="/baanerp/tp/glossary/glossary#000012" role="glossary">sales price</Link>.</FuncDesc>
               <SimpleSection>
                  <Paragraph>This calculation is performed as
				  follows:</Paragraph>
                  <Formula space-and-orientation="indented-estimated">
                     <Paragraph>sales price = cost price * (1 + (surcharge percentage / 100))</Paragraph>
                  </Formula>
               </SimpleSection>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>This is only relevant for <Link href="/baanerp/tp/glossary/glossary#CostPlusCont_tp" role="glossary">cost plus</Link> projects or <Link href="/baanerp/tp/glossary/glossary#000017" role="glossary">extensions</Link>.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pcic">
               <Header>
                  <Title>Sundry Cost</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#Surcharges_tp" role="glossary">surcharge</Link> percentage
				used in the <Link href="/baanerp/tp/ppc/tpppc2191s000" role="session">Sundry Costs (tpppc2191s000)</Link> session to calculate the default value of the
				sales rate.</FuncDesc>
               <SimpleSection>
                  <Paragraph>This calculation is performed as
				  follows:</Paragraph>
                  <Formula space-and-orientation="indented-estimated">
                     <Paragraph>surcharge percentage sales rate = cost rate * (1 + (surcharge percentage / 100))</Paragraph>
                  </Formula>
               </SimpleSection>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>This is only relevant for <Link href="/baanerp/tp/glossary/glossary#CostPlusCont_tp" role="glossary">cost plus</Link> projects or <Link href="/baanerp/tp/glossary/glossary#000017" role="glossary">extensions</Link>.</Paragraph>
               </Note>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Financial</Title>
         <FieldHelp ID="tppdm600.pstf">
            <Header>
               <Title>Financial Result Status</Title>
            </Header>
            <FuncDesc>This field determines the procedure for calculating the
			 financial project result in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</FuncDesc>
         </FieldHelp>
         <FieldGroup>
            <Title> Fixed Assets</Title>
            <FieldHelp ID="tppdm600.anbr">
               <Header>
                  <Title>Asset Number</Title>
               </Header>
               <FuncDesc>If you select the <GUIRef href="/baanerp/tp/pdm/tppdm6100s000#tppdm600.capp" role="manual">Capital Project</GUIRef> check box and you want to link the
				project to a fixed asset code, you can enter an asset number and an extension.
				The fixed asset will be appreciated at the closure of the project's actual
				costs. Zoom to the <GUIRef href="/baanerp/tf/fam/tffam1500m000" role="session">Assets (tffam1500m000)</GUIRef> session to
				enter the fixed asset.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.aext">
               <Header>
                  <Title>Asset Extension</Title>
               </Header>
               <FuncDesc>The asset extension is a descriptional field. You can enter
				up to 15 characters. You can use this field to, for example, choose from a
				range of fixed assets that belong to one asset number in the <GUIRef href="/baanerp/tf/fam/tffam1500m000" role="session">Assets (tffam1500m000)</GUIRef> session.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Bank Guarantee</Title>
            <FieldHelp ID="tppdm600.bqua">
               <Header>
                  <Title>Bank Guarantee Amount</Title>
               </Header>
               <FuncDesc>To reduce the customer's risk exposure, it is customary for
				the contractor to place an amount of money on deposit as a guarantee against
				the failure of the project. This field gives the amount of the guarantee.
				Alternatively, you can specify a percentage of the total contract value as a
				guarantee: use the <GUIRef href="/baanerp/tp/pdm/tppdm6100s000#tppdm600.pcbq" role="manual">Bank Guarantee %</GUIRef> field.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="bqua.ccur">
               <Header>
                  <Title>Bank Guarantee Amount</Title>
               </Header>
               <FuncDesc>One of a company's base currencies in which LN registers and
		reports amounts.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>In a multicurrency system, up to three home currencies can
			 be defined:</ListIntro>
                     <ListItem>The <Link href="/baanerp/tc/glossary/glossary#000062" role="glossary">local currency</Link>
                     </ListItem>
                     <ListItem>Two <Link href="/baanerp/tc/glossary/glossary#000065" role="glossary" Update="No">reporting currencies</Link>
                     </ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pcbq">
               <Header>
                  <Title>Bank Guarantee %</Title>
               </Header>
               <FuncDesc>Alternatively to filling in the bank guarantee amount, you
				can specify a percentage of the total contract value as a guarantee.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.edbg">
               <Header>
                  <Title>Expiry Date</Title>
               </Header>
               <FuncDesc>The finish date of the bank guarantee is the last date on
				which it is valid.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="rbqu.ccur">
               <Header>
                  <Title>Bank Guarantee Reduction</Title>
               </Header>
               <FuncDesc>One of a company's base currencies in which LN registers and
		reports amounts.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>In a multicurrency system, up to three home currencies can
			 be defined:</ListIntro>
                     <ListItem>The <Link href="/baanerp/tc/glossary/glossary#000062" role="glossary">local currency</Link>
                     </ListItem>
                     <ListItem>Two <Link href="/baanerp/tc/glossary/glossary#000065" role="glossary" Update="No">reporting currencies</Link>
                     </ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rbqu">
               <Header>
                  <Title>Bank Guarantee Reduction</Title>
               </Header>
               <FuncDesc>During execution of the project the bank guarantee can be
				reduced.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rpcb">
               <Header>
                  <Title>Bank Guarantee Reduction %</Title>
               </Header>
               <FuncDesc>While executing the project the bank guarantee can be
				reduced. In this field you can enter the percentage by which the bank guarantee
				will be reduced.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rdbg">
               <Header>
                  <Title>Reduction Date</Title>
               </Header>
               <FuncDesc>The effective date of the reduction in the bank guarantee.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Terms of Payment for Financial Analysis</Title>
            <FieldHelp ID="tppdm600.psit">
               <Header>
                  <Title>Material</Title>
               </Header>
               <FuncDesc>The average number of days between order date and payment
				date.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.psta">
               <Header>
                  <Title>Labor</Title>
               </Header>
               <FuncDesc>The average number of days between order date and payment
				date.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pseq">
               <Header>
                  <Title>Equipment</Title>
               </Header>
               <FuncDesc>The average number of days between order date and payment
				date.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pssc">
               <Header>
                  <Title>Subcontracting</Title>
               </Header>
               <FuncDesc>The average number of days between order date and payment
				date.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.psic">
               <Header>
                  <Title>Sundry Cost</Title>
               </Header>
               <FuncDesc>The average number of days between order date and payment
				date.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rsrv">
               <Header>
                  <Title>Business Partners</Title>
               </Header>
               <FuncDesc>The average number of days between order date and payment
				date.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Budget</Title>
         <FieldGroup>
            <Title> Methods</Title>
            <FieldHelp ID="tppdm600.btpr">
               <Header>
                  <Title>Budget by</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000337" role="glossary">project budget</Link> type determines the way you look at your budget.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>You can budget the project by:</ListIntro>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/domains/pdm.bdtp#struct.budget" role="option">Element</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/domains/pdm.bdtp#activity.budget" role="option">Activity</GUIRef>
                     </ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.btco">
               <Header>
                  <Title>Control By</Title>
               </Header>
               <FuncDesc/>
               <SimpleSection>
                  <List>
                     <ListIntro>The project can be controlled by:</ListIntro>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/domains/pdm.bdtp#struct.budget" role="option">Element</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/domains/pdm.bdtp#activity.budget" role="option">Activity</GUIRef>
                     </ListItem>
                  </List>
               </SimpleSection>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <List>
                     <ListIntro>The <Link href="/baanerp/tp/glossary/glossary#000337" role="glossary">project budget</Link> uses project control to:</ListIntro>
                     <ListItem>Monitor the project outcome, the revenues, the costs.</ListItem>
                     <ListItem>Make a plan, if the Project control type is Activity
					 Budget.</ListItem>
                  </List>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.bdmt">
               <Header>
                  <Title>Budgeting Method</Title>
               </Header>
               <FuncDesc>The way to measure expected productivity.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>LN distinguishes the following two methods in the bottom-up budget:</ListIntro>
                     <ListItem>
                        <GUIRef href="/baanerp/tp/domains/pdm.bdmt#production.rate" role="option">Production Rate</GUIRef>: the number of production units produced
			 per unit of time.</ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/tp/domains/pdm.bdmt#task.norms" role="option">Labor Norms</GUIRef>: the number of hours required to carry out one
			 unit of the cost object.</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.lwta" OtherIDs="tppdm600.lwtb tppdm600.lwtc">
               <Header>
                  <Title>Path Budget Labor Rate</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000098" role="glossary">budget labor-rate search path</Link> for the labor cost rate and the sales rate in
				labor lines in the budget.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.stus">
               <Header>
                  <Title>Extensions in Budget</Title>
               </Header>
               <FuncDesc> If this check box is selected, extensions are used in
				the budget and in cost control.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.tbdg">
               <Header>
                  <Title>Main Proj. Budgeting</Title>
               </Header>
               <FuncDesc> If this check box is selected, the budget cost analysis
				and the generated control data only include the budgeted costs of the main
				project itself. The actual costs include both the cost of the main project and
				the costs of the corresponding subprojects.</FuncDesc>
               <SimpleSection>
                  <Paragraph> If this check box is cleared, the
				  budget cost analysis and the generated control data include both the budgeted
				  cost of the main project and the budgeted costs of the corresponding
				  subproject.</Paragraph>
               </SimpleSection>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Actuals</Title>
            <FieldHelp ID="tppdm600.cspa">
               <Header>
                  <Title>Top Element</Title>
               </Header>
               <FuncDesc>The top element of a project element or activity structure.
				The project budget is composed of a tree-like structure. The structure has only
				one top element or activity.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ccal">
               <Header>
                  <Title>Budget Cost Analysis</Title>
               </Header>
               <FuncDesc>Based on the project budget, several budget cost analyses
				can be performed in the <Link href="/baanerp/tp/ptc/tpptc3200m000" role="session">Generate Budget Cost Analysis (tpptc3200m000)</Link> session. Each budget cost analysis is stored
				under the combination of project code and budget cost analysis code. For each
				project it is indicated which budget cost analysis code must be regarded as
				actual.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>The actual budget cost analysis is defaulted in, for
					 example, these sessions:</ListIntro>
                     <ListItem>
                        <GUIRef href="/baanerp/tp/pss/tppss0701m000" role="session">Display Financial Analysis (tppss0701m000)</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/tp/ptc/tpptc3440m000" role="session">Print Budgeted Project Costs (tpptc3440m000)</GUIRef>
                     </ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.tpac">
               <Header>
                  <Title>Time-Phased Budget Anal</Title>
               </Header>
               <FuncDesc>Based on the actual budget, several budget cost analyses
				can be performed in the <Link href="/baanerp/tp/ptc/tpptc3200m000" role="session">Generate Budget Cost Analysis (tpptc3200m000)</Link> session. Each budget cost analysis is stored
				with the combination of project code and budget cost analysis code. For each
				project it is indicated which budget cost analysis code must be regarded as
				actual. In the case of cost comparisons between the estimate, the actual budget
				and/or the actual costing, LN always shows the cost data of the actual budget on the basis of
				the actual budget cost analysis code.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rtyp">
               <Header>
                  <Title>Exchange Rate Type</Title>
               </Header>
               <FuncDesc>The default <Link href="/baanerp/tp/glossary/glossary#000046" role="glossary">exchange-rate type</Link> used for budget cost analysis across the package. The user can
				change the value while generating the budget cost analysis.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Defaults</Title>
            <FieldHelp ID="tppdm600.btdt">
               <Header>
                  <Title>Budget Date</Title>
               </Header>
               <FuncDesc>Enter the start date of the budget.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ratc">
               <Header>
                  <Title>Labor Cost Rate</Title>
               </Header>
               <FuncDesc/>
               <SimpleSection>
                  <List>
                     <ListIntro>The project-specific labor cost rate is one of the
					 three possible default values for the labor rate if the following is recorded:</ListIntro>
                     <ListItem>Labor lines of the actual budget</ListItem>
                     <ListItem>Hours registration</ListItem>
                  </List>
               </SimpleSection>
               <SimpleSection>
                  <List>
                     <ListIntro>The other defaults are:</ListIntro>
                     <ListItemHead>
                        <GUIRef href="/baanerp/tp/domains/pdm.lwtc#task" role="option">Labor</GUIRef>
                     </ListItemHead>
                     <ListItem>The labor rates defined in either the <GUIRef href="/baanerp/tp/pdm/tppdm6111s000" role="session">Project Labor (tppdm6111s000)</GUIRef> session or the <GUIRef href="/baanerp/tp/pdm/tppdm0511m000" role="session">Standard Labor (tppdm0511m000)</GUIRef> session.</ListItem>
                     <ListItemHead>
                        <GUIRef href="/baanerp/tp/domains/pdm.lwtc#trade.group" role="option">Trade Group</GUIRef>
                     </ListItemHead>
                     <ListItem>The labor rate codes associated with trade groups as
					 defined in the <GUIRef href="/baanerp/tp/pdm/tppdm0130s000" role="session">Trade Group (tppdm0130s000)</GUIRef> session. Trade groups are linked to standard labor rates. When a project is
					 started, LN copies all
					 existing standard labor rates to project-specific labor rates. Because of this,
					 the project-specific labor rates are associated with particular trade groups.
					 So, through the trade group, the cost rate of the project labor rate is known
					 as the labor cost object.</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ccur">
               <Header>
                  <Title>Project Currency</Title>
               </Header>
               <FuncDesc>If the project is performed in another country, the project
		currency is useful for monitoring. This currency can be an external currency
		that is not specified as one of the home currencies.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ltrc">
               <Header>
                  <Title>Trans.Date</Title>
               </Header>
               <FuncDesc>Whenever the general labor cost rate is changed in a
				project, the transaction date of the labor cost rate is automatically filled
				with the system date, so that it is always known when the latest labor cost
				rate change took place.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rcmc">
               <Header>
                  <Title>In Home Currency</Title>
               </Header>
               <FuncDesc>The cost rate in home currency.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rats">
               <Header>
                  <Title>Labor Sales Rate</Title>
               </Header>
               <FuncDesc>A general sales rate for the labor costs in a project.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="home.ccur.c">
               <Header>
                  <Title>In Home Currency</Title>
               </Header>
               <FuncDesc>One of a company's base currencies in which LN registers and
		reports amounts.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>In a multicurrency system, up to three home currencies can
			 be defined:</ListIntro>
                     <ListItem>The <Link href="/baanerp/tc/glossary/glossary#000062" role="glossary">local currency</Link>
                     </ListItem>
                     <ListItem>Two <Link href="/baanerp/tc/glossary/glossary#000065" role="glossary" Update="No">reporting currencies</Link>
                     </ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ltrs">
               <Header>
                  <Title>Trans.Date</Title>
               </Header>
               <FuncDesc>Whenever the general sales rate is changed in a project,
				the transaction date of the sales rate is automatically filled with the system
				date, so that it is always known when the latest sales rate change took place.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rsmc">
               <Header>
                  <Title>In Home Currency</Title>
               </Header>
               <FuncDesc>The sales rate in home currency.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="home.ccur.s">
               <Header>
                  <Title>In Home Currency</Title>
               </Header>
               <FuncDesc>One of a company's base currencies in which LN registers and
		reports amounts.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>In a multicurrency system, up to three home currencies can
			 be defined:</ListIntro>
                     <ListItem>The <Link href="/baanerp/tc/glossary/glossary#000062" role="glossary">local currency</Link>
                     </ListItem>
                     <ListItem>Two <Link href="/baanerp/tc/glossary/glossary#000065" role="glossary" Update="No">reporting currencies</Link>
                     </ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.cuni">
               <Header>
                  <Title>Rate Unit</Title>
               </Header>
               <FuncDesc>For example, the cost rate is 25 EUR and the unit is hours,
				this means the costs are 25 euros per hour.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Planning</Title>
         <FieldGroup>
            <Title> Scheduling</Title>
            <FieldHelp ID="tppdm600.cpla">
               <Header>
                  <Title>Active Plan</Title>
               </Header>
               <FuncDesc>The project plan used in the project. This field must be
				filled if the costs are controlled by the activity budget type.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.stdt">
               <Header>
                  <Title>Start Date/Finish Date</Title>
               </Header>
               <FuncDesc>This date is default for plans and of importance while
				running budget cost analysis and using surcharges. The start date is used to
				decide what (budget) surcharges are valid for the budget cost analysis. Lack of
				a start date will result in all surcharges to be used.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>If you use an extension for a
				  fluctuation with invoice calculation method <GUIRef href="/baanerp/tp/domains/ptc.stlm#real.costs" role="option">Actual Costs</GUIRef> (set in the <GUIRef href="/baanerp/tp/ptc/tpptc0110s000" role="session">Extension (tpptc0110s000)</GUIRef> session), it is mandatory to enter the project start
				  date.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.dldt">
               <Header>
                  <Title>/</Title>
               </Header>
               <FuncDesc>The finish date of a project is only used to provide
				information.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.kptm">
               <Header>
                  <Title>Proj Lead Time Type</Title>
               </Header>
               <FuncDesc>The way time is looked at in a plan.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.espt">
               <Header>
                  <Title>Estimated Lead Time</Title>
               </Header>
               <FuncDesc>This field enables you to record the time which is expected
				to be needed for the execution of a project. The field only serves to provide
				information. The required project time can be expressed in workdays or in
				calendar days, depending on the setting of the <GUIRef href="/baanerp/tp/pdm/tppdm6100s000#tppdm600.kptm" role="manual">Project Lead Time Type</GUIRef> field.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ptcs">
               <Header>
                  <Title>Final Project Lead Time</Title>
               </Header>
               <FuncDesc>This field indicates the project lead time according to the
				specifications. The field is only used to provide information. The required
				project time can be expressed in workdays or in calendar days, depending on the
				setting of the <GUIRef href="/baanerp/tp/pdm/tppdm6100s000#tppdm600.kptm" role="manual">Project Lead Time Type</GUIRef> field.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.cstg">
               <Header>
                  <Title>Phase</Title>
               </Header>
               <FuncDesc>You can link a phase to a project in every status. A phase
				can be used to differentiate the project.</FuncDesc>
               <SimpleSection>
                  <SectionTitle> Example</SectionTitle>
                  <Paragraph>You can link the Phase code 001 with
				  description Delete Data to a range of projects. To delete the right projects,
				  you just select the phase code 001.</Paragraph>
               </SimpleSection>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Requirements Planning</Title>
            <FieldHelp ID="tppdm600.invr">
               <Header>
                  <Title>Commit Inventory On</Title>
               </Header>
               <FuncDesc>Specify the phase when the inventory in the warehouse must
				be committed to the project, based on the availability.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro> Allowed values:</ListIntro>
                     <ListItemHead> 
                        <GUIRef href="/baanerp/tp/domains/pdm.invr#insert" role="option">Insert</GUIRef>
                     </ListItemHead>
                     <ListItem>You can reserve the real inventory, that is, commit
					 the inventory in the warehouse when you insert a planned warehouse order in the <GUIRef href="/baanerp/tp/pss" role="module">Project Requirements</GUIRef> module</ListItem>
                     <ListItemHead> 
                        <GUIRef href="/baanerp/tp/domains/pdm.invr#confirm" role="option">Confirm</GUIRef>
                     </ListItemHead>
                     <ListItem>The inventory is committed when you confirm the
					 planned warehouse order.</ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/domains/pdm.invr#none" role="option">Not Applicable</GUIRef>
                     </ListItem>
                  </List>
               </SimpleSection>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>An inventory reservation in <GUIRef href="/baanerp/tp" role="package">Project</GUIRef> is an inventory
				  commitment in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>
                  </Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pwar">
               <Header>
                  <Title>Priority Supply Warehouse</Title>
               </Header>
               <FuncDesc>A general warehouse that receives the deliveries for more
				than one project. The goods are sent from the priority supply warehouse to the
				project warehouse.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/wh/onlinemanual/wmd00201" role="manual">Using warehouses</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="tppdm600.dwar">
               <Header>
                  <Title>Default project warehouse</Title>
               </Header>
               <FuncDesc>A <Link href="/baanerp/tp/glossary/glossary#000353" role="glossary">project warehouse</Link> is used to store the delivered goods coming from the priority
				supply warehouse. Enter a warehouse in this field if you want to use one
				warehouse for the project. All inventory will be sent to that warehouse. You
				can also leave this field empty and link the warehouse on a lower level to an
				element or activity to improve inventory control.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Project Created From</Title>
            <FieldHelp ID="tppdm600.dpcd" OtherIDs="dpcd.dsca">
               <Header>
                  <Title>Project Template</Title>
               </Header>
               <FuncDesc>The code of the template used to create the
				project.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Control</Title>
         <FieldGroup>
            <Title> Control</Title>
            <FieldHelp ID="tppdm600.prit">
               <Header>
                  <Title>Material Phys. Progress</Title>
               </Header>
               <FuncDesc>The level at which you can record the progress for this
				cost type.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.prts">
               <Header>
                  <Title>Labor Phys. Progress</Title>
               </Header>
               <FuncDesc>The level at which you can record the progress for this
				cost type.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.preq">
               <Header>
                  <Title>Equipment Phys. Progr.</Title>
               </Header>
               <FuncDesc>The cost price.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.prsb">
               <Header>
                  <Title>Subc. Phys. Progress</Title>
               </Header>
               <FuncDesc>The level at which you can record the progress for this
				cost type.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pric">
               <Header>
                  <Title>Sndry Cost Phys. Progr.</Title>
               </Header>
               <FuncDesc>The cost price.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.prre">
               <Header>
                  <Title>Register Progress</Title>
               </Header>
               <FuncDesc> 
                  <Link href="/baanerp/tp/onlinemanual/000104" role="manual">To use progress result</Link>
               </FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Cost Registration</Title>
            <FieldHelp ID="tppdm600.lwha" OtherIDs="tppdm600.lwhb tppdm600.lwhc tppdm600.lwhd">
               <Header>
                  <Title>Path Hours Labor Rate</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000102" role="glossary">labor rate for hours registration search path</Link> for the labor cost rate per hour and
				the sales rate per hour in the labor lines.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Logging</Title>
            <FieldHelp ID="tppdm600.lcdt">
               <Header>
                  <Title>Control Data Generation Date</Title>
               </Header>
               <FuncDesc>The last date the <GUIRef href="/baanerp/tp/ptc/tpptc1230m000" role="session">Generate Control Data (tpptc1230m000)</GUIRef> was run for this project.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.lclg">
               <Header>
                  <Title>Control Data Generated By</Title>
               </Header>
               <FuncDesc>The logon code of the user who last ran the <GUIRef href="/baanerp/tp/ptc/tpptc1230m000" role="session">Generate Control Data (tpptc1230m000)</GUIRef> session for this project.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.lpdt">
               <Header>
                  <Title>Last History Posting Date</Title>
               </Header>
               <FuncDesc>The latest date on which actual cost transactions were
				posted to the history. This date is automatically saved by LN during execution of
				the <GUIRef href="/baanerp/tp/ppc/tpppc4202m000" role="session">Post Transactions (tpppc4202m000)</GUIRef> session. This field is only used to
				provide information.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.logh">
               <Header>
                  <Title>Login Last History Posting</Title>
               </Header>
               <FuncDesc>This field shows the logon code of the user who last posted
				actual cost transactions for this project to the history. The value of this
				field is automatically updated during execution of the session.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ccdt">
               <Header>
                  <Title>Actual Cost Last Build</Title>
               </Header>
               <FuncDesc>Date of last generated control data.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.logc">
               <Header>
                  <Title>Login Cost Ctrl Data</Title>
               </Header>
               <FuncDesc>The logon code of the user who last ran the <GUIRef href="/baanerp/tp/ppc/tpppc4803m000" role="session">Build Actual Cost Control (tpppc4803m000)</GUIRef> session for this project. This field is only
				used to provide information.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Estimating</Title>
         <FieldHelp ID="tppdm600.rjct">
            <Header>
               <Title>Rejected</Title>
            </Header>
            <FuncDesc>A project can be rejected after being estimated. This field
			 indicates whether the estimated project can continue with its life cycle of
			 estimating, budgeting and invoicing.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tppdm600.cdis">
            <Header>
               <Title>Reason Code</Title>
            </Header>
            <FuncDesc>Use this field, for example, in situations where a particular
			 estimate is either rejected or the project is delayed. The reason code is
			 mandatory if the estimate is rejected.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tppdm600.ripr">
            <Header>
               <Title>Resulted in Project</Title>
            </Header>
            <FuncDesc>This field is filled only if different series are used for
			 projects and estimates. The target project is displayed, after the copy
			 process.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tppdm600.ofes">
            <Header>
               <Title>Originated from Estimate</Title>
            </Header>
            <FuncDesc>This field is filled only if different series are used for
			 projects and estimates. The estimate project used as the source is displayed.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tppdm600.lcla">
            <Header>
               <Title>Last Launched by</Title>
            </Header>
            <FuncDesc>The logon code of the person who has launched the estimate to
			 a project. The logon will be registered from the last launch.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tppdm600.dlau">
            <Header>
               <Title>Date of Launch</Title>
            </Header>
            <FuncDesc>The latest date that the launch process is run.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title> Interim Results</Title>
         <FieldGroup>
            <Title> Revenue Interim Results</Title>
            <FieldHelp ID="tppdm600.revr">
               <Header>
                  <Title>Revenue Recognition</Title>
               </Header>
               <FuncDesc/>
               <SimpleSection>
                  <List>
                     <ListIntro>Select the method for <Link href="/baanerp/tp/glossary/glossary#000377" role="glossary">revenue recognition</Link>:</ListIntro>
                     <ListItem> 
                        <Link href="/baanerp/tp/onlinemanual/000338" role="manual">Completed Project Method (RR)</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/tp/onlinemanual/000339" role="manual">Percentage Complete Method</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/tp/onlinemanual/000342" role="manual">Earned Revenue Factor Method</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/tp/onlinemanual/000343" role="manual">Actual Revenue Method</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/tp/onlinemanual/000340" role="manual">Reimbursement Contract Method</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/tp/onlinemanual/000341" role="manual">Milestone Method</Link> (only for projects controlled by Activity)</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pcmp">
               <Header>
                  <Title>Percentage Completed</Title>
               </Header>
               <FuncDesc>The percentage of completion of the project. You must
				multiply this percentage with the contract amount to calculate the revenue to
				be recognized.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>You can manually enter the percentage of
				  completion or click <GUIRef href="/baanerp/tp/pdm/tppdm6100s000#calc.perc.completed" role="command">Perc. Complete</GUIRef> to get the calculated value. LN calculates the
				  percentage using the following formula:</Paragraph>
                  <Formula space-and-orientation="indented-estimated">
                     <Paragraph>percentage of completion = costs (incurred) / estimate at completion cost </Paragraph>
                  </Formula>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.earf">
               <Header>
                  <Title>Earned Revenue Factor</Title>
               </Header>
               <FuncDesc>Specify the earned revenue factor. You must multiply this
				factor with the the cost to calculate the revenue to be recognized.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>You can manually enter the earned
				  revenue factor or click <GUIRef href="/baanerp/tp/pdm/tppdm6100s000#calc.earned.revenue.fact" role="command">Calculate ERF</GUIRef> to get the calculated value. LN calculates the
				  factor using the following formula:</Paragraph>
                  <Formula space-and-orientation="indented-estimated">
                     <Paragraph>ERF = project contract amount / total budgeted costs</Paragraph>
                  </Formula>
                  <Paragraph>To calculate ERF, the project status
				  must be <GUIRef href="/baanerp/tp/domains/pdm.psts#construction" role="option">Active</GUIRef>, because the total budgeted cost is known only for
				  active projects.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.revt">
               <Header>
                  <Title>Revenue Recognition Threshold</Title>
               </Header>
               <FuncDesc>The minimum percentage completion expected before revenue
				is recognized.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>Only if the percentage completion is
				  greater than or equal to this field, revenue is recognized when interim results
				  are generated using the <GUIRef href="/baanerp/tp/ppc/tpppc2260m000" role="session">Generate Financial Interim Results (tpppc2260m000)</GUIRef> session. However, if the <GUIRef href="/baanerp/tp/ppc/tpppc2260m000#prop.c" role="manual">Profit Percentage</GUIRef> is negative, revenue will be recognized irrespective of
				  minimum percentage completion being met or not.</Paragraph>
               </Note>
               <DefaultValue>
                  <SectionTitle>Default value</SectionTitle>
                  <Paragraph>0</Paragraph>
               </DefaultValue>
            </FieldHelp>
            <FieldHelp ID="tppdm600.revl">
               <Header>
                  <Title>Revenue Recognition Limit</Title>
               </Header>
               <FuncDesc>The limit on the revenue to be recognized. Specify a
				maximum percentage.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>The value can be changed. The revenue
				  recognition limit is valid for all RR methods except the <GUIRef href="/baanerp/tp/domains/pdm.revr#cmpl" role="option">Completed Project</GUIRef> method. The percentage times the contract amount gives the
				  maximum revenue that can be recognized (until the completion of the project).
				  This percentage is ignored when the project is complete and the final revenue
				  (and COGS) is posted.</Paragraph>
               </Note>
               <DefaultValue>
                  <SectionTitle>Default value</SectionTitle>
                  <Paragraph>100</Paragraph>
               </DefaultValue>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Cost Interim Results</Title>
            <FieldHelp ID="tppdm600.cogs">
               <Header>
                  <Title>Costs of Goods Sold</Title>
               </Header>
               <FuncDesc/>
               <SimpleSection>
                  <List>
                     <ListIntro>Select the method to calculate the <Link href="/baanerp/tp/glossary/glossary#000327" role="glossary" Update="No">cost of goods sold</Link>:</ListIntro>
                     <ListItem> 
                        <Link href="/baanerp/tp/onlinemanual/000344" role="manual">Completed Project Method (COGS)</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/tp/onlinemanual/000345" role="manual">Profit Percentage method</Link>
                     </ListItem>
                     <ListItem> 
                        <Link href="/baanerp/tp/onlinemanual/000346" role="manual">Reimbursement Contract Method</Link>
                     </ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.prpc">
               <Header>
                  <Title>Profit Percentage</Title>
               </Header>
               <FuncDesc>Specify the profit percentage. The COGS is calculated on
				the basis of this percentage and the revenue recognized.</FuncDesc>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <Paragraph>You can manually enter the percentage or
				  click <GUIRef href="/baanerp/tp/pdm/tppdm6100s000#calc.profit.percentage" role="command">Calculate Profit Percentage</GUIRef> to get the calculated
				  value. LN calculates
				  the percentage using one of the following formulas:</Paragraph>
                  <Formula space-and-orientation="indented-estimated">
                     <Paragraph>profit percentage = budget / contract amount</Paragraph>
                  </Formula>
                  <Paragraph> 
                     <Emphasis>or</Emphasis>
                  </Paragraph>
                  <Formula space-and-orientation="indented-estimated">
                     <Paragraph>profit percentage = EAC (Estimate at Completion) / contract amount</Paragraph>
                  </Formula>
                  <Paragraph>When the COGS is determined at project
				  level, LN allows you to
				  select the base to calculate the profit percentage. You can either select <GUIRef href="/baanerp/tp/domains/pdm.bapp#budget" role="option">Budget</GUIRef> or select <GUIRef href="/baanerp/tp/domains/pdm.bapp#eac" role="option">Estimate at Completion</GUIRef> as the base to calculate the profit percentage.</Paragraph>
               </Note>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Miscellaneous</Title>
         <FieldGroup>
            <Title> Classification</Title>
            <FieldHelp ID="tppdm600.ccam">
               <Header>
                  <Title>Acquiring Method</Title>
               </Header>
               <FuncDesc>For statistical reasons you can enter the method you used
				to acquire this project.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.cfac">
               <Header>
                  <Title>Financing Method</Title>
               </Header>
               <FuncDesc>The code that identifies the financing method used for this
				project.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.csec">
               <Header>
                  <Title>Business Sector</Title>
               </Header>
               <FuncDesc>The code that identifies a business sector.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.creg">
               <Header>
                  <Title>Geographical Area</Title>
               </Header>
               <FuncDesc>The geographical area.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ccat">
               <Header>
                  <Title>Category</Title>
               </Header>
               <FuncDesc>A user-definable classification for projects.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ccot">
               <Header>
                  <Title>Group</Title>
               </Header>
               <FuncDesc>A user-defined classification of projects.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Miscellaneous</Title>
            <FieldHelp ID="tppdm600.rsip">
               <Header>
                  <Title>Sundry Cost Code for Provisional Amounts</Title>
               </Header>
               <FuncDesc>Costs relating to an <Link href="/baanerp/tp/glossary/glossary#000017" role="glossary">extension</Link> of the <GUIRef href="/baanerp/tp/domains/ptc.stlt#provision.entry" role="option">Provisional Amount</GUIRef> type are posted to a sundry cost
				object.</FuncDesc>
               <SimpleSection>
                  <Paragraph>This field identifies the code of the
				  sundry cost object (standard or project-specific) used for this project.</Paragraph>
                  <Paragraph>This field takes its default value from
				  the <GUIRef href="/baanerp/tp/pdm/tppdm6100s000#tppdm600.rsip" role="manual">Sundry Cost Code for Provisional Amounts</GUIRef> field in the <GUIRef href="/baanerp/tp/pdm/tppdm6100s000" role="session">Project (tppdm6100s000)</GUIRef> session.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="tppdm600.rsac">
               <Header>
                  <Title>Default Cost Account/Work Package</Title>
               </Header>
               <FuncDesc>The activity is used as default in processes in which an
				amount must be posted to an activity and the activity is not specified.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>This occurs in the following cases:</ListIntro>
                     <ListItem>If installments are generated automatically through the <GUIRef href="/baanerp/tp/pin/tppin1210m000" role="session">Create Progress Invoice Installments (tppin1210m000)</GUIRef> session.</ListItem>
                     <ListItem>If provisional amount settlements are generated through
					 the <GUIRef href="/baanerp/tp/ppc/tpppc3210m000" role="session">Generate Provisional Amount Transactions (tpppc3210m000)</GUIRef> session.</ListItem>
                     <ListItem>If invoices are generated for extensions.</ListItem>
                     <ListItem>If unit rate invoices are generated.</ListItem>
                  </List>
               </SimpleSection>
               <Note>
                  <SectionTitle> Note</SectionTitle>
                  <List>
                     <ListIntro>The default activity comes from the <GUIRef href="/baanerp/tp/pdm/tppdm6100s000" role="session">Project (tppdm6100s000)</GUIRef> session.</ListIntro>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/pin/tppin1210m000" role="session">Create Progress Invoice Installments (tppin1210m000)</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/ppc/tpppc3210m000" role="session">Generate Provisional Amount Transactions (tpppc3210m000)</GUIRef>
                     </ListItem>
                  </List>
               </Note>
            </FieldHelp>
            <FieldHelp ID="tppdm600.ussu">
               <Header>
                  <Title>Use Surcharges</Title>
               </Header>
               <FuncDesc>The surcharges used.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.cmud">
               <Header>
                  <Title>Sufferance Tax</Title>
               </Header>
               <FuncDesc>The code that identifies the <Link href="/baanerp/tp/glossary/glossary#SufferTax_tp" role="glossary">sufferance tax</Link> that
				applies to this project.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.wipc">
               <Header>
                  <Title>WIP Surcharge</Title>
               </Header>
               <FuncDesc>The surcharge percentage calculated on the total costs of
				the project to determine the financial value of the work in process (WIP). This
				surcharge percentage is used only if the <Link href="/baanerp/tp/ppc/tpppc0100s000#amos" role="formfield">Sales Value Surcharge Costs in WIP</Link> check box in the <GUIRef href="/baanerp/tp/ppc/tpppc0100s000" role="session">PPC Parameters (tpppc0100s000)</GUIRef> session is selected.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Subcontractor's data (as per Dutch WKA law)</Title>
            <FieldHelp ID="tppdm600.pcwa">
               <Header>
                  <Title>Wage in Contract Amount</Title>
               </Header>
               <FuncDesc>The percentage of the total contract amount which has been
				agreed upon with the main contractor that is formed by wage costs.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tppdm600.pcba">
               <Header>
                  <Title>Wage B-Account</Title>
               </Header>
               <FuncDesc>This field is only relevant in the Netherlands.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Login</Title>
            <FieldHelp ID="tppdm600.user" OtherIDs="user.desc">
               <Header>
                  <Title>User</Title>
               </Header>
               <FuncDesc>The user who creates the project. The default value is the
				login name of the user. The value can be changed.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Project Created From</Title>
            <FieldHelp ID="tppdm600.pror">
               <Header>
                  <Title>Project Origin</Title>
               </Header>
               <FuncDesc/>
               <SimpleSection>
                  <List>
                     <ListIntro>Indicates how the project was created:</ListIntro>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/domains/pdm.pror#project" role="option">Copied from Project</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/domains/pdm.pror#template" role="option">Copied from Template</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/domains/pdm.pror#estimate" role="option">Copied from Estimate</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/domains/pdm.pror#extern" role="option">Inserted by external Package</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/tp/domains/pdm.pror#manual" role="option">Manually entered</GUIRef>
                     </ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="project.origin" OtherIDs="origin.desc">
               <Header>
                  <Title>Project Origin</Title>
               </Header>
               <FuncDesc>If applicable, the source from which this project was
				copied.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
   </Fields>
</Session>