<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/pcs/tipcs4502m000" xml:lang="en">
   <Header>
      <Title>Activity Overview by Project (tipcs4502m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to display the activity
		  list by project.</Paragraph>
      </AimSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tipcs400.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>Indicates the current progress of the project.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.cact">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>This code identifies an activity in the network planning for a
		  project.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.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="tipcs400.tano">
         <Header>
            <Title>Task</Title>
         </Header>
         <FuncDesc>ERP Enterprise shows
		  the number of the <Link href="/baanerp/ti/glossary/glossary#Task_ti" role="glossary">task</Link> linked to the activity.</FuncDesc>
         <SimpleSection>
            <Paragraph>The task number
			 gives more detailed information about the activity.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs400.cwoc">
         <Header>
            <Title>Work Center</Title>
         </Header>
         <FuncDesc>The code of the <Link href="/baanerp/ti/glossary/glossary#000000000000036" role="glossary">work center</Link> or the <Link href="/baanerp/ti/glossary/glossary#MainWorkCent_ti" role="glossary">main work center</Link> where the activity is
		  carried out.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.acmn">
         <Header>
            <Title>Activity Manager</Title>
         </Header>
         <FuncDesc>A person responsible for planning or carrying out a project
		activity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="txta.yn">
         <Header>
            <Title>Text</Title>
         </Header>
         <FuncDesc>This field shows whether or not a text is present.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.rcld">
         <Header>
            <Title>Capacity Load Table</Title>
         </Header>
         <FuncDesc>A table in which you can define how the rough capacity
		  requirements are to be distributed over the capacity duration. The x coordinate
		  is a percentage of the activity duration. The y coordinate is a percentage of
		  rough capacity requirements.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.ecpr">
         <Header>
            <Title>Rough Capacity</Title>
         </Header>
         <FuncDesc>The globally needed capacity in hours for the execution of the
		  relevant activity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.ecpa">
         <Header>
            <Title>Aggregated Capacity</Title>
         </Header>
         <FuncDesc>The aggregated capacity requirements in hours of the work
		  center where the activity is scheduled to be carried out. The aggregated
		  capacity requirements are calculated in the <GUIRef href="/baanerp/ti/pcs/tipcs4201m000" role="session">Aggregate Estimated Capacity to Project (tipcs4201m000)</GUIRef> session on the basis of the
		  project structure and the project engineering. You can only do this if the
		  operations have been linked to activities in the customized routing. Dependent
		  on the value of the <GUIRef href="/baanerp/ti/rou/tirou0101m000#tirou001.ccap" role="manual">Critical Capacity for Planning</GUIRef> field in the <GUIRef href="/baanerp/ti/rou/tirou0101m000" role="session">Work Centers (tirou0101m000)</GUIRef> session, <GUIRef href="/baanerp/tc/domains/ccap#man.capacity" role="option">Man Capacity</GUIRef> or <GUIRef href="/baanerp/tc/domains/ccap#mach.capacity" role="option">Machine Capacity</GUIRef> is used to calculate the aggregated capacity.</FuncDesc>
         <SimpleSection>
            <Paragraph>The aggregated
			 capacity requirements are only shown for your information and can be used for
			 checking or monitoring the rough planned hours by activity.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs400.acap">
         <Header>
            <Title>Average Capacity</Title>
         </Header>
         <FuncDesc>Enter the available capacity in hours per day. This capacity is
		  used to calculate the default activity duration. The planning factor enables
		  you to record the available capacity in hours per day for each employee or
		  machine.</FuncDesc>
         <SimpleSection>
            <Paragraph>Based on this capacity, ERP Enterprise calculates the default
			 duration of an activity using the appropriate formula:</Paragraph>
            <Paragraph>Default acitivity duration = Rourh capacity requirement /
			 (Planning factor x Available Capacity)</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs400.eplf">
         <Header>
            <Title>Planning Factor</Title>
         </Header>
         <FuncDesc>The planning factor indicates how many employees or machines
		  are employed simultaneously for the execution of an activity. This factor is
		  used only to calculate the default duration of the activity on the basis of the
		  global capacity requirements and the available hours per day.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.adur">
         <Header>
            <Title>Lead Time</Title>
         </Header>
         <FuncDesc>The time between the production start date and the delivery
		date. The lead time can include order preparation time, transportation time,
		and inspection time.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.esdt">
         <Header>
            <Title>Earliest Start Date</Title>
         </Header>
         <FuncDesc>The earliest date on which the activity can be started. You can
		  determine this date using the <Link href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</Link> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.lsdt">
         <Header>
            <Title>Latest Start Date</Title>
         </Header>
         <FuncDesc>The last date on which the activity can be started. Determine
		  this date by using the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.efdt">
         <Header>
            <Title>Earliest End Date</Title>
         </Header>
         <FuncDesc>Rhe earliest date on which the activity can be completed.
		  Determine this date using the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.lfdt">
         <Header>
            <Title>Latest End Date</Title>
         </Header>
         <FuncDesc>The last date on which the activity can be completed. Determine
		  this day using the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.totf">
         <Header>
            <Title>Total Float</Title>
         </Header>
         <FuncDesc>The total float of an activity is the maximum time expressed in
		  (working) days in which that activity can be shifted without affecting the
		  planned completion date of the relevant project.</FuncDesc>
         <SimpleSection>
            <Paragraph>The total float-time
			 is calculated as follows:</Paragraph>
            <Paragraph>Total Float = Latest
			 Finish - Earliest Start - Activity Duration</Paragraph>
            <Paragraph>The latest finish
			 date and earliest start date are expressed in project days.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000150" role="manual">Float times</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs400.fref">
         <Header>
            <Title>Free Float</Title>
         </Header>
         <FuncDesc>The free float time between one activity and the next. The free
		  float time indicates how many days the activity can be extended without
		  jeopardizing the progress of other related activities.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000150" role="manual">Float times</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs400.dsdt">
         <Header>
            <Title>Desired Start Date</Title>
         </Header>
         <FuncDesc>The date on which you want to start the relevant activity. This
		  date is only used for information. However, the desired start date is compared
		  to the earliest and latest finish dates and the reference date in the <GUIRef href="/baanerp/ti/pcs/tipcs4211m000" role="session">Generate Network Messages (tipcs4211m000)</GUIRef> session. This can result in the creation of
		  exception messages.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.dfdt">
         <Header>
            <Title>Desired Finish Date</Title>
         </Header>
         <FuncDesc>The date on which you want to stop the execution of the
		  relevant activity. This date is only used for information. However, the desired
		  finish date is compared to the earliest and latest finish date and the
		  reference date via the session <GUIRef href="/baanerp/ti/pcs/tipcs4211m000" role="session">Generate Network Messages (tipcs4211m000)</GUIRef>, which can result in the creation of
		  exception messages.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.acal">
         <Header>
            <Title>Make Estimate</Title>
         </Header>
         <FuncDesc>Indicates whether the relevant activity must be included in the
		  estimated cost-price calculation for the project. This can be especially
		  important for indirect activities, such as engineering.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.llcd">
         <Header>
            <Title>Low Level Code</Title>
         </Header>
         <FuncDesc>The Low Level code indicates the lowest level at which the
		  activity is found in the activity network for the project. This code is
		  determined by the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.asdt">
         <Header>
            <Title>Actual Start Date</Title>
         </Header>
         <FuncDesc>The actual start date for the activity is the date on which its
		  execution was started. ERP Enterprise fills the actual start date, when transaction hours are processed with the <GUIRef href="/baanerp/bp/tmm/bptmm1203m000" role="session">Process Hours and Expenses (bptmm1203m000)</GUIRef> session, or when a network calculation is
		  executed using the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session. You can change this date manually.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.afdt">
         <Header>
            <Title>Actual End Date</Title>
         </Header>
         <FuncDesc>The actual finish date for the activity is the date on which
		  time was last spent on or on which the activity was completed. ERP Enterprise fills the actual
		  finish date, when transaction hours are processed with the <GUIRef href="/baanerp/bp/tmm/bptmm1203m000" role="session">Process Hours and Expenses (bptmm1203m000)</GUIRef> session, or when a network calculation is
		  executed using the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session. You can change this date manually.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.ascp">
         <Header>
            <Title>Spent Critical Capacity</Title>
         </Header>
         <FuncDesc>The actual hours spent on the relevant activity. Based on the
		  hours transactions linked to the activity, ERP Enterprise automatically updates
		  this value in the <GUIRef href="/baanerp/bp/tmm/bptmm1203m000" role="session">Process Hours and Expenses (bptmm1203m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs400.pctc">
         <Header>
            <Title>Percentage Completed</Title>
         </Header>
         <FuncDesc>The percentage completed shows the activity's progress.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Because of the
			 non-linear distribution of capacity-requirements, the percentage completed is
			 not related to the lead-time but to the global capacity-requirements. If you
			 choose an automatic calculation of the percentage completed, this percentage is
			 determined on the basis of the global capacity-requirements and the actual
			 hours spent.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tipcs400.aupc">
         <Header>
            <Title>Automatic Update</Title>
         </Header>
         <FuncDesc>This field indicates whether the percentage completed must be
		  automatically determined using either the <GUIRef href="/baanerp/bp/tmm/bptmm1203m000" role="session">Process Hours and Expenses (bptmm1203m000)</GUIRef> session when transaction hours are processed,
		  or the <GUIRef href="/baanerp/ti/pcs/tipcs4210m000" role="session">Generate Network Planning (tipcs4210m000)</GUIRef> session when a network calculation is
		  executed for the project.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>