<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/inr/whinr1550m100" xml:lang="en">
   <Header>
      <Title>Item - Inventory Structure (whinr1550m100)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to keep
		  track of the inventory structure. You can see per item and warehouse which
		  quantities are stored in which locations.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>In this session you
		  can only select the location from or to which deviations of the packing-slip
		  quantity are subtracted or added.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>You can only start
			 this session from the <GUIRef href="/baanerp/wh/inh/whinh3121s000#new.location" role="manual">Adjust Location</GUIRef> field of the <GUIRef href="/baanerp/wh/inh/whinh3121s000" role="session">Receipt Correction (whinh3121s000)</GUIRef> session.</Paragraph>
         </Note>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="whinr150.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>In ERP Enterprise,
		the raw materials, subassemblies, finished products, and tools that can be
		purchased, stored, manufactured, sold, and so on.</FuncDesc>
         <SimpleSection>
            <Paragraph>An item can also represent a set of items handled as one kit,
		  or exist in multiple product variants.</Paragraph>
            <List>
               <ListIntro>You can also define nonphysical items, which are not held
			 in inventory but can be used to post costs or to invoice services to customers.
			 The following are examples of nonphysical items:</ListIntro>
               <ListItem>Cost items (for example, electricity)</ListItem>
               <ListItem>Service items</ListItem>
               <ListItem>Subcontracting services</ListItem>
               <ListItem>List items (menus/options)</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinr150.cwar">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>A place for storing goods. For each warehouse, you can enter
		address data and data relating to its type.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr150.loca">
         <Header>
            <Title>Location</Title>
         </Header>
         <FuncDesc>A distinct place in a warehouse where goods are stored.</FuncDesc>
         <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>
      </FieldHelp>
      <FieldHelp ID="whinr150.idat">
         <Header>
            <Title>Inventory Date</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
         <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>
      </FieldHelp>
      <FieldHelp ID="whinr150.pkdf">
         <Header>
            <Title>Package Definition</Title>
         </Header>
         <FuncDesc>A particular configuration of items and their packaging. A
		package definition for an item can, for example, be the following: a pallet
		contains 12 boxes and each box contains 4 pieces.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr150.levl">
         <Header>
            <Title>Level</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/wh/glossary/glossary#000357" role="glossary">package definition</Link> level of
		  the item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr150.qhds">
         <Header>
            <Title>Inventory on Hand (Storage Unit)</Title>
         </Header>
         <FuncDesc>The physical quantity of goods in one or more warehouses
		(including the inventory on hold).</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr150.cuni">
         <Header>
            <Title>Unit</Title>
         </Header>
         <FuncDesc>The unit of measure in which the inventory of an item is
		recorded, such as piece, kilogram, box of 12, or meter.</FuncDesc>
         <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>
      </FieldHelp>
   </Fields>
</Session>