<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/inr/whinr1558m000" xml:lang="en">
   <Header>
      <Title>Inventory Ownership of not Shipped Goods (whinr1558m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view the ownership of
		  unshipped items. Unshipped items are displayed in this session if the ownership
		  registration level for the warehouse and the item is <GUIRef href="/baanerp/tc/domains/owrl#location" role="option">Location</GUIRef> or <GUIRef href="/baanerp/tc/domains/owrl#phys.item.loc" role="option">Physical Item and Location</GUIRef>.</Paragraph>
         <Paragraph>The items shown in this session are staged goods that are not
		  shipped for some reason but stay on the staging location. These goods can be
		  returned to the pick or bulk location by an internal warehouse transfer, or
		  allocated to another order line.</Paragraph>
         <Paragraph>If the ownership registration level is by location, the
		  ownership information is registered for pick or bulk locations, but not for
		  staging locations. Because the ownership information is lost for unshipped
		  goods after the shipment is confirmed, the ownership information for unshipped
		  goods is stored in this session.</Paragraph>
         <Paragraph>When ERP Enterprise creates outbound advice ownership records for an internal
		  warehouse transfer that transfers goods from the staging location to a pick or
		  bulk location and the ownership registration level is by location, ERP Enterprise retrieves the
		  ownership information from this session. When the outbound advice is generated
		  and the outbound advice ownership records are created, the allocated quantity
		  is increased in this session. After the outbound advice for an internal
		  warehouse transfer is released, the staged quantity and the allocated quantity
		  in this session is decreased accordingly.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/000460" role="manual">Ownership registration setup in Warehousing</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/000478" role="manual">Ownership records</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/000373" role="manual">Inbound and outbound procedures</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/wmd00310" role="manual">Using locations</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="whinr158.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="tcmcs003.dsca">
         <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="whinr158.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="tcibd001.dsca">
         <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="whinr158.clot">
         <Header>
            <Title>Lot</Title>
         </Header>
         <FuncDesc>A number of items produced and stored together that are
		identified by a (lot) code. Lots identify goods.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr158.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="whinr158.loca">
         <Header>
            <Title>Staging Location</Title>
         </Header>
         <FuncDesc>A shipping dock in the warehouse where items are held just
		before they are placed on any means of transport for shipment.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd300.loct">
         <Header>
            <Title>Staging Location</Title>
         </Header>
         <FuncDesc>A shipping dock in the warehouse where items are held just
		before they are placed on any means of transport for shipment.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr158.ownr">
         <Header>
            <Title>Owner</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#BusinePartne_tc" role="glossary">business partner</Link> who owns the
		  items.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr158.owns">
         <Header>
            <Title>Ownership</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
         <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>
      </FieldHelp>
      <FieldHelp ID="whinr158.qhnd">
         <Header>
            <Title>Inventory on Hand</Title>
         </Header>
         <FuncDesc>The physical quantity of goods in one or more warehouses
		(including the inventory on hold).</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcibd001.cuni">
         <Header>
            <Title>Inventory on Hand</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Units_tc" role="glossary">unit</Link> used to express the <Link href="/baanerp/wh/glossary/glossary#000330" role="glossary">inventory on hand</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr158.qlal">
         <Header>
            <Title>Inventory Allocated</Title>
         </Header>
         <FuncDesc>The inventory that is allocated to an order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinr158.serl">
         <Header>
            <Title>Serial Number</Title>
         </Header>
         <FuncDesc>The unique identification of a single physical item. ERP Enterprise 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>