<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/bp/tmm/bptmm1111m400" xml:lang="en">
   <Header>
      <Title>Project Approval (bptmm1111m400)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view or approve project
		  hours and expenses for a specific period. Together with the project hours, the
		  labor rate and its origin are shown.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>Use the commands on the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu on the <GUIRef href="/baanerp/bp/domains/mdm.session#proj.hrs" role="option">Project Hours</GUIRef> tab to view more details.</Paragraph>
         <Paragraph>For a given combination of rate code, origin and actual cost
		  and sales rate, you can consider to change the source for the rate to be used
		  when a transaction is processed.</Paragraph>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <Paragraph>Based on the origin of an hours line, business partner rate
			 code xxx will be used for a specific hours transaction. You can add a rate at
			 project level to ensure this more detailed level will be used.</Paragraph>
         </ExampleSection>
      </GeneralSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>You can only see the hours and expenses related to the
		  projects to which you are authorized via the Approval Authorizations
		  (bpmdm0111m000) session.</Paragraph>
      </Note>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="approver">
         <Header>
            <Title>Approver</Title>
         </Header>
         <FuncDesc>The name of the user logged on.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bptmm111.year">
         <Header>
            <Title>Year/Period</Title>
         </Header>
         <FuncDesc>The year for which you want to view or approve hours and
		  expenses.</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="bptmm111.peri" OtherIDs="peri.dsca">
         <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="form.peri.stdt">
         <Header>
            <Title>Registration/Start Date</Title>
         </Header>
         <FuncDesc>The project start date.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="form.peri.endt">
         <Header>
            <Title>End Date</Title>
         </Header>
         <FuncDesc>The project end date.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="include.processed">
         <Header>
            <Title>Include Processed</Title>
         </Header>
         <FuncDesc>Use this command to also display hours and expenses that were
		  already processed.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="approve.all">
         <Header>
            <Title>Approve All</Title>
         </Header>
         <FuncDesc>Approves all hours and expenses for the specific period.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="unapprove.all">
         <Header>
            <Title>Unapprove All</Title>
         </Header>
         <FuncDesc>Reverses an approval action.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>