<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/wmd/whwmd6140m000" xml:lang="en">
   <Header>
      <Title>Blocked Handling Units (whwmd6140m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to to block or unblock <Link href="/baanerp/wh/glossary/glossary#000432" role="glossary">handling units</Link>.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/000000000000041" role="manual">To block and unblock</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="whwmd640.huid">
         <Header>
            <Title>Handling Unit</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/wh/glossary/glossary#000432" role="glossary">handling unit</Link> number that is
		  used to uniquely identify the handling unit in LN.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd530.hust">
         <Header>
            <Title>Status</Title>
         </Header>
         <FuncDesc>The handling unit's status.</FuncDesc>
         <SimpleSection>
            <Paragraph>
               <Link href="/baanerp/wh/domains/hust" role="domain">Handling Unit Status</Link>
            </Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whwmd640.bloc">
         <Header>
            <Title>Reason for Blocking</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tf/glossary/glossary#000101" role="glossary">reason code</Link> (of type <GUIRef href="/baanerp/tc/domains/mcs.rstp#blocking" role="option">Inventory Blocking excluding EP</GUIRef> or <GUIRef href="/baanerp/tc/domains/mcs.rstp#blocking.irp" role="option">Inventory Blocking including EP</GUIRef>) as defined in the <GUIRef href="/baanerp/tc/mcs/tcmcs0105m000" role="session">Reasons (tcmcs0105m000)</GUIRef> session.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/wh/onlinemanual/000000000000041#incl_excl_EP" role="manual"
                     Update="No">Inventory blocking including or excluding EP</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="whwmd640.logn">
         <Header>
            <Title>User</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#000068" role="glossary">logon code</Link> of the employee who activates a blocking. Only
		  the user who activated a block can remove it</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd640.date">
         <Header>
            <Title>Date</Title>
         </Header>
         <FuncDesc>The date and time of the blocking action.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whwmd530.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="whwmd530.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="whwmd530.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="whwmd530.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="whwmd530.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>
   </Fields>
</Session>