<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/inh/whinh5240m000" xml:lang="en">
   <Header>
      <Title>Remove Unused Cycle Counting Data (whinh5240m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to delete cycle counting
		  data that you will not use anymore.</Paragraph>
         <Paragraph>This session deletes cycle counting data for items if the stock point
		  is no longer present. This can be useful if the cycle counting data contains a
		  large quantity of stock point history data that should not be counted anymore
		  (because a stock point with that particular inventory date will no longer be
		  created).</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>The following restrictions are applicable:</Paragraph>
         <List>
            <ListItem>Cycle counting data is not deleted if the <GUIRef href="/baanerp/wh/inh/whinh5140m000#whinh540.fcnt" role="manual">Force Cycle Count</GUIRef> option in the <GUIRef href="/baanerp/wh/inh/whinh5140m000" role="session">Cycle Counting Data (whinh5140m000)</GUIRef> session is selected.</ListItem>
            <ListItem>Cycle counting data is not deleted if an active cycle
			 counting order is present for the stock point.</ListItem>
         </List>
         <Paragraph>To print a report on the cycle count data that you remove
		  using this session, select the <GUIRef href="/baanerp/wh/inh/whinh5240m000#pr.cc.data" role="manual">Removed Cycle Counting Data</GUIRef> check box.</Paragraph>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="pr.cc.data">
         <Header>
            <Title>Removed Cycle Counting Data</Title>
         </Header>
         <FuncDesc>If this check box is selected, a report on the cycle count data that you
		  remove using this session is printed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cwar.f">
         <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="cwar.t">
         <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="loca.f">
         <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="loca.t">
         <Header>
            <Title>Location</Title>
         </Header>
         <FuncDesc>
            <Link href="/baanerp/wh/glossary/glossary#000013" role="glossary">location</Link> 
            <Link href="/baanerp/wh/glossary/glossary#000343" role="glossary">lot</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="clot.f">
         <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="clot.t">
         <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="date.f">
         <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="date.t">
         <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="item.f">
         <Header>
            <Title>From 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="item.t">
         <Header>
            <Title>To 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>
   </Fields>
   <FormCommands>
      <CommandHelp ID="exec.cont.process">
         <Header>
            <Title>Continue</Title>
         </Header>
         <FuncDesc>Use this command to start the cycle counting removal
		  process.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>