<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/fm/lbd/fmlbd4510m000" xml:lang="en">
   <Header>
      <Title>Master Loads (fmlbd4510m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view
		  master loads. A master load is a group of loads that travel a <Link href="/baanerp/fm/glossary/glossary#000024" role="glossary">route plan</Link>.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/fm/onlinemanual/000022" role="manual">The use of route plans</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/fm/onlinemanual/000019" role="manual">The load building process</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/fm/onlinemanual/000025" role="manual">Load plan, load, and shipment maintenance</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="fmlbd410.plan">
         <Header>
            <Title>Plan</Title>
         </Header>
         <FuncDesc>The load plan to which the master load belongs.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd410.msld">
         <Header>
            <Title>Master Load</Title>
         </Header>
         <FuncDesc>The master load. A master load is a group of loads that travel
		  the same route plan.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd410.load">
         <Header>
            <Title>Load</Title>
         </Header>
         <FuncDesc>A load that belongs to the master load.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd410.shpm">
         <Header>
            <Title>Shipment</Title>
         </Header>
         <FuncDesc>A shipment of the load that belongs to the master load.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd410.pono">
         <Header>
            <Title>Shipment Line</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/fm/glossary/glossary#000029" role="glossary">shipment line</Link> number of the
		  shipment.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd410.trip">
         <Header>
            <Title>Trip</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/fm/glossary/glossary#000034" role="glossary">trip</Link> on which the shipment
		  is based.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd410.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>
      </FieldHelp>
      <FieldHelp ID="fmlbd410.rplg">
         <Header>
            <Title>Route Plan Leg</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="fmlbd410.rpln">
         <Header>
            <Title>Route Plan Line</Title>
         </Header>
         <FuncDesc>The identifying number of the route plan leg.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="fmlbd410.rpsq">
         <Header>
            <Title>Route Plan Sequence</Title>
         </Header>
         <FuncDesc>The sequence number of an advance or beyond leg. The sequence
		  number indicates the order in which the addresses along the route plan legs are
		  called at.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="freight.order">
         <Header>
            <Title>Freight Order Line</Title>
         </Header>
         <FuncDesc>The freight order from which the loads of the master load are
		  created.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="freight.order.ln">
         <Header>
            <Title>Freight Order Line</Title>
         </Header>
         <FuncDesc>The freight order line from which the loads of the master load
		  are created.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>