<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ts/acm/tsacm1601m100" xml:lang="en">
   <Header>
      <Title>Master Routing - Lines (tsacm1601m100)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to maintain and create <Link href="/baanerp/ts/glossary/glossary#000388" role="glossary">master routings</Link>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <List>
            <ListTitle>Master routing lines</ListTitle>
            <ListIntro>The lines on the tabs refer to the following sessions:</ListIntro>
            <ListItem>Operations: The lines on the operations tab refer to the <Link href="/baanerp/ts/acm/tsacm2100m100" role="session">Operations (tsacm2100m100)</Link> session. Double-click the operations for more
			 detailed information.</ListItem>
            <ListItem>Routing Options: The
			 lines on the routing options tab refer to the <Link href="/baanerp/ts/acm/tsacm1101m200" role="session">Routing Options (tsacm1101m200)</Link> session. Double-click the routing
			 options for more detailed information.</ListItem>
            <ListItem>Routing Matrix: The lines on the routing matrix tab refer to
			 the <Link href="/baanerp/ts/acm/tsacm2800m000" role="session">Routing Matrix (tsacm2800m000)</Link> session. Double-click the routing matrix for more
			 detailed information.</ListItem>
         </List>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tsacm101.cact">
         <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="tsacm101.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm101.sear">
         <Header>
            <Title>Search Argument</Title>
         </Header>
         <FuncDesc>An alternative form of a description used for convenience
		during searching. A search key is usually an abbreviation, an acronym, or a
		mnemonic alternative to a full description.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm101.actu">
         <Header>
            <Title>Activity Use</Title>
         </Header>
         <FuncDesc>The reference activity can be used for either of the following
		  reasons: Field Service: The reference activity can be used only for Field
		  Service usage. Depot Repair: The reference activity can be used only for Depot
		  Repair usage. General: The reference activity is not restricted to any
		  particular usage and can be used generally. This activity can be used for Field
		  Service and/or depot repair.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm101.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#000001" role="glossary">item</Link> for which the master
		  routing is defined.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="parent.item.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm101.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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Functional elements
			 can only be defined if the <GUIRef href="/baanerp/ts/mdm/tsmdm0100m000#tsmdm000.feyn" role="manual">Functional Elements Active</GUIRef> check box in the <GUIRef href="/baanerp/ts/mdm/tsmdm0100m000" role="session">General Service Parameters (tsmdm0100m000)</GUIRef> session is selected.</Paragraph>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ts/onlinemanual/000324" role="manual">To use functional elements</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="felm.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm101.actg">
         <Header>
            <Title>Activity Group</Title>
         </Header>
         <FuncDesc>A group of reference activities with similar characteristics.
		For example, the Cleaning reference activity group or the Inspection reference
		activity group.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm010.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm101.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#000001" role="glossary">item</Link> for which the master
		  routing is defined.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="parent.item.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm101.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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Functional elements
			 can only be defined if the <GUIRef href="/baanerp/ts/mdm/tsmdm0100m000#tsmdm000.feyn" role="manual">Functional Elements Active</GUIRef> check box in the <GUIRef href="/baanerp/ts/mdm/tsmdm0100m000" role="session">General Service Parameters (tsmdm0100m000)</GUIRef> session is selected.</Paragraph>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ts/onlinemanual/000324" role="manual">To use functional elements</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="felm.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm101.cwoc">
         <Header>
            <Title>Service Department</Title>
         </Header>
         <FuncDesc>The department that is responsible for the execution of a work
		order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs065.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm101.bfbp">
         <Header>
            <Title>Buy-from BP</Title>
         </Header>
         <FuncDesc>The business partner from whom you order goods or services;
		this usually represents a supplier's sales department. The definition includes
		the default price and discount agreements, purchase-order defaults, delivery
		terms, and the related ship-from and invoice-from business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="buy.from.name">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tsacm101.sitm">
         <Header>
            <Title>Service/Cost Item</Title>
         </Header>
         <FuncDesc> 
            <Link href="/baanerp/ts/glossary/glossary#000014" role="glossary">service item</Link> or <Link href="/baanerp/tc/glossary/glossary#000059" role="glossary">cost item</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcibd001.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>