<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/inh/whinh5557m000" xml:lang="en">
   <Header>
      <Title>Cycle Counting Order Line Project Data History (whinh5557m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view the history of
		  projects for which an inventory variance occurs. The project data is specified
		  for warehouses of the <GUIRef href="/baanerp/tc/domains/typw#project" role="option">Project</GUIRef> type.</Paragraph>
      </AimSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="whinh557.orno">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>The number of the <Link href="/baanerp/wh/glossary/glossary#000036" role="glossary">cycle-count order</Link> or the <Link href="/baanerp/wh/glossary/glossary#000000000000018" role="glossary">inventory adjustment order</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh557.cntn">
         <Header>
            <Title>/</Title>
         </Header>
         <FuncDesc>The number of counts that are performed on one or more lines of
		  this order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh557.pono">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc>The warehousing order line number. If the order is generated by
		a package other than <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>, this number is the same as the original order line number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh557.prsn">
         <Header>
            <Title>Sequence</Title>
         </Header>
         <FuncDesc>The sequence umber of the project record.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh557.trdt">
         <Header>
            <Title>Transaction Date</Title>
         </Header>
         <FuncDesc>The date on which the order is changed and/or written to the
		history file. For each change, LN inserts a new line and a new transaction date. This applies to any
		type of order.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Among other things, the transaction date is important for:</ListIntro>
               <ListItem>Scheduling</ListItem>
               <ListItem>Statistics</ListItem>
               <ListItem>Determining due dates and currency exchange rates</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh557.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>An endeavor with a specific objective to be met within the
		prescribed time and financial limitation, and that has been assigned for
		definition or execution.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh557.cspa">
         <Header>
            <Title>Element</Title>
         </Header>
         <FuncDesc>The smallest part of an element structure. An element is used
		to define the (structure of the) work of the project, so that you can carry it
		out.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh557.cact">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>The smallest part of the activity structure used for a
		time-scaled budget. An entity that is used to represent a part of a project in
		an activity structure.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>LN distinguishes the following activity types:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#wbsel" role="option">WBS Element</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#cosac" role="option">Project Cost Account</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#worpa" role="option">Work Package</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#plapa" role="option">Planning Package</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#milst" role="option">Milestone</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh557.cstl">
         <Header>
            <Title>Extension</Title>
         </Header>
         <FuncDesc>The specific agreements within or in addition to the initial
		contract. An extension falls outside the initial contract with the sold-to
		business partner. Extensions can be assigned to the bottom-up
		budget.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>LN distinguishes four extension types:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#additional.work" role="option">Scope Change</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#provision.entry" role="option">Provisional Amount</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#risc.settl" role="option">Fluctuation Settlement</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/ptc.stlt#quan.settl" role="option">Quantities to be Settled</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="whinh557.ccco">
         <Header>
            <Title>Cost Component</Title>
         </Header>
         <FuncDesc>A cost component is a collection of cost objects with a certain
		characteristic. A cost component does not depend on the cost type, therefore,
		for example, a project can be monitored from another dimension. For example,
		all the costs that refer to electrical work, for example, cable and
		installation work, are visible if the applicable cost objects are linked to the
		cost component Electrical work.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="whinh557.qvrc">
         <Header>
            <Title>Variance</Title>
         </Header>
         <FuncDesc>The difference between the quantity as registered in LN and the quantity
		  actually counted at the stockpoint, expressed in <Link href="/baanerp/wh/glossary/glossary#000337" role="glossary">inventory unit</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="inventory.unit">
         <Header>
            <Title>Variance</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="whinh557.hist">
         <Header>
            <Title>History Status</Title>
         </Header>
         <FuncDesc>The history status of the cycle counting order.</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <List>
               <ListIntro>The order can have one of the below status:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/wh/domains/hist#created" role="option">Created</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/wh/domains/hist#modified" role="option">Modified</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/wh/domains/hist#processed" role="option">Processed</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/wh/domains/hist#removed" role="option">Removed</GUIRef>
               </ListItem>
            </List>
         </AllowedValues>
      </FieldHelp>
      <FieldHelp ID="whinh557.logn">
         <Header>
            <Title>User</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#000068" role="glossary">logon code</Link> of the person who modified the order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="user.name">
         <Header>
            <Title>User name</Title>
         </Header>
         <FuncDesc>The name of the person.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>