<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tp/pss/tppss6501m000" xml:lang="en">
   <Header>
      <Title>Order Line Balance (Equipment) (tppss6501m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view the transactions,
		  which influence the order line balance and to track the ordering flow from
		  budget to final delivery.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>Delivered orders to the project or project warehouse are
				displayed in the <GUIRef href="/baanerp/tp/pss/tppss6550m000" role="session">Delivered Order Lines (Material) (tppss6550m000)</GUIRef> session.</ListItem>
               <ListItem>Transactions between a project and a project warehouse, and
				transactions from a project to a normal warehouse are not displayed.</ListItem>
            </List>
         </Note>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tppss601.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>The code that uniquely identifies the <Link href="/baanerp/tp/glossary/glossary#000063" role="glossary">project</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs052.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppdm600.psts">
         <Header>
            <Title>Project Status</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000087" role="glossary">project status</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="trans.origin">
         <Header>
            <Title>Transaction Origin</Title>
         </Header>
         <FuncDesc>This indicates the origin of this particular transaction. The
		  transaction origin is the object driving the transaction.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For equipment, this field can have the following values:</ListIntro>
               <ListItem> 
                  <GUIRef href="/baanerp/tp/domains/pss.tror#act.pur" role="option">Purchase Order</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tp/domains/pss.tror#prp.pur" role="option">PRP Purchase Order</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tp/domains/pss.tror#budget" role="option">Budget</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tp/domains/pss.tror#act.rfq" role="option">Request for Quotation</GUIRef>
               </ListItem>
            </List>
            <Paragraph> 
               <Link href="/baanerp/tp/domains/pss.tror" role="domain">Transaction origin</Link>
            </Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tppss601.orno">
         <Header>
            <Title>Order Number</Title>
         </Header>
         <FuncDesc>The code that uniquely identifies the planned order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.pono">
         <Header>
            <Title>Pos.</Title>
         </Header>
         <FuncDesc>The position number of the order line. As an order can have
		  multiple order lines, this number is used to identify the particular line to
		  which the transaction applies.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.sqnb">
         <Header>
            <Title>Seq. No.</Title>
         </Header>
         <FuncDesc>The sequence number of the order line detail.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.cequ">
         <Header>
            <Title>Equipment</Title>
         </Header>
         <FuncDesc>The code that uniquely identifies the <Link href="/baanerp/tp/glossary/glossary#000044" role="glossary">equipment</Link> involved in this
		  transaction.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="desc.cequ">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.reft">
         <Header>
            <Title>Reference Type</Title>
         </Header>
         <FuncDesc>The planned order's reference type.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.quan">
         <Header>
            <Title>Amount of Time</Title>
         </Header>
         <FuncDesc>The number of time units for which the equipment is ordered.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cuti.cequ">
         <Header>
            <Title>Unit</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000080" role="glossary">unit of measure</Link> in which the amount of time is expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.kotr">
         <Header>
            <Title>Transaction Type</Title>
         </Header>
         <FuncDesc>The transaction type indicates whether the transaction
		  increases or decreases the inventory balance.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.buyr">
         <Header>
            <Title>Buyer</Title>
         </Header>
         <FuncDesc>The code that uniquely identifies the buyer. The <Link href="/baanerp/td/glossary/glossary#Buyer_td" role="glossary">buyer</Link> is an employee of the organization.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>LN defaults the value when the planned PRP orders are generated,
			 using the <GUIRef href="" role="manual">Generate Planned PRP Orders (tppss6200m000)</GUIRef> session.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tccom001.nama">
         <Header>
            <Title>Name</Title>
         </Header>
         <FuncDesc>The name of the employee. The employee can be a buyer or a
		  planner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="cequ.balance">
         <Header>
            <Title>Balance</Title>
         </Header>
         <FuncDesc>The budget balance on the current project.</FuncDesc>
         <SimpleSection>
            <Paragraph>Balance (t) = Delivered on project (t) + Receipt (t) -
			 Requirement (t) (Where t is in days. This ensures that all transactions are
			 taken from one date).</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="quan.on.hand">
         <Header>
            <Title>Delivered on project</Title>
         </Header>
         <FuncDesc>The quantity that is delivered and available to the project.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.date">
         <Header>
            <Title>Start Time</Title>
         </Header>
         <FuncDesc>The first day of the period for which you need the equipment.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.cact">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>The activity in the activity budget to which the cost object
		  belongs.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss200.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.cspa">
         <Header>
            <Title>Element</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#Element_tp" role="glossary">element</Link> in the element budget to which the cost object
		  belongs.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpptc100.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.cstl">
         <Header>
            <Title>Ext.</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000017" role="glossary">extension</Link> to which the cost object belongs.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tpptc050.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tppss601.ccco">
         <Header>
            <Title>Cost Comp.</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tp/glossary/glossary#000360" role="glossary">cost component</Link> to which the cost object belongs.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs048.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="tppss6400m000">
         <Header>
            <Title>Print Planned Transactions by Cost Object</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="" role="manual">Print Planned Transactions by Cost Object (tppss6400m000)</GUIRef> session to print planned transactions with the <GUIRef href="" role="manual">Firm Planned</GUIRef> or <GUIRef href="" role="manual">Confirmed</GUIRef> status by cost
		  object.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>