<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ts/ctm/tsctm1135m300" xml:lang="en">
   <Header>
      <Title>Contract Helpdesk Terms (tsctm1135m300)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to maintain the selected
		  help desk <Link href="/baanerp/ts/glossary/glossary#000056" role="glossary">cost-term</Link> that is associated
		  with the coverage term that is selected from the <Link href="/baanerp/ts/glossary/glossary#ServicContra_ts" role="glossary">service contract</Link>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If you must change
			 the terms, after a certain number of calls, for example, then a new coverage
			 term must be created.</Paragraph>
         </Note>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="appl.header">
         <Header>
            <Title>Service Contract</Title>
         </Header>
         <FuncDesc>A sales agreement between a service organization and a customer
		for a specific period, that states the configurations (clusters or serialized
		items) to be maintained, the coverage terms, and the agreed price.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.cfln">
         <Header>
            <Title>Configuration Line</Title>
         </Header>
         <FuncDesc>The line number identifying the <Link href="/baanerp/ts/glossary/glossary#Configuratio_ts" role="glossary">configuration</Link> for which the total amounts
		  apply.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm110.cltp">
         <Header>
            <Title>Line Type</Title>
         </Header>
         <FuncDesc>The classification of the line. The line type can either be
		  Normal, Total or Calculation. A total line is a sum total of calculation lines.
		  A Calculation line is a partial configuration and contributes to the overall
		  configuration of the type Total line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="change.numb">
         <Header>
            <Title>Contract Change</Title>
         </Header>
         <FuncDesc>Following are the types of contract changes:</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>
                  <GUIRef href="" role="manual">Renewal</GUIRef>: The option allows you to extend the
			 contract period beyond its current validity duration.</ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Incidental Changes</GUIRef>: The option allows you to
			 implement changes to an existing contract. Changes such as addition/deletion of
			 one or more configuration lines, changes to price and discounts, and so on are
			 categorized as incidental changes.</ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Indexation</GUIRef>: The option allows you to change
			 the contract price based on the changes in the value of consumer price
			 index.</ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Renewal with Indexation</GUIRef>: The option allows
			 you to perform indexation and renewal at the same time.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="change.type">
         <Header>
            <Title>Contract Change</Title>
         </Header>
         <FuncDesc>The description of the contract change.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.cctp">
         <Header>
            <Title>Coverage Type</Title>
         </Header>
         <FuncDesc>A financial classification that indicates to what extent work
		is covered under warranty or contract, and what part of the activities can be
		charged.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.nrbt">
         <Header>
            <Title>Coverage Term</Title>
         </Header>
         <FuncDesc>For a service type / term type combination, this is a unique
		sequence number.</FuncDesc>
         <SimpleSection>
            <Paragraph> Default value of step size: 10</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The default value can be changed if required.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tsctm110.clst">
         <Header>
            <Title>Cluster</Title>
         </Header>
         <FuncDesc>A set of serialized items that have the same location and are
		owned by the same business partner. Grouping serialized items into a cluster
		enables you to maintain them collectively.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cluster.desc">
         <Header>
            <Title>Cluster</Title>
         </Header>
         <FuncDesc>The description of the cluster.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm110.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>A standard maintenance item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm110.sern">
         <Header>
            <Title>Serial Number</Title>
         </Header>
         <FuncDesc>A number that, together with the item code or manufacturer part
		number, uniquely identifies a component, an item, a machine, or an
		installation.</FuncDesc>
         <SimpleSection>
            <Paragraph>This serial number is usually shown together with the
		  manufacturer part number and other identification data on an identification
		  plate that is attached to the item.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="item.desc">
         <Header>
            <Title>Item Description</Title>
         </Header>
         <FuncDesc>The description of the item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.cseq">
         <Header>
            <Title>Helpdesk Term</Title>
         </Header>
         <FuncDesc>The number used to identify the cost term of the coverage term.
		The default step size is 10.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.nrun">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description of the contract helpdesk.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.nrcl">
         <Header>
            <Title>Covered calls</Title>
         </Header>
         <FuncDesc>The number of calls that are covered by the contract or
		warranty.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.nrun">
         <Header>
            <Title>Covered Call Units</Title>
         </Header>
         <FuncDesc>The number of call units that are covered by the contract or
		warranty.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.cinv">
         <Header>
            <Title>Invoice Interval</Title>
         </Header>
         <FuncDesc>The invoice interval's code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.cuni">
         <Header>
            <Title>Time Unit</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Units_tc" role="glossary">unit</Link> in which time is quantified.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.clrt">
         <Header>
            <Title>Labor Rate</Title>
         </Header>
         <FuncDesc>The labor rate code, defined in the <GUIRef href="/baanerp/tc/ppl/tcppl0190m000" role="session">Labor Rate Codes (tcppl0190m000)</GUIRef> session in <GUIRef href="/baanerp/bp" role="package">People</GUIRef>. A sales rate and cost rate can be specified in
		this labor rate code.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>You can assign labor rates on a wider scale to, for
			 example,</ListIntro>
               <ListItem>A service department, for all work done by the service
			 department.</ListItem>
               <ListItem>A cluster, for all work carried out on the cluster.</ListItem>
            </List>
            <List>
               <ListIntro>In the <GUIRef href="/baanerp/ts/soc/tssoc0100m000" role="session">Service Order Parameters (tssoc0100m000)</GUIRef> session, default labor rate search paths
			 can be set for the following:</ListIntro>
               <ListItem>Estimated sales rate</ListItem>
               <ListItem>Estimated cost rate</ListItem>
               <ListItem>Actual sales rate</ListItem>
               <ListItem>Actual cost rate</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tcppl090.desc">
         <Header>
            <Title>Labor Rate</Title>
         </Header>
         <FuncDesc>The description of the labor rate.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.wrac">
         <Header>
            <Title>Cost Rate</Title>
         </Header>
         <FuncDesc>The price, budgeted or actual, per reference unit. For example,
		the price of a machine per hour.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.wras">
         <Header>
            <Title>Sales Rate</Title>
         </Header>
         <FuncDesc>The price or rate of cost objects, elements or activities, at
		which you sell, that are used for your project.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.camt">
         <Header>
            <Title>Cost Amount</Title>
         </Header>
         <FuncDesc>The sum of the cost amounts of all coverage terms that are
		associated with the indicated service type or term type.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The amount is expressed in the home currency.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="home.ccur">
         <Header>
            <Title>Cost Rate</Title>
         </Header>
         <FuncDesc>Your company's <Link href="/baanerp/tc/glossary/glossary#000017" role="glossary">reference currency</Link>, which is
		  defined in the <GUIRef href="/baanerp/tc/emm/tcemm1170m000" role="session">Companies (tcemm1170m000)</GUIRef> session.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ts/onlinemanual/000050" role="manual">To use currencies</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tsctm135.amnt">
         <Header>
            <Title>Sales Amount</Title>
         </Header>
         <FuncDesc>The sum of the sales amounts of all coverage terms that are
		associated with the indicated service type or term type.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="home.ccur">
         <Header>
            <Title>Sales Amount</Title>
         </Header>
         <FuncDesc>Your company's <Link href="/baanerp/tc/glossary/glossary#000017" role="glossary">reference currency</Link>, which is
		  defined in the <GUIRef href="/baanerp/tc/emm/tcemm1170m000" role="session">Companies (tcemm1170m000)</GUIRef> session.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ts/onlinemanual/000050" role="manual">To use currencies</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="txta.yn">
         <Header>
            <Title>Text</Title>
         </Header>
         <FuncDesc> 
            <Link href="/baanerp/ts/onlinemanual/000069" role="manual">Text (additional)</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.crtc">
         <Header>
            <Title>Response Time</Title>
         </Header>
         <FuncDesc>A response time defines, from the time a call is registered,
		the period of time within which: The service provider must react to the call; A
		solution to the call's problem must be started; A solution to the call's
		problem must be finished.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsclm020.desc">
         <Header>
            <Title>Response Time</Title>
         </Header>
         <FuncDesc>The description of the response time.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.rstu">
         <Header>
            <Title>Response Time Unit</Title>
         </Header>
         <FuncDesc>The unit used to quantify the response time.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs001.dsca">
         <Header>
            <Title>Time Unit</Title>
         </Header>
         <FuncDesc>The description of the response time unit.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.ccal">
         <Header>
            <Title>Coverage Time Calendar</Title>
         </Header>
         <FuncDesc>The calender used to calculate the coverage time applicable for
		  the helpdesk call.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcccp010.dsca">
         <Header>
            <Title>Coverage Time Calendar</Title>
         </Header>
         <FuncDesc>The description of the coverage time calender.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.rctt">
         <Header>
            <Title>Reaction Period</Title>
         </Header>
         <FuncDesc>The time taken to react to the helpdesk call.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.rsin">
         <Header>
            <Title>Resp. Time Defn. Method</Title>
         </Header>
         <FuncDesc>The mthod used to calculate the response time. You can either
		  use time units or business days to calculate.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.slst">
         <Header>
            <Title>Solution Start Period</Title>
         </Header>
         <FuncDesc>The time by which the support engineer must start solving the
		call.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.bsls">
         <Header>
            <Title>Solution Start BD Counter</Title>
         </Header>
         <FuncDesc>If Response Time Definition method is set to Business days,then
		  the solution start business days counter must be entered. The Solution start
		  date is measured in terms of Business days.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.slfn">
         <Header>
            <Title>Solution Finish Period</Title>
         </Header>
         <FuncDesc>The time by which the support engineer must finish solving the
		call.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.bsfn">
         <Header>
            <Title>Solution Finish BD Counter</Title>
         </Header>
         <FuncDesc>If Response Time Definition method is set to Business days,then
		  the solution finish business days counter must be entered. The Solution Finish
		  date is measured in terms of Business days.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsctm135.spco">
         <Header>
            <Title>Spent Costs</Title>
         </Header>
         <FuncDesc>The sum of costs due to service activities that have been
		financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>, expressed in the home currency.</FuncDesc>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <List>
               <ListItem>Service orders</ListItem>
               <ListItem>Traveling costs</ListItem>
            </List>
         </ExampleSection>
      </FieldHelp>
      <FieldHelp ID="tsctm135.alco">
         <Header>
            <Title>Allocated Costs</Title>
         </Header>
         <FuncDesc>The sum of costs due to service activities that have not been
		financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>, expressed in the home currency.</FuncDesc>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <List>
               <ListItem>Service orders</ListItem>
               <ListItem>Traveling costs</ListItem>
            </List>
         </ExampleSection>
      </FieldHelp>
      <FieldHelp ID="tsctm135.spsa">
         <Header>
            <Title>Spent Sales</Title>
         </Header>
         <FuncDesc>The sum of sales amounts due to service activities that have
		been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>, expressed in the
		currency chosen in the contract header.</FuncDesc>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <List>
               <ListItem>Service orders</ListItem>
               <ListItem>Helpdesk calls</ListItem>
            </List>
         </ExampleSection>
      </FieldHelp>
      <FieldHelp ID="tsctm135.alsa">
         <Header>
            <Title>Allocated Sales</Title>
         </Header>
         <FuncDesc>The sum of the sales amounts due to service activities that
		have not been financially approved in <GUIRef href="/baanerp/ts/soc" role="module">Service Order Control</GUIRef>,
		expressed in the home currency.</FuncDesc>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <List>
               <ListItem>Service orders</ListItem>
               <ListItem>Traveling costs</ListItem>
            </List>
         </ExampleSection>
      </FieldHelp>
   </Fields>
</Session>