<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/td/pur/tdpur1502s000" xml:lang="en">
   <Header>
      <Title>Linked Order Line Data (tdpur1502s000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to track the destination
		  purchase order of the processed request-for-quotation (RFQ) lines.</Paragraph>
      </AimSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tdpur402.qono">
         <Header>
            <Title>Request for Quotation</Title>
         </Header>
         <FuncDesc>The number of the <Link href="/baanerp/td/glossary/glossary#RequesForQuo_td" role="glossary">request for quotation (RFQ)</Link>
         </FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur402.qpon">
         <Header>
            <Title>Position</Title>
         </Header>
         <FuncDesc>The number of the <Link href="/baanerp/td/glossary/glossary#000239" role="glossary">request-for-quotation (RFQ) line</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur402.qseq">
         <Header>
            <Title>Alternative</Title>
         </Header>
         <FuncDesc>The request for quotation (RFQ)) line's sequence number, which
		  you must define manually in the <GUIRef href="/baanerp/td/pur/tdpur1502m000" role="session">Purchase Request for Quotation Lines (tdpur1502m000)</GUIRef> session.</FuncDesc>
         <SimpleSection>
            <Paragraph>If an RFQ line contains an item that can be an alternative
			 for the preferred item and for which you send a request for quotation (RFQ) at
			 the same time, the sequence number has a number greater than zero.</Paragraph>
            <Paragraph>The sequence numbers defined in the current field, represent
			 the RFQ lines in the most suitable alternative sequence. So, sequence number
			 one represents the first preferable item that can be an alternative for the
			 originally preferred item, sequence number two represents the second item that
			 can be an alternative, and so on.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdpur402.orno">
         <Header>
            <Title>Purchase Order</Title>
         </Header>
         <FuncDesc>The number of the destination purchase order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur402.pono">
         <Header>
            <Title>Position</Title>
         </Header>
         <FuncDesc>The number used to identify the position of the order line on
		the sales or purchase order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur402.sqnb">
         <Header>
            <Title>Sequence Number</Title>
         </Header>
         <FuncDesc>The number used to identify in detail the position number of a
		sales order (delivery) line or a purchase order line (detail).</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur401.item">
         <Header>
            <Title>Sequence Number</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>
   </Fields>
</Session>