<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/fm/foc/fmfoc1151m000" xml:lang="en">
   <Header>
      <Title>Route Plan Legs (fmfoc1151m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view and maintain <Link href="/baanerp/fm/glossary/glossary#000027" role="glossary">route plan</Link> legs.</Paragraph>
      </AimSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>Use the Maps section to view the location of the <GUIRef href="/baanerp/fm/foc/fmfoc1151m000#fmfoc151.orig" role="manual">Origin Address</GUIRef> and the <GUIRef href="/baanerp/fm/foc/fmfoc1151m000#fmfoc151.dsad" role="manual">Destination Address</GUIRef>. You must select only one record
		  at a time.</Paragraph>
      </Note>
      <GeneralSection>
         <Paragraph>Advance, main, and
		  beyond legs are used in multi-modal routes, where the pooling planning
		  algorithm is used.</Paragraph>
         <GeneralSection>
            <SectionTitle>Options on the Specific menu</SectionTitle>
            <Paragraph>On the Specific
			 menu, you can access the <GUIRef href="/baanerp/tc/com/tccom4537m000" role="session">Distance Table by City (tccom4537m000)</GUIRef> session and the <GUIRef href="/baanerp/tc/com/tccom4538m000" role="session">Distance Table by ZIP Code/Postal Code (tccom4538m000)</GUIRef> session to define the distance of
			 the <GUIRef href="/baanerp/fm/foc/fmfoc1150m000#fmfoc150.rtpn" role="manual">Route Plan</GUIRef> Leg.</Paragraph>
         </GeneralSection>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/fm/onlinemanual/000022" role="manual">The use of route plans</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="fmfoc151.rtpn">
         <Header>
            <Title>Route Plan</Title>
         </Header>
         <FuncDesc>A network of loading and unloading addresses, one of which is a
		pooling point. A route plan is usually defined for routes that involve
		multi-modal transport. A route plan consists of one or more legs. Each leg, or
		part of the route, can be handled differently depending on the specified
		transport category and transport means group.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000022" role="manual">The use of route plans</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.ltyp">
         <Header>
            <Title>Leg Type</Title>
         </Header>
         <FuncDesc>The advance leg is the first part of the route where goods are
		  picked up and transported to a pooling point, such as an airport, a train
		  station, or a port.</FuncDesc>
         <SimpleSection>
            <Paragraph>The main leg starts
			 at the pooling point and ends at the intermediate destination. At the pooling
			 point, the goods from the advance leg are loaded into an aircraft, ship, train,
			 or truck, and brought to the intermediate destination.</Paragraph>
            <Paragraph>The beyond leg spans
			 the intermediate destination and the final destination. At the intermediate
			 destination, the goods are transferred from the airplane to trucks to bring the
			 goods to their final destination.</Paragraph>
            <Paragraph>A route plan may
			 consist of more than one advance and beyond legs, but one main leg.</Paragraph>
            <Paragraph>The first leg that
			 you define is always of the main type.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.lino">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc>The identifying number of the leg.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.trmd">
         <Header>
            <Title>Transport Category</Title>
         </Header>
         <FuncDesc>Transport category</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Not <GUIRef href="/baanerp/tc/domains/com.trmd#none" role="option">Not Applicable</GUIRef> means that the <GUIRef href="/baanerp/fm/foc/fmfoc1150m000#fmfoc150.rtpn" role="manual">Route Plan</GUIRef> Leg is
			 not limited to one particular <GUIRef href="/baanerp/fm/foc/fmfoc1151m000#fmfoc151.trmd" role="manual">Transport Category</GUIRef>.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.tmcb">
         <Header>
            <Title>Transport Means Combination</Title>
         </Header>
         <FuncDesc> 
            <Link href="/baanerp/fm/glossary/glossary#000080" role="glossary" Update="No">Transport means combination</Link>.</FuncDesc>
         <SimpleSection>
            <Paragraph>If a transport means
			 group is selected in the <GUIRef href="/baanerp/fm/foc/fmfoc1151m000#fmfoc151.cmtg" role="manual">Transport Means Group</GUIRef> field, you cannot select a
			 transport means combination. If a carrier is inserted for the current leg, the
			 transport means combination must be attached to this carrier. In the <GUIRef href="/baanerp/fm/fmd/fmfmd0144m000" role="session">Transport Means Combinations by Carrier/LSP (fmfmd0144m000)</GUIRef> session, you can attach
			 transport means combinations to carriers.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000005" role="manual">The use of transport means groups</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000108" role="manual">Multiple means of transport by load</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.cmtg">
         <Header>
            <Title>Transport Means Group</Title>
         </Header>
         <FuncDesc>You can select one of the <Link href="/baanerp/fm/glossary/glossary#000004" role="glossary">transport means groups</Link> that
		  are defined for the selected carrier. For the transport means group that you
		  select in this field, the <GUIRef href="/baanerp/fm/fmd/fmfmd0150m000#fmfmd050.indp" role="manual">Independent Use Allowed</GUIRef> check box must be selected.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000005" role="manual">The use of transport means groups</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000108" role="manual">Multiple means of transport by load</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.orig">
         <Header>
            <Title>Origin Address</Title>
         </Header>
         <FuncDesc>The starting address of the route plan leg.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.dsad">
         <Header>
            <Title>Destination Address</Title>
         </Header>
         <FuncDesc>The destination of the route plan leg. At this address, the
		  goods are loaded onto another means of transport to begin the next leg, or they
		  are unloaded if the current leg is the last leg of the route plan.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.csrt">
         <Header>
            <Title>Standard Route</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/fm/glossary/glossary#000031" role="glossary">standard route</Link> that is used
		  for the <GUIRef href="/baanerp/fm/foc/fmfoc1150m000#fmfoc150.rtpn" role="manual">Route Plan</GUIRef>.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000021" role="manual">The use of standard routes</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.dist">
         <Header>
            <Title>Distance</Title>
         </Header>
         <FuncDesc>The distance between the origin address and the destination
		  address of the current route plan leg. If you manually enter a distance, this
		  distance overwrites the distance defined in the <GUIRef href="/baanerp/tc/com/tccom4537m000" role="session">Distance Table by City (tccom4537m000)</GUIRef> session and the <GUIRef href="/baanerp/tc/com/tccom4538m000" role="session">Distance Table by ZIP Code/Postal Code (tccom4538m000)</GUIRef> session. Note that you can only
		  insert a distance if the transport category is <GUIRef href="/baanerp/tc/domains/com.trmd#none" role="option">Not Applicable</GUIRef> and no carrier, transport means group, or transport means
		  combination is entered.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.dstu">
         <Header>
            <Title>Distance</Title>
         </Header>
         <FuncDesc>The length <Link href="/baanerp/tc/glossary/glossary#Units_tc" role="glossary">unit</Link> used to express the
		  distance.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.seqn">
         <Header>
            <Title>Route Plan Sequence</Title>
         </Header>
         <FuncDesc>The sequence number of an advance or beyond leg.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.cfrw">
         <Header>
            <Title>Carrier/LSP</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/fm/glossary/glossary#000067" role="glossary">carrier</Link> that is to carry out
		  the transportation of the goods.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.ttme">
         <Header>
            <Title>Travelling Time</Title>
         </Header>
         <FuncDesc>The time it takes to cover the distance between the origin and
		  the destination address. The travelling time entered in this field is an
		  estimate that is used for transport lead time calculations carried out from
		  sales and purchase orders, when the transport means group is not known. To
		  carry out such lead time calculations, a route must be defined for the sales or
		  purchase order and the route plan. When load building is carried out, transport
		  lead times are calculated by dividing the distances of leg addresses by the
		  average speed of the specified transport means group. Travelling times can be
		  defined in the <GUIRef href="/baanerp/tc/com/tccom4537m000" role="session">Distance Table by City (tccom4537m000)</GUIRef> session and the <GUIRef href="/baanerp/tc/com/tccom4538m000" role="session">Distance Table by ZIP Code/Postal Code (tccom4538m000)</GUIRef> session. You can also manually
		  enter a <GUIRef href="/baanerp/fm/foc/fmfoc1151m000#fmfoc151.ttme" role="manual">Travelling Time</GUIRef>.
		  This will overwrite the <GUIRef href="/baanerp/fm/foc/fmfoc1151m000#fmfoc151.ttme" role="manual">Travelling Time</GUIRef> defined in the <GUIRef href="/baanerp/tc/com/tccom4537m000" role="session">Distance Table by City (tccom4537m000)</GUIRef> session and the <GUIRef href="/baanerp/tc/com/tccom4538m000" role="session">Distance Table by ZIP Code/Postal Code (tccom4538m000)</GUIRef> session.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000019" role="manual">The load building process</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000031" role="manual">Lead time calculations for originating orders</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="fmfoc151.ttun">
         <Header>
            <Title>Travelling Time</Title>
         </Header>
         <FuncDesc>The time unit used to express the travelling time.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>