<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/wh/glossary/glossary" xml:lang="en">
   <Header>
      <Title>Glossary for Warehousing</Title>
   </Header>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000306">
      <Term>ABC analysis</Term>
      <Definition>An evaluative process in which items are classified into those
		making a large contribution (A items), an intermediate contribution (B items),
		and a small contribution (C items) to the total inventory turnover.</Definition>
      <Keyword type="glentry" order="d1e2581707">
         <Level1>ABC analysis</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000307">
      <Term>ABC code</Term>
      <Definition>A code that shows each item's contribution to the total
		inventory turnover. A items are high-value items and C items constitute low
		value.</Definition>
      <Keyword type="glentry" order="d1e2581712">
         <Level1>ABC code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000008">
      <Term>activity</Term>
      <Definition>A step in a warehousing procedure. An activity corresponds with
		a session of the <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> package. For example, the inbound activity Generate Inbound
		Advice is performed using the <GUIRef href="/baanerp/wh/inh/whinh3201m000" role="session">Generate Inbound Advice (whinh3201m000)</GUIRef> session.</Definition>
      <Keyword type="glentry" order="d1e2581278">
         <Level1>activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000452">
      <Term>actual log date</Term>
      <Definition>The current date and time when the inventory transaction took
		place. In contrast with the <Emphasis>transaction date</Emphasis>, the actual
		log date cannot be changed.</Definition>
      <Keyword type="glentry" order="d1e2581074">
         <Level1>actual log date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B61a" ID="additionalinformation_wh">
      <Term>additional information fields</Term>
      <Definition>User-defined fields that can be linked to LN tables.</Definition>
      <SimpleSection>
         <Paragraph>The contents of additional fields can be transferred between LN tables. Additional
		  information fields are meaningless to LN as no functional logic is linked to the contents
		  of these fields.</Paragraph>
      </SimpleSection>
      <CrossRef>
         <Link href="/baanerp/wh/onlinemanual/000560" role="manual">Additional information fields</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582838">
         <Level1>additional information fields</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000037">
      <Term>adjustment order</Term>
      <Definition>A warehouse order created specifically to adjust inventory
		where a variance has occurred. An adjustment order adjusts inventory and
		creates financial transactions.</Definition>
      <Keyword type="glentry" order="d1e2581498">
         <Level1>adjustment order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000490">
      <Term>administrative shipment structure</Term>
      <Definition>The administrative structure is the arrangement of shipment
		headers and shipment lines.</Definition>
      <Keyword type="glentry" order="d1e2580693">
         <Level1>administrative shipment structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000467">
      <Term>administrative warehouse</Term>
      <Definition>A warehouse that offers a view of a warehouse that is managed
		by a business partner. An administrative warehouse corresponds with a physical
		warehouse controlled by the business partner's system. In that physical
		warehouse, the inbound and outbound processing takes place. The administrative
		warehouse mirrors the inventory levels present in the business partner's
		warehouse.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Administrative warehouses are used in situations such as the
			 following:</ListIntro>
            <ListItem>The warehouse is located at your site, but a supplier
			 manages and possibly owns the inventory until you use the items.</ListItem>
            <ListItem>The warehouse is located at a customer's site. You own the
			 inventory until the customer uses the items, but the customer manages the
			 inventory.</ListItem>
            <ListItem>The warehouse is located at a subcontractor's site. You own
			 the unfinished goods present in the warehouse, but the subcontractor manages
			 the inventory.</ListItem>
         </List>
         <Paragraph>Administrative warehouse is not one of the warehouse types
		  that you can define in LN, setting up an administrative warehouse requires various parameter
		  settings.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2580907">
         <Level1>administrative warehouse</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000308">
      <Term>advance shipment notice</Term>
      <Definition>A notification that a shipment has been sent. Advanced shipment
		notices are sent and received by means of EDI. You can receive advance shipment
		notices from your supplier informing you that goods are to arrive at your
		warehouse, and/or you can send advance shipment notices to your customers that
		the goods they ordered are about to be delivered.</Definition>
      <Abbreviation>ASN</Abbreviation>
      <Synonym>shipment
		notice</Synonym>
      <Keyword type="glentry" order="d1e2581717">
         <Level1>advance shipment notice</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2581717">
         <Level1>ASN</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2581717">
         <Level1>shipment notice</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000025">
      <Term>advice number</Term>
      <Definition>The number of the individual advice line. A warehousing order
		line can be subdivided into one or more advice lines depending on the number of
		lots and/or locations that have been assigned.</Definition>
      <Keyword type="glentry" order="d1e2581437">
         <Level1>advice number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000309">
      <Term>allocated inventory</Term>
      <Definition>Inventory throughout all warehouses that is allocated to
		outbound order lines. After the inventory is shipped, that is, has left the
		warehouse, the allocation is deleted. Also referred to as standard allocation
		or soft allocation. See also inventory location allocation.</Definition>
      <SimpleSection>
         <Paragraph>See also <Link href="/baanerp/wh/glossary/glossary#000030" role="glossary">location allocation</Link>
         </Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581731">
         <Level1>allocated inventory</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000482">
      <Term>allocation buffer</Term>
      <Definition>Inventory that is allocated to a specification. This inventory
		is not allocated to a specific order, but can be consumed by any order line
		with a specification whose characteristics match the characteristics of the
		specification of the allocation buffer.</Definition>
      <Keyword type="glentry" order="d1e2580745">
         <Level1>allocation buffer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000481">
      <Term>allocation change order</Term>
      <Definition>A commission to change the allocation of
		inventory.</Definition>
      <Keyword type="glentry" order="d1e2580750">
         <Level1>allocation change order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2581722">
      <Term>ASN</Term>
      <Definition>See: <Link href="#000308" role="internal">advance shipment notice</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000300">
      <Term>assembly kit</Term>
      <Definition>An order-dependent set of items that must be supplied together
		to the shop-floor warehouse.</Definition>
      <Keyword type="glentry" order="d1e2581677">
         <Level1>assembly kit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000310">
      <Term>assembly location</Term>
      <Definition>The location at which subassemblies or parts are put together.</Definition>
      <Keyword type="glentry" order="d1e2581741">
         <Level1>assembly location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000000000000023">
      <Term>availability planning</Term>
      <Definition>The planning method which indicates the availability of tools
		for the planned production orders, service orders, and the actual production
		orders. Availability data enables you to check the future availability of the
		tools for these orders. If a tool is not available for the operation or service
		activity, you can take appropriate action.</Definition>
      <Keyword type="glentry" order="d1e2581087">
         <Level1>availability planning</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000391">
      <Term>batch size</Term>
      <Definition>The number of assembly kits to be called off.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000300" role="glossary">assembly kit</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582348">
         <Level1>batch size</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000311">
      <Term>bill of enterprise</Term>
      <Definition>The search structure by company for warehouses based on the
		numeric priorities assigned to the warehouses. 1 is the highest priority, and
		999 the lowest.</Definition>
      <Keyword type="glentry" order="d1e2581746">
         <Level1>bill of enterprise</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000312">
      <Term>bill of lading</Term>
      <Definition>The legal document used by the carrier that states what is
		transported (nature, quantity, weights, and so on) to what address.</Definition>
      <Keyword type="glentry" order="d1e2581752">
         <Level1>bill of lading</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000313">
      <Term>blocking</Term>
      <Definition>A function used to block inventory transactions. You can define
		blockings by zone, location, lot, stockpoint, or serialized item.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000368" role="glossary">reason for blocking</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581757">
         <Level1>blocking</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000027">
      <Term>BOM line</Term>
      <Definition>The line number within the bill of material.</Definition>
      <Keyword type="glentry" order="d1e2581447">
         <Level1>BOM line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="BOMPositiNum_wh">
      <Term>BOM position number</Term>
      <Definition>A reference number identifying a specific combination of
		manufactured and component items in a bill of material. The position number is
		subdivided by sequence numbers that are used to refer to usage of a component
		between particular dates.</Definition>
      <Keyword type="glentry" order="d1e2582790">
         <Level1>BOM position number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000314">
      <Term>bulk location</Term>
      <Definition>The location used mainly for large inbound quantities and/or
		containers and to indicate from which pick locations can be replenished.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000364" role="glossary">pick location</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581765">
         <Level1>bulk location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000479">
      <Term>Business Object Document (BOD)</Term>
      <Definition>An XML message used to exchange data between enterprises or
		enterprise applications. The BOD is composed of a noun, which identifies the
		message content, and a verb, which identifies the action to be taken with the
		document. The unique combination of the Noun and the Verb forms the name of the
		BOD. For example, noun ReceiveDelivery combined with verb Sync results in BOD
		SyncReceiveDelivery.</Definition>
      <Keyword type="glentry" order="d1e2580801">
         <Level1>Business Object Document (BOD)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000474">
      <Term>by location</Term>
      <Definition>An outbound method that determines the physical outbound
		priority of a specific item. The inventory is issued from inventory based on
		the <Link href="/baanerp/wh/glossary/glossary#000335" role="glossary">outbound priority</Link> of the
		locations. The inventory date will not be taken into account.</Definition>
      <Keyword type="glentry" order="d1e2580843">
         <Level1>by location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000050">
      <Term>class of risk</Term>
      <Definition>A code indicating the type of hazard. This code is only used if
		a shipment has been flagged as containing hazardous material.</Definition>
      <Keyword type="glentry" order="d1e2581592">
         <Level1>class of risk</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000032">
      <Term>commitment time fence</Term>
      <Definition>The time interval in which an order must be committed. Ideally,
		you only want to commit inventory to orders that must be shipped before you can
		receive the next purchase/replenishment/production order for that item.</Definition>
      <Keyword type="glentry" order="d1e2581477">
         <Level1>commitment time fence</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000468">
      <Term>company owned</Term>
      <Definition>Goods owned by your organization. A type of ownership behavior pertaining to
		goods in inventory or on order, which is set for standard business processes
		based on standard attributes such as <Link href="/baanerp/tc/glossary/glossary#TermsOfDeliv_tc" role="glossary">delivery terms</Link> and <Link href="/baanerp/tc/glossary/glossary#000371" role="glossary">point of title passage</Link>. After your customer receives or
		stores the goods, the customer will take ownership of the goods. If you
		purchase goods from your supplier, you become the owner after receipt or
		storage of the goods.</Definition>
      <SimpleSection>
         <Paragraph>See also: <Link href="/baanerp/wh/glossary/glossary#000480" role="glossary">ownership</Link>
         </Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2580891">
         <Level1>company owned</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000466">
      <Term>consigned</Term>
      <Definition>A type of ownership
		behavior pertaining to goods in inventory or on order.</Definition>
      <SimpleSection>
         <Paragraph>If you are a customer, consigned goods are goods delivered by
		  the supplier that you do not own and for which you have not paid. You become
		  the owner, and payment is due, when you use or sell the goods, or after a given
		  number of days after you receive the goods.</Paragraph>
         <Paragraph>If you are a supplier, consigned goods are goods that you
		  delivered to your customer, but the customer will not take ownership or pay
		  until he uses or sells the goods, or until a given period of time after receipt
		  of the goods has passed.</Paragraph>
         <Paragraph>The period of time between the receipt of the goods and the
		  date on which the customer becomes the owner, and payment is due, is laid down
		  in the contract drawn up between the supplier and the customer.</Paragraph>
         <Paragraph>See also: <Link href="/baanerp/wh/glossary/glossary#000480" role="glossary">ownership</Link>
         </Paragraph>
      </SimpleSection>
      <Synonym>Pay on Use</Synonym>
      <Keyword type="glentry" order="d1e2580924">
         <Level1>consigned</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2580924">
         <Level1>Pay on Use</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000315">
      <Term>consignment inventory</Term>
      <Definition>The goods owned by a third party and that are stored in a
		warehouse belonging to another party.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Two types of consignment inventory exist:</ListIntro>
            <ListItemHead>Owned consignment inventory</ListItemHead>
            <ListItem>Goods your company owns and stores in a customer's warehouse
			 without receiving payment until the goods are used or sold. You do not register
			 the goods as consignment inventory, because the goods are still part of your
			 inventory.</ListItem>
            <ListItemHead>Not-owned consignment inventory</ListItemHead>
            <ListItem>Goods a supplier owns, but that are stored in your warehouse
			 without being paid for until the goods are used or sold. You register the goods
			 as consignment inventory.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581773">
         <Level1>consignment inventory</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000473">
      <Term>consumption</Term>
      <Definition>The issue from the warehouse of <Link href="/baanerp/wh/glossary/glossary#000466" role="glossary">consigned</Link> items by or on behalf of the customer. The
		customer's purpose is to use these items for sale, production, and so on. After
		the items are issued, the customer becomes the owner of the items and the
		customer must pay the supplier.</Definition>
      <Keyword type="glentry" order="d1e2580851">
         <Level1>consumption</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy05" ContextApps="wh" ID="000019">
      <Term>cross-docking</Term>
      <Definition>The process by which inbound goods are immediately taken from
		the receipt location to the staging location for issue. For example, this
		process is used to fulfill an existing sales order for which no inventory is
		available.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>LN distinguishes the following three types of cross-docking:</ListIntro>
            <ListItemHead>
               <GUIRef href="/baanerp/wh/domains/inh.cdty#static" role="option">Static</GUIRef>
            </ListItemHead>
            <ListItem>To initiate this type of cross-docking, you must generate a
			 purchase order from a sales order in <GUIRef href="/baanerp/sales" role="package">Sales</GUIRef>.</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/wh/domains/inh.cdty#dynamic" role="option">Dynamic</GUIRef>
            </ListItemHead>
            <ListItem>This type of cross-docking, available in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>, can
			 be: <List>
                  <ListItem>Based on inventory shortages.</ListItem>
                  <ListItem>Defined explicitly during receipt of goods.</ListItem>
                  <ListItem>Created on an ad hoc basis.</ListItem>
               </List>
            </ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/wh/domains/inh.cdty#dms" role="option">Direct Material Supply</GUIRef>
            </ListItemHead>
            <ListItem>You can use this type of cross-docking, available in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>, to
			 meet demand in a cluster of warehouses, and is based on: <List>
                  <ListItem>Receipts</ListItem>
                  <ListItem>Inventory on hand</ListItem>
               </List>
            </ListItem>
         </List>
      </SimpleSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>You can maintain cross-dock orders that originate from <GUIRef href="/baanerp/sales" role="package">Sales</GUIRef> in the same way as
		  cross-dock orders created in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>, with the exception of the
		  sales order/purchase order link, which you cannot change.</Paragraph>
      </Note>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000458" role="glossary">direct material supply</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581342">
         <Level1>cross-docking</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy05" ContextApps="wh" ID="000440">
      <Term>cross-dock lead time</Term>
      <Definition>The time interval, defined in hours or days, between receiving
		the goods on the receiving location until the moment the goods leave the
		warehouse from the staging location. It includes the normal waiting times on
		the receiving location and/or staging location, and inspection
		time.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>You can define cross-dock lead times for warehouses and/or
		  item-warehouse combinations.</Paragraph>
      </Note>
      <Keyword type="glentry" order="d1e2581092">
         <Level1>cross-dock lead time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" Version="B60asy05" ID="000441">
      <Term>cross-dock order</Term>
      <Definition>An outbound order line for which the goods must be
		cross-docked. A cross-dock order can be fulfilled by creating cross-dock order
		lines for it.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000442" role="glossary">cross-dock order line</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581103">
         <Level1>cross-dock order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" Version="B60asy05" ID="000442">
      <Term>cross-dock order line</Term>
      <Definition>An inbound order line for which the goods must be cross-docked.
		Cross-dock order lines are used to fulfill cross-dock orders.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000441" role="glossary">cross-dock order</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581112">
         <Level1>cross-dock order line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" Version="B60asy05" ID="000443">
      <Term>cross-dock order priority definition</Term>
      <Definition>A user-defined set of priorities assigned to one or more LN table fields. LN uses the cross-dock
		order priority definition to generate the cross-dock order system
		priority.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListItem>You can use cross-dock order priority definitions for <GUIRef href="/baanerp/wh/domains/inh.cdty#dynamic" role="option">Dynamic</GUIRef> cross-docking only.</ListItem>
            <ListItem>Instead of cross-dock order priority definitions, and
			 dependent on a parameter setting, you can apply planning priority rules to <GUIRef href="/baanerp/wh/domains/inh.cdty#dynamic" role="option">Dynamic</GUIRef> cross-docking.</ListItem>
         </List>
      </Note>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000444" role="glossary">system priority</Link>, <Link href="/baanerp/wh/glossary/glossary#000457" role="glossary">planning priority rule</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581120">
         <Level1>cross-dock order priority definition</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000456">
      <Term>cross-dock restriction definition</Term>
      <Definition>A user-defined set of rules that LN uses to determine
		whether to create cross-dock orders. The rules are checked one after the other.
		If a valid condition is met, no cross-dock orders will be created. If no rule
		applies, LN permits
		creation of cross-dock orders. Cross-dock restriction rules are taken into
		account regardless of the use of direct material supply.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000019" role="glossary">cross-docking</Link>, <Link href="/baanerp/wh/glossary/glossary#000458" role="glossary">direct material supply</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581040">
         <Level1>cross-dock restriction definition</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000465">
      <Term>customer owned</Term>
      <Definition>A type
		of ownership behavior pertaining to goods in inventory or on order. Customer
		owned goods are goods whose ownership will not change during any of the inbound
		or outbound warehousing processes.</Definition>
      <SimpleSection>
         <Paragraph>For example, a customer sent you some components that you, as
		  a subcontractor, will use to manufacture a product for this customer. The
		  customer owns the components while they are stored in your warehouse and
		  throughout all the logistic and production processes involved in manufacturing
		  and delivering the product to the customer.</Paragraph>
         <Paragraph>See also: <Link href="/baanerp/wh/glossary/glossary#000480" role="glossary">ownership</Link>
         </Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2580942">
         <Level1>customer owned</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000316">
      <Term>cycle counting</Term>
      <Definition>The periodical count of the item inventory to verify if the
		system data is still accurate.</Definition>
      <Keyword type="glentry" order="d1e2581790">
         <Level1>cycle counting</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000036">
      <Term>cycle count order</Term>
      <Definition>An order generated by LN to count the inventory by stockpoint at a
		particular frequency and to subsequently register the counted quantities. A
		cycle count order consists of an order number and a sequence number indicating
		the number of counts performed on this order. As a result of the count action,
		you can adjust the inventory.</Definition>
      <Keyword type="glentry" order="d1e2581493">
         <Level1>cycle count order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2582361">
      <Term>DDC</Term>
      <Definition>See: <Link href="#000394" role="internal">distributed data collection</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000454">
      <Term>delivery code</Term>
      <Definition>A reason code that indicates who is to pay for the
		transportation of the goods.</Definition>
      <Keyword type="glentry" order="d1e2581056">
         <Level1>delivery code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000453">
      <Term>delivery note</Term>
      <Definition>A transport document that provides information on a consignment
		contained in one truck (or other vehicle) and refers to an order or a set of
		orders for one consignee at a delivery address. If the truck load contains
		shipments for various business partners, the load includes more than one
		delivery note. The information on a delivery note includes the delivery date
		and address, the customer's name, the contents of the consignment, and so on.
		In Italy, a delivery note is a legally required document, where it used to be
		called BAM (Bolla Accompagnamento Merci). Currently it is called DDT (Documento
		di Trasporto). In Portugal and Spain delivery notes are also used, but there
		they do not have the same legal status as in Italy.</Definition>
      <Keyword type="glentry" order="d1e2581061">
         <Level1>delivery note</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000049">
      <Term>delivery terms</Term>
      <Definition>The terms or agreements concerning the delivery of goods.</Definition>
      <Keyword type="glentry" order="d1e2581587">
         <Level1>delivery terms</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000035">
      <Term>demand data</Term>
      <Definition>The actual demand that is collected at the point of sales order
		entry. Each sales order is an instance of actual demand. Therefore, data
		associated with the sales order is collected.</Definition>
      <Keyword type="glentry" order="d1e2581488">
         <Level1>demand data</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000018">
      <Term>demand forecast</Term>
      <Definition>The level of demand that is expected in future periods.</Definition>
      <SimpleSection>
         <Paragraph>The demand forecast is based on historical demand data and
		  can be used to determine the optimal safety stock and reorder point.</Paragraph>
      </SimpleSection>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000377" role="glossary">safety stock</Link>, <Link href="/baanerp/wh/glossary/glossary#000374" role="glossary">reorder point</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581328">
         <Level1>demand forecast</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000483">
      <Term>demand order</Term>
      <Definition>An order, usually a sales order or sales schedule, fulfilling
		the demand of a customer.</Definition>
      <Keyword type="glentry" order="d1e2580740">
         <Level1>demand order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000458">
      <Term>direct material supply</Term>
      <Definition>A supply method in which (pending) receipts and available
		inventory on hand are used to meet high-priority demand within a user-specific
		cluster of warehouses. This supply method can be run either automatically,
		interactively, or manually, using the <GUIRef href="/baanerp/wh/inh/whinh6130m000" role="session">Direct Material Supply Distribution (whinh6130m000)</GUIRef> session.</Definition>
      <Abbreviation>DMS</Abbreviation>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000019" role="glossary">cross-docking</Link>, <Link href="/baanerp/wh/glossary/glossary#000459" role="glossary">warehouse supply structure</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2580994">
         <Level1>direct material supply</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2580994">
         <Level1>DMS</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000394">
      <Term>distributed data collection</Term>
      <Definition>A method of entering data without the use of the standard GUI.
		For example, entering data by the use of a remote scanner.</Definition>
      <Abbreviation>DDC</Abbreviation>
      <Keyword type="glentry" order="d1e2582356">
         <Level1>distributed data collection</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2582356">
         <Level1>DDC</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2581002">
      <Term>DMS</Term>
      <Definition>See: <Link href="#000458" role="internal">direct material supply</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000317">
      <Term>dock</Term>
      <Definition>A location in a warehouse where goods can be loaded or
		unloaded.</Definition>
      <Keyword type="glentry" order="d1e2581795">
         <Level1>dock</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000318">
      <Term>economic stock</Term>
      <Definition>The inventory that is available to be sold.</Definition>
      <Keyword type="glentry" order="d1e2581800">
         <Level1>economic stock</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000042">
      <Term>equipment description code</Term>
      <Definition>A code identifying the type of equipment used for the shipment.
		For example, TL = trailer.</Definition>
      <Keyword type="glentry" order="d1e2581536">
         <Level1>equipment description code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000043">
      <Term>equipment initial</Term>
      <Definition>The prefix (or alphabetic part) of the equipment's ID code.</Definition>
      <Keyword type="glentry" order="d1e2581541">
         <Level1>equipment initial</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000044">
      <Term>equipment number</Term>
      <Definition>The sequencing (or numeric) part of an equipment unit's ID code
		number.</Definition>
      <Keyword type="glentry" order="d1e2581546">
         <Level1>equipment number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" Expired="Yes" ID="000478">
      <Term>ESB LN Adapter</Term>
      <Definition>Connects the ERP LN application server to the <Link href="/baanerp/wh/glossary/glossary#000477" role="glossary">Enterprise Service Bus (ESB)</Link>. In this fashion, the ESB LN
		Adapter acts as a dispatcher for inbound and outbound BOD messages.</Definition>
      <Keyword type="glentry" order="d1e2580806">
         <Level1>ESB LN Adapter</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2581979">
      <Term>FIFO</Term>
      <Definition>See: <Link href="#000340" role="internal">first in, first out (FIFO)</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000463">
      <Term>financial warehouse</Term>
      <Definition>A warehouse with warehouse type <GUIRef href="/baanerp/tc/domains/typw#financial" role="option">Financial</GUIRef>. A financial warehouse is used to show the
		inventory levels and enable financial processing of owned inventory that is
		actually stored in a physical, that is, "real," warehouse belonging to another
		business unit or branch office within the same organization. The owning unit
		and the unit storing the inventory have their own p &amp; l accountability.</Definition>
      <SimpleSection/>
      <Keyword type="glentry" order="d1e2580959">
         <Level1>financial warehouse</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000340">
      <Term>first in, first out (FIFO)</Term>
      <Definition>An inventory valuation method for accounting purposes. The
		assumption is that the oldest inventory value (first in) is the first to be
		used or sold (first out). However, this method assumes no necessary
		relationship with the actual physical movement of specific items.</Definition>
      <SimpleSection>
         <Paragraph>FIFO can also be an outbound method that determines the
		  physical outbound priority of a specific item. The oldest inventory is the
		  first to be issued, taking into account the ordered packaging level, that is
		  leading over the inventory date.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListIntro>A box containing 10 pieces is ordered and you have the
			 following inventory:</ListIntro>
            <ListItem>5 pieces, receipt date 01-01</ListItem>
            <ListItem>1 box containing 10 pieces, receipt date 05-01</ListItem>
            <ListItem>1 box containing 10 pieces, receipt date 10-01</ListItem>
            <ListItem>7 pieces, receipt date 15-01</ListItem>
         </List>
         <Paragraph>If the outbound priority of the item is FIFO, the box with
		  receipt date 05-01 is issued.</Paragraph>
      </ExampleSection>
      <Abbreviation>FIFO</Abbreviation>
      <Keyword type="glentry" order="d1e2581955">
         <Level1>first in, first out (FIFO)</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2581955">
         <Level1>FIFO</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="FixedLocati_wh">
      <Term>fixed location</Term>
      <Definition>A location that is assigned to a specific item. If you link a
		location to an item, the item is always stored in that location. A fixed
		location can contain different items.</Definition>
      <Keyword type="glentry" order="d1e2582795">
         <Level1>fixed location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000319">
      <Term>fixed transfer price (FTP)</Term>
      <Definition>The firm value against which an item is valuated in the
		inventory. This value equals the item cost price, including any surcharges or
		discounts.</Definition>
      <SimpleSection>
         <Paragraph>FTP also is an inventory valuation method for accounting
		  purposes. FTP uses the fixed transfer price to valuate the inventory.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581805">
         <Level1>fixed transfer price (FTP)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000322">
      <Term>forecast method</Term>
      <Definition>A technique used to forecast the demand for items.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The following forecast methods are available:</ListIntro>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/fmod#mov.aver" role="option">Moving Average</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/fmod#exp.smooth" role="option">Exponential Smoothing</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/fmod#cons.pryr" role="option">Previous Year's Calculation</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/fmod#last.per.dem" role="option">Last Period's Demand</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581823">
         <Level1>forecast method</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000031">
      <Term>future ordered quantity</Term>
      <Definition>Quantity associated with a sales order detail whose planned
		delivery date is outside the commitment time fence.</Definition>
      <Keyword type="glentry" order="d1e2581472">
         <Level1>future ordered quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000447">
      <Term>general-level package definition</Term>
      <Definition>A package definition that you can use for various items. You
		can link a general-level package definition to an item to adjust the package
		definition data for the item. In this way, you create an item-level package
		definition.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000357" role="glossary">package definition</Link>, <Link href="/baanerp/wh/glossary/glossary#000448" role="glossary">item-level package definition</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582091">
         <Level1>general-level package definition</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000439">
      <Term>goods received note</Term>
      <Definition>A document that lists expected items and their quantities. Dock
		personnel can use goods received notes to compare against receiving documents
		provided by the supplier.</Definition>
      <Keyword type="glentry" order="d1e2581726">
         <Level1>goods received note</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000320">
      <Term>goods-received note</Term>
      <Definition>The note used to register the quantities received in a
		warehouse. LN prints
		the expected quantity on the note.</Definition>
      <Keyword type="glentry" order="d1e2581813">
         <Level1>goods-received note</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000432">
      <Term>handling unit</Term>
      <Definition>A uniquely identifiable physical unit that consists of
		packaging and contents. A handling unit can contain <Link href="/baanerp/tc/glossary/glossary#000001" role="glossary">items</Link> registered in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> and
		other handling units. A handling unit has a structure of packaging materials
		used to pack items, or is a part of such a structure.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>A handling unit includes the following attributes:</ListIntro>
            <ListItem>Identification code</ListItem>
            <ListItem>Packaging item (optional)</ListItem>
            <ListItem>Quantity of packaging items (optional)</ListItem>
         </List>
         <Paragraph>If you link an item to a handling unit, the item is packed by
		  means of the handling unit. The packaging item refers to the type of container
		  or other packing material of which the handling unit consists. For example, by
		  defining a packaging item such as Wooden Crate for a handling unit, you specify
		  that the handling unit is a wooden crate.</Paragraph>
      </SimpleSection>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000433" role="glossary">handling unit structure</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582651">
         <Level1>handling unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000433">
      <Term>handling unit structure</Term>
      <Definition>A description of the way items are packaged by means of
		handling units.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>A handling unit structure includes any of the following
			 elements:</ListIntro>
            <ListItemHead>Top</ListItemHead>
            <ListItem>Handling unit that includes the entire structure, such as a
			 pallet.</ListItem>
            <ListItemHead>Parent</ListItemHead>
            <ListItem>Handling unit that includes one or more children, such as a
			 box on a pallet.</ListItem>
            <ListItemHead>Child</ListItemHead>
            <ListItem>Handling unit that is linked to a parent, such as items that
			 are packed in a box.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582677">
         <Level1>handling unit structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy05" ContextApps="wh" ID="000446">
      <Term>handling unit template</Term>
      <Definition>One of the elements of a package definition. A handling unit
		template provides information on the packing materials that must be used to
		pack items and on the way the packaging materials are structured. The package
		structure is hierarchical and consists of several nodes that are related in a
		parent-child fashion. The packaging materials refer to handling units, each
		node represents a handling unit.</Definition>
      <SimpleSection>
         <Paragraph>When handling units are generated for the items of a
		  particular order, the handling units are created and structured as defined in
		  the handling unit template of the package definition that is linked to the
		  order.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582698">
         <Level1>handling unit template</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000324">
      <Term>inbound</Term>
      <Definition>A procedure in which received goods are stored in a warehouse.</Definition>
      <Keyword type="glentry" order="d1e2581850">
         <Level1>inbound</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000323">
      <Term>inbound advice</Term>
      <Definition>A list generated by LN that indicates the location where received goods
		must be stored, taking into account storage conditions, blockings, and so on.</Definition>
      <Keyword type="glentry" order="d1e2581845">
         <Level1>inbound advice</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000395">
      <Term>inbound lead time</Term>
      <Definition>The time interval between the arrival of the items and the
		actual storage in the warehouse.</Definition>
      <Keyword type="glentry" order="d1e2582363">
         <Level1>inbound lead time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000396">
      <Term>inbound-order line</Term>
      <Definition>A warehousing-order line used for the inbound of goods. An
		inbound-order line gives detailed information about planned receipts and actual
		receipts.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>For example:</ListIntro>
            <ListItem>Item data</ListItem>
            <ListItem>Ordered quantity</ListItem>
            <ListItem>Warehouse and location of receipt</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582368">
         <Level1>inbound-order line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000325">
      <Term>inbound priority</Term>
      <Definition>The sequence in which inventory locations are considered for
		storing received goods.</Definition>
      <Keyword type="glentry" order="d1e2581855">
         <Level1>inbound priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000477">
      <Term>Infor ION</Term>
      <Definition>An event-driven and XML-based messaging engine. This is the
		standard message bus. The message bus and its message standards provide the
		infrastructure for transporting messages to other application modules in a
		secure way.</Definition>
      <Keyword type="glentry" order="d1e2580814">
         <Level1>Infor ION</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000326">
      <Term>inspection location</Term>
      <Definition>A type of inventory location exclusively designated to store
		purchased items that are eligible for inspection upon receipt.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>After the items have passed inspection, they are
			 transferred to:</ListIntro>
            <ListItem>A normal location if they are approved.</ListItem>
            <ListItem>A reject location if they are rejected.</ListItem>
         </List>
         <Paragraph>Goods in an inspection location are always considered to be
		  on-hold inventory.</Paragraph>
      </SimpleSection>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000326" role="glossary">inspection location</Link>, <Link href="/baanerp/wh/glossary/glossary#000412" role="glossary">reject location</Link>, <Link href="/baanerp/wh/glossary/glossary#000331" role="glossary">inventory on hold</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581860">
         <Level1>inspection location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000333">
      <Term>inventory</Term>
      <Definition>The goods stored in a warehouse.</Definition>
      <Keyword type="glentry" order="d1e2581913">
         <Level1>inventory</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000000000000018">
      <Term>inventory adjustment order</Term>
      <Definition>A manually entered order to increase or decrease the system
		inventory.</Definition>
      <Keyword type="glentry" order="d1e2581082">
         <Level1>inventory adjustment order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000034">
      <Term>inventory buffer</Term>
      <Definition>A repository where inventory can be reserved for special
		purposes. A separate order origin (called inventory buffer) is used to do this.</Definition>
      <Keyword type="glentry" order="d1e2581482">
         <Level1>inventory buffer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000328">
      <Term>inventory-carrying costs</Term>
      <Definition>The costs for holding an item (per inventory unit) in
		inventory, including costs for interest, storage space, and risk.</Definition>
      <Keyword type="glentry" order="d1e2581884">
         <Level1>inventory-carrying costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000029">
      <Term>inventory commitment</Term>
      <Definition>The reservation of inventory for an order without taking into
		account the physical storage of the goods within the warehouse. Previously
		referred to as hard allocation.</Definition>
      <Keyword type="glentry" order="d1e2581457">
         <Level1>inventory commitment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="InventCommit_wh">
      <Term>inventory commitment</Term>
      <Definition>The reservation of inventory for an order without taking into
		account the physical storage of the goods within the warehouse. Previously
		referred to as <Emphasis>hard allocation</Emphasis>.</Definition>
      <Keyword type="glentry" order="d1e2582800">
         <Level1>inventory commitment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000437">
      <Term>inventory commitment date</Term>
      <Definition>The date on which or after which inventory on hand must be
		reserved for a specific order.</Definition>
      <Keyword type="glentry" order="d1e2582779">
         <Level1>inventory commitment date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000016">
      <Term>inventory date</Term>
      <Definition>A date that is assigned to items when they are stored. You can
		use inventory dates to retrieve items based on FIFO (First In First Out) or
		LIFO (Last In First Out), without carrying out extensive lot control.</Definition>
      <SimpleSection>
         <Paragraph>The meaning of the inventory date is connected to the
		  outbound priority of LIFO, FIFO, or the product expiry date of the item.</Paragraph>
         <Paragraph>With outbound priority LIFO or FIFO, the default for the
		  inventory date is the system date; however, you can overwrite this so that the
		  inventory date does not have to be equal to the storage date. If the item has a
		  particular shelf life, the inventory date is the product expiry date defined
		  for the item.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581313">
         <Level1>inventory date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000334">
      <Term>inventory handling</Term>
      <Definition>The way in which the inventory is handled, both physically and
		in LN, if BOM items or
		list items are received or issued.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The inventory can be handled:</ListIntro>
            <ListItem>By main item.</ListItem>
            <ListItem>By component.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581918">
         <Level1>inventory handling</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000476">
      <Term>inventory level</Term>
      <Definition>The inventory quantity that can be available in a warehouse. In
		VMI or subcontracting scenarios, warehouse supply can be based on inventory
		levels laid down in contracts between suppliers and customers.</Definition>
      <Keyword type="glentry" order="d1e2580819">
         <Level1>inventory level</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000030">
      <Term>inventory location allocation</Term>
      <Definition>Inventory stored in specific warehouses or warehouse locations
		that is allocated to outbound order lines for which outbound advice is created
		that is not yet shipped. Also referred to as firm allocation or hard
		allocation. After the inventory is shipped, that is, has left the warehouse,
		the allocation is deleted.</Definition>
      <SimpleSection>
         <Paragraph>See also <Link href="/baanerp/wh/glossary/glossary#000309" role="glossary">allocated inventory</Link>
         </Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581462">
         <Level1>inventory location allocation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000464">
      <Term>inventory management business partner</Term>
      <Definition>The business partner who is responsible for inventory
		management at a warehouse.</Definition>
      <Keyword type="glentry" order="d1e2580954">
         <Level1>inventory management business partner</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000330">
      <Term>inventory on hand</Term>
      <Definition>The physical quantity of goods in one or more warehouses
		(including the inventory on hold).</Definition>
      <Synonym>on-hand inventory</Synonym>
      <Keyword type="glentry" order="d1e2581889">
         <Level1>inventory on hand</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2581889">
         <Level1>on-hand inventory</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000331">
      <Term>inventory on hold</Term>
      <Definition>A quantity of goods that is blocked. On-hold inventory can
		arise when the location, the lot, the zone, or the stockpoint is blocked. You
		can block inventory for various reasons, for example, for inspection or
		cycle-counting.</Definition>
      <SimpleSection>
         <Paragraph>If a location has been blocked for all transactions, the
		  blocked quantity is equal to the inventory on hand. You cannot partially block
		  the inventory at a location.</Paragraph>
      </SimpleSection>
      <Synonym>on-hold inventory</Synonym>
      <Keyword type="glentry" order="d1e2581896">
         <Level1>inventory on hold</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2581896">
         <Level1>on-hold inventory</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000332">
      <Term>inventory on order</Term>
      <Definition>The planned receipts. The inventory that has been ordered but
		not yet received. This quantity is included in the economic stock.</Definition>
      <Synonym>on-order inventory</Synonym>
      <Keyword type="glentry" order="d1e2581906">
         <Level1>inventory on order</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2581906">
         <Level1>on-order inventory</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000470">
      <Term>inventory ownership change order</Term>
      <Definition>A commission to change the ownership of goods from the
		supplier, that is, the <Link href="/baanerp/tc/glossary/glossary#BuyfroBusine_tc" role="glossary">buy-from business partner</Link>, to the own
		company, if the ownership is time based. See also <Link href="/baanerp/wh/glossary/glossary#000480" role="glossary">ownership</Link>.</Definition>
      <SimpleSection>
         <Paragraph>An inventory ownership change order consists of an order
		  header providing general information and one or more order lines providing
		  details about the items involved. In addition, if resulting from the ownership
		  change relocation is required involving adjustments of the handling unit
		  structure, line handling information is also provided.</Paragraph>
         <Paragraph>Time based change orders are generated by users for items due
		  for ownership change. LN uses change orders to generate financial transactions related to
		  the ownership change and to track the whereabouts of inventory.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2580864">
         <Level1>inventory ownership change order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000336">
      <Term>inventory transaction</Term>
      <Definition>Any change in the inventory records.</Definition>
      <Keyword type="glentry" order="d1e2581937">
         <Level1>inventory transaction</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000004">
      <Term>inventory transaction type</Term>
      <Definition>A classification that is used to indicate the type of inventory
		movement.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The following inventory transaction types are available:</ListIntro>
            <ListItemHead>
               <GUIRef href="/baanerp/wh/domains/inh.ittp#issue" role="option">Issue</GUIRef>
            </ListItemHead>
            <ListItem>From warehouse to other entity than warehouse.</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/wh/domains/inh.ittp#receipt" role="option">Receipt</GUIRef>
            </ListItemHead>
            <ListItem>From other entity than warehouse to warehouse.</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/wh/domains/inh.ittp#transfer" role="option">Transfer</GUIRef>
            </ListItemHead>
            <ListItem>From one warehouse to another.</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/wh/domains/inh.ittp#wip.transfer" role="option">WIP Transfer</GUIRef>
            </ListItemHead>
            <ListItem>From one costing work center to another.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581239">
         <Level1>inventory transaction type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000386">
      <Term>inventory turnover</Term>
      <Definition>The number of times that an inventory cycles during a year.</Definition>
      <Keyword type="glentry" order="d1e2582296">
         <Level1>inventory turnover</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000337">
      <Term>inventory unit</Term>
      <Definition>The unit of measure in which the inventory of an item is
		recorded, such as piece, kilogram, box of 12, or meter.</Definition>
      <SimpleSection>
         <Paragraph>The inventory unit is also used as the base unit in measure
		  conversions, especially for conversions that concern the order unit and the
		  price unit on a purchase order or a sales order. These conversions always use
		  the inventory unit as the base unit. An inventory unit therefore applies to all
		  item types, also to item types that cannot be kept in stock.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581942">
         <Level1>inventory unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000001">
      <Term>inventory valuation method</Term>
      <Definition>A method to calculate the inventory value.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The inventory is valued at either its fixed price or its
			 actual receipt price. Because inventory value can change with time, the age of
			 inventory needs to be noted. In LN, the following inventory valuation methods are available:</ListIntro>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/ina.valm#ftp" role="option">Fixed Transfer Price (FTP)</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/wh/domains/ina.valm#fifo" role="option">First In First Out (FIFO)</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/ina.valm#lifo" role="option">Last In First Out (LIFO)</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/wh/domains/ina.valm#lot" role="option">Lot Price (Lot)</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/wh/domains/ina.valm#mauc" role="option">Mov. Aver. Unit Cost (MAUC)</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/wh/domains/ina.valm#serial" role="option">Serial Price (Serial)</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581205">
         <Level1>inventory valuation method</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000301">
      <Term>inventory variance</Term>
      <Definition>The difference between the valuation amount that is recorded
		after the receipt of goods and the updated value for that particular receipt.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>An inventory variance can be created:</ListIntro>
            <ListItem>If the receipt price is changed after the receipt is
			 confirmed</ListItem>
            <ListItem>If the invoice price differs from the receipt price</ListItem>
            <ListItem>If a production order is closed and the actual cost price
			 differs from the estimated cost price</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581682">
         <Level1>inventory variance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000339">
      <Term>issue</Term>
      <Definition>The transaction type that is used to withdraw goods from
		inventory.</Definition>
      <Keyword type="glentry" order="d1e2581950">
         <Level1>issue</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000399">
      <Term>issue price</Term>
      <Definition>The price against which goods are issued from the warehouse.
		The issue price is based on the inventory valuation price plus issuing
		surcharges.</Definition>
      <Keyword type="glentry" order="d1e2582383">
         <Level1>issue price</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000448">
      <Term>item-level package definition</Term>
      <Definition>A package definition that is defined for a specific item. An
		item-level package definition is created from a general-level package
		definition.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000447" role="glossary">general-level package definition</Link>, <Link href="/baanerp/wh/glossary/glossary#000357" role="glossary">package definition</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582102">
         <Level1>item-level package definition</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000450">
      <Term>item valuation group</Term>
      <Definition>An entity that is used to group items for inventory valuation
		purposes. To define an item valuation group, you must link an item valuation
		group code to the items that you want to include in the warehouse valuation
		group. Item valuation groups and warehouse valuation groups are linked, for
		example, to inventory valuation methods to valuate the item-warehouse
		combinations included in the warehouse and item valuation groups.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000449" role="glossary">warehouse valuation group</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582121">
         <Level1>item valuation group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000400">
      <Term>Kanban</Term>
      <Definition>A demand-pull system of just-in-time production that regulates
		the supply of items to shop floor warehouses.</Definition>
      <SimpleSection>
         <Paragraph>Kanban uses standard containers or lot sizes (also called
		  bins) to deliver items to shop floor warehouses. In the shop floor warehouse,
		  two or more bins are available with the same items. Items are only taken from
		  one bin. If a bin is empty, a new bin is ordered and the items are taken from
		  the (second) full bin. To each bin a label is attached. The line stations use
		  the label to order a full bin with the required items. As a result, no
		  inventory administration is done in the shop floor warehouse for the floor
		  stock items that are used.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582389">
         <Level1>Kanban</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000488">
      <Term>kit order</Term>
      <Definition>A sales order or warehousing order created using the extended
		kit handling functionality.</Definition>
      <Keyword type="glentry" order="d1e2580709">
         <Level1>kit order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000434">
      <Term>label</Term>
      <Definition>A printed piece of paper with information about items,
		quantities, packaging items and so on. A label often contains bar codes to
		enable scanning.</Definition>
      <Keyword type="glentry" order="d1e2582706">
         <Level1>label</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000341">
      <Term>last in, first out (LIFO)</Term>
      <Definition>An inventory valuation method for accounting purposes. The
		assumption is that the most recently received value item (last in) is the first
		to be used or sold (first out). However, this method assumes no necessary
		relationship with the actual physical movement of specific items.</Definition>
      <SimpleSection>
         <Paragraph>LIFO can also be an outbound method that determines the
		  physical outbound priority of a specific item. The newest inventory is the
		  first to be issued, taking into account the ordered packaging level, that is
		  leading over the inventory date.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListIntro>A box containing 10 pieces is ordered and you have the
			 following inventory:</ListIntro>
            <ListItem>5 pieces, receipt date 01-01</ListItem>
            <ListItem>1 box containing 10 pieces, receipt date 05-01</ListItem>
            <ListItem>1 box containing 10 pieces, receipt date 10-01</ListItem>
            <ListItem>7 pieces, receipt date 15-01</ListItem>
         </List>
         <Paragraph>If the outbound priority of the item is LIFO, the box with
		  receipt date 10-01 is issued.</Paragraph>
      </ExampleSection>
      <Abbreviation>LIFO</Abbreviation>
      <Keyword type="glentry" order="d1e2581981">
         <Level1>last in, first out (LIFO)</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2581981">
         <Level1>LIFO</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000401">
      <Term>lead-time unit</Term>
      <Definition>The unit in which lead time is expressed.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The following lead-time units are available:</ListIntro>
            <ListItem>Hour</ListItem>
            <ListItem>Day</ListItem>
            <ListItem>Week</ListItem>
            <ListItem>Month</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582397">
         <Level1>lead-time unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2582005">
      <Term>LIFO</Term>
      <Definition>See: <Link href="#000341" role="internal">last in, first out (LIFO)</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000011">
      <Term>list</Term>
      <Definition>In LN,
		an enumeration of components. A list can be a kit, a menu, an option, or an
		accessory.</Definition>
      <Keyword type="glentry" order="d1e2581295">
         <Level1>list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000022">
      <Term>load</Term>
      <Definition>In LN,
		all goods and/or shipments carried by one means of transport on a specific date
		and time and using a specific route.</Definition>
      <Keyword type="glentry" order="d1e2581418">
         <Level1>load</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000013">
      <Term>location</Term>
      <Definition>A distinct place in a warehouse where goods are stored.</Definition>
      <SimpleSection>
         <Paragraph>A warehouse can be divided into locations to manage the
		  available space, and to locate the stored goods. Storage conditions and blocks
		  can be applied to individual locations.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581305">
         <Level1>location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000038">
      <Term>location type</Term>
      <Definition>The location type indicates the purpose of the location, for
		example, receipt, inspection, bulk, pick, staging, assembly.</Definition>
      <Keyword type="glentry" order="d1e2581503">
         <Level1>location type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000343">
      <Term>lot</Term>
      <Definition>A number of items produced and stored together that are
		identified by a (lot) code. Lots identify goods.</Definition>
      <Keyword type="glentry" order="d1e2582007">
         <Level1>lot</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000344">
      <Term>lot-feature value</Term>
      <Definition>Value assigned to a variable lot feature. A shortened version
		of variable lot-feature value. Such features can have a different value for
		each project, item, or lot.</Definition>
      <Keyword type="glentry" order="d1e2582012">
         <Level1>lot-feature value</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000345">
      <Term>lot-for-lot</Term>
      <Definition>An ordering process that generates planned orders in quantities
		equal to the net requirements in each period.</Definition>
      <Keyword type="glentry" order="d1e2582017">
         <Level1>lot-for-lot</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000347">
      <Term>lot item</Term>
      <Definition>An item that is subject to lot control.</Definition>
      <Keyword type="glentry" order="d1e2582022">
         <Level1>lot item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000402">
      <Term>lot price (lot)</Term>
      <Definition>An inventory valuation method for accounting purposes that is
		used to separately calculate the lot price or cost price for each lot. The lot
		price is based on the actual receipt price.</Definition>
      <Keyword type="glentry" order="d1e2582414">
         <Level1>lot price (lot)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000348">
      <Term>lot selection</Term>
      <Definition>The specific conditions that can be established for lot items
		on order lines.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>These conditions are:</ListIntro>
            <ListItemHead>
               <GUIRef href="/baanerp/tc/domains/lsel#any" role="option">Any</GUIRef>
            </ListItemHead>
            <ListItem>The goods to be received or shipped are not subject to
			 specific lot conditions. You can use more than one lot.</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/tc/domains/lsel#same" role="option">Same</GUIRef>
            </ListItemHead>
            <ListItem>You can select any lot for receipt or shipment, but the
			 entire receipt or shipment must have the same lot.</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/tc/domains/lsel#specific" role="option">Specific</GUIRef>
            </ListItemHead>
            <ListItem>You can receive or ship only one, specific lot.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582027">
         <Level1>lot selection</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000349">
      <Term>lot size</Term>
      <Definition>The number of items in a lot.</Definition>
      <Keyword type="glentry" order="d1e2582051">
         <Level1>lot size</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000350">
      <Term>lot tracking</Term>
      <Definition>The ability to trace lots during the logistical process.</Definition>
      <Keyword type="glentry" order="d1e2582057">
         <Level1>lot tracking</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000436">
      <Term>lower cost or market value (LCMV)</Term>
      <Definition>A valuation method that compares the inventory value based on
		one of the inventory valuation methods (see below) with the inventory's market
		value. If the market value is lower, the entire inventory of a specific item is
		valued in the balance sheet using the market value.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The following inventory valuation methods can be used to
			 determine the inventory value:</ListIntro>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/ina.valm#ftp" role="option">Fixed Transfer Price (FTP)</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/ina.valm#mauc" role="option">Mov. Aver. Unit Cost (MAUC)</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/ina.valm#fifo" role="option">First In First Out (FIFO)</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/ina.valm#lifo" role="option">Last In First Out (LIFO)</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/ina.valm#lot" role="option">Lot Price (Lot)</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/wh/domains/ina.valm#serial" role="option">Serial Price (Serial)</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582747">
         <Level1>lower cost or market value (LCMV)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000403">
      <Term>maximum-time interval</Term>
      <Definition>A defined period of time in a calendar, for which a resource
		can be planned.</Definition>
      <Keyword type="glentry" order="d1e2582419">
         <Level1>maximum-time interval</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000455">
      <Term>motive of transport</Term>
      <Definition>A reason code that indicates why transportation takes place,
		for example, Repair, Sales, Transfer, and so on.</Definition>
      <Keyword type="glentry" order="d1e2581051">
         <Level1>motive of transport</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000351">
      <Term>moving-average unit cost (MAUC)</Term>
      <Definition>An inventory valuation method for accounting purposes.</Definition>
      <SimpleSection>
         <Paragraph>The MAUC is the average value for each unit of the current
		  inventory. For each new receipt the MAUC is updated.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582062">
         <Level1>moving-average unit cost (MAUC)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2581894">
      <Term>on-hand inventory</Term>
      <Definition>See: <Link href="#000330" role="internal">inventory on hand</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2581904">
      <Term>on-hold inventory</Term>
      <Definition>See: <Link href="#000331" role="internal">inventory on hold</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2581911">
      <Term>on-order inventory</Term>
      <Definition>See: <Link href="#000332" role="internal">inventory on order</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000404">
      <Term>order controlled/Batch</Term>
      <Definition>A demand-pull system that regulates the supply of items to shop
		floor warehouses.</Definition>
      <SimpleSection>
         <Paragraph>In this supply system, items that are required at a
		  particular line station of the assembly line are called off at an earlier line
		  station, called the trigger-from station. The number of items that is called
		  off depends on what is needed on the assembly line in a specified time fence,
		  called the maximum time interval.</Paragraph>
         <Paragraph>In general, the items that are supplied to the shop floor
		  warehouse by batch, are fast movers and are processed in high volumes. There is
		  no direct link between these items and the assembly orders they are used for.
		  In addition, one warehouse order set can be used to supply the goods needed by
		  several assembly orders.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582424">
         <Level1>order controlled/Batch</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000405">
      <Term>order controlled/SILS</Term>
      <Definition>A demand-pull system that regulates the supply of items to shop
		floor warehouses in the sequence in which they are needed.</Definition>
      <SimpleSection>
         <Paragraph>In this supply system, items that are required for a specific
		  assembly order, and at a particular line station of the assembly line, are
		  called off at an earlier line station, called the trigger-from station. The
		  number of items that is called off depends on what is needed for specific
		  assembly orders in a specified time fence, called the maximum time interval.</Paragraph>
         <Paragraph>In general, the items that are supplied to the shop floor
		  warehouse by SILS, are fast movers and are processed in high volumes. There is
		  a direct link between these items and the assembly orders they are used for. In
		  addition, one warehouse order set can only supply the goods needed by one
		  assembly order.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582434">
         <Level1>order controlled/SILS</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" Version="B60asy10" ID="000408">
      <Term>order controlled/single</Term>
      <Definition>A demand-pull system that regulates the supply of items to shop
		floor warehouses.</Definition>
      <SimpleSection>
         <Paragraph>In this supply system, a specific production order for a
		  specific product pulls the required items from a supply warehouse to the shop
		  floor warehouse. A direct link is established between the production order for
		  which the items are required, and the warehousing order that regulates the
		  supply of the required items to the shop floor warehouse.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582464">
         <Level1>order controlled/single</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" Version="B60asy10" ID="000414">
      <Term>order horizon</Term>
      <Definition>The time interval for which demand (actual and forecasted) is
		taken into account to determine the net order quantity.</Definition>
      <SimpleSection>
         <Paragraph>LN uses the following formula to calculate the order horizon:</Paragraph>
         <Formula space-and-orientation="indented-estimated">
            <Paragraph>factor * lead time (= LT + ST) + constant</Paragraph>
         </Formula>
      </SimpleSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListItem>The factor can be used to make sure that ordering will be in
			 time.</ListItem>
            <ListItem>The constant can be used to: <List>
                  <ListItem>Reduce the risks that result from unstable lead times.
				  (SIC)</ListItem>
                  <ListItem>Limit the order horizon to the duration of a shift, in
				  order to replenish only stock for the period of the shift-work. Then the factor
				  must be zero. (TPOP)</ListItem>
               </List>
            </ListItem>
         </List>
      </Note>
      <Keyword type="glentry" order="d1e2582516">
         <Level1>order horizon</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000051">
      <Term>order set</Term>
      <Definition>The order set groups order lines of the same order together
		according to the following attributes:</Definition>
      <SimpleSection>
         <List>
            <ListItem>Ship-from partner</ListItem>
            <ListItem>Ship-to partner</ListItem>
            <ListItem>Ship-from address</ListItem>
            <ListItem>Ship-to address</ListItem>
            <ListItem>Carrier</ListItem>
            <ListItem>Shipping date</ListItem>
            <ListItem>Original company</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581597">
         <Level1>order set</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000053">
      <Term>order-type priority</Term>
      <Definition>The priority fields show the priority in which the various
		types of outbound advice are processed.</Definition>
      <SimpleSection>
         <Paragraph>Each advice type can only appear once in the list of
		  priorities. Whenever you make a change in the priorities, a corresponding
		  change appears elsewhere in the list.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>If priority 4 contains advice type sales and you change it to
		  contain advice type purchase, the two advice types swap places in the
		  priorities list.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2581623">
         <Level1>order-type priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000356">
      <Term>outbound</Term>
      <Definition>The act of retrieving goods from a warehouse.</Definition>
      <Keyword type="glentry" order="d1e2582075">
         <Level1>outbound</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000354">
      <Term>outbound advice</Term>
      <Definition>A list generated by LN that advises you the location and lot from which
		goods must be picked and possibly issued, taking into account factors such as
		blocked locations and the outbound method.</Definition>
      <Keyword type="glentry" order="d1e2582070">
         <Level1>outbound advice</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000406">
      <Term>outbound lead time</Term>
      <Definition>The time interval between taking the items out of the warehouse
		and the departure of the carrier on which the items are placed.</Definition>
      <Keyword type="glentry" order="d1e2582444">
         <Level1>outbound lead time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B61a" ID="000451">
      <Term>outbound method</Term>
      <Definition>The method by which LN determines the order of issuing items. The
		outbound method can be <GUIRef href="/baanerp/tc/domains/obpr#lifo" role="option">LIFO</GUIRef> (last received items first), <GUIRef href="/baanerp/tc/domains/obpr#fifo" role="option">FIFO</GUIRef> (oldest
		items first), or <GUIRef href="/baanerp/tc/domains/obpr#loca" role="option">By Location</GUIRef> (based on the warehouse location's outbound priority).</Definition>
      <Keyword type="glentry" order="d1e2582824">
         <Level1>outbound method</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000407">
      <Term>outbound-order line</Term>
      <Definition>A warehouse-order line that is used to issue goods from a
		warehouse.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>An outbound-order line gives detailed information about
			 planned issues and actual issues, for example:</ListIntro>
            <ListItem>Item data.</ListItem>
            <ListItem>Ordered quantity.</ListItem>
            <ListItem>Warehouse from where the goods are issued.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582449">
         <Level1>outbound-order line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000335">
      <Term>outbound priority</Term>
      <Definition>The information that determines the sequence of locations from
		which an item must be retrieved.</Definition>
      <Keyword type="glentry" order="d1e2581931">
         <Level1>outbound priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000480">
      <Term>ownership</Term>
      <Definition>Indicates if, and at which point in the supply chain, the
		ownership of goods changes from the supplier to the customer. Ownership changes
		also occur between departments or business units within an organization. When
		the ownership changes, payment is due.</Definition>
      <SimpleSection>
         <Paragraph>In traditional, non-VMI scenarios, the ownership of an item
		  changes from the supplier to the customer after the customer has received the
		  item from the supplier. The customer must pay for the item on receipt of the
		  goods.</Paragraph>
         <Paragraph>In various <Link href="/baanerp/ti/glossary/glossary#000044" role="glossary">subcontracting</Link> scenarios, ownership will not change
		  during any of the inbound or outbound warehousing processes. In such cases, the
		  ownership is <Link href="/baanerp/wh/glossary/glossary#000465" role="glossary">customer owned</Link>.</Paragraph>
         <List>
            <ListIntro>In <Link href="/baanerp/wh/glossary/glossary#000469" role="glossary">vendor managed inventory (VMI)</Link> scenarios, the ownership
			 can be <Link href="/baanerp/wh/glossary/glossary#000466" role="glossary">consigned</Link>. If the ownership is consigned, the ownership
			 change is either time based or consumption based.</ListIntro>
            <ListItemHead>Consumption based</ListItemHead>
            <ListItem>The customer issues the goods to sell them or to <Link href="/baanerp/wh/glossary/glossary#000473" role="glossary" Update="No">consume</Link> them</ListItem>
            <ListItemHead>Time based</ListItemHead>
            <ListItem> 
               <List>
                  <ListIntro>Some time after:</ListIntro>
                  <ListItem>The customer receives the goods</ListItem>
                  <ListItem>The last issue or receipt of the goods</ListItem>
               </List>
            </ListItem>
         </List>
         <Paragraph>For time based ownership change, the period of time is laid
		  down in the contract between the customer and the supplier.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2580756">
         <Level1>ownership</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000475">
      <Term>ownership record</Term>
      <Definition>An ownership record specifies the owner of the items listed on
		any of the following objects:</Definition>
      <SimpleSection>
         <List>
            <ListItem>Receipt line</ListItem>
            <ListItem>Outbound advice line</ListItem>
            <ListItem>Shipment line</ListItem>
            <ListItem>Cycle counting order line</ListItem>
            <ListItem>Adjustment order line</ListItem>
         </List>
         <Paragraph>These objects can include items from various owners, and some
		  of the items can be company owned. A separate ownership record is manually or
		  automatically created for each owner. For example, if a receipt line has
		  inventory for two owners, two ownership records are present for the receipt
		  line.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2580824">
         <Level1>ownership record</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000357">
      <Term>package definition</Term>
      <Definition>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.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000447" role="glossary">general-level package definition</Link>, <Link href="/baanerp/wh/glossary/glossary#000448" role="glossary">item-level package definition</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582080">
         <Level1>package definition</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="PackagItem_wh">
      <Term>packaging item</Term>
      <Definition>The containers or supports that are used to hold and move goods
		within manufacturing, distribution processes, and, specifically, within the
		warehouse. For example: boxes, pallets.</Definition>
      <Keyword type="glentry" order="d1e2582808">
         <Level1>packaging item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000358">
      <Term>packing list</Term>
      <Definition>A document that shows all shipments of a load.</Definition>
      <Keyword type="glentry" order="d1e2582129">
         <Level1>packing list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000359">
      <Term>packing slip</Term>
      <Definition>An order document that shows in detail the contents of a
		particular package for shipment. The details include a description of the
		items, the shippers or customers item number, the quantity shipped, and the
		inventory unit of the shipped items.</Definition>
      <Keyword type="glentry" order="d1e2582134">
         <Level1>packing slip</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2580940">
      <Term>Pay on Use</Term>
      <Definition>See: <Link href="#000466" role="internal">consigned</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000360">
      <Term>picking</Term>
      <Definition>The process of withdrawing from inventory the components to
		make the products or the finished goods to be shipped to a customer.</Definition>
      <Keyword type="glentry" order="d1e2582140">
         <Level1>picking</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000361">
      <Term>picking list</Term>
      <Definition>A document that lists the material to be picked for
		manufacturing or shipping orders. This document is used by operating personnel
		to pick manufacturing or shipping orders.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000360" role="glossary">picking</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582145">
         <Level1>picking list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000362">
      <Term>picking mission</Term>
      <Definition>A specific picking round performed by one employee or vehicle.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000360" role="glossary">picking</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582153">
         <Level1>picking mission</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000026">
      <Term>picking sequence</Term>
      <Definition>A sequence number used to print the picking list.</Definition>
      <Keyword type="glentry" order="d1e2581442">
         <Level1>picking sequence</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000364">
      <Term>pick location</Term>
      <Definition>The inventory location designated for order picking purposes. A
		pick location is mainly used for the outbound of small quantities and/or
		containers that can be replenished by bulk locations.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000314" role="glossary">bulk location</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582161">
         <Level1>pick location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000017">
      <Term>planned delivery date</Term>
      <Definition>The date for which delivery of a shipment is planned.</Definition>
      <Keyword type="glentry" order="d1e2581323">
         <Level1>planned delivery date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000012">
      <Term>planned inventory transactions</Term>
      <Definition>The expected changes in the inventory levels due to planned
		orders for items.</Definition>
      <Keyword type="glentry" order="d1e2581300">
         <Level1>planned inventory transactions</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000366">
      <Term>planned receipt</Term>
      <Definition>An anticipated receipt that corresponds to an open purchase
		order or open production order.</Definition>
      <Keyword type="glentry" order="d1e2582169">
         <Level1>planned receipt</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000409">
      <Term>planned receipt date</Term>
      <Definition>The date on which the goods are expected to arrive in the
		destination warehouse.</Definition>
      <Keyword type="glentry" order="d1e2582472">
         <Level1>planned receipt date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000457">
      <Term>planning priority rule</Term>
      <Definition>A user-defined condition that you can apply to a specific
		situation and a specific order, and that results in a priority figure when
		applied to a specific order. Aggregating the priority figures of all applicable
		priority rules results in a planning priority, which in turn is used as the
		system priority.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListItem>For cross-dock orders of type <GUIRef href="/baanerp/wh/domains/inh.cdty#dms" role="option">Direct Material Supply</GUIRef>, you can only use planning priority rules.</ListItem>
            <ListItem>In case of <GUIRef href="/baanerp/wh/domains/inh.cdty#dynamic" role="option">Dynamic</GUIRef> cross-docking, you can use either planning
			 priority rules or cross-dock order priority definitions.</ListItem>
         </List>
      </Note>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000019" role="glossary">cross-docking</Link>, <Link href="/baanerp/wh/glossary/glossary#000443" role="glossary">cross-dock order priority definition</Link>, <Link href="/baanerp/wh/glossary/glossary#000444" role="glossary">system priority</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581011">
         <Level1>planning priority rule</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000023">
      <Term>position (number)</Term>
      <Definition>The warehousing order line number. If the order is generated by
		a package other than <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>, this number is the same as the original order line number.</Definition>
      <Keyword type="glentry" order="d1e2581424">
         <Level1>position (number)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000367">
      <Term>product expiry date</Term>
      <Definition>The best-before date; the date up to which you can keep the
		goods.</Definition>
      <Keyword type="glentry" order="d1e2582174">
         <Level1>product expiry date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000410">
      <Term>production-order advice</Term>
      <Definition>A recommendation based on the economic stock and the reorder
		point of an item. Production order advices must be confirmed and transferred to
		convert them into actual production orders.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000318" role="glossary">economic stock</Link>, <Link href="/baanerp/wh/glossary/glossary#000374" role="glossary">reorder point</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582477">
         <Level1>production-order advice</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000435">
      <Term>projected on hand</Term>
      <Definition>The inventory on hand projected into the future, taking into
		account the planned inventory transactions.</Definition>
      <SimpleSection>
         <Paragraph>LN calculates the projected on hand as follows:</Paragraph>
         <Formula space-and-orientation="indented-estimated">
            <Paragraph>projected on hand = I - PI + PR</Paragraph>
            <FigLegend>
               <LegendEntry>
                  <Symbol>I</Symbol>
                  <Desc>Inventory on hand</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>PI</Symbol>
                  <Desc>Planned issues</Desc>
               </LegendEntry>
               <LegendEntry>
                  <Symbol>PR</Symbol>
                  <Desc>Planned receipts</Desc>
               </LegendEntry>
            </FigLegend>
         </Formula>
      </SimpleSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>You can view the planned inventory transactions in the <GUIRef href="/baanerp/wh/inp/whinp1500m000" role="session">Planned Inventory Transactions (whinp1500m000)</GUIRef> session.</Paragraph>
      </Note>
      <Keyword type="glentry" order="d1e2582711">
         <Level1>projected on hand</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000000000000025">
      <Term>purchase order advice</Term>
      <Definition>A recommendation based on the economic stock and the reorder
		point of an item. Purchase order advices must be confirmed and transferred to
		convert them into actual purchase orders.</Definition>
      <Keyword type="glentry" order="d1e2581200">
         <Level1>purchase order advice</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="QualifDemand_wh">
      <Term>qualified demand</Term>
      <Definition>The corrected demand during a specific period. The qualified
		demand is determined by the sales orders during that period.</Definition>
      <SimpleSection>
         <Paragraph>The qualified demand is used for forecasting purposes and is,
		  therefore, corrected for exceptional demands. So, if the demand forecast is
		  calculated, the exceptional demands are not taken into account.</Paragraph>
      </SimpleSection>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000018" role="glossary">demand forecast</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582813">
         <Level1>qualified demand</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000368">
      <Term>reason for blocking</Term>
      <Definition>The reason of the blocking. This reason can be linked to a
		blocking of a zone, location, lot, stockpoint, or serialized item.</Definition>
      <Keyword type="glentry" order="d1e2582179">
         <Level1>reason for blocking</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000369">
      <Term>reason for rejection</Term>
      <Definition>The reason why received goods did not pass the inspection.</Definition>
      <Keyword type="glentry" order="d1e2582184">
         <Level1>reason for rejection</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000373">
      <Term>receipt</Term>
      <Definition>The physical acceptance of an item into a warehouse. A receipt
		registers: received quantity, receipt date, packing-slip data, inspection data,
		and so on.</Definition>
      <Keyword type="glentry" order="d1e2582208">
         <Level1>receipt</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000370">
      <Term>receipt date</Term>
      <Definition>The date on which the items are actually received in the
		destination warehouse.</Definition>
      <Keyword type="glentry" order="d1e2582189">
         <Level1>receipt date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000372">
      <Term>receipt number</Term>
      <Definition>The sequence number assigned to every individual receipt of
		goods.</Definition>
      <Keyword type="glentry" order="d1e2582202">
         <Level1>receipt number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000411">
      <Term>receipt price</Term>
      <Definition>The price against which goods are received in the warehouse.</Definition>
      <Keyword type="glentry" order="d1e2582489">
         <Level1>receipt price</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000371">
      <Term>receiving location</Term>
      <Definition>The location in which the received goods are placed while they
		await the generation of an inbound advice.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000323" role="glossary">inbound advice</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582194">
         <Level1>receiving location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000462">
      <Term>reconciliation</Term>
      <Definition>The process of comparing inventory levels between the WMS and LN, analyzing the
		results, and processing any detected differences, preferably by correcting the
		related orders.</Definition>
      <Keyword type="glentry" order="d1e2580968">
         <Level1>reconciliation</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000056">
      <Term>re-executable activity</Term>
      <Definition>A session or manual step that can be executed more than once as
		part of a warehousing procedure. For example, a print session.</Definition>
      <Keyword type="glentry" order="d1e2581641">
         <Level1>re-executable activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000460">
      <Term>rejected inventory</Term>
      <Definition>Received inventory that is rejected during inspection and that
		you have not yet paid for. Therefore, you do not own rejected
		inventory.</Definition>
      <Keyword type="glentry" order="d1e2580981">
         <Level1>rejected inventory</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000412">
      <Term>reject location</Term>
      <Definition>A location in a warehouse in which the rejected goods are
		stored.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>From a reject location you can:</ListIntro>
            <ListItem>Accept the rejected goods</ListItem>
            <ListItem>Return the rejected goods to the buy-from business partner</ListItem>
            <ListItem>Destroy the rejected goods</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582494">
         <Level1>reject location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000374">
      <Term>reorder point</Term>
      <Definition>A set inventory level where, if the total stock on-hand plus
		total on-order falls below that point, action is taken to replenish the
		stock.</Definition>
      <Keyword type="glentry" order="d1e2582213">
         <Level1>reorder point</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000375">
      <Term>replenishment</Term>
      <Definition>The procedure in which inventory is transferred from one
		(location in the) warehouse to another because insufficient inventory is
		available at the destination (location of the) warehouse.</Definition>
      <Keyword type="glentry" order="d1e2582218">
         <Level1>replenishment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000321">
      <Term>replenishment matrix</Term>
      <Definition>The relations that define the replenishment of items from bulk
		locations or bulk zones to pick locations or pick zones in a warehouse.</Definition>
      <Keyword type="glentry" order="d1e2581818">
         <Level1>replenishment matrix</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000376">
      <Term>replenishment order</Term>
      <Definition>An order that transfers goods between two physical
		locations/warehouses.</Definition>
      <Keyword type="glentry" order="d1e2582223">
         <Level1>replenishment order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000028">
      <Term>routing sequence code</Term>
      <Definition>A priority code or number defining the position of the carrier
		in the sequence of carriers used for a shipment. Where more than one carrier is
		used, one must be first, the next is second, and so on.</Definition>
      <Keyword type="glentry" order="d1e2581452">
         <Level1>routing sequence code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000020">
      <Term>run number</Term>
      <Definition>A code assigned to a group of warehousing order lines when they
		are advised. LN assigns
		or generates a run number if a user does not manually enter or select a run
		number while he generates inbound or outbound advice for a group of warehousing
		order lines. This is the case if, for example, a user generates outbound advice
		by means of the <GUIRef href="/baanerp/wh/inh/whinh2120m000#generate.advice" role="command">Generate Advice</GUIRef> command in the <GUIRef href="/baanerp/wh/inh/whinh2120m000" role="session">Outbound Order Lines (whinh2120m000)</GUIRef> session. LN assigns run numbers
		by user. For example, all inbound advice generated by user A on a particular
		day obtain a particular run number, and those generated by user B obtain
		another run number. For outbound movements, the user can release outbound
		advice, generate picking lists, and confirm picking lists by run. For inbound
		movements, the user can generate storage lists and confirm storage lists by
		run.</Definition>
      <Keyword type="glentry" order="d1e2581402">
         <Level1>run number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000377">
      <Term>safety stock</Term>
      <Definition>The buffer inventory necessary to meet fluctuations in demand
		and delivery lead time. In general, safety stock is a quantity of inventory
		planned to be in inventory to protect against fluctuations in demand or supply.
		In the context of master production scheduling, safety stock is the additional
		inventory and capacity planned as protection against forecast errors and
		short-term changes in the backlog.</Definition>
      <Keyword type="glentry" order="d1e2582228">
         <Level1>safety stock</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000046">
      <Term>seal number</Term>
      <Definition>The number on the shipments seal.</Definition>
      <Keyword type="glentry" order="d1e2581551">
         <Level1>seal number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000024">
      <Term>sequence number</Term>
      <Definition>The sequence number of the warehousing order line.</Definition>
      <Keyword type="glentry" order="d1e2581432">
         <Level1>sequence number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000461">
      <Term>serial price</Term>
      <Definition>An inventory valuation method for accounting purposes that is
		used to separately calculate the price or cost price for each <Link href="/baanerp/wh/onlinemanual/000382#382_low_volume" role="manual" Update="No">low volume</Link> serialized item. The serial price is based on the
		actual receipt price.</Definition>
      <Keyword type="glentry" order="d1e2580973">
         <Level1>serial price</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000413">
      <Term>serial-shipping container code (SSCC)</Term>
      <Definition>A code that is used to identify a handling unit. SSCC is a
		non-significant number with a fixed length (18 digits), which does not contain
		any classifying elements.</Definition>
      <Abbreviation>SSCC</Abbreviation>
      <Keyword type="glentry" order="d1e2582509">
         <Level1>serial-shipping container code (SSCC)</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2582509">
         <Level1>SSCC</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000039">
      <Term>shelf life</Term>
      <Definition>The amount of time an item may be held in inventory without
		deterioration in quality.</Definition>
      <Keyword type="glentry" order="d1e2581508">
         <Level1>shelf life</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000059">
      <Term>ship-from code</Term>
      <Definition>A code used, together with the ship-from type, to identify the
		exact source of a warehousing order.</Definition>
      <Keyword type="glentry" order="d1e2581671">
         <Level1>ship-from code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000058">
      <Term>ship-from type</Term>
      <Definition>The ship-from type is used, together with the ship-from code,
		to identify the exact source of a warehousing order.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The ship-from 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>
      <Keyword type="glentry" order="d1e2581646">
         <Level1>ship-from type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000021">
      <Term>shipment</Term>
      <Definition>All goods that are transported to a specific address on a
		specific date and time by using a specific route. An identifiable part of a
		load.</Definition>
      <Keyword type="glentry" order="d1e2581413">
         <Level1>shipment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000054">
      <Term>shipment line</Term>
      <Definition>An individual line of detail in a shipment.</Definition>
      <Keyword type="glentry" order="d1e2581636">
         <Level1>shipment line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2581724">
      <Term>shipment notice</Term>
      <Definition>See: <Link href="#000308" role="internal">advance shipment notice</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000438">
      <Term>shipment reference</Term>
      <Definition>Identifies a group of items that are called off at the same
		time.</Definition>
      <Keyword type="glentry" order="d1e2582785">
         <Level1>shipment reference</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000378">
      <Term>shipping</Term>
      <Definition>The function that provides facilities for the outgoing shipment
		of parts, products, and components. Shipping includes packaging, marking,
		weighing, and loading for shipment and the printing of the shipment documents.</Definition>
      <Keyword type="glentry" order="d1e2582233">
         <Level1>shipping</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000485">
      <Term>shipping container</Term>
      <Definition>A subdivision of a <Link href="/baanerp/wh/glossary/glossary#000022" role="glossary">load</Link> that contains shipments. The packaging items defined for a container determines
		the type of container.</Definition>
      <Keyword type="glentry" order="d1e2580724">
         <Level1>shipping container</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000487">
      <Term>shipping manifest</Term>
      <Definition>A shipping document that describes the content of the shipping
		structure consisting of loads, shipments, and, if implemented, containers,
		created for a warehousing order or order set. The shipping structure can
		contain separate items or items included in BOM or kit structures.</Definition>
      <Keyword type="glentry" order="d1e2580714">
         <Level1>shipping manifest</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000048">
      <Term>ship-to code</Term>
      <Definition>A code used, together with the ship-to type, to identify where
		goods are shipped to.</Definition>
      <Keyword type="glentry" order="d1e2581582">
         <Level1>ship-to code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000047">
      <Term>ship-to type</Term>
      <Definition>The ship-to type is used, together with the ship-to code, to
		identify where goods are shipped to.</Definition>
      <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>
      <Keyword type="glentry" order="d1e2581557">
         <Level1>ship-to type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000380">
      <Term>slow-moving analysis</Term>
      <Definition>A method of analyzing the inventory, based on the turnover of
		items. Items with a low turnover (slow moving items) have a relatively low rate
		of usage compared to the normal amount of inventory carried.</Definition>
      <Keyword type="glentry" order="d1e2582243">
         <Level1>slow-moving analysis</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000379">
      <Term>slow-moving percentage</Term>
      <Definition>The limit up to which an item is identified as a slow moving
		item.</Definition>
      <Keyword type="glentry" order="d1e2582238">
         <Level1>slow-moving percentage</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2582514">
      <Term>SSCC</Term>
      <Definition>See: <Link href="#000413" role="internal">serial-shipping container code (SSCC)</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000381">
      <Term>staging location</Term>
      <Definition>A shipping dock in the warehouse where items are held just
		before they are placed on any means of transport for shipment.</Definition>
      <Keyword type="glentry" order="d1e2582248">
         <Level1>staging location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000382">
      <Term>stockpoint</Term>
      <Definition>The smallest inventory level that can be registered in LN.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The stockpoint is defined by the following data:</ListIntro>
            <ListItem>Warehouse</ListItem>
            <ListItem>Location: only if you have locations</ListItem>
            <ListItem>Item</ListItem>
            <ListItem>Inventory date: important if you work with LIFO or FIFO</ListItem>
            <ListItem>Lot: only if the item is lot controlled</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582253">
         <Level1>stockpoint</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000383">
      <Term>storage condition</Term>
      <Definition>A condition that must be satisfied to store goods. Storage
		conditions must be linked to item(group)s and to warehouse locations to prevent
		storage of items at unsuitable locations.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>Storage can be performed in two ways:</ListIntro>
            <ListItem>By item, by excluding unsuitable locations</ListItem>
            <ListItem>By location, by excluding undesirable items</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582272">
         <Level1>storage condition</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000384">
      <Term>storage list</Term>
      <Definition>The document that states the warehouse or locations where goods
		are to be stored. A storage list is used by warehouse personnel to place the
		received items in the right location within the warehouse.</Definition>
      <Keyword type="glentry" order="d1e2582286">
         <Level1>storage list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000002">
      <Term>storage mission</Term>
      <Definition>A specific storage round carried out by one employee or one
		vehicle.</Definition>
      <Keyword type="glentry" order="d1e2581234">
         <Level1>storage mission</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000040">
      <Term>storage unit</Term>
      <Definition>The unit in which the quantity of goods stored is expressed.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Storage unit: box</Paragraph>
         <Paragraph>Inventory unit: liter</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e2581513">
         <Level1>storage unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000486">
      <Term>subkit</Term>
      <Definition>A phantom item that represent a number of component items or a
		main item for a (sub-) assembly.</Definition>
      <Keyword type="glentry" order="d1e2580719">
         <Level1>subkit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000484">
      <Term>supply order</Term>
      <Definition>An order, usually a production order or a purchase order, that
		contains a quantity of a particular item needed to fulfill a <Link href="/baanerp/wh/glossary/glossary#000483" role="glossary">demand order</Link>.</Definition>
      <Keyword type="glentry" order="d1e2580732">
         <Level1>supply order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000417">
      <Term>supply quantity</Term>
      <Definition>The quantity that must be supplied to a shop floor warehouse.</Definition>
      <Keyword type="glentry" order="d1e2582541">
         <Level1>supply quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000418">
      <Term>supply sequence</Term>
      <Definition>The sequence in which the items must be supplied to the shop
		floor warehouse.</Definition>
      <Keyword type="glentry" order="d1e2582546">
         <Level1>supply sequence</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc1" ContextApps="wh" ID="000419">
      <Term>supply system</Term>
      <Definition>The system that is used to coordinate the timely supply of
		goods to the production lines or assembly lines.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The following supply systems are available in LN:</ListIntro>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/sups#tpop" role="option">Time-Phased Order Point</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/sups#kanban" role="option">KANBAN</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/sups#batch" role="option">Order Controlled/Batch</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/sups#sils" role="option">Order Controlled/SILS</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/tc/domains/sups#single" role="option">Order Controlled/Single</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582551">
         <Level1>supply system</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000420">
      <Term>supply type</Term>
      <Definition>The type of the source that supplies the items.</Definition>
      <SimpleSection>
         <List>
            <ListIntro> LN distinguishes three supply types:</ListIntro>
            <ListItem>
               <GUIRef href="/baanerp/wh/domains/wmd.supt#supplier" role="option">Supplier</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/wh/domains/wmd.supt#warehouse" role="option">Warehouse</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/wh/domains/wmd.supt#workcenter" role="option">Workcenter</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2582580">
         <Level1>supply type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000421">
      <Term>supply warehouse</Term>
      <Definition>The warehouse that supplies goods and materials to the shop
		floor warehouse.</Definition>
      <Keyword type="glentry" order="d1e2582598">
         <Level1>supply warehouse</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" Version="B60asy05" ID="000444">
      <Term>system priority</Term>
      <Definition>A priority that is based on the planning priority rules or the
		cross-dock order priorities. LN uses the system priority along with the user priority to determine
		a cross-dock order's priority. LN generates cross-dock order lines and, during inbound advice,
		advise cross-dock order lines for cross-dock orders with the highest priority
		first.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListItem>If you use planning priority rules, in case of <GUIRef href="/baanerp/wh/domains/inh.cdty#dms" role="option">Direct Material Supply</GUIRef> and, optionally, in case of <GUIRef href="/baanerp/wh/domains/inh.cdty#dynamic" role="option">Dynamic</GUIRef> cross-docking, the system priority of generated
			 cross-dock orders matches the planning priority.</ListItem>
            <ListItem>For cross-dock orders of type <GUIRef href="/baanerp/wh/domains/inh.cdty#dms" role="option">Direct Material Supply</GUIRef>, the system priority is used as default value for the user
			 priority.</ListItem>
            <ListItem>The user priority is taken into account before the system
			 priority.</ListItem>
         </List>
      </Note>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000445" role="glossary">user priority</Link>, <Link href="/baanerp/wh/glossary/glossary#000443" role="glossary">cross-dock order priority definition</Link>, <Link href="/baanerp/wh/glossary/glossary#000457" role="glossary">planning priority rule</Link>, <Link href="/baanerp/wh/glossary/glossary#000458" role="glossary">direct material supply</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581146">
         <Level1>system priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000424">
      <Term>time-phased order point</Term>
      <Definition>A push system that regulates the time-phased supply of items to
		warehouses.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The quantity of items that is supplied to the warehouse
			 depends on:</ListIntro>
            <ListItem>The available inventory in the warehouse.</ListItem>
            <ListItem>The inventory that is planned to be delivered to the
			 warehouse within the specified order horizon.</ListItem>
            <ListItem>The specified safety stock, optionally adjusted to the
			 seasonal factor for the current period, for the item and warehouse.</ListItem>
         </List>
         <Paragraph>If the available inventory plus the planned inventory are
		  below the reorder point, the inventory in the warehouse is replenished.</Paragraph>
      </SimpleSection>
      <Abbreviation>TPOP</Abbreviation>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000377" role="glossary">safety stock</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582603">
         <Level1>time-phased order point</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2582603">
         <Level1>TPOP</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000489">
      <Term>topkit</Term>
      <Definition>An item representing a group of items that make up a set, for
		example, an airplane modification set consisting of the materials and tools to
		convert a passenger plane to a freight carrier plane, or the end-item - the
		highest level - of a <Link href="/baanerp/ti/glossary/glossary#BillOfMateri_ti" role="glossary">bill of material (BOM)</Link> of a manufactured item. A topkit consists of various <Link href="/baanerp/wh/glossary/glossary#000486" role="glossary">subkits</Link>.</Definition>
      <Keyword type="glentry" order="d1e2580698">
         <Level1>topkit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2582620">
      <Term>TPOP</Term>
      <Definition>See: <Link href="#000424" role="internal">time-phased order point</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000472">
      <Term>transaction date</Term>
      <Definition>The date and time on which the inventory transaction was
		processed. In case of antedating, the transaction date (= receipt date)
		precedes the <Emphasis>actual log date</Emphasis>.</Definition>
      <Keyword type="glentry" order="d1e2581066">
         <Level1>transaction date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000385">
      <Term>transfer</Term>
      <Definition>The transfer of goods from one warehouse to another (possibly
		including such activities as repacking).</Definition>
      <Keyword type="glentry" order="d1e2582291">
         <Level1>transfer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000304">
      <Term>transfer order</Term>
      <Definition>A type of warehousing order that is created to register
		inventory transactions from a replenishing warehouse to a destination
		warehouse. A transfer order can be generated by other packages/modules in LN or defined manually.</Definition>
      <Keyword type="glentry" order="d1e2581702">
         <Level1>transfer order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000426">
      <Term>trigger-from station</Term>
      <Definition>The line station from which the supply of items is triggered.</Definition>
      <Keyword type="glentry" order="d1e2582625">
         <Level1>trigger-from station</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy05" ContextApps="wh" ID="000445">
      <Term>user priority</Term>
      <Definition>A priority that is entered by the user. LN uses the user
		priority along with the system priority to determine a cross-dock order's
		priority. LN will
		generate cross-dock order lines and, during inbound advice, advise cross-dock
		order lines for cross-dock orders with the highest priority first.</Definition>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>The user priority is taken into account before the system
		  priority.</Paragraph>
      </Note>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000444" role="glossary">system priority</Link>, <Link href="/baanerp/wh/glossary/glossary#000458" role="glossary">direct material supply</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2581183">
         <Level1>user priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000387">
      <Term>variable lot feature</Term>
      <Definition>The lot features that apply to some lots but not to others and
		are, therefore, not defined in the general lot data but are assigned to
		individual items.</Definition>
      <Keyword type="glentry" order="d1e2582301">
         <Level1>variable lot feature</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000469">
      <Term>vendor managed inventory (VMI)</Term>
      <Definition>Vendor managed inventory is an inventory management method
		according to which the supplier usually manages the inventory of his customer
		or subcontractor. Sometimes, the supplier manages the supply planning as well.
		Alternatively, the customer manages the inventory but the supplier is
		responsible for supply planning. Inventory management or inventory planning can
		also be subcontracted to a logistics service provider (LSP).</Definition>
      <SimpleSection>
         <Paragraph>The supplier or the customer may own the inventory delivered
		  by the supplier. Often, the ownership of the inventory changes from the
		  supplier to the customer when the customer consumes the inventory, but other
		  ownership transfer moments occur, which are laid down by contract.</Paragraph>
         <Paragraph>Vendor-managed inventory reduces internal costs associated
		  with planning and procuring materials and enables the vendor to better manage
		  his inventory through higher visibility to the supply chain.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2580880">
         <Level1>vendor managed inventory (VMI)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000471">
      <Term>VMI warehouse</Term>
      <Definition>A warehouse for which the supplier of the stored goods
		performs one or both of the following tasks: manage the warehouse, including
		activities surrounding inbound and outbound processes, or plan the supply of
		the goods in the warehouse. The supplier may also be the owner of the inventory
		in the warehouse. The warehouse is usually located at the customer's premises.</Definition>
      <Keyword type="glentry" order="d1e2580859">
         <Level1>VMI warehouse</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000302">
      <Term>warehouse address</Term>
      <Definition>The address of the warehouse or place where the goods must be
		delivered.</Definition>
      <Keyword type="glentry" order="d1e2581697">
         <Level1>warehouse address</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000427">
      <Term>warehouse-from</Term>
      <Definition>The warehouse from which the issue will take place.</Definition>
      <Keyword type="glentry" order="d1e2582631">
         <Level1>warehouse-from</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e2582341">
      <Term>warehouse order</Term>
      <Definition>See: <Link href="#000388" role="internal">warehousing order</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry ContextApps="wh" ID="000459">
      <Term>warehouse supply structure</Term>
      <Definition>Defined for direct material supply, a user-specific cluster of
		warehouses, which consists of one or more supply warehouses and a number of
		destination warehouses.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000458" role="glossary">direct material supply</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2580986">
         <Level1>warehouse supply structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000428">
      <Term>warehouse-to</Term>
      <Definition>The warehouse in which the receipt will take place.</Definition>
      <Keyword type="glentry" order="d1e2582636">
         <Level1>warehouse-to</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000449">
      <Term>warehouse valuation group</Term>
      <Definition>An entity that is used to group warehouses for inventory
		valuation purposes. To define a warehouse valuation group, you must link a
		warehouse valuation group code to the warehouses that you want to include in
		the warehouse valuation group. Warehouse valuation groups and item valuation
		groups are linked, for example, to inventory valuation methods to valuate the
		item-warehouse combinations included in the warehouse and item valuation
		groups.</Definition>
      <CrossRef>
         <Link href="/baanerp/wh/glossary/glossary#000450" role="glossary">item valuation group</Link>
      </CrossRef>
      <Keyword type="glentry" order="d1e2582113">
         <Level1>warehouse valuation group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000041">
      <Term>warehousing</Term>
      <Definition>All actions related to the receipt, storage, treatment, and
		issuing of goods within a warehouse.</Definition>
      <SimpleSection>
         <Paragraph>The <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> package coordinates all transactions of goods in the
		  warehouses by using warehousing orders. This relates to inbound and outbound of
		  goods, transfer of goods, cycle counting of goods, ABC analysis, inventory
		  commitments, and various kinds of inventory reporting.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e2581525">
         <Level1>warehousing</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000005">
      <Term>warehousing assembly order</Term>
      <Definition>A commission to assemble the components of an end item.</Definition>
      <Keyword type="glentry" order="d1e2581268">
         <Level1>warehousing assembly order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000388">
      <Term>warehousing order</Term>
      <Definition>An order for handling goods in the warehouse.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>A warehouse order can be of the following
			 inventory-transaction types:</ListIntro>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/inh.ittp#receipt" role="option">Receipt</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/inh.ittp#issue" role="option">Issue</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/wh/domains/inh.ittp#transfer" role="option">Transfer</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/wh/domains/inh.ittp#wip.transfer" role="option">WIP Transfer</GUIRef>
            </ListItem>
         </List>
         <Paragraph>Each order has an origin and contains all the information
		  required for warehouse handling. Depending on the item (lot or non-lot) and
		  warehouse (with or without locations), lots and/or locations can be assigned.
		  The order follows a predefined warehousing procedure.</Paragraph>
      </SimpleSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>In <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef> a warehousing order is often called a
		  warehouse order.</Paragraph>
      </Note>
      <Synonym>warehouse order</Synonym>
      <Keyword type="glentry" order="d1e2582306">
         <Level1>warehousing order</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e2582306">
         <Level1>warehouse order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000429">
      <Term>warehousing-order line</Term>
      <Definition>A generic term for inbound order lines and outbound order
		lines.</Definition>
      <Keyword type="glentry" order="d1e2582641">
         <Level1>warehousing-order line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000052">
      <Term>warehousing-order number</Term>
      <Definition>The code of the warehousing order. If the order is generated by
		another package, this number will correspond to the original order number.</Definition>
      <Keyword type="glentry" order="d1e2581618">
         <Level1>warehousing-order number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000009">
      <Term>warehousing order type</Term>
      <Definition>A code that identifies the type of a warehousing order. The
		default warehousing procedure that you link to a warehousing order type
		determines how the warehousing orders to which the order type is allocated are
		processed in the warehouse, although you can modify the default procedure for
		individual warehousing orders or order lines.</Definition>
      <Keyword type="glentry" order="d1e2581290">
         <Level1>warehousing order type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000007">
      <Term>warehousing procedure</Term>
      <Definition>A procedure to handle warehousing orders and handling units. A
		warehousing procedure comprises various steps, also called activities, that a
		warehousing order or a handling unit must take to be received, stored,
		inspected, or issued. A warehousing procedure is linked to a warehousing order
		type, which in turn is allocated to warehousing orders.</Definition>
      <Keyword type="glentry" order="d1e2581273">
         <Level1>warehousing procedure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="wh" ID="000430">
      <Term>zero receipt</Term>
      <Definition>A receipt line with quantity zero.</Definition>
      <Keyword type="glentry" order="d1e2582646">
         <Level1>zero receipt</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60adoc0" ContextApps="wh" ID="000389">
      <Term>zone</Term>
      <Definition>A part of the warehouse that can be assigned to specific
		employees or vehicles. Each location can be assigned to a zone.</Definition>
      <Keyword type="glentry" order="d1e2582343">
         <Level1>zone</Level1>
      </Keyword>
   </GlossaryEntry>
</Glossary>