<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/td/pur/tdpur4534m000" xml:lang="en">
   <Header>
      <Title>Purchase Order Line Status (tdpur4534m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to list the current <Link href="/baanerp/td/glossary/glossary#000129" role="glossary">activity</Link> of a purchase order
		  line and the next order step that must be performed.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>In the <GUIRef href="/baanerp/td/pur/tdpur4534m000#tdpur4534sDF1" role="groupbox" Update="No">Activities</GUIRef> column ERP Enterprise displays the activities that are
		  linked to the purchase order line and the activity status. These are the steps
		  (statuses) the purchase order has to go through in the ordering process.</Paragraph>
         <Paragraph>In the <GUIRef href="/baanerp/td/pur/tdpur4534m000#gen.execute" role="groupbox" Update="No">Done</GUIRef> column you can see the actual status
		  of the purchase order line. The actual status is the last activity with the
		  value Yes. The next status, the first with the value No, is the next activity
		  to be carried out.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000007" role="manual">Overview of purchase order handling</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000406" role="manual">Flexible purchase order processing</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tdpur401.orno">
         <Header>
            <Title>Purchase Order</Title>
         </Header>
         <FuncDesc>The number that identifies the <Link href="/baanerp/td/glossary/glossary#PurchaOrders_td" role="glossary">purchase order</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur401.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="tdpur401.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>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000014" role="manual">Sequence numbers on purchase orders</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdpur401.appr">
         <Header>
            <Title>Approved</Title>
         </Header>
         <FuncDesc>If this check box is selected, the purchase order line is approved.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur401.fire">
         <Header>
            <Title>Final Receipt</Title>
         </Header>
         <FuncDesc>If this check box is selected, a final receipt has taken place for the
		  purchase order line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur401.clyn">
         <Header>
            <Title>Canceled</Title>
         </Header>
         <FuncDesc>If this check box is selected, the <Link href="/baanerp/td/glossary/glossary#PurchaOrderL_td" role="glossary">purchase order line</Link> is canceled.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur401.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#000023" role="glossary">project</Link> for which the item
		  is required.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpur401.item">
         <Header>
            <Title>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="tdpur401.effn">
         <Header>
            <Title>Effectivity Unit</Title>
         </Header>
         <FuncDesc>A reference number, for example a sales order line or a project
		deliverable line, that is used to model deviations for a unit effective item.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tc/onlinemanual/000300" role="manual">Overview of unit effectivity</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="stepno.dsca">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>A step that you must carry out for the purchase/sales order
		type. An activity represents the sessions or the manual action that you must
		carry our for the purchase/sales order type.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="exec.yn">
         <Header>
            <Title>Done</Title>
         </Header>
         <FuncDesc>This field indicates whether the <Link href="/baanerp/td/glossary/glossary#000129" role="glossary">activity</Link> is executed or not.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="auto.yn">
         <Header>
            <Title>Automatic</Title>
         </Header>
         <FuncDesc>This field indicates whether the <Link href="/baanerp/td/glossary/glossary#000129" role="glossary">activity</Link> is executed
		  automatically or not.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="doc.no">
         <Header>
            <Title>Document Number</Title>
         </Header>
         <FuncDesc>The identification of a transaction.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The document code is a combination of:</ListIntro>
               <ListItem>Transaction-type code</ListItem>
               <ListItem>Series number</ListItem>
               <ListItem>Sequence number</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="next.step">
         <Header>
            <Title>Next Step</Title>
         </Header>
         <FuncDesc>The next order step that must be executed for the purchase
		  order line.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="start.warehousing.orders">
         <Header>
            <Title>Warehousing Orders</Title>
         </Header>
         <FuncDesc>Starts the <Link href="/baanerp/wh/inh/whinh2100m000" role="session">Warehousing Orders (whinh2100m000)</Link> session.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>