<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/inr/whinr1500m000" xml:lang="en">
   <Header>
      <Title>Warehouse - Item - Stock Point Transactions (whinr1500m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to display inventory
		  transactions by item and warehouse.</Paragraph>
      </AimSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>To view only inventory transactions that resulted from either
		  the <GUIRef href="/baanerp/wh/inr/whinr1250m000" role="session">Easy Inventory Movement (whinr1250m000)</GUIRef> session or the <GUIRef href="/baanerp/wh/inr/whinr1252m000" role="session">Easy Inventory Movement (Range) (whinr1252m000)</GUIRef> session, you can create a filter
		  using the following condition: <GUIRef href="/baanerp/wh/inr/whinr1500s000#whinr100.inmv" role="manual">Internal Move</GUIRef> is (exactly) <GUIRef href="/baanerp/tc/domains/yesno.ync#yes" role="option">Yes</GUIRef>.</Paragraph>
      </Note>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/000020" role="manual">Inventory reporting</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="whinr100.cwar">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>The code of the <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr100.loca">
         <Header>
            <Title>Location</Title>
         </Header>
         <FuncDesc>The code of the inventory <Link href="/baanerp/wh/glossary/glossary#000013" role="glossary">location</Link> within a warehouse.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr100.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>In LN,
		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.
			 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="tcibd001.cuni">
         <Header>
            <Title>Inventory 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>
      <FieldHelp ID="whinr100.idat">
         <Header>
            <Title>Inventory Date</Title>
         </Header>
         <FuncDesc>The date assigned to the item when it was stored. If the item
		  has a particular shelf life, the inventory date is the <Link href="/baanerp/ti/glossary/glossary#ProducExpiry_ti" role="glossary">product expiry date</Link> defined
		  for the item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr100.trdt">
         <Header>
            <Title>Transaction Date</Title>
         </Header>
         <FuncDesc>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>.</FuncDesc>
         <SimpleSection>
            <Paragraph>You cannot change this date.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinr100.kost">
         <Header>
            <Title>Transaction Type</Title>
         </Header>
         <FuncDesc>A classification that is used to indicate the type of inventory
		movement.</FuncDesc>
         <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>
      </FieldHelp>
      <FieldHelp ID="whinr100.qstk">
         <Header>
            <Title>Quantity</Title>
         </Header>
         <FuncDesc>The quantity with wich the inventory is adjusted.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr100.koor">
         <Header>
            <Title>Order Origin</Title>
         </Header>
         <FuncDesc>A group of orders that are processed according to the same
		procedure (series of order steps = sessions). In addition, these orders share a
		number of other characteristics (return order y/n, collect order y/n,
		subcontracting order y/n, and so on).</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr100.qhnd">
         <Header>
            <Title>Inventory After Transaction</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/wh/glossary/glossary#000330" role="glossary">inventory on hand</Link> available after the inventory
		  transaction.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr100.clot">
         <Header>
            <Title>Lot</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/wh/glossary/glossary#000343" role="glossary">lot's</Link> code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr100.serl">
         <Header>
            <Title>Serial Number</Title>
         </Header>
         <FuncDesc>The unique identification of a single physical item. LN uses a mask to
		generate the serial number. The serial number can consist of multiple data
		segments that represent, for example, a date, model and color information,
		sequence number, and so on.</FuncDesc>
         <SimpleSection>
            <Paragraph>Serial numbers can be generated for items and for tools.</Paragraph>
         </SimpleSection>
      </FieldHelp>
   </Fields>
</Session>