<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/bp/tmm/bptmm1201m000" xml:lang="en">
   <Header>
      <Title>Global Registration of Hours (bptmm1201m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to register hours for a
		  range of employees, for example, for a public holiday.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>Click <GUIRef href="/baanerp/bp/tmm/bptmm1201m000#ibpmdm0020.spec.employees" role="command">Spec. Employees</GUIRef> to use the list of specific
		  employees rather than specifying a range of employees.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>If hours are already present for an employee, ERP Enterprise generates an
				error report, depending on the <GUIRef href="/baanerp/bp/tmm/bptmm1204m000#ovlp" role="manual">Overlap Allowed</GUIRef> setting in the <GUIRef href="/baanerp/bp/tmm/bptmm1204m000" role="session">Use Assignments (bptmm1204m000)</GUIRef> session.</ListItem>
               <ListItem>If the <GUIRef href="/baanerp/bp/tmm/bptmm1201m000#ovta" role="manual">Overlapping Tasks Allowed</GUIRef> check box is selected, tasks can overlap. The employee
				must edit the overlapping hours manually.</ListItem>
               <ListItem>If, in the <GUIRef href="/baanerp/bp/mdm/bpmdm0100m000" role="session">People Parameters (bpmdm0100m000)</GUIRef> session, a <Link href="/baanerp/bp/glossary/glossary#000324" role="glossary">transaction type's</Link> 
                  <GUIRef href="/baanerp/bp/domains/mdm.proc#direct" role="option">Direct</GUIRef> check box is selected, that transaction type's data do not appear in the
				applicable session, but are automatically transferred.</ListItem>
            </List>
         </Note>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/bp/onlinemanual/000302" role="manual">
               <GUIRef href="/baanerp/bp" role="package">People</GUIRef> – overview</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/basictasks/000006" role="manual">To use From and To fields</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="sono">
         <Header>
            <Title>Service Order</Title>
         </Header>
         <FuncDesc>Orders that are used to plan, carry out, and control all repair
		and maintenance on configurations as present on customer sites or as present
		with the company.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="serl">
         <Header>
            <Title>Cost Type</Title>
         </Header>
         <FuncDesc>Categories that are used to register the type of costs. Cost
		types enable you to have a more detailed view of the source of costs.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="lbln">
         <Header>
            <Title>Labor Line</Title>
         </Header>
         <FuncDesc>The labor line number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tvln">
         <Header>
            <Title>Travel Line</Title>
         </Header>
         <FuncDesc>The travel line number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="saln">
         <Header>
            <Title>Activity Line</Title>
         </Header>
         <FuncDesc>The activity line number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="stsk">
         <Header>
            <Title>Service Task</Title>
         </Header>
         <FuncDesc>A specification of the type of work that is carried out by a
		service employee. You can use tasks to specify the labor required to carry out
		an activity. A specific labor rate can be linked to a task.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="sowc">
         <Header>
            <Title>Service Department</Title>
         </Header>
         <FuncDesc>The department that is responsible for the execution of a work
		order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="socp">
         <Header>
            <Title>Cost Component</Title>
         </Header>
         <FuncDesc>A cost component is a collection of cost objects with a certain
		characteristic. A cost component does not depend on the cost type, therefore,
		for example, a project can be monitored from another dimension. For example,
		all the costs that refer to electrical work, for example, cable and
		installation work, are visible if the applicable cost objects are linked to the
		cost component Electrical work.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="mono">
         <Header>
            <Title>Work Order</Title>
         </Header>
         <FuncDesc>A schedule of maintenance activities.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="maln">
         <Header>
            <Title>Activity Line</Title>
         </Header>
         <FuncDesc>The activity line number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="refa">
         <Header>
            <Title>Reference Activity</Title>
         </Header>
         <FuncDesc>A group activity or a single activity (directive) that is
		planned for a serialized item or Installation
		group. A list of reference activities for an item
		forms a maintenance concept.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="mowc">
         <Header>
            <Title>Service Department</Title>
         </Header>
         <FuncDesc>The department that is responsible for the execution of a work
		order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="mocp">
         <Header>
            <Title>Cost Component</Title>
         </Header>
         <FuncDesc>A cost component is a collection of cost objects with a certain
		characteristic. A cost component does not depend on the cost type, therefore,
		for example, a project can be monitored from another dimension. For example,
		all the costs that refer to electrical work, for example, cable and
		installation work, are visible if the applicable cost objects are linked to the
		cost component Electrical work.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pcsp">
         <Header>
            <Title>Project (PCS)</Title>
         </Header>
         <FuncDesc>The PCS project code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pcsa">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>Activity of the PCS project.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pcst">
         <Header>
            <Title>Task</Title>
         </Header>
         <FuncDesc>An activity to manufacture or repair an item. For example,
		sawing, drilling, or painting.</FuncDesc>
         <SimpleSection>
            <Paragraph>A task is carried out on a work center, and can be related to
		  a machine.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="pcwc">
         <Header>
            <Title>Work Center</Title>
         </Header>
         <FuncDesc>A specific production area consisting of one or more people
		and/or machines with identical capabilities, that can be considered as one unit
		for purposes of the capacity requirement planning and detailed scheduling.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pcmc">
         <Header>
            <Title>Machine</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#Machines_ti" role="glossary">machine</Link> number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="hrmp">
         <Header>
            <Title>Machine Time</Title>
         </Header>
         <FuncDesc>A department's total machine time spent on a specific order or
		a specific project in a given year and period.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cuni">
         <Header>
            <Title>Labor Time</Title>
         </Header>
         <FuncDesc>The unit that is used to specify the physical quantity time.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pono">
         <Header>
            <Title>Production Order</Title>
         </Header>
         <FuncDesc>An order to produce a specified quantity of an item on a
		specified delivery date.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="opno">
         <Header>
            <Title>Operation</Title>
         </Header>
         <FuncDesc>One of a series of steps in a routing that are carried out
		successively to produce an item.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The following data is collected during a routing operation:</ListIntro>
               <ListItem>The task. For example, sawing.</ListItem>
               <ListItem>The machine used to carry out the task (optional). For
			 example, sawing machine.</ListItem>
               <ListItem>The place where the task is carried out (work center). For
			 example, woodwork.</ListItem>
               <ListItem>The number of employees required to carry out the task.</ListItem>
            </List>
            <Paragraph>This data is used to compute order lead times, to plan
		  production orders and to calculate cost prices.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tano">
         <Header>
            <Title>Task</Title>
         </Header>
         <FuncDesc>An activity to manufacture or repair an item. For example,
		sawing, drilling, or painting.</FuncDesc>
         <SimpleSection>
            <Paragraph>A task is carried out on a work center, and can be related to
		  a machine.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="powc">
         <Header>
            <Title>Work Center</Title>
         </Header>
         <FuncDesc>A specific production area consisting of one or more people
		and/or machines with identical capabilities, that can be considered as one unit
		for purposes of the capacity requirement planning and detailed scheduling.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="mcno">
         <Header>
            <Title>Machine</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#Machines_ti" role="glossary">machine</Link> number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="hrma">
         <Header>
            <Title>Machine Time</Title>
         </Header>
         <FuncDesc>A department's total machine time spent on a specific order or
		a specific project in a given year and period.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="stup">
         <Header>
            <Title>Setup Time</Title>
         </Header>
         <FuncDesc>If this check box is selected, <Link href="/baanerp/ti/glossary/glossary#000363" role="glossary">setup time</Link> is
		  included.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="lsno">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>Production order for an assembly line station.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="hrmc">
         <Header>
            <Title>Machine Time</Title>
         </Header>
         <FuncDesc>A department's total machine time spent on a specific order or
		a specific project in a given year and period.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="lswc">
         <Header>
            <Title>Line Station</Title>
         </Header>
         <FuncDesc>A work center that is part of an assembly line. A line station
		is used in the production of FAS (final assembly schedule) items. A line
		station can have multiple positions, which enables more than one item to be
		present in one line station.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="asln">
         <Header>
            <Title>Assembly Line</Title>
         </Header>
         <FuncDesc>A set of consecutive line stations in which FAS (Final Assembly
		Schedule) items are manufactured. The items are manufactured by passing the
		items from line station to line station and by carrying out operations at each
		line station. An assembly line is subdivided into a number of line segments
		separated by buffers. An assembly line can be either a main line or a supplying
		line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>An endeavor with a specific objective to be met within the
		prescribed time and financial limitation, and that has been assigned for
		definition or execution.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cspa">
         <Header>
            <Title>Element</Title>
         </Header>
         <FuncDesc>The smallest part of an element structure. An element is used
		to define the (structure of the) work of the project, so that you can carry it
		out.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cact">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>The smallest part of the activity structure used for a
		time-scaled budget. An entity that is used to represent a part of a project in
		an activity structure.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>ERP Enterprise distinguishes these activity types:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#wbsel" role="option">WBS Element</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#cosac" role="option">Project Cost Account</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#worpa" role="option">Work Package</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#plapa" role="option">Planning Package</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#milst" role="option">Milestone</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="cstl">
         <Header>
            <Title>Extension</Title>
         </Header>
         <FuncDesc>The specific agreements within or in addition to the initial
		contract. An extension falls outside the initial contract with the sold-to
		business partner. Extensions can be assigned to the bottom-up
		budget.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>ERP Enterprise distinguishes four extension types:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#additional.work" role="option">Scope Change</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#provision.entry" role="option">Provisional Amount</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#risc.settl" role="option">Fluctuation Settlement</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#quan.settl" role="option">Quantities to be Settled</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="prtk">
         <Header>
            <Title>Task</Title>
         </Header>
         <FuncDesc>A type of cost carrier for the resources used in your
		project.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>These cost objects are available:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tcre#item" role="option">Material</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tcre#task" role="option">Labor</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tcre#equipment" role="option">Equipment</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tcre#subcontract" role="option">Subcontracting</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tcre#indirect" role="option">Sundry Costs</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tcre#overhead" role="option">Overhead</GUIRef>
               </ListItem>
            </List>
            <Paragraph>Cost objects can be standard or specific for a project. The
		  cost object is related to a control code for cost controlling purposes.</Paragraph>
         </SimpleSection>
         <SimpleSection>
            <List>
               <ListIntro>If required, select the appropriate cost object from one
				of the following sessions:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tp/pdm/tppdm0511m000" role="session">Standard Labor (tppdm0511m000)</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/pdm/tppdm6511m000" role="session">Project Labor (tppdm6511m000)</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/ptc/tpptc1536m000" role="session">Control Data (Labor Lines) (tpptc1536m000)</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="prcp">
         <Header>
            <Title>Cost Component</Title>
         </Header>
         <FuncDesc>A cost component is a collection of cost objects with a certain
		characteristic. A cost component does not depend on the cost type, therefore,
		for example, a project can be monitored from another dimension. For example,
		all the costs that refer to electrical work, for example, cable and
		installation work, are visible if the applicable cost objects are linked to the
		cost component Electrical work.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="wtsc">
         <Header>
            <Title>Working Time Schedule</Title>
         </Header>
         <FuncDesc>A schedule used to define the number of working hours per day
		and distribute these hours according to different labor types. As a result,
		different labor rates can be used for regular time and overtime.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="start.date">
         <Header>
            <Title>Start Date</Title>
         </Header>
         <FuncDesc>The date on which the employee is scheduled to start working on
		a task, an activity, or an assignment.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="end.date">
         <Header>
            <Title>End Date</Title>
         </Header>
         <FuncDesc>The date on which the employee is scheduled to stop working on
		a task, an activity, or an assignment.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="nhrs">
         <Header>
            <Title>Labor Time</Title>
         </Header>
         <FuncDesc>The amount of time spent by an employee on a task or
		activity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="chlt">
         <Header>
            <Title>Labor Type</Title>
         </Header>
         <FuncDesc>The classification of work performed, and the time of day at
		which the work is performed (either normal working hours or overtime). Based on
		the kind of work and the hour type, you can use labor types to specify
		surcharges so that ERP Enterprise can
		calculate the actual labor costs in <GUIRef href="/baanerp/bp" role="package">People</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ovta">
         <Header>
            <Title>Overlapping Tasks Allowed</Title>
         </Header>
         <FuncDesc>If this check box is selected, the start and end time of different tasks can
		  overlap.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tran.type">
         <Header>
            <Title>Logistic Data</Title>
         </Header>
         <FuncDesc>The logistic entity type to which an employee's hours are
		allocated and to which the employee costs must be posted.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>In ERP Enterprise, hours can be allocated to the following transaction
			 types:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/bp/domains/tmm.tran#general" role="option">General Task</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/bp/domains/tmm.tran#project" role="option">Project</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/bp/domains/tmm.tran#pcs.project" role="option">Project (PCS)</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/bp/domains/tmm.tran#prod.order" role="option">Production Order</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/bp/domains/tmm.tran#assembly" role="option">Assembly Order</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/bp/domains/tmm.tran#serv.order" role="option">Service Order</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/bp/domains/tmm.tran#main.order" role="option">Work Order</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="gtsk">
         <Header>
            <Title>General Task</Title>
         </Header>
         <FuncDesc>A user-defined task that does not contribute or relate to the
		costs of a specific order or project.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>In ERP Enterprise, two types of general tasks exist:</ListIntro>
               <ListItemHead>
                  <GUIRef href="/baanerp/bp/domains/ckot#indirect" role="option">Indirect Task</GUIRef>
               </ListItemHead>
               <ListItem>To be used for indirect hours, such as administration and
			 general meetings, also called overhead.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/bp/domains/ckot#absence" role="option">Absence Task</GUIRef>
               </ListItemHead>
               <ListItem>To be used for absence hours, such as vacation, illness, or a
			 doctor's visit.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="gtyp">
         <Header>
            <Title>Task Type</Title>
         </Header>
         <FuncDesc>A user-defined task that does not contribute or relate to the
		costs of a specific order or project.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>In ERP Enterprise, two types of general tasks exist:</ListIntro>
               <ListItemHead>
                  <GUIRef href="/baanerp/bp/domains/ckot#indirect" role="option">Indirect Task</GUIRef>
               </ListItemHead>
               <ListItem>To be used for indirect hours, such as administration and
			 general meetings, also called overhead.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/bp/domains/ckot#absence" role="option">Absence Task</GUIRef>
               </ListItemHead>
               <ListItem>To be used for absence hours, such as vacation, illness, or a
			 doctor's visit.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="gtwc">
         <Header>
            <Title>Department</Title>
         </Header>
         <FuncDesc>A company's organizational unit that carries out a specific set
		of tasks, for example, a sales office or a purchase office. Departments are
		assigned number groups for the orders they issue. The department's enterprise
		unit determines the financial company to which the financial transactions that
		the department generates are posted.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="gtcp">
         <Header>
            <Title>Cost Component</Title>
         </Header>
         <FuncDesc>A cost component is a user-defined category for the
		classification of costs.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Cost components have the following functions:</ListIntro>
               <ListItem>To break down an item's cost price, sales price, or valuation
			 price.</ListItem>
               <ListItem>To create a comparison between the estimated production order
			 costs and the actual production order costs.</ListItem>
               <ListItem>To calculate production variances.</ListItem>
               <ListItem>To view the distribution of your costs over the various cost
			 components in the <GUIRef href="/baanerp/tf/cat" role="module">Cost Accounting</GUIRef> module.</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <List>
               <ListIntro>Cost components can be of the following cost types:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tc/domains/cref#material" role="option">Material Costs</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tc/domains/cref#operation" role="option">Operation Costs</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tc/domains/cref#chg.material" role="option">Surcharge on Material Costs</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tc/domains/cref#chg.operation" role="option">Surcharge on Operation Costs</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tc/domains/cref#transfer" role="option">WIP Transfer Costs</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tc/domains/cref#general" role="option">General Costs</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If you use <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef> (ASC), you cannot use cost components
		  of the <GUIRef href="/baanerp/tc/domains/cref#general" role="option">General Costs</GUIRef> type.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="ppl.type">
         <Header>
            <Title>Employee/Team</Title>
         </Header>
         <FuncDesc>You can either register hours for an employee or for a team.
		  You can later distribute the hours of a team among all team members through the <GUIRef href="/baanerp/bp/tmm/bptmm1220m000" role="session">Distribute Team Hours (bptmm1220m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="ibpmdm0020.spec.employees">
         <Header>
            <Title>Spec. Employees</Title>
         </Header>
         <FuncDesc>Selects all (active) employees in the <GUIRef href="/baanerp/bp/mdm/bpmdm1140m000" role="session">Specific Employees (bpmdm1140m000)</GUIRef> session. As a result, the employee range fields become
		  unavailable.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="ibpmdm0020.reset.spec.sel">
         <Header>
            <Title>Reset Selection</Title>
         </Header>
         <FuncDesc>Cancels the selection of specific employees. As a result, the
		  employee range fields become available.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="tcppl1100m000">
         <Header>
            <Title>Working Time Schedule</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/tc/ppl/tcppl1100m000" role="session">Working Time Schedule (tcppl1100m000)</GUIRef> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="ibpmdm0010.start.emno.det">
         <Header>
            <Title>Details</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/bp/mdm/bpmdm1800m000" role="session">Selection Details (bpmdm1800m000)</GUIRef> session.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>