<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/trp/titrp0513m000" xml:lang="en">
   <Header>
      <Title>Availability Planning (titrp0513m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to list orders that make
		  use of a critical tool. The orders are sorted on the basis of the start date of
		  the order that is displayed in the <GUIRef href="/baanerp/ti/trp/titrp0513m000#titrp013.date" role="manual">Start Date</GUIRef> field. For every order, the tool
		  requirements are indicated.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/ti/onlinemanual/000012" role="manual">Tools planning and tracking</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/ti/onlinemanual/000014" role="manual">Tool requirements planning</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="titrp013.tltp">
         <Header>
            <Title>Tool Type</Title>
         </Header>
         <FuncDesc>The tool type is the first level that is used to identify the
		tool in the coding system for tools.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Some examples of tool types are:</ListIntro>
               <ListItem>Hammer</ListItem>
               <ListItem>Screwdriver</ListItem>
               <ListItem>Wheelbarrows</ListItem>
            </List>
            <Paragraph>Hammer 1, screwdriver 2 and wheelbarrow 3 are examples of
		  tool types in combination with a tool serial number, and represent unique
		  tools.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="titrp013.date">
         <Header>
            <Title>Start Date</Title>
         </Header>
         <FuncDesc>The start date of, for example, the operation or activity for
		  which the tool is used.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="titrp013.endt">
         <Header>
            <Title>End Date</Title>
         </Header>
         <FuncDesc>The end date of, for example, the operation or activity for
		  which the tool is used.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="titrp013.koor">
         <Header>
            <Title>Kind of Order</Title>
         </Header>
         <FuncDesc>The order type for which the tools requirements are displayed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="titrp013.orno">
         <Header>
            <Title>Order Number</Title>
         </Header>
         <FuncDesc>The number of the order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="titrp013.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="titrp013.lino">
         <Header>
            <Title>Line Number</Title>
         </Header>
         <FuncDesc>The line number of the service order for which the time phased
		  availability of tools is performed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="titrp013.acln">
         <Header>
            <Title>Activity Line</Title>
         </Header>
         <FuncDesc>The activity line on the service order for which the tool is
		  issued.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="titrp013.srno">
         <Header>
            <Title>Sequence Number</Title>
         </Header>
         <FuncDesc>The number that identifies a data record or a step in a
		sequence of activities. Sequence numbers are used in many contexts. Usually LN generates the
		sequence number for the next item or step. Depending on the context, you can
		overwrite this number. You can sometimes influence the numbering by setting the
		corresponding parameters.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="titrp013.tnum">
         <Header>
            <Title>Tool Serial Number</Title>
         </Header>
         <FuncDesc>A number to identify a tool. The combination of a tool type,
		for example, hammer, and a tool serial number, for example, 1, results in a
		unique identification of a tool in LN.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="titrp013.rtlu">
         <Header>
            <Title>Required Tool Usage</Title>
         </Header>
         <FuncDesc>The required tool usages are expressed in the number of times
		  that the tool is used, or in the amount of hours that the tool is used. The
		  quantity of required usages are deducted from value in the <GUIRef href="/baanerp/ti/trp/titrp0101m000#titrp001.tllf" role="manual">Tool's Life</GUIRef> field.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If the <GUIRef href="/baanerp/ti/trp/titrp0101m000#titrp001.tlbo" role="manual">Tool's Life Based On</GUIRef> field is <GUIRef href="/baanerp/ti/domains/trp.tlbo#not.applicable" role="option">Not Applicable</GUIRef> this field is empty.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="titrp001.tlbo">
         <Header>
            <Title>Tool's Life Based On</Title>
         </Header>
         <FuncDesc>The measurement upon which the tool's life is based.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="titrp013.ostp">
         <Header>
            <Title>Operation Step</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#000365" role="glossary">operation step</Link> for which the tool is planned.</FuncDesc>
         <SimpleSection>
            <Paragraph>This field is only applicable if the <GUIRef href="/baanerp/ti/trp/titrp0513m000#titrp013.koor" role="manual">Kind of Order</GUIRef> field
			 in the current session is <GUIRef href="/baanerp/ti/domains/trp.otyp#sfc.order" role="option">SFC Production Order</GUIRef>.</Paragraph>
         </SimpleSection>
      </FieldHelp>
   </Fields>
</Session>