<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/wmd/whwmd2120m000" xml:lang="en">
   <Header>
      <Title>Warehouse - Dock Locations (whwmd2120m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to set up and manage the
		  search structure for <Link href="/baanerp/wh/glossary/glossary#000317" role="glossary">docks</Link>. Docks can be assigned
		  to a business partner or an item, and can be of type <GUIRef href="/baanerp/wh/domains/wmd.loct#receiving" role="option">Receiving</GUIRef> or <GUIRef href="/baanerp/wh/domains/wmd.loct#staging" role="option">Staging</GUIRef>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <List>
            <ListIntro>If the dock is of type:</ListIntro>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/wmd.loct#receiving" role="option">Receiving</GUIRef>: you can
			 assign the dock to a ship-from business partner.</ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/wmd.loct#staging" role="option">Staging</GUIRef>: you can assign
			 the dock to a ship-to business partner.</ListItem>
         </List>
         <Paragraph>Dock locations are
		  used, for example, if items must be received into a specific dock because these
		  items require a special form of transport.</Paragraph>
         <Paragraph>Locations are created
		  in the <GUIRef href="/baanerp/wh/wmd/whwmd3500m000" role="session">Warehouse - Locations (whwmd3500m000)</GUIRef> session. Locations used as docks have one of
		  the location types that indicate the dock locations. You can enter these dock
		  locations into the search structure. For more information, refer to <Link href="/baanerp/wh/onlinemanual/000510" role="manual">Dock Locations - Search Criteria</Link>
         </Paragraph>
         <Paragraph>You can leave the
		  business partner and/or the item empty. If the business partner is empty and
		  the item code is filled, a dock location is recommended for a specific item
		  without regarding the business partner. The same applies if the item is empty
		  and the business partner is filled. If both are empty, a dock location is
		  recommended, regardless of item and business partner.</Paragraph>
         <ProcedureList>
            <ListIntro>The search structure has the following priority:</ListIntro>
            <ListItem>Look for a specific
			 item and a specific business partner.</ListItem>
            <ListItem>Look for a specific
			 item without a business partner.</ListItem>
            <ListItem>Look for a specific
			 business partner without an item.</ListItem>
            <ListItem>Look for a dock
			 location without a business partner and without an item.</ListItem>
         </ProcedureList>
         <Paragraph>If no dock locations
		  exist, the default receiving or staging location is taken. This default
		  location is defined at warehouse level ( <GUIRef href="/baanerp/wh/wmd/whwmd2500m000" role="session">Warehouses (whwmd2500m000)</GUIRef>. Dock
		  locations are used at the moment warehousing orders are generated or entered
		  manually. Dock locations enable you to ship or receive from the correct dock.</Paragraph>
         <Paragraph>Only warehouses that
		  use locations, as indicated in the locations field, can use dock locations.
		  These warehouses must have at least one dock location of type <GUIRef href="/baanerp/wh/domains/wmd.loct#receiving" role="option">Receiving</GUIRef> and one of
		  type <GUIRef href="/baanerp/wh/domains/wmd.loct#staging" role="option">Staging</GUIRef>, however, they can
		  have more.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Performance aspects</SectionTitle>
         <Paragraph>A limited number of staging and dock locations may affect
		  system performance. For more information, refer to <Link href="/baanerp/performance/wh/P000007_nr_of_staging_locations" role="manual">Number of staging locations</Link>.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/wmd00360" role="manual">Using dock locations</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/000510" role="manual">Dock Locations - Search Criteria</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="whwmd220.cwar">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd220.dktp">
         <Header>
            <Title>Dock Type</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/wh/glossary/glossary#000317" role="glossary">dock's</Link> type.</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <List>
               <ListItem> 
                  <Link href="/baanerp/wh/glossary/glossary#000371" role="glossary">Receiving location</Link>
               </ListItem>
               <ListItem> 
                  <Link href="/baanerp/wh/glossary/glossary#000381" role="glossary">Staging location</Link>
               </ListItem>
            </List>
         </AllowedValues>
      </FieldHelp>
      <FieldHelp ID="whwmd220.loca">
         <Header>
            <Title>Dock Location</Title>
         </Header>
         <FuncDesc> 
            <Link href="/baanerp/wh/glossary/glossary#000317" role="glossary">dock</Link> For more information, refer to <Link href="/baanerp/wh/onlinemanual/000510" role="manual">Dock Locations - Search Criteria</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd220.zone">
         <Header>
            <Title>Storage Zone</Title>
         </Header>
         <FuncDesc>The storage <Link href="/baanerp/wh/glossary/glossary#000389" role="glossary">zone</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd220.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>The item code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcibd001.dsca">
         <Header>
            <Title>Item Description</Title>
         </Header>
         <FuncDesc>The description of the item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd220.pkdf">
         <Header>
            <Title>Package Definition</Title>
         </Header>
         <FuncDesc>A particular configuration of items and their packaging. A
		package definition for an item can, for example, be the following: a pallet
		contains 12 boxes and each box contains 4 pieces.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd410.dsca">
         <Header>
            <Title>Package Definition</Title>
         </Header>
         <FuncDesc>The description of the package definition.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd220.rush">
         <Header>
            <Title>Rush Order</Title>
         </Header>
         <FuncDesc>If this check box is selected, the order is a <Link href="/baanerp/td/glossary/glossary#000374" role="glossary">rush order</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd220.sfty">
         <Header>
            <Title>Ship-from Code</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/wh/glossary/glossary#000058" role="glossary">ship-from type</Link> of the warehousing order for which the current dock location is
		  selected.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The field is unavailable in case the dock type is <GUIRef href="/baanerp/wh/domains/wmd.loct#staging" role="option">Staging</GUIRef>.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="whwmd220.sfco">
         <Header>
            <Title>Ship-from Code</Title>
         </Header>
         <FuncDesc>A code used, together with the ship-from type, to identify the
		exact source of a warehousing order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="sfco.dsca">
         <Header>
            <Title>Ship-from Code</Title>
         </Header>
         <FuncDesc>A code used, together with the ship-from type, to identify the
		exact source of a warehousing order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd220.stty">
         <Header>
            <Title>Ship-to Code</Title>
         </Header>
         <FuncDesc>The ship-to type is used, together with the ship-to code, to
		identify where goods are shipped to.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The ship-to type can have the following values:</ListIntro>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#partner" role="option">Business Partner</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#warehouse" role="option">Warehouse</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#work.center" role="option">Work Center</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tc/domains/typs#project" role="option">Project</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The field is unavailable in case the dock type is <GUIRef href="/baanerp/wh/domains/wmd.loct#receiving" role="option">Receiving</GUIRef>.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="whwmd220.stco">
         <Header>
            <Title>Ship-to Code</Title>
         </Header>
         <FuncDesc>A code used, together with the ship-to type, to identify where
		goods are shipped to.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="stco.dsca">
         <Header>
            <Title>Ship-to Code</Title>
         </Header>
         <FuncDesc>The description of the <Link href="/baanerp/wh/glossary/glossary#000048" role="glossary">ship-to code</Link> code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd220.carr">
         <Header>
            <Title>Carrier/LSP</Title>
         </Header>
         <FuncDesc>An organization that provides transport services. You can link
		a default carrier to both ship-to and ship-from business partners. In addition,
		you can print sales and purchase orders on a packing list, sorted by carrier.</FuncDesc>
         <SimpleSection>
            <Paragraph>For ordering and invoicing, you must define a carrier as a
		  business partner.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tcmcs080.dsca">
         <Header>
            <Title>Carrier/LSP</Title>
         </Header>
         <FuncDesc>An organization that provides transport services. You can link
		a default carrier to both ship-to and ship-from business partners. In addition,
		you can print sales and purchase orders on a packing list, sorted by carrier.</FuncDesc>
         <SimpleSection>
            <Paragraph>For ordering and invoicing, you must define a carrier as a
		  business partner.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whwmd220.crte">
         <Header>
            <Title>Route</Title>
         </Header>
         <FuncDesc>Line of travel from your warehouses to the ship-to or ship-from
		business partner's warehouse and vice versa. Use routes to group business
		partners that are located in the same area or along one convenient route.</FuncDesc>
         <SimpleSection>
            <Paragraph>You can arrange addresses by routes to print picking lists
		  and shipping notes sorted by route.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The field is not available in case the <GUIRef href="/baanerp/wh/wmd/whwmd2120m000#whwmd220.cstr" role="manual">Standard Route</GUIRef> or <GUIRef href="/baanerp/wh/wmd/whwmd2120m000#rtpn.dsca" role="manual">Route Plan</GUIRef> is specified.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tcmcs004.dsca">
         <Header>
            <Title>Route</Title>
         </Header>
         <FuncDesc>Line of travel from your warehouses to the ship-to or ship-from
		business partner's warehouse and vice versa. Use routes to group business
		partners that are located in the same area or along one convenient route.</FuncDesc>
         <SimpleSection>
            <Paragraph>You can arrange addresses by routes to print picking lists
		  and shipping notes sorted by route.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whwmd220.cdec">
         <Header>
            <Title>Delivery Terms</Title>
         </Header>
         <FuncDesc>The terms or agreements concerning the delivery of goods.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs041.dsca">
         <Header>
            <Title>Delivery Terms</Title>
         </Header>
         <FuncDesc>The terms or agreements concerning the delivery of goods.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd220.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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>The field is unavailable in case the <GUIRef href="/baanerp/tc/com/tccom0100s000#tccom000.frmi" role="manual">Freight Management (FM)</GUIRef> check box is not selected in
				the <GUIRef href="/baanerp/tc/com/tccom0500m000" role="session">Implemented Software Components (tccom0500m000)</GUIRef> session.</ListItem>
               <ListItem>The field is unavailable in case the <GUIRef href="/baanerp/wh/wmd/whwmd2120m000#whwmd220.crte" role="manual">Route</GUIRef> is specified.</ListItem>
            </List>
         </Note>
      </FieldHelp>
      <FieldHelp ID="cstr.dsca">
         <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>
      </FieldHelp>
      <FieldHelp ID="whwmd220.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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>
                  <Paragraph>The field is unavailable in case the <GUIRef href="/baanerp/tc/com/tccom0100s000#tccom000.frmi" role="manual">Freight Management (FM)</GUIRef> check box is not selected in
				  the <GUIRef href="/baanerp/tc/com/tccom0500m000" role="session">Implemented Software Components (tccom0500m000)</GUIRef> session.</Paragraph>
               </ListItem>
               <ListItem>
                  <Paragraph>The field is unavailable in case the <GUIRef href="/baanerp/wh/wmd/whwmd2120m000#whwmd220.crte" role="manual">Route</GUIRef> is specified.</Paragraph>
               </ListItem>
            </List>
         </Note>
      </FieldHelp>
      <FieldHelp ID="rtpn.dsca">
         <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="whwmd220.tmgp">
         <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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>
                  <Paragraph>The field is unavailable in case the <GUIRef href="/baanerp/tc/com/tccom0100s000#tccom000.frmi" role="manual">Freight Management (FM)</GUIRef> check box is not selected in
				  the <GUIRef href="/baanerp/tc/com/tccom0500m000" role="session">Implemented Software Components (tccom0500m000)</GUIRef> session.</Paragraph>
               </ListItem>
               <ListItem>
                  <Paragraph>The field is unavailable in case the <GUIRef href="/baanerp/wh/wmd/whwmd2120m000#whwmd220.tmcb" role="manual">Transport Means Combination</GUIRef> is specified.</Paragraph>
               </ListItem>
            </List>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tmgp.dsca">
         <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="whwmd220.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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>
                  <Paragraph>The field is unavailable in case the <GUIRef href="/baanerp/tc/com/tccom0100s000#tccom000.frmi" role="manual">Freight Management (FM)</GUIRef> check box is not selected in
				  the <GUIRef href="/baanerp/tc/com/tccom0500m000" role="session">Implemented Software Components (tccom0500m000)</GUIRef> session.</Paragraph>
               </ListItem>
               <ListItem>
                  <Paragraph>The field is unavailable in case the <GUIRef href="/baanerp/wh/wmd/whwmd2120m000#whwmd220.tmgp" role="manual">Transport Means Group</GUIRef> is specified.</Paragraph>
               </ListItem>
            </List>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tmcb.dsca">
         <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="whwmd220.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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The field is unavailable in case the <GUIRef href="/baanerp/tc/com/tccom0100s000#tccom000.frmi" role="manual">Freight Management (FM)</GUIRef> check box is not selected in
			 the <GUIRef href="/baanerp/tc/com/tccom0500m000" role="session">Implemented Software Components (tccom0500m000)</GUIRef> session.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="ttyp.dsca">
         <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>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="renumber.priorities">
         <Header>
            <Title>Renumber</Title>
         </Header>
         <FuncDesc>Reassigns the numbers to the priorities. The lowest number is
		  given the highest priority and vice-versa. The highest priority is number 10,
		  followed by 20, 30, and so on in decreasing order. Example Two priorities
		  are assigned the following numbers:</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>
                  <Paragraph>Priority A is assigned the number 5000.</Paragraph>
               </ListItem>
               <ListItem>
                  <Paragraph>Priority B is assigned the number 10000.</Paragraph>
               </ListItem>
            </List>
            <Paragraph>If you renumber, the following numbers are assigned to the
			 priorities:</Paragraph>
            <List>
               <ListItem>
                  <Paragraph>Priority A is assigned the number 10.</Paragraph>
               </ListItem>
               <ListItem>
                  <Paragraph>Priority B is assigned the number 20.</Paragraph>
               </ListItem>
            </List>
         </SimpleSection>
      </CommandHelp>
      <CommandHelp ID="move.priority.up">
         <Header>
            <Title>Up</Title>
         </Header>
         <FuncDesc>Assigns higher priority to the selected record.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="move.priority.down">
         <Header>
            <Title>Down</Title>
         </Header>
         <FuncDesc>Assigns lower priority to the selected record.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>