<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tc/bgc/tcbgc1100m000" xml:lang="en">
   <Header>
      <Title>Budget Account Distribution (tcbgc1100m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to display and maintain the
		  ledger accounts or dimensions for the selected document line. The combinations
		  of ledger accounts and dimensions are used to map the budget accounts on the
		  first level of budget in the budget structure.</Paragraph>
         <Paragraph>To modify the percentages of the item quantity, click the <GUIRef href="/baanerp/tc/bgc/tcbgc1100m000#reconcile" role="manual">Reconcile Current Line</GUIRef> button.</Paragraph>
      </AimSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tcbgc100.botp">
         <Header>
            <Title>Business Object Type</Title>
         </Header>
         <FuncDesc>The type of <Link href="/baanerp/tf/glossary/glossary#000452" role="glossary">business object</Link>. Example: <GUIRef href="/baanerp/tc/domains/bgc.botp#bdgt.adjustment" role="option">Budget Adjustment</GUIRef>, <GUIRef href="/baanerp/tc/domains/bgc.botp#jrn.vch" role="option">Journal Voucher</GUIRef>, <GUIRef href="/baanerp/tc/domains/bgc.botp#pur.ord" role="option">Purchase Order</GUIRef> and so on.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcbgc100.bobj">
         <Header>
            <Title>Business Object</Title>
         </Header>
         <FuncDesc>The unique code that identifies a specific business object. For
		example, business object ID of a <GUIRef href="" role="manual">Purchase Order</GUIRef> business
		object is the purchase order number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcbgc100.borf">
         <Header>
            <Title>Business Object Reference</Title>
         </Header>
         <FuncDesc>A transaction identification more detailed than the business
		object, for example, a receipt number or an order number. You can use the
		reference during reconciliation to match transactions if the business object
		alone does not provide enough information, for example, during GRNI
		reconciliation.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The business object reference is not the same as a reference
		  link.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tcbgc100.seqn">
         <Header>
            <Title>Sequence</Title>
         </Header>
         <FuncDesc>The sequence number of the generated line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="order.nr">
         <Header>
            <Title>Purchase Order</Title>
         </Header>
         <FuncDesc>The order that indicates which items are delivered by a
		buy-from business partner according to certain terms and conditions.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>A purchase order contains:</ListIntro>
               <ListItem>A header with general order data, buy-from business partner
			 data, payment terms, and delivery terms.</ListItem>
               <ListItem>One or more order lines with more detailed information about
			 the actual items to be delivered.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="line">
         <Header>
            <Title>Line</Title>
         </Header>
         <FuncDesc/>
         <SimpleSection>
            <List>
               <ListIntro>The lines on purchase orders that record detailed
			 information about, for example:</ListIntro>
               <ListItem>The ordered items.</ListItem>
               <ListItem>The price agreements.</ListItem>
               <ListItem>The delivery dates.</ListItem>
               <ListItem>Shipping.</ListItem>
               <ListItem>Invoicing.</ListItem>
            </List>
            <Paragraph>You can have one or more lines on a purchase order.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="business.partner" OtherIDs="bus.partner.descr">
         <Header>
            <Title>Business Partner</Title>
         </Header>
         <FuncDesc>A party with whom you carry out business transactions, for
		example, a customer or a supplier. You can also define departments within your
		organization that act as customers or suppliers to your own department as
		business partners.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The business partner definition includes:</ListIntro>
               <ListItem>The organization's name and main address.</ListItem>
               <ListItem>The language and currency used.</ListItem>
               <ListItem>Taxation and legal identification data.</ListItem>
            </List>
            <Paragraph>You address the business partner in the person of the
		  business partner's contact. The business-partner status determines if you can
		  carry out transactions. The transactions type (sales orders, invoices,
		  payments, shipments) is defined by the business partner's role.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="bus.partner.name">
         <Header>
            <Title>Name</Title>
         </Header>
         <FuncDesc>The business partner's name.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bank" OtherIDs="bank.descr">
         <Header>
            <Title>Bank</Title>
         </Header>
         <FuncDesc>A record of debit and credit entries to cover transactions
		involving a particular item, person, or concern. The bank account is identified
		by a number.</FuncDesc>
         <SimpleSection>
            <Paragraph>LN can
		  be set to check bank account numbers when you enter them. If the account number
		  does not pass the check, LN displays a warning message.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="batch">
         <Header>
            <Title>EBS Batch</Title>
         </Header>
         <FuncDesc>A batch that converts a sequential file of electronic bank
		statements to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="sequence">
         <Header>
            <Title>Sequence</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/td/glossary/glossary#000208" role="glossary">sequence number</Link> of the purchase order line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="item" OtherIDs="item.label">
         <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="item.descr">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcbgc100.quan">
         <Header>
            <Title>Quantity</Title>
         </Header>
         <FuncDesc>The quantity that must be delivered according to the terms on
		the order line. The quantity is expressed in the purchase unit or the sales
		unit of the item.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcbgc100.perc">
         <Header>
            <Title>Percentage</Title>
         </Header>
         <FuncDesc>The percentage of the quantity distributed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcbgc100.glcd">
         <Header>
            <Title>GL Code</Title>
         </Header>
         <FuncDesc>Represents a ledger account and the corresponding dimensions.
		GL codes are used to represent ledger accounts to users who are not familiar
		with the structure of the chart of accounts.</FuncDesc>
         <SimpleSection>
            <Paragraph>To specific logistic transactions, you can link a GL code.
		  Such integration transactions are mapped directly to the ledger account and
		  dimensions of the GL code, they are not included in the mapping process.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tcbgc100.acnt">
         <Header>
            <Title>Account</Title>
         </Header>
         <FuncDesc>A register used to record financial transactions and to
		accumulate the values of the transactions for reporting and analysis. The
		ledger accounts classify the transactions into categories such as revenues,
		expenses, assets, and liabilities.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="quantity">
         <Header>
            <Title>Quantity</Title>
         </Header>
         <FuncDesc>The quantity of the item after the budget account
		  distribution.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcbgc100.dim1"
                 OtherIDs="tcbgc100.dim2 tcbgc100.dim3 tcbgc100.dim4 tcbgc100.dim5 tcbgc100.dim6 tcbgc100.dim7 tcbgc100.dim8 tcbgc100.dim9 tcbgc100.dm10 tcbgc100.dm11 tcbgc100.dm12">
         <Header>
            <Title>Dimension 1</Title>
         </Header>
         <FuncDesc>Analysis account for ledger accounts to get a vertical view on
		ledger accounts. Dimensions are used to specify ledger account information.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="quantity.unit">
         <Header>
            <Title>unit</Title>
         </Header>
         <FuncDesc>The unit in which the item quantity is expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcbgc100.bgcd">
         <Header>
            <Title>Budget Check Date</Title>
         </Header>
         <FuncDesc>The date on which the budget check is performed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcbgc100.bgxc">
         <Header>
            <Title>Budget Exception</Title>
         </Header>
         <FuncDesc>If this check box is selected, there is a budget exception to be handled.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="quantity.inv.unit">
         <Header>
            <Title>Quantity in Inventory Unit</Title>
         </Header>
         <FuncDesc>The quantity of the item displayed in the required inventory
		  unit.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="inventory.unit">
         <Header>
            <Title>Unit</Title>
         </Header>
         <FuncDesc>The inventory unit in which the item quantity is
		  expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="amount">
         <Header>
            <Title>Amount</Title>
         </Header>
         <FuncDesc>The transaction line amount.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="currency">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>The currency in which the transaction line amount is
		  expressed.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="requisition">
         <Header>
            <Title>Purchase Requisition</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/td/glossary/glossary#000153" role="glossary">purchase requisition</Link> code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pur.rq.item.descr">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="invoice">
         <Header>
            <Title>Purchase Invoice</Title>
         </Header>
         <FuncDesc>Purchased goods that are received, inspected (if required), and
		posted to inventory are placed on a purchase invoice. You must pay the buy-from
		business partner for the quantity on the invoice.</FuncDesc>
         <SimpleSection>
            <Paragraph>The buy-from business partner, order, item data, prices, and
		  discounts are printed on the invoice. You can compare the data on the invoice
		  to the invoice you receive from the buy-from business partner.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="standing.order">
         <Header>
            <Title>Standing Order</Title>
         </Header>
         <FuncDesc>An order to which no invoices are linked, for example,
		recurring payments.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="transaction.type" OtherIDs="trans.type.descr">
         <Header>
            <Title>Transaction Type</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="transaction.docum">
         <Header>
            <Title>Transaction Document</Title>
         </Header>
         <FuncDesc>The transaction document number.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="wh.order.nr">
         <Header>
            <Title>Warehouse Order</Title>
         </Header>
         <FuncDesc>A place for storing goods. For each warehouse, you can enter
		address data and data relating to its type.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ship.code" OtherIDs="ship.code.descr">
         <Header>
            <Title>Warehouse Order</Title>
         </Header>
         <FuncDesc>All goods that are transported to a specific address on a
		specific date and time by using a specific route. An identifiable part of a
		load.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="wh.receipt.line">
         <Header>
            <Title>Receipt Line</Title>
         </Header>
         <FuncDesc>The warehouse <Link href="/baanerp/wh/glossary/glossary#000372" role="glossary">receipt number</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="wh.shipment.line">
         <Header>
            <Title>Shipment Line</Title>
         </Header>
         <FuncDesc>An individual line of detail in a shipment.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>