<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tf/acp/tfacp2555m300" xml:lang="en">
   <Header>
      <Title>Invoice Peg Distribution (tfacp2555m300)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view the <Link href="/baanerp/tc/glossary/glossary#000600" role="glossary">peg</Link> distribution across invoices.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tc/onlinemanual/000600" role="manual">Project pegging overview</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tfacp255.icom">
         <Header>
            <Title>Invoice Document</Title>
         </Header>
         <FuncDesc>The company where the invoice was created.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.ityp">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>A user-defined three-position code used to identify documents.
		The series linked to the transaction type give documents the sequence number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.idoc">
         <Header>
            <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="f.inv.status">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>The stage the invoice has reached in the matching/approval
		  process.</FuncDesc>
         <SimpleSection>
            <ProcedureList>
               <ListIntro>The invoice status reflects the various stages of the
				process, and can change as follows:</ListIntro>
               <ListItem> 
                  <GUIRef href="/baanerp/tf/domains/acp.stin#open" role="option">Received</GUIRef>--&gt; <GUIRef href="/baanerp/tf/domains/acp.stap#registered" role="option">Registered</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tf/domains/acp.stap#registered" role="option">Registered</GUIRef>--&gt; <GUIRef href="/baanerp/tf/domains/acp.stap#linked" role="option">Matched</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tf/domains/acp.stap#linked" role="option">Matched</GUIRef>--&gt; <GUIRef href="/baanerp/tf/domains/acp.stap#approved" role="option">Approved</GUIRef>
               </ListItem>
               <ListItem> 
                  <GUIRef href="/baanerp/tf/domains/acp.stap#approved" role="option">Approved</GUIRef>--&gt; <GUIRef href="/baanerp/tf/domains/acp.stap#linked" role="option">Matched</GUIRef> if you unapprove the invoice</ListItem>
            </ProcedureList>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="f.ifbp" OtherIDs="f.ifbp.name">
         <Header>
            <Title>Invoice-from Business Partner</Title>
         </Header>
         <FuncDesc>The business partner that sends invoices to your organization.
		This usually represents a supplier's accounts receivable department. The
		definition includes the default currency and exchange rate, invoicing method
		and frequency, information about your organization's credit limit, the terms
		and method of payment, and the related pay-to business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="f.inv.date">
         <Header>
            <Title>Invoice Date</Title>
         </Header>
         <FuncDesc>The date on which the invoice is printed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="f.inv.amount">
         <Header>
            <Title>Net Invoice Amount</Title>
         </Header>
         <FuncDesc>The net amount in the invoice currency.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="f.inv.currency">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>The currency in which the invoice amount is expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.dlin">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc>The line number that identifies the <Link href="/baanerp/tc/glossary/glossary#000600" role="glossary">peg</Link> in
		  the distribution.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>An endeavor with a specific objective to be met within the
		prescribed time and financial limitation, and that has been assigned for
		definition or execution.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.cspa">
         <Header>
            <Title>Element</Title>
         </Header>
         <FuncDesc>The smallest part of an element structure. An element is used
		to define the (structure of the) work of the project, so that you can carry it
		out.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.cact">
         <Header>
            <Title>Activity</Title>
         </Header>
         <FuncDesc>The smallest part of the activity structure used for a
		time-scaled budget. An entity that is used to represent a part of a project in
		an activity structure.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>ERP Enterprise distinguishes these activity types:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#wbsel" role="option">WBS Element</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#cosac" role="option">Project Cost Account</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#worpa" role="option">Work Package</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#plapa" role="option">Planning Package</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tp/domains/pdm.tact#milst" role="option">Milestone</GUIRef>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="f.logistic.comp">
         <Header>
            <Title>Logistic Company</Title>
         </Header>
         <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="f.item" OtherIDs="f.item.desc">
         <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="f.order">
         <Header>
            <Title>Order</Title>
         </Header>
         <FuncDesc>The order number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="f.order.line">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>The order line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="f.order.seqn">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>The order sequence number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.rcno">
         <Header>
            <Title>Receipt</Title>
         </Header>
         <FuncDesc>Received items.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.rseq">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>The receipt line number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.lcln">
         <Header>
            <Title>Landed Cost Line</Title>
         </Header>
         <FuncDesc>The number of the landed cost line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.pamt">
         <Header>
            <Title>Matched Amount in Order Currency</Title>
         </Header>
         <FuncDesc>The matched amount expressed in order currency.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If this amount and the matched invoice amount in order
			 currency do not match, a price difference exists.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tfacp255.ocur">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>The order currency.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.iaoc">
         <Header>
            <Title>Matched Invoice Amount in Order Currency</Title>
         </Header>
         <FuncDesc>The matched invoice amount expressed in order currency or
		  landed cost currency. A peg line for a landed cost line applies if the <GUIRef href="/baanerp/tf/acp/tfacp2555m300#tfacp255.lcln" role="manual">Landed Cost Line</GUIRef> field has a non-zero
		  value.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.iaic">
         <Header>
            <Title>Matched Invoice Amount in Invoice Currency</Title>
         </Header>
         <FuncDesc>The matched invoice amount expressed in invoice
		  currency.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.icur">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>The currency in which the invoice amount is expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="f.lc.line">
         <Header>
            <Title>Landed Cost Line</Title>
         </Header>
         <FuncDesc>The total of all costs that are associated with the procurement
		of an item until delivery and receipt in a warehouse. Landed costs typically
		include freight costs, insurance costs, customs duties, and handling
		costs.</FuncDesc>
         <SimpleSection>
            <Paragraph>In ERP Enterprise,
		  landed costs can be part of multiple <Link href="/baanerp/tc/glossary/glossary#000481" role="glossary" Update="No">landed costs sets</Link>.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tfacp255.iamh">
         <Header>
            <Title>Matched Invoice Amount in Home Currency</Title>
         </Header>
         <FuncDesc>The matched invoice amount expressed in home
		  currency.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="attr.currency$">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>One of a company's base currencies in which ERP Enterprise registers and
		reports amounts.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>In a multicurrency system, up to three home currencies can
			 be defined:</ListIntro>
               <ListItem>The <Link href="/baanerp/tc/glossary/glossary#000062" role="glossary">local currency</Link>
               </ListItem>
               <ListItem>Two <Link href="/baanerp/tc/glossary/glossary#000065" role="glossary" Update="No">reporting currencies</Link>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tfacp255.rqty">
         <Header>
            <Title>Received Quantity</Title>
         </Header>
         <FuncDesc>The quantity delivered by the supplier identified in the
		purchase unit or the inventory unit.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.iuni">
         <Header>
            <Title/>
         </Header>
         <FuncDesc>The unit of measure in which the inventory of an item is
		recorded, such as piece, kilogram, box of 12, or meter.</FuncDesc>
         <SimpleSection>
            <Paragraph>The inventory unit is also used as the base unit in measure
		  conversions, especially for conversions that concern the order unit and the
		  price unit on a purchase order or a sales order. These conversions always use
		  the inventory unit as the base unit. An inventory unit therefore applies to all
		  item types, also to item types that cannot be kept in stock.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tfacp255.aqty">
         <Header>
            <Title>Approved Quantity in Inventory Unit</Title>
         </Header>
         <FuncDesc>The number of delivered items that is approved.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.rjqu">
         <Header>
            <Title>Rejected Quantity in Inventory Unit</Title>
         </Header>
         <FuncDesc>The number of delivered items that is rejected.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.iqty">
         <Header>
            <Title>Invoiced Quantity</Title>
         </Header>
         <FuncDesc>The number of items actually billed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tfacp255.shpm">
         <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>
      </FieldHelp>
   </Fields>
</Session>