<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/fm/lbd/fmlbd1500m000" xml:lang="en">
   <Header>
      <Title>Stops (fmlbd1500m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view the <Link href="/baanerp/fm/glossary/glossary#000032" role="glossary">stops</Link> created for a load
		  plan.</Paragraph>
      </AimSection>
      <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/000051" role="manual">Examples of the execution of the load building process</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="fmlbd100.cpln">
         <Header>
            <Title>Plan</Title>
         </Header>
         <FuncDesc>The load plan for which the stops are created.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.vino">
         <Header>
            <Title>Stop</Title>
         </Header>
         <FuncDesc>The identification number of the <Link href="/baanerp/fm/glossary/glossary#000032" role="glossary">stop</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.vico">
         <Header>
            <Title>Stop Type</Title>
         </Header>
         <FuncDesc>The type of stop. A stop is either a load stop or an unload
		  stop.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.vipo">
         <Header>
            <Title>Stop Position</Title>
         </Header>
         <FuncDesc>The position number of the stop.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.sseq">
         <Header>
            <Title>Stop Sequence</Title>
         </Header>
         <FuncDesc>The sequence number of the stop. If the stop is included in a
		  route plan, this field shows the order in which the stop is visited. For
		  example, one is the first stop visited in the route plan, two the second, and
		  so on.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.rono">
         <Header>
            <Title>Trip</Title>
         </Header>
         <FuncDesc>If the stop address is included in a route plan, this field
		  shows the sequence number of the route plan leg of the stop.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.cadr">
         <Header>
            <Title>Address</Title>
         </Header>
         <FuncDesc>The address of the stop. It depends on the stop type, whether
		  this is a loading or an unloading address.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.mndt">
         <Header>
            <Title>Minimum Load/Unload Date</Title>
         </Header>
         <FuncDesc>The minimum load date of a stop of the load type or the minimum
		  unload date of a stop of the unload type.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000051" role="manual">Examples of the execution of the load building process</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.mxdt">
         <Header>
            <Title>Maximum Load/Unload Date</Title>
         </Header>
         <FuncDesc>The maximum load date of a stop of the load type or the maximum
		  unload date of a stop of the unload type.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000051" role="manual">Examples of the execution of the load building process</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.opdt">
         <Header>
            <Title>Optimal Date</Title>
         </Header>
         <FuncDesc>It depends on the stop type whether this is an optimal load
		  date or an optimal unload date. The optimal date calculation is controlled by
		  the setting of the planned date determiner.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000041" role="manual">To use the planned date determiner options</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000051" role="manual">Examples of the execution of the load building process</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.sgsh">
         <Header>
            <Title>Single Shipment</Title>
         </Header>
         <FuncDesc>If this check box is selected, the stop must be planned
		  as a single shipment using the Direct Shipping algorithm.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.cfrw">
         <Header>
            <Title>Carrier/LSP</Title>
         </Header>
         <FuncDesc>An organization that provides transport services. To use a
		carrier for load building, freight order clustering, transport cost
		calculation, and invoicing, you must define the carrier both as a carrier and a
		buy-from business partner in <GUIRef href="/baanerp/tc" role="package">Common</GUIRef>. A carrier is also referred to as a forwarding agent.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.cbin">
         <Header>
            <Title>Carrier/LSP Binding</Title>
         </Header>
         <FuncDesc>If this check box is selected, the carrier selected in
		  this field cannot be overruled by the load building engine of <GUIRef href="/baanerp/fm" role="package">Freight</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.tmcb">
         <Header>
            <Title>Transport Means Combination</Title>
         </Header>
         <FuncDesc>A combined means of transport that consists of various <Link href="/baanerp/fm/glossary/glossary#000081" role="glossary" Update="No">vehicle types</Link> and/or <Link href="/baanerp/fm/glossary/glossary#000017" role="glossary">means of transport</Link> which jointly transport a <Link href="/baanerp/wh/glossary/glossary#000022" role="glossary">load</Link>. If a transport means combination includes more than
		one means of transport, <GUIRef href="/baanerp/fm" role="package">Freight</GUIRef> can perform load building for more than one means of
		transport per load. Transport means combinations are also used in freight order
		clustering. A transport means combination shows the combined means of transport
		that is to transport the goods listed on a freight order cluster.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.cmtg">
         <Header>
            <Title>Transport Means Group</Title>
         </Header>
         <FuncDesc>A classification used to group means of transport, such as:</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>Vans</ListItem>
               <ListItem>Trucks</ListItem>
               <ListItem>Container ships</ListItem>
               <ListItem>Cargo aircraft</ListItem>
            </List>
            <List>
               <ListIntro>For each group, properties are defined, such as:</ListIntro>
               <ListItem>The average speed</ListItem>
               <ListItem>The loading capacity</ListItem>
            </List>
            <Paragraph>Each means of transport defined in <GUIRef href="/baanerp/fm" role="package">Freight</GUIRef> belongs
		  to a transport means group. For example, transport means group: Vans, means of
		  transport: van with licence number XX333444 .</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.motr">
         <Header>
            <Title>Means of Transport</Title>
         </Header>
         <FuncDesc>An individual identifiable means of transport used for freight
		planning and freight order clustering, such as:</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>Truck</ListItem>
               <ListItem>Airplane</ListItem>
            </List>
            <Paragraph>For load building and freight order clustering purposes, <GUIRef href="/baanerp/fm" role="package">Freight</GUIRef> checks
		  the availability of individual means of transport, if specified for a load or a
		  freight order line.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000043" role="manual">Means of transport selection</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.ccmb">
         <Header>
            <Title>Combination Code</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/fm/glossary/glossary#0000001" role="glossary">combination code</Link> of the
		  stop.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.ttyp">
         <Header>
            <Title>Transport Type</Title>
         </Header>
         <FuncDesc>A code that refers to special properties of a means of
		transport, or of a transport means group, such as:</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>Cold storage</ListItem>
               <ListItem>Armored; high security</ListItem>
            </List>
            <Paragraph>Transport types are used in the load building and freight
		  order clustering engines of the <GUIRef href="/baanerp/fm" role="package">Freight</GUIRef> package. The main purpose of
		  Transport types is to ensure that items are transported by a means of transport
		  that has particular properties. Transport types are also used as a criterion to
		  determine the costs of transportation.</Paragraph>
         </SimpleSection>
         <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="fmlbd100.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="fmlbd100.rlty">
         <Header>
            <Title>Route Plan Leg</Title>
         </Header>
         <FuncDesc>If the stop address is included in a route plan, this field
		  shows the type of route plan leg of the stop address.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.rlin">
         <Header>
            <Title>Route Plan Line</Title>
         </Header>
         <FuncDesc>If the stop address is included in a route plan, this field
		  shows the line number of the route plan leg of the stop.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.rseq">
         <Header>
            <Title>Route Plan Sequence</Title>
         </Header>
         <FuncDesc>If the stop address is included in a route plan, this field
		  shows the sequence number of the route plan leg of the stop.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd100.cstr">
         <Header>
            <Title>Standard Route</Title>
         </Header>
         <FuncDesc>A standard route is a fixed route that is traveled with a
		particular frequency, such as a truck that visits delivery and/or loading
		addresses according to a fixed schedule, a rail service, or a boat service.
		Usually, transportation via standard routes costs less than travel via
		non-fixed routes. For example, you can define a route like Amsterdam via
		Rotterdam to Antwerp that is run once a day.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/fm/onlinemanual/000021" role="manual">The use of standard routes</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
   </Fields>
</Session>