<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ts/acm/tsacm2100m100" xml:lang="en">
   <Header>
      <Title>Master Routing - Operations (tsacm2100m100)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to define <Link href="/baanerp/ts/glossary/glossary#000404" role="glossary">operations</Link> for the selected <Link href="/baanerp/ts/glossary/glossary#000388" role="glossary">master routing</Link>. These
		  operations will then be available for the <Link href="/baanerp/ts/glossary/glossary#000387" role="glossary">routing options</Link> that can be
		  defined in the <GUIRef href="/baanerp/ts/acm/tsacm1101m200" role="session">Master Routing - Routing Options (tsacm1101m200)</GUIRef> session.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If you have started
			 this session by zooming, you can only find and select a record.</Paragraph>
         </Note>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/ts/onlinemanual/000325" role="manual">Master routings and routing options</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tsacm200.pact">
         <Header>
            <Title>Master Routing</Title>
         </Header>
         <FuncDesc>A set of operations that can be carried out. The reference
		activities based on which operations are added to a master routing, must have
		the same characteristics, such as item, functional element, and service
		department.</FuncDesc>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <Paragraph>All the inspections, tests, cleaning activities, assembly
		  activities, disassembly activities, and repair activities that you can carry
		  out on an engine.</Paragraph>
         </ExampleSection>
      </FieldHelp>
      <FieldHelp ID="parent.desc">
         <Header>
            <Title>Master Routing</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ts/glossary/glossary#000388" role="glossary">master routing</Link>'s
		  description.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm200.posi">
         <Header>
            <Title>Position</Title>
         </Header>
         <FuncDesc>The number that is used to enable master routings to have
		  multiple operations.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm200.vers">
         <Header>
            <Title>/</Title>
         </Header>
         <FuncDesc>The version number of the operation. This number is used to
		  keep track of user changes.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm200.seqn">
         <Header>
            <Title>Sequence Number</Title>
         </Header>
         <FuncDesc>A unique number that defines the way operations of a master
		  routing are ordered.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm200.cact">
         <Header>
            <Title>Reference Activity</Title>
         </Header>
         <FuncDesc>The code that identifies the <Link href="/baanerp/ts/glossary/glossary#000405" role="glossary">reference activity</Link> on which
		  the operation is based.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ts/onlinemanual/000319" role="manual">To use reference activities</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="child.desc">
         <Header>
            <Title>Reference Activity</Title>
         </Header>
         <FuncDesc>The description of the <Link href="/baanerp/ts/glossary/glossary#000405" role="glossary">reference activity</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="parent.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>In LN,
		the raw materials, subassemblies, finished products, and tools that can be
		purchased, stored, manufactured, sold, and so on.</FuncDesc>
         <SimpleSection>
            <Paragraph>An item can also represent a set of items handled as one
		  (kit), or exist in multiple product variants.</Paragraph>
            <List>
               <ListIntro>You can also define nonphysical items, which are not held
			 in inventory but can be used to post costs or to invoice services to customers.
			 Examples of nonphysical items:</ListIntro>
               <ListItem>Cost items (for example, electricity)</ListItem>
               <ListItem>Service items</ListItem>
               <ListItem>Subcontracting services</ListItem>
               <ListItem>List items (menus/options)</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="parent.item.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#000001" role="glossary">item</Link> description.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="parent.felm">
         <Header>
            <Title>Functional Element</Title>
         </Header>
         <FuncDesc>A grouping of exchangeable items with identical functions.
		Functional elements can be used in item breakdowns, physical breakdowns, and
		reference activities.</FuncDesc>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <Paragraph>When a maintenance activity is defined for a configuration, a
		  functional element can be specified. This way, the activity applies to all
		  items covered by that functional element, and multiple, identical reference
		  activities for similar items are avoided.</Paragraph>
         </ExampleSection>
      </FieldHelp>
      <FieldHelp ID="parent.felm.desc">
         <Header>
            <Title>Functional Element</Title>
         </Header>
         <FuncDesc>The description of the <Link href="/baanerp/ts/glossary/glossary#000350" role="glossary">functional element</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm200.sutm">
         <Header>
            <Title>Setup Time</Title>
         </Header>
         <FuncDesc>The time required for setting up or changing over a machine
		before you start running the machine. Setup time can be long, for example, if
		you change over from using black paint to using white paint. Setup time can be
		short, for example, if you change over from using white paint to using yellow
		paint. The setup time must indicate an average of all possible setup times.</FuncDesc>
         <SimpleSection>
            <Paragraph>This time is
			 interpreted as labor time.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tsmdm000.untd">
         <Header>
            <Title>Setup Time</Title>
         </Header>
         <FuncDesc>The time duration unit that is defined in the <GUIRef href="/baanerp/ts/mdm/tsmdm0100m000" role="session">General Service Parameters (tsmdm0100m000)</GUIRef> session.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm200.lrtm">
         <Header>
            <Title>Labor Run Time</Title>
         </Header>
         <FuncDesc>The total time that is required for all employees involved to
		  carry out the activity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm200.mrtm">
         <Header>
            <Title>Machine Run Time</Title>
         </Header>
         <FuncDesc>The time that is required for the machine to carry out the
		  activity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm200.eftm">
         <Header>
            <Title>Effective Time</Title>
         </Header>
         <FuncDesc>The first day on which a record or a setting is valid. The
		effective date often includes the effective time.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm200.extm">
         <Header>
            <Title>Expiry Time</Title>
         </Header>
         <FuncDesc>The last date on which a record or a setting is valid. The
		expiry date often includes the expiry time.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If the expiry date
			 is in the past, you cannot modify this operation.</Paragraph>
         </Note>
      </FieldHelp>
   </Fields>
</Session>