<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/pcs/tipcs2130m000" xml:lang="en">
   <Header>
      <Title>Project Details (tipcs2130m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to list
		  general project details.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>In the details
		  session, you can maintain project details. This data is related to the
		  logistical actions and financial consequences of a customized demand.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If you started the <GUIRef href="/baanerp/ti/pcs/tipcs2130m000" role="session">Project Details (tipcs2130m000)</GUIRef> session by zooming, you can only find and select a
			 record.</Paragraph>
         </Note>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/ti/onlinemanual/000175" role="manual">Project types</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tipcs030.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>A collection of manufacturing and purchasing actions that are
		performed especially for a particular customer order. A project is initiated by
		a customer order for items having a <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> order policy. The purpose of a project is to plan and coordinate the production
		of these items.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For a standard-to-order production, the project is only
			 used to link the item with the customer order. Otherwise, a project can
			 include:</ListIntro>
               <ListItem>Customized item data (BOMs and routings)</ListItem>
               <ListItem>Project planning (activity planning)</ListItem>
            </List>
            <Paragraph>A budget is a special type of project. A budget is used to
		  plan and estimate, not to carry out production.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000175" role="manual">Project types</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.psts">
         <Header>
            <Title>Project Status</Title>
         </Header>
         <FuncDesc>The status that is assigned to the project. This status, which
		  is displayed in most sessions, indicates the project progress. Depending on the
		  project status, some sessions cannot be executed or cannot yet be executed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.psta">
         <Header>
            <Title>Project Stage</Title>
         </Header>
         <FuncDesc>The current execution stage of the project. Stages are entered
		  in the <GUIRef href="/baanerp/ti/pcs/tipcs2110m000" role="session">Project Stages (tipcs2110m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.cbdg">
         <Header>
            <Title>Budget</Title>
         </Header>
         <FuncDesc>The project of the type <Link href="/baanerp/ti/glossary/glossary#000082" role="glossary">budget</Link> that originated the
		  actual project.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.soco">
         <Header>
            <Title>Stage of Completion</Title>
         </Header>
         <FuncDesc>The percentage of work that is completed on the PCS
		  project.</FuncDesc>
         <SimpleSection>
            <Paragraph>The percentage that you type in this field is displayed in
			 the <Link href="/baanerp/ti/pcs/tipcs3190m000#tipcs390.pocm" role="formfield">POC (Manual)</Link> field of the <GUIRef href="/baanerp/ti/pcs/tipcs3190m000" role="session">Interim COGS and Revenues by Project (tipcs3190m000)</GUIRef> session. The percentage can be
			 used in revenue recognition calculations to determine interim Cost of Goods
			 Sold (COGS) and interim revenue for a PCS project.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000370" role="manual">Overview of interim revenue recognition in Project Control (PCS)</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000371" role="manual">Procedure for interim revenue recognition in Project Control (PCS)</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.intp">
         <Header>
            <Title>Investment Project</Title>
         </Header>
         <FuncDesc>Internal projects are used to collect costs, such as costs
		  relating to warranties, product development, and investments. These projects
		  must not be included in Work In Process (WIP), but must be posted to separate
		  general ledger accounts in the Balance Sheet or P&amp;L Statement.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>If this check box is selected, the project is an internal project. As a
				result:</ListIntro>
               <ListItem>No sales order can
				be created</ListItem>
               <ListItem>No financial entries
				are made for Combination of PCS and Estimated Cost of Goods Sold or Combination
				of PCS and Act. Costs of Goods Sold</ListItem>
            </List>
            <List>
               <ListIntro>If this check box is cleared, the project is an external project. As a
				result:</ListIntro>
               <ListItem>A sales order can be
				created.</ListItem>
               <ListItem>Financial entries
				can be made for Combination of PCS and Estimated cost of Goods (with the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session).</ListItem>
            </List>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>You cannot change
				this field if one or more financial transactions are already being processed.</ListItem>
               <ListItem>Also an internal
				project cannot be linked to a sales order line in the <GUIRef href="/baanerp/td/sls/tdsls4101m000" role="session">Sales Order Lines (tdsls4101m000)</GUIRef> session.</ListItem>
            </List>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tf/integrations/400000" role="manual">Financial integrations - overview</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.erev">
         <Header>
            <Title>Revenue Expected</Title>
         </Header>
         <FuncDesc>This checkbox is used to determine whether or not turnover is
		  expected for the project. This outcome determines when and how sales cost price
		  bookings are carried out.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is selected, the sales
			 cost price bookings are created on the basis of an actual turnover. If it is an
			 actual turnover, the right sales cost price bookings will be created at the
			 next cost price calculation for the project.</Paragraph>
            <Paragraph>If this check box is cleared, sales cost
			 price bookings are created on the basis of the parts of the project. Once there
			 are sales orders for a project for which invoicing has taken place, or there
			 are no sales orders, then at the next cost-price calculation for the project
			 sales cost price bookings will be carried out for all parts of the project.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs030.ncac">
         <Header>
            <Title>Net Change Actual Costs</Title>
         </Header>
         <FuncDesc>If this check box is selected, financial transactions were recorded for this
		  project after the last time the actual cost prices were calculated in the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session. If you perform a net-change
		  actual cost price calculation, LN skips the projects for which this check box is cleared, because
		  the actual cost prices have not changed since the previous
		  calculation.</FuncDesc>
         <SimpleSection>
            <Paragraph>If you perform an
			 actual cost price calculation in the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session, LN clears this check
			 box. If a financial transaction is recorded for a project, LN selects this check
			 box for that project.</Paragraph>
            <Paragraph>To perform a
			 net-change actual cost price calculation, in the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session, select the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000#net.calc" role="manual">Net Change Only</GUIRef> check box.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs030.pocm">
         <Header>
            <Title>POC Method</Title>
         </Header>
         <FuncDesc>With revenue recognition, you can calculate interim Cost of
		  Goods Sold (COGS) and interim revenue for a PCS project. The interim COGS and
		  revenue are based on the percentage of the work that is completed on the PCS
		  project. In this field, you must determine how the Percentage of Completion
		  (POC) is calculated for the PCS project.</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/ti/domains/pcs.pocm" role="domain">Percentage of Completion Method</Link>
            </Paragraph>
         </AllowedValues>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000370" role="manual">Overview of interim revenue recognition in Project Control (PCS)</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000371" role="manual">Procedure for interim revenue recognition in Project Control (PCS)</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.intc">
         <Header>
            <Title>Post Interim Results by Cost Component</Title>
         </Header>
         <FuncDesc>With revenue recognition, you can calculate interim Cost of
		  Goods Sold (COGS) and interim revenue for a PCS project.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is selected, the interim COGS is specified by detailed
			 cost components. You can view and maintain the detailed interim COGS in the <Link href="/baanerp/ti/pcs/tipcs3191m000" role="session">COGS by Cost Component (tipcs3191m000)</Link> session.</Paragraph>
            <Paragraph>If this check box is cleared, the interim COGS is not specified by
			 detailed cost components. Instead, the interim COGS is posted on the cost
			 component that is specified in the <GUIRef href="/baanerp/ti/pcs/tipcs2130m000#tipcs030.incp" role="manual">Cost Component for Interim Postings</GUIRef> field.</Paragraph>
         </SimpleSection>
         <SimpleSection>
            <SectionTitle>Performance aspects</SectionTitle>
            <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/ti/P000010_int_result_cost_comp" role="manual">Interim results by cost component</Link>.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000370" role="manual">Overview of interim revenue recognition in Project Control (PCS)</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000371" role="manual">Procedure for interim revenue recognition in Project Control (PCS)</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.incp" OtherIDs="tcmcs048.dsca">
         <Header>
            <Title>Cost Component for Interim Postings</Title>
         </Header>
         <FuncDesc>The cost component on which the interim Cost of Goods Sold
		  (COGS) is posted. You can only enter a cost component if the <GUIRef href="/baanerp/ti/pcs/tipcs2130m000#tipcs030.intc" role="manual">Post Interim Results by Cost Component</GUIRef> check box is
		  cleared.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000370" role="manual">Overview of interim revenue recognition in Project Control (PCS)</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000371" role="manual">Procedure for interim revenue recognition in Project Control (PCS)</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.crfc">
         <Header>
            <Title>COGS and Revenues restricted to Financial Company of PCS Project</Title>
         </Header>
         <FuncDesc>If this check box is selected, PCS related COGS and
		  revenues are all posted on the financial company of the PCS project's <Link href="/baanerp/ti/glossary/glossary#000053" role="glossary">calculation office</Link>.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is cleared, PCS related COGS and
			 revenues are posted on the financial companies of the service department, sales
			 office and/or warehouse.</Paragraph>
            <Paragraph>This field is defaulted from the corresponding field in the <GUIRef href="/baanerp/ti/pcs/tipcs0100m000" role="session">Project Control Parameters (tipcs0100m000)</GUIRef> session.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If this check box is selected, and you clear the check
			 box, you cannot select the check box again. The reason is that before selecting
			 the check box again, you could have posted PCS related COGS and revenues to
			 financial companies that are different from the PCS project's financial
			 company, which is not allowed if this check box is selected.</Paragraph>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000435" role="manual">COGS and revenue postings for PCS projects in a multisite environment</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.dstr">
         <Header>
            <Title>COGS Distribution based on</Title>
         </Header>
         <FuncDesc>If the <Link href="/baanerp/ti/pcs/tipcs0100m000#tipcs000.crfc" role="formfield">COGS and Revenues restricted to Financial Company of PCS Project</Link> check box is cleared, the general COGS is distributed among
		  several departments instead of only on the PCS project's calculation office.
		  You can use this field to indicate whether you want to enter the COGS
		  distribution manually in the <Link href="/baanerp/ti/pcs/tipcs3110m000" role="session">Project COGS Distribution (tipcs3110m000)</Link> session, or
		  that LN calculates the
		  COGS distribution based on the revenue of the sales order, service order,
		  and/or warehouse order.</FuncDesc>
         <SimpleSection>
            <Paragraph>This field is defaulted from the corresponding field in the <GUIRef href="/baanerp/ti/pcs/tipcs0100m000" role="session">Project Control Parameters (tipcs0100m000)</GUIRef> session.</Paragraph>
         </SimpleSection>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/ti/domains/pcs.distr" role="domain">COGS Distribution based on</Link>
            </Paragraph>
         </AllowedValues>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000435" role="manual">COGS and revenue postings for PCS projects in a multisite environment</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.tpsr">
         <Header>
            <Title>Transfer between PCS Projects considered as Selling Relation</Title>
         </Header>
         <FuncDesc>If this check box is selected, the transfer of items
		  from one PCS project (the source project) to another PCS project (the target
		  project) results in a revenue on the source project.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is cleared, the transfer of items from
			 one PCS project (the source project) to another PCS project (the target
			 project) results in a negative material cost booking on the source project. You
			 can consider such a negative booking as a correction of the actual costs on the
			 source project.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs030.bkcs">
         <Header>
            <Title>Post on Current Date</Title>
         </Header>
         <FuncDesc>In <GUIRef href="/baanerp/ti/pcs/tipcs0100m000" role="session">Project Control Parameters (tipcs0100m000)</GUIRef> session the field <GUIRef href="/baanerp/ti/pcs/tipcs0100m000#tipcs000.bkcs" role="manual">Post Project Transactions on Current Date</GUIRef> which will
		  be copied to the <GUIRef href="/baanerp/ti/pcs/tipcs2130m000" role="session">Project Details (tipcs2130m000)</GUIRef> which a PCS Project is
		  created.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is cleared, then <GUIRef href="/baanerp/ti/pcs/tipcs2130m000#tipcs030.bkdt" role="manual">Posting Date Cost/Turnover Sales</GUIRef> is filled with the
			 day of today.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs030.bkdt">
         <Header>
            <Title>Posting Date</Title>
         </Header>
         <FuncDesc>The date on which the cost price and the sales turnover must be
		  entered upon the closing of the project. The value of this field can be
		  overwritten during the execution of session <GUIRef href="/baanerp/ti/pcs/tipcs2250m000" role="session">Close Project (tipcs2250m000)</GUIRef>.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tf/integrations/400009" role="manual">Integration document types</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.tinv">
         <Header>
            <Title>Invoiced Amount</Title>
         </Header>
         <FuncDesc>The total invoiced amount for the project in question. If it is
		  a main project, the invoiced amounts for the subprojects are automatically
		  aggregated to the main project with the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session.</FuncDesc>
         <SimpleSection>
            <Paragraph>The invoiced amount
			 is updated during project cost calculation in the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session and <GUIRef href="/baanerp/ti/pcs/tipcs2250m000" role="session">Close Project (tipcs2250m000)</GUIRef> session.</Paragraph>
            <Paragraph>The amount is
			 derived from all sales orders, service orders and warehouse orders at the
			 delivery side of the project for which invoices have been printed by the <GUIRef href="/baanerp/ci/sli" role="module">Sales Invoicing</GUIRef> module.</Paragraph>
            <Paragraph>If the POC method is <GUIRef href="/baanerp/ti/domains/pcs.pocm#none" role="option">None</GUIRef>,
			 which means that no revenue recognition is used, the percentage invoiced is
			 calculated on the basis of this amount and the total expected amount of <Link href="/baanerp/ts/glossary/glossary#Revenue_ts" role="glossary">revenue</Link>. This percentage is
			 then used as a base for posting cost of goods sold on non-closed projects.</Paragraph>
            <Paragraph>The interim COGS bookings are based on the interim COGS
			 percentage in the <GUIRef href="/baanerp/ti/pcs/tipcs3190m000" role="session">Interim COGS and Revenues by Project (tipcs3190m000)</GUIRef> session.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cprj.ccur">
         <Header>
            <Title>Invoiced Amount</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Currency_tc" role="glossary">currency</Link> in which the
		  invoiced amount is expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.plcd">
         <Header>
            <Title>Planning Method</Title>
         </Header>
         <FuncDesc>The planning method indicates whether the start date or
		  completion date in the network planning for the project should be regarded as
		  firm.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>You can select a
			 planning method only in the case of a main or single project. A subproject
			 automatically inherits the planning data of the main project.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tipcs030.sdat">
         <Header>
            <Title>Start Date</Title>
         </Header>
         <FuncDesc>The desired or planned start date for the project. This date is
		  used or calculated by <Link href="/baanerp/ti/glossary/glossary#NetworPlanni_ti" role="glossary">network planning</Link>.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro>You can only fill in a start date if:</ListIntro>
               <ListItem>The project is a
				main or single project.</ListItem>
               <ListItem>The forward planning
				method is chosen.</ListItem>
            </List>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000178" role="manual">Network planning</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.ddat">
         <Header>
            <Title>Completion Date</Title>
         </Header>
         <FuncDesc>The desired or planned completion date for the project.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>You can only enter a delivery date if:</ListIntro>
               <ListItem>The project is a
				main or single project.</ListItem>
               <ListItem>The backward
				planning method is chosen.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs030.acdt">
         <Header>
            <Title>Actualization Date</Title>
         </Header>
         <FuncDesc>The date that the cost price(s) and valuation price(s) for the
		  PCS project are calculated and actualized using the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session. Note that the actualization
		  date can differ from the effective date of the costing data. You must determine
		  the effective date in the <GUIRef href="/baanerp/ti/pcs/tipcs3250m000" role="session">Calculate Cost Prices by Project (tipcs3250m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.cldt">
         <Header>
            <Title>Actual Closing Date</Title>
         </Header>
         <FuncDesc>The date that the project is closed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.defc">
         <Header>
            <Title>Definitively Closed</Title>
         </Header>
         <FuncDesc>If this check box is selected, all financial
		  transactions for the project are deleted by the <GUIRef href="/baanerp/ti/pcs/tipcs3200m000" role="session">Delete Financial Transactions by Project (tipcs3200m000)</GUIRef> session. You cannot reset the
		  project status anymore.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.ecpr">
         <Header>
            <Title>H</Title>
         </Header>
         <FuncDesc>The total estimated capacity requirements for the project.
		  Using the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session, this value is automatically
		  calculated on the basis of the estimated capacity requirements per activity.
		  For main projects, the estimated capacity requirements of the subprojects are
		  automatically aggregated to the main project.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.ecpa">
         <Header>
            <Title>[H]</Title>
         </Header>
         <FuncDesc>The total aggregated capacity requirements for the project.
		  Using the <GUIRef href="/baanerp/ti/pcs/tipcs4201m000" role="session">Aggregate Estimated Capacity to Project (tipcs4201m000)</GUIRef> session, this value is
		  automatically calculated on the basis of the project structure and the work
		  assembly per customized manufactured item. For main projects, the aggregated
		  capacity requirements for the subprojects are automatically aggregated to the
		  main project using the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.ascp">
         <Header>
            <Title>[H]</Title>
         </Header>
         <FuncDesc>The total number of hours spent on activities for the project
		  that have been accounted for. This value is automatically updated with the <GUIRef href="/baanerp/bp/tmm/bptmm1203m000" role="session">Process Hours and Expenses (bptmm1203m000)</GUIRef> session. For main projects, the hours are
		  also aggregated for subprojects of the main project in the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.aman">
         <Header>
            <Title>Actual Man Hours</Title>
         </Header>
         <FuncDesc>The actual man hours that are the posted to and processed by <GUIRef href="/baanerp/bp" role="package">People</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs030.amch">
         <Header>
            <Title>Actual Machine Hours</Title>
         </Header>
         <FuncDesc>The actual machine hours that are the posted to and processed
		  by <GUIRef href="/baanerp/bp" role="package">People</GUIRef>.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="project.status">
         <Header>
            <Title>Project Status</Title>
         </Header>
         <FuncDesc>Starts the <Link href="/baanerp/ti/pcs/tipcs2102m000" role="session">Project Status (tipcs2102m000)</Link> session.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>