<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/wh/inp/whinp2202m000" xml:lang="en">
   <Header>
      <Title>Consumption of the Inventory Buffers (whinp2202m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to commit inventory, that
		  was previously reserved in <Link href="/baanerp/wh/glossary/glossary#000034" role="glossary">inventory buffers</Link>, to
		  specific orders. To use this session, you must be authorized (authorizations
		  are set up in <GUIRef href="/baanerp/tt" role="package">Enterprise Server</GUIRef>).</Paragraph>
      </AimSection>
      <GeneralSection>
         <List>
            <ListIntro>For an order with origin <GUIRef href="/baanerp/wh/domains/inp.corg#inv.buffer" role="option">Inventory Buffer</GUIRef> (dummy order), a quantity can be committed as follows:</ListIntro>
            <ListItem>By warehouse and item
			 (in this case, the order number can be zero).</ListItem>
            <ListItem>By dummy order,
			 warehouse, and item (in this case, the order number can be equal to, for
			 example, a customer code).</ListItem>
         </List>
         <List>
            <ListIntro>Updates after consuming the inventory buffers:</ListIntro>
            <ListItem>The inventory buffers and the destination order data are
			 updated with the transfer quantity entered in the <GUIRef href="/baanerp/wh/inp/whinp2100m000" role="session">Inventory Commitments (whinp2100m000)</GUIRef> session. If a buffer has been completely
			 consumed, you can delete the buffer.</ListItem>
            <ListItem>For orders with a sales order as the destination, in the <GUIRef href="/baanerp/td/sls/tdsls4101m000" role="session">Sales Order Lines (tdsls4101m000)</GUIRef> session, the <GUIRef href="/baanerp/td/sls/tdsls4101m000#qicm.ou" role="manual">Committed Quantity in Order Unit</GUIRef> field is updated with the committed quantity.</ListItem>
         </List>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/wh/onlinemanual/000034" role="manual">Inventory commitment</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="koor.f">
         <Header>
            <Title>Order Origin</Title>
         </Header>
         <FuncDesc>The <GUIRef href="" role="optionlist">Order Origin for Commitment</GUIRef> is always <GUIRef href="/baanerp/wh/domains/inp.corg#inv.buffer" role="option">Inventory Buffer</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="orno.f">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>The order number of the inventory commitment order from which
		  the goods are to be consumed. The <GUIRef href="" role="optionlist">Order Origin for Commitment</GUIRef> must be of the <GUIRef href="/baanerp/wh/domains/inp.corg#inv.buffer" role="option">Inventory Buffer</GUIRef> type.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pono.f">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc>The line number of the order line within the warehouse order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="koor.t">
         <Header>
            <Title>Order Origin</Title>
         </Header>
         <FuncDesc>The order origin of the order to which the inventory buffer is
		  transferred.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="orno.t">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>The order number of the order to which the inventory buffer is
		  transferred.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pono.t">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc>The line number of the order line within the warehouse order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="oqua.t">
         <Header>
            <Title>Ordered</Title>
         </Header>
         <FuncDesc>The quantity ordered, expressed in the order unit.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="sera.t">
         <Header>
            <Title>Sequence</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#SequenNumber_tc" role="glossary">sequence number</Link> of the
		  order-line detail.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="qoqu.t">
         <Header>
            <Title>Committed</Title>
         </Header>
         <FuncDesc>The quantity committed to the order, expressed in the order
		  unit.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="serb.t">
         <Header>
            <Title>BOM Line</Title>
         </Header>
         <FuncDesc>A reference number identifying a specific combination of
		manufactured and component items in a bill of material. The position number is
		subdivided by sequence numbers that are used to refer to usage of a component
		between particular dates.</FuncDesc>
         <SimpleSection>
            <Paragraph>This number must
			 only be entered if the item is a component of a <Link href="/baanerp/ti/glossary/glossary#BillOfMateri_ti" role="glossary">bill of material</Link>. Otherwise,
			 this field must contain the default zero.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tran.t">
         <Header>
            <Title>Transfer</Title>
         </Header>
         <FuncDesc>The quantity to be transferred from the inventory buffer to the
		  committed order. This quantity cannot be greater than the quantity in the
		  buffer, nor greater than the order quantity of the destination order. The
		  quantity is expressed in the order unit.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="item.f">
         <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="cwar.f">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#Warehouse_tc" role="glossary">warehouse</Link> in which the quantity of the inventory
		  commitment is stored.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>You cannot use warehouses of the <GUIRef href="/baanerp/tc/domains/typw#project" role="option">Project</GUIRef> type.</Paragraph>
         </Note>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="exec.cont.process">
         <Header>
            <Title>Transfer</Title>
         </Header>
         <FuncDesc>Starts the transfer of inventory commitment to actual orders.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>