<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/td/sls/tdsls4141m000" xml:lang="en">
   <Header>
      <Title>Inventory Consumption Lines (tdsls4141m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view, enter, and
		  maintain the individual <Link href="/baanerp/wh/glossary/glossary#000473" role="glossary">consumptions</Link> for a combination of item,
		  sold-to business partner, ship-to business partner, and warehouse. These are
		  the <Link href="/baanerp/wh/glossary/glossary#000473" role="glossary">consumption</Link> issues of a specific item from
		  the customer's or the subcontractor's warehouse.</Paragraph>
         <List>
            <ListIntro>Consumption lines can be created as a result of:</ListIntro>
            <ListItem>Receiving a LoadInventoryConsumption <Link href="/baanerp/wh/glossary/glossary#000479" role="glossary">Business Object Document (BOD)</Link>.</ListItem>
            <ListItem>Manually entering an inventory consumption line.</ListItem>
         </List>
      </AimSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListItem>Consumption lines are linked to a consumption header in the <Link href="/baanerp/td/sls/tdsls4140m000" role="session">Inventory Consumptions (tdsls4140m000)</Link> session. If a consumption line is added for
			 which no consumption header record is available yet, this consumption is
			 automatically created in the <GUIRef href="/baanerp/td/sls/tdsls4140m000" role="session">Inventory Consumptions (tdsls4140m000)</GUIRef> session.</ListItem>
            <ListItem>You can delete registered consumption headers if no related
			 consumption lines exist.</ListItem>
         </List>
      </Note>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000451" role="manual">Inventory consumption - process overview</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tdsls441.ofbp">
         <Header>
            <Title>Sold-to Business Partner</Title>
         </Header>
         <FuncDesc>Usually a customer's purchase department, the business partner
		who orders goods or services from your organization, that owns the
		configurations you maintain, or for whom you perform a project.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Details of the agreement with the sold-to business partner
			 can include the following:</ListIntro>
               <ListItem>Default price and discount agreements</ListItem>
               <ListItem>Sales order defaults</ListItem>
               <ListItem>Delivery terms</ListItem>
               <ListItem>The related ship-to and invoice-to business partner</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <List>
               <ListItem>In a <Link href="/baanerp/wh/glossary/glossary#000469" role="glossary">vendor managed inventory (VMI)</Link> context, this is the customer who performs the
				consumption or for whom the consumption is performed.</ListItem>
               <ListItem>In a <Link href="/baanerp/tc/glossary/glossary#Subcontracti_tc" role="glossary">subcontracting</Link> context, this is the subcontractor who
				consumes the materials supplied by the manufacturer to produce the items for
				the manufacturer.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls441.cwar" OtherIDs="tcmcs003.dsca">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>The ship-to warehouse.</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>In a <Link href="/baanerp/wh/glossary/glossary#000469" role="glossary">vendor managed inventory (VMI)</Link> context, this is the supplier's administrative <Link href="/baanerp/wh/glossary/glossary#000471" role="glossary">VMI warehouse</Link>, which reflects the customer's "real" warehouse.</ListItem>
               <ListItem>In a <Link href="/baanerp/tc/glossary/glossary#Subcontracti_tc" role="glossary">subcontracting</Link> context, this is the manufacturer's
				administrative warehouse, which reflects the subcontractor's
				warehouse.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls441.item" OtherIDs="tcibd001.dsca">
         <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="tdsls441.csdt">
         <Header>
            <Title>Consumption Date</Title>
         </Header>
         <FuncDesc>The date and time the consumption is issued in the customer's
		  or the subcontractor's warehouse. The date can be in the past or in the
		  future.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls441.qccs">
         <Header>
            <Title>Consumed Quantity</Title>
         </Header>
         <FuncDesc>The quantity actually consumed by the customer, expressed in
		  the consumption unit.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls441.cucs">
         <Header>
            <Title>Consumed Quantity</Title>
         </Header>
         <FuncDesc>The unit in which the consumed quantity is
		  expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls441.pric">
         <Header>
            <Title>Price</Title>
         </Header>
         <FuncDesc>The price the customer expects to pay. This informational field
		  can be especially helpful in case of <Link href="/baanerp/tf/glossary/glossary#000008" role="glossary">self-billing</Link>, when misunderstandings about the price can
		  be detected at an early stage.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls441.ccur">
         <Header>
            <Title>Price</Title>
         </Header>
         <FuncDesc>A generally accepted medium of exchange (such as: coins,
		treasury notes, and banknotes).</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>LN distinguishes two currency types:</ListIntro>
               <ListItem>Home currency, used internally by companies for example, to
			 calculate costs, to record budgets, and to register tax amounts</ListItem>
               <ListItem>Transaction currency, used in transactions with business
			 partners, such as orders and invoices</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls441.cupr">
         <Header>
            <Title>Price</Title>
         </Header>
         <FuncDesc>The unit to which the (sales/purchase) price applies.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls441.corn">
         <Header>
            <Title>Customer Order</Title>
         </Header>
         <FuncDesc>In a <Link href="/baanerp/wh/glossary/glossary#000469" role="glossary">vendor managed inventory (VMI)</Link> context, the customer's purchase order ID is
		  used to search for the supplier's sales order/schedule with which the VMI
		  warehouse was replenished. The payment type in the <Link href="/baanerp/td/sls/tdsls4101m000#tdsls401.pmnt" role="formfield">Payment</Link> field of the sales order/schedule is used to
		  determine whether invoicing is required for the consumption.</FuncDesc>
         <SimpleSection>
            <Paragraph>This field is empty if the supplier performs supply planning
			 and creates sales orders/schedules to replenish the customer's inventory before
			 the customer sends a purchase order. For example, this occurs in the Supply
			 planning by supplier scenario. For more information, refer to <Link href="/baanerp/wh/onlinemanual/000462" role="manual">Overview of VMI business scenarios</Link>.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/wh/onlinemanual/000462" role="manual">Overview of VMI business scenarios</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000451#Process_overview_consumptions"
                     role="manual">How LN processes consumptions - outline</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000451#VMI_order" role="manual">VMI order/schedule</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/wh/onlinemanual/000458" role="manual">Vendor managed inventory</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls441.corp">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>In a <Link href="/baanerp/wh/glossary/glossary#000469" role="glossary">vendor managed inventory (VMI)</Link> context, the customer's purchase order line ID
		  is used to search for the supplier's sales order/schedule line with which the
		  VMI warehouse is replenished. The sales order/schedule is used to determine
		  whether invoicing is required for the consumption.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls441.cors">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>In a <Link href="/baanerp/wh/glossary/glossary#000469" role="glossary">vendor managed inventory (VMI)</Link> context, the customer's purchase order sequence
		  ID is used to search for the supplier's sales order/schedule line with which
		  the VMI warehouse is replenished. The sales order/schedule is used to determine
		  whether invoicing is required for the consumption.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls441.pksp">
         <Header>
            <Title>Packing Slip</Title>
         </Header>
         <FuncDesc>An order document that shows in detail the contents of a
		particular package for shipment. The details include a description of the
		items, the shippers or customers item number, the quantity shipped, and the
		inventory unit of the shipped items.</FuncDesc>
         <SimpleSection>
            <Paragraph>In a <Link href="/baanerp/wh/glossary/glossary#000469" role="glossary">vendor managed inventory (VMI)</Link> context, this is the packing slip used for the
			 shipment to the VMI warehouse.</Paragraph>
            <Paragraph>This field is used to search for the corresponding sales
			 schedule shipment and to post it to <GUIRef href="/baanerp/ci" role="package">Invoicing</GUIRef>.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls441.pksl">
         <Header>
            <Title>Packing Slip (external)</Title>
         </Header>
         <FuncDesc>In a <Link href="/baanerp/wh/glossary/glossary#000469" role="glossary">vendor managed inventory (VMI)</Link> context, this is the <Link href="/baanerp/wh/glossary/glossary#000359" role="glossary">packing slip</Link> used for the shipment from the VMI warehouse to the
		  manuafacturer.</FuncDesc>
         <SimpleSection>
            <Paragraph>This packing slip is posted to <GUIRef href="/baanerp/ci" role="package">Invoicing</GUIRef> for
			 informational purposes only.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdsls441.sbrf">
         <Header>
            <Title>Subcontracting Reference</Title>
         </Header>
         <FuncDesc>The reference that the manufacturer sent to the subcontractor
		  through the subcontracting purchase order. The subcontractor used this
		  reference when reporting the consumption to the manufacturer.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000451#Process_overview_consumptions"
                     role="manual">How LN processes consumptions - outline</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000451#Subcontracting_order" role="manual">Subcontracting order</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000450" role="manual">Overview of subcontracting</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls441.alrf">
         <Header>
            <Title>Allocated-to Reference</Title>
         </Header>
         <FuncDesc>The reference of the consumed inventory originating from the
		  customer. The reference is one of the attributes that you can define for a <Link href="/baanerp/tc/glossary/glossary#000455" role="glossary">specification</Link>. LN can attach specifications to
		  order/schedule lines and inventory if the applicable terms and conditions
		  determine that the allocation and hard pegging functionality is used.</FuncDesc>
         <SimpleSection>
            <Paragraph>If inventory is received in the customer's warehouse based
			 on an order/schedule with a reference, the reference is passed on to the
			 inventory. The inventory is then available for consumption issues made for
			 demand orders/schedules with matching references.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls441.csrf">
         <Header>
            <Title>Consumption Reference</Title>
         </Header>
         <FuncDesc>Informational reference to the customer's consumption ID.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000451#Process_overview_consumptions"
                     role="manual">How LN processes consumptions - outline</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000451#VMI_order" role="manual">VMI order/schedule</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/wh/onlinemanual/000458" role="manual">Vendor managed inventory</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls441.retn">
         <Header>
            <Title>Return</Title>
         </Header>
         <FuncDesc>If this check box is selected, the consumed quantity on
		  the consumption line is returned, and is therefore not invoiced.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If applicable, credit notes are handled by manually created <Link href="/baanerp/td/glossary/glossary#ReturnOrder_td" role="glossary" Update="No">return orders</Link>.</Paragraph>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000009" role="manual">Sales return orders</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls441.invr">
         <Header>
            <Title>Invoicing Required</Title>
         </Header>
         <FuncDesc>If this check box is selected, the consumed quantity
		  must be invoiced. Therefore, the <Link href="/baanerp/wh/glossary/glossary#000468" role="glossary">company owned</Link> inventory is reduced and invoicing is performed.</FuncDesc>
         <SimpleSection>
            <Paragraph>LN clears this check box if a subcontracting reference is present in the <Link href="/baanerp/td/sls/tdsls4141m000#tdsls441.sbrf" role="formfield">Subcontracting Reference</Link> field for the current
			 consumption line because typically, the subcontractor is not invoiced for
			 materials supplied by the manufacturer that the subcontractor consumes to
			 produce the items for the manufacturer.</Paragraph>
            <Paragraph>If no subcontracting reference is present on the consumption
			 line, and no sales order/schedule is found using the <GUIRef href="/baanerp/td/sls/tdsls4141m000#tdsls441.corn" role="manual">Customer Order</GUIRef> field, LN checks the <GUIRef href="/baanerp/tc/trm/tctrm1130m000#tctrm130.pmnt" role="manual">Payment</GUIRef> field of the <GUIRef href="/baanerp/tc/trm/tctrm1130m000" role="session">Order Terms and Conditions (tctrm1130m000)</GUIRef> session for the relevant terms and
			 conditions. If payment is <GUIRef href="/baanerp/tc/domains/pmnt#pay.on.use" role="option">Pay on Use</GUIRef> or payment is not defined, invoicing is required.</Paragraph>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>If this check box is cleared, invoicing is not required.
			 Therefore, only the <Link href="/baanerp/wh/glossary/glossary#000465" role="glossary">customer owned</Link> inventory is reduced and no invoicing is performed.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro>The consumption line is not invoiced if:</ListIntro>
               <ListItem>The <GUIRef href="/baanerp/td/sls/tdsls4141m000#tdsls441.retn" role="manual">Return</GUIRef> check box is selected.</ListItem>
               <ListItem>The <GUIRef href="/baanerp/td/sls/tdsls4140m000#tdsls440.pcit" role="manual">Packaging Item</GUIRef> check box is selected for the item in
				the <GUIRef href="/baanerp/td/sls/tdsls4140m000" role="session">Inventory Consumptions (tdsls4140m000)</GUIRef> session.</ListItem>
            </List>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tdsls441.prcd">
         <Header>
            <Title>Processed</Title>
         </Header>
         <FuncDesc>If this check box is selected, the consumption line is
		  processed. This means that the related sales orders/schedules, warehouse
		  orders, production order, and purchase orders are updated to decrease inventory
		  in the <Link href="/baanerp/wh/glossary/glossary#000467" role="glossary">administrative warehouse</Link> and to create invoicing lines if
		  required.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000451" role="manual">Inventory consumption - process overview</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls441.stbp">
         <Header>
            <Title>Ship-to Business Partner</Title>
         </Header>
         <FuncDesc>The business partner to which you ship the ordered goods. This
		usually represents a customer's distribution center or warehouse. The
		definition includes the default warehouse from which you send the goods, the
		carrier who carries out the transport, and the related sold-to business
		partner.</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>In a <Link href="/baanerp/wh/glossary/glossary#000469" role="glossary">vendor managed inventory (VMI)</Link> context, this is the distribution center or
				warehouse of the customer who performs the consumption or for whom the
				consumption is performed.</ListItem>
               <ListItem>In a <Link href="/baanerp/tc/glossary/glossary#Subcontracti_tc" role="glossary">subcontracting</Link> context, this is the distribution center
				or warehouse of the subcontractor who consumes the materials supplied by the
				manufacturer to produce the items for the manufacturer.</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection/>
      </FieldHelp>
      <FieldHelp ID="form.lot.code">
         <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="form.serial">
         <Header>
            <Title>Serial Number</Title>
         </Header>
         <FuncDesc>The unique identification of a single physical item. LN 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>
      <FieldHelp ID="tcibd420.albp">
         <Header>
            <Title>Allocated to Business Partner</Title>
         </Header>
         <FuncDesc>The supply that fills this demand must have been <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link> to the <Link href="/baanerp/tc/glossary/glossary#SoldtoBusine_tc" role="glossary">sold-to business partner</Link> displayed in the <GUIRef href="/baanerp/td/sls/tdsls4140m000" role="session">Inventory Consumptions (tdsls4140m000)</GUIRef> session.</FuncDesc>
         <SimpleSection>
            <Paragraph>LN uses this characteristic to find a matching supply for this demand.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tcibd420.albt">
         <Header>
            <Title>Allocated to Business Object</Title>
         </Header>
         <FuncDesc>The supply that fills this demand must have been <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link> to the type of order displayed in this field.</FuncDesc>
         <SimpleSection>
            <Paragraph>LN uses this characteristic to find a matching supply for this demand.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro>The following fields are always used in combination;
				together, they identify the relevant order or order line:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albt" role="manual">Business Object Type</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albo" role="manual">Business Object</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.abor" role="manual">Business Object Reference</GUIRef>
               </ListItem>
            </List>
         </Note>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/tc/domains/albt" role="domain">Allocated to Business Object Type</Link>
            </Paragraph>
         </AllowedValues>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tcibd420.albo">
         <Header>
            <Title>Allocated to Business Object</Title>
         </Header>
         <FuncDesc>The supply that fills this demand must have been <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link> to the <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link>, or order line, displayed in this field.</FuncDesc>
         <SimpleSection>
            <Paragraph>LN uses this characteristic to find a matching supply for this demand.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro>The following fields are always used in combination;
				together, they identify the relevant order or order line:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albt" role="manual">Business Object Type</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albo" role="manual">Business Object</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.abor" role="manual">Business Object Reference</GUIRef>
               </ListItem>
            </List>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tcibd420.abor">
         <Header>
            <Title>Allocated to Business Object Reference</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/fm/glossary/glossary#000008" role="glossary">order</Link> or order line to which the items were <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link>.</FuncDesc>
         <SimpleSection>
            <Paragraph>LN can use this characteristic to find a matching supply for this
			 demand.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro>The combination of the following fields identifies the
				order or order line to which the ordered items were allocated:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/wh/inp/whinp1500m000#tcibd420.albt" role="manual">Business Object Type</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/wh/inp/whinp1500m000#tcibd420.albo" role="manual">Business Object</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/wh/inp/whinp1500m000#tcibd420.abor" role="manual">Business Object Reference</GUIRef>
               </ListItem>
            </List>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tcibd420.alrf">
         <Header>
            <Title>Allocated to Reference</Title>
         </Header>
         <FuncDesc>The supply that fills this demand is <Link href="/baanerp/cp/glossary/glossary#000450" role="glossary">allocated</Link> or <Link href="/baanerp/cp/glossary/glossary#000451" role="glossary">hard pegged</Link> to the reference code displayed in this
		  field.</FuncDesc>
         <SimpleSection>
            <Paragraph>LN uses this characteristic to find a matching supply for this demand.</Paragraph>
         </SimpleSection>
         <SimpleSection>
            <List>
               <ListIntro>LN can use this field in two ways:</ListIntro>
               <ListItem>If the <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albp" role="manual">Business Partner</GUIRef> field is filled, LN uses the <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.alrf" role="manual">Reference</GUIRef> field to record a reference code defined by
				a customer.</ListItem>
               <ListItem>If the <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.albp" role="manual">Business Partner</GUIRef> field is empty, LN uses the <GUIRef href="/baanerp/wh/inp/whinp2100m000#tcibd420.alrf" role="manual">Reference</GUIRef> field to record an internal
				reference.</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <Paragraph>You can use a reference code to keep a collection of parts
			 linked together, even if they follow different routings, for example, if some
			 of the parts are transported to a <Link href="/baanerp/td/glossary/glossary#Subcontracto_td" role="glossary">subcontractor</Link> to be returned later.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/cp/onlinemanual/000460" role="manual">Allocation and hard pegging overview</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="start.lot.and.serial.set">
         <Header>
            <Title>Lot and Serial Set</Title>
         </Header>
         <FuncDesc>Starts the <Link href="/baanerp/tc/ibd/tcibd4111m000" role="session">Lot and Serial Set (tcibd4111m000)</Link> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="process.consumption.line">
         <Header>
            <Title>Process Consumption Line</Title>
         </Header>
         <FuncDesc>Processes the selected consumption line.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>