<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/bp/tmm/bptmm1100m000" xml:lang="en">
   <Header>
      <Title>Hours and Expenses by Employee Overview (bptmm1100m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view <Link href="/baanerp/bp/glossary/glossary#000313" role="glossary">hours transactions</Link>. To maintain hours for a task by
		  employee or team, on the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu, choose the appropriate <Link href="/baanerp/bp/glossary/glossary#000324" role="glossary">transaction type</Link>.</Paragraph>
      </AimSection>
      <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/bp/onlinemanual/000303" role="manual">Working time schedules</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="bptmm100.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="bptmm100.emno">
         <Header>
            <Title>Employee</Title>
         </Header>
         <FuncDesc>The employee's code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bpmdm000.defu">
         <Header>
            <Title>Total</Title>
         </Header>
         <FuncDesc>The unit in which regular time and overtime is expressed.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Overtime is usually booked in hours.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="nhrs">
         <Header>
            <Title>Total</Title>
         </Header>
         <FuncDesc>The regular time accumulated for this period.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ohrs">
         <Header>
            <Title>Total</Title>
         </Header>
         <FuncDesc>The overtime hours accumulated for this period.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bpmdm001.hwem">
         <Header>
            <Title>Employment</Title>
         </Header>
         <FuncDesc>The number of regular hours that an employee works per defined
		period.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bptmm100.year">
         <Header>
            <Title>Year/Period</Title>
         </Header>
         <FuncDesc>The year for which the hours were registered.</FuncDesc>
         <SimpleSection>
            <Paragraph>The year and the <Link href="/baanerp/tc/glossary/glossary#PeriodCode_tc" role="glossary">period code</Link> identify
			 a unique period.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="bptmm100.peri">
         <Header>
            <Title>Period</Title>
         </Header>
         <FuncDesc>The identification of a period table. The different periods of
		a year, including the period number, start date and end date are linked to the
		period-table code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcccp070.stdt">
         <Header>
            <Title>Start Date</Title>
         </Header>
         <FuncDesc>Start date of the period.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcccp070.endt">
         <Header>
            <Title>End Date</Title>
         </Header>
         <FuncDesc>End date of the period.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="t110.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="t110.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="t110.swct">
         <Header>
            <Title>Cost Type</Title>
         </Header>
         <FuncDesc>If you entered labor time, the cost type is <GUIRef href="/baanerp/bp/domains/mdm.swct#labor" role="option">Labor</GUIRef>.
		  If you entered expenses, it can be either <GUIRef href="/baanerp/bp/domains/mdm.swct#labor" role="option">Labor</GUIRef> or <GUIRef href="/baanerp/bp/domains/mdm.swct#indirect" role="option">Sundry Costs</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="t110.cpcp">
         <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="t120.orno">
         <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="t120.opno">
         <Header>
            <Title>Operation</Title>
         </Header>
         <FuncDesc>A step or a series of steps performed by an employee or a
		machine.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="t120.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="bptmm100.perc">
         <Header>
            <Title>Percentage Completed</Title>
         </Header>
         <FuncDesc>If the <Link href="/baanerp/bp/glossary/glossary#000324" role="glossary">transaction type</Link> is <GUIRef href="/baanerp/bp/domains/tmm.tran#prod.order" role="option">Production Order</GUIRef>, this field is available. The default value is calculated based
		  on the estimated hours present for the operation.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="t130.orno">
         <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="t130.acln">
         <Header>
            <Title>Activity Line</Title>
         </Header>
         <FuncDesc>Activity line number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="t130.lbln">
         <Header>
            <Title>Labor Line</Title>
         </Header>
         <FuncDesc>The labor line on which the employee registers hours.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="t130.cpcp">
         <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="t140.orno">
         <Header>
            <Title>Work Order</Title>
         </Header>
         <FuncDesc>A schedule of maintenance activities.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="t140.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="t140.cpcp">
         <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="t150.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="t150.cwoc">
         <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="t150.cpcp">
         <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="bptmm100.hrdv">
         <Header>
            <Title>Hours Distribution Done</Title>
         </Header>
         <FuncDesc>If this check box is selected, the hours were
		  distributed among the team members.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bptmm100.stup">
         <Header>
            <Title>Setup Time</Title>
         </Header>
         <FuncDesc>If this check box is selected, the entered labor or
		  machine time is <Link href="/baanerp/ti/glossary/glossary#000363" role="glossary">setup time</Link>, otherwise the entered labor or machine time is run time.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This field must be filled if the <Link href="/baanerp/bp/glossary/glossary#000324" role="glossary">transaction type</Link> is <GUIRef href="/baanerp/bp/domains/tmm.tran#prod.order" role="option">Production Order</GUIRef>.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="bptmm100.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="t120.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="bptmm100.htst">
         <Header>
            <Title>Transaction Status</Title>
         </Header>
         <FuncDesc>If the <Link href="/baanerp/bp/glossary/glossary#000324" role="glossary">transaction type</Link> is <GUIRef href="/baanerp/bp/domains/tmm.type#prod.order" role="option">Production</GUIRef>, <GUIRef href="/baanerp/bp/domains/tmm.type#assembly" role="option">Assembly</GUIRef> or <GUIRef href="/baanerp/bp/domains/tmm.type#pcs.project" role="option">Project (PCS)</GUIRef>, the transaction status can be one of the following:</FuncDesc>
         <SimpleSection>
            <List>
               <ListItemHead>
                  <GUIRef href="/baanerp/tc/domains/htst#active" role="option">Active</GUIRef>
               </ListItemHead>
               <ListItem>The task's start date was entered.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/tc/domains/htst#interrupted" role="option">Interrupted</GUIRef>
               </ListItemHead>
               <ListItem>The task's hours registration was suspended.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/tc/domains/htst#closed" role="option">Closed</GUIRef>
               </ListItemHead>
               <ListItem>The task's end date was entered.</ListItem>
            </List>
            <Paragraph>See also <Link href="/baanerp/tc/domains/htst" role="domain">Hours Transaction Status</Link>.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>For all other transaction types, the status is not
			 applicable and only <GUIRef href="/baanerp/tc/domains/htst#closed" role="option">Closed</GUIRef> will be displayed.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="bptmm100.stdt">
         <Header>
            <Title>Registration/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="bptmm100.endt">
         <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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This date is only entered if you use <Link href="/baanerp/bp/glossary/glossary#000326" role="glossary">working time schedules</Link>.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="bptmm100.cuni">
         <Header>
            <Title>Time Unit</Title>
         </Header>
         <FuncDesc>The time unit in which the labor time and machine time is
		  expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bptmm100.hrea">
         <Header>
            <Title>Labor Time</Title>
         </Header>
         <FuncDesc>The amount of time spent by an employee on a task or
		activity.</FuncDesc>
         <SimpleSection>
            <Paragraph>ERP Enterprise enters the difference between the start date and end date as a default value.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If you enter the actual time and the start date in the <GUIRef href="/baanerp/bp/tmm/bptmm1100m000" role="session">Hours and Expenses by Employee Overview (bptmm1100m000)</GUIRef> session, ERP Enterprise automatically
			 calculates the end date.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="ccur">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>The currency in which expenses are entered.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="amnt">
         <Header>
            <Title>Expense Amount</Title>
         </Header>
         <FuncDesc>Amount spent on a project, which will be accounted as sundry.
		  If you enter expenses, the costs can be booked on either the <GUIRef href="/baanerp/bp/domains/mdm.swct#labor" role="option">Labor</GUIRef> or
		  the <GUIRef href="/baanerp/bp/domains/mdm.swct#indirect" role="option">Sundry Costs</GUIRef> cost type.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro>When expenses are processed, the following
				happens:</ListIntro>
               <ListItem>Project expenses are booked to <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>, then to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</ListItem>
               <ListItem>General expenses are booked to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> straightaway.</ListItem>
            </List>
         </Note>
      </FieldHelp>
      <FieldHelp ID="bptmm100.chlt">
         <Header>
            <Title>Labor Type</Title>
         </Header>
         <FuncDesc>Labor can be entered in overtime and regular time.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ovrt">
         <Header>
            <Title>Overtime</Title>
         </Header>
         <FuncDesc>If this check box is selected, the entered labor type
		  is <GUIRef href="/baanerp/bp/tmm/bptmm1100m000#ovrt" role="manual">Overtime</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bptmm100.type">
         <Header>
            <Title>Transaction Type</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="txta.yn">
         <Header>
            <Title>Text</Title>
         </Header>
         <FuncDesc>If this check box is selected, a text is present.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bpmdm050.ckot">
         <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="bptmm100.cnfd">
         <Header>
            <Title>Approved</Title>
         </Header>
         <FuncDesc>If this check box is selected, you either approved the
		  hours in the overview session via the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu <GUIRef href="/baanerp/bp/tmm/bptmm1111m000#ibptmm1110.approve" role="command">Approve Hours</GUIRef> command, or you globally approved the
		  hours when you finished entering all lines.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bptmm100.proc">
         <Header>
            <Title>Processed</Title>
         </Header>
         <FuncDesc>If this check box is selected, the hours were
		  processed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="t170.mcno">
         <Header>
            <Title>Machine</Title>
         </Header>
         <FuncDesc>In ERP Enterprise,
		a mechanical object on which operations can be carried out to produce items.</FuncDesc>
         <SimpleSection>
            <Paragraph>Machines are linked to operation rates. The operation rate
		  and the labor rate together form the basis for the actual costing of production
		  orders.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="t160.orno">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>An order to produce a specified quantity of an item on a
		specified delivery date.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="t160.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="t170.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="t120.mcno">
         <Header>
            <Title>Machine</Title>
         </Header>
         <FuncDesc>In ERP Enterprise,
		a mechanical object on which operations can be carried out to produce items.</FuncDesc>
         <SimpleSection>
            <Paragraph>Machines are linked to operation rates. The operation rate
		  and the labor rate together form the basis for the actual costing of production
		  orders.</Paragraph>
         </SimpleSection>
      </FieldHelp>
   </Fields>
</Session>