<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tf/fst/tffst1180m000" xml:lang="en">
   <Header>
      <Title>Display Transactions (tffst1180m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph> Use this session to list all transactions
		  that are required for the selected financial statement.</Paragraph>
      </AimSection>
   </HelpTopic>
   <Fields>
      <FieldGroup>
         <Title> General Data</Title>
         <FieldHelp ID="tffst180.fstm" OtherIDs="tffst100.desc">
            <Header>
               <Title>Statement</Title>
            </Header>
            <FuncDesc>An account structure that can consist of child statement
		accounts and parent statement accounts. At the child level, the statement
		accounts are linked to ledger accounts and dimensions. With a financial
		statement, you can collect the desired financial values from the <GUIRef href="/baanerp/tf/gld" role="module">General Ledger</GUIRef> and <GUIRef href="/baanerp/tf/fbs" role="module" Update="No">Budgeting</GUIRef> modules, and use this data for internal and external financial reporting and
		analysis.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tffst180.accn" OtherIDs="tffst120.desc">
            <Header>
               <Title>Statement Account</Title>
            </Header>
            <FuncDesc>The account number.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tffst180.scol" OtherIDs="e.column.desc">
            <Header>
               <Title>Statement Column</Title>
            </Header>
            <FuncDesc>The column number.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tffst180.vari">
            <Header>
               <Title>Variable</Title>
            </Header>
            <FuncDesc>The elements included in the formula used to calculate the
		statement column values. They correspond with the statement account
		values.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tffst180.comp">
            <Header>
               <Title>Company</Title>
            </Header>
            <FuncDesc>A company that is used for posting financial data in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. You can link one
		or more enterprise units from multiple logistic companies to one financial
		company.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="tffst180.leac" OtherIDs="tfgld008.desc">
            <Header>
               <Title>Ledger Account / Cash Flow Reason</Title>
            </Header>
            <FuncDesc> 
               <Link href="/baanerp/tf/glossary/glossary#LedgerAccoun_tf" role="glossary">ledger account</Link>/ <Link href="/baanerp/tf/glossary/glossary#000471" role="glossary">cash flow reason</Link>
            </FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title> Dimensions</Title>
         <FieldHelp ID="tffst180.dim1">
            <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="tffst180.dim2">
            <Header>
               <Title>Dimension 2</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="tffst180.dim3">
            <Header>
               <Title>Dimension 3</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="tffst180.dim4">
            <Header>
               <Title>Dimension 4</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="tffst180.dim5">
            <Header>
               <Title>Dimension 5</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>
      </FieldGroup>
      <FieldGroup>
         <Title> General Data</Title>
         <FieldGroup>
            <Title> Origin</Title>
            <FieldHelp ID="tffst180.orig">
               <Header>
                  <Title>Origin</Title>
               </Header>
               <FuncDesc>Indicates the type of transaction.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.sequ">
               <Header>
                  <Title>Sequence Number</Title>
               </Header>
               <FuncDesc>The number that identifies a data record or a step in a
		sequence of activities. Sequence numbers are used in many contexts. Usually ERP Enterprise generates the
		sequence number for the next item or step. Depending on the context, you can
		overwrite this number. You can sometimes influence the numbering by setting the
		corresponding parameters.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.budg">
               <Header>
                  <Title>Budget</Title>
               </Header>
               <FuncDesc>A plan of units or amounts allowed to be spent on certain
		objects such as departments, cost centers, items, or item groups.</FuncDesc>
               <SimpleSection>
                  <Paragraph>This plan can be evaluated with the actual figures
		  afterwards, and it can be compared with other budgets. In addition, you can
		  simulate different scenarios.</Paragraph>
               </SimpleSection>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Transaction</Title>
            <FieldHelp ID="tffst180.catg">
               <Header>
                  <Title>Transaction Category</Title>
               </Header>
               <FuncDesc>A way to categorize transaction types, for example journal
		vouchers, recurring/reverse journals, purchase invoices, and sales invoices.
		The category defines how to process a transaction linked to the selected
		transaction type.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.ttyp">
               <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="tffst180.docn">
               <Header>
                  <Title>Document</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="tffst180.lino">
               <Header>
                  <Title>Line</Title>
               </Header>
               <FuncDesc>The line number.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.serl">
               <Header>
                  <Title>Document Sequence Number</Title>
               </Header>
               <FuncDesc>The number that identifies a data record or a step in a
		sequence of activities. Sequence numbers are used in many contexts. Usually ERP Enterprise generates the
		sequence number for the next item or step. Depending on the context, you can
		overwrite this number. You can sometimes influence the numbering by setting the
		corresponding parameters.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.srno">
               <Header>
                  <Title>Background Sequence No.</Title>
               </Header>
               <FuncDesc/>
            </FieldHelp>
            <FieldHelp ID="tffst180.btno">
               <Header>
                  <Title>Batch</Title>
               </Header>
               <FuncDesc>A group of financial transactions processed together. If you
		finalize a batch, all the transactions are processed, or if an error occurs, no
		transactions are processed.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Amounts</Title>
            <FieldHelp ID="tffst180.amnt">
               <Header>
                  <Title>Report Amount</Title>
               </Header>
               <FuncDesc>The amount in the statement currency.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst100.rcur">
               <Header>
                  <Title>Report Amount</Title>
               </Header>
               <FuncDesc>The currency in which the report amount is
				expressed.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.tamn">
               <Header>
                  <Title>Transaction Amount</Title>
               </Header>
               <FuncDesc>The amount in the transaction currency. (Finalized or
				non-finalized transactions only.)</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.ccur">
               <Header>
                  <Title>Transaction Amount</Title>
               </Header>
               <FuncDesc>The currency in which the transaction amount is
				expressed.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.tamh">
               <Header>
                  <Title>Amount in Home Currency</Title>
               </Header>
               <FuncDesc>The amount in the home currency. (Finalized or
				non-finalized transactions only.)</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="e.screen.hcur">
               <Header>
                  <Title>Amount in Home Currency</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>
         </FieldGroup>
         <FieldGroup>
            <Title> Transaction Data</Title>
            <FieldHelp ID="tffst180.year">
               <Header>
                  <Title>Year</Title>
               </Header>
               <FuncDesc>The fiscal year to which the transaction
				applies.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.peri">
               <Header>
                  <Title>Period</Title>
               </Header>
               <FuncDesc>The fiscal period to which the transaction
				applies.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.duac">
               <Header>
                  <Title>Dual Accounting Indicator</Title>
               </Header>
               <FuncDesc>Indicates whether the amount is a debit amount or a credit
				amount.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="tffst180.bpid">
               <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>
         </FieldGroup>
      </FieldGroup>
   </Fields>
   <FormCommands>
      <CommandHelp ID="show.finalized.trans">
         <Header>
            <Title>Finalized Transaction Lines</Title>
         </Header>
         <FuncDesc>Starts the <Link href="/baanerp/tf/gld/tfgld1509m000" role="session">Finalized Transaction Lines (tfgld1509m000)</Link> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="show.finalized.detail">
         <Header>
            <Title>Finalized Transaction Details</Title>
         </Header>
         <FuncDesc>Starts the <Link href="/baanerp/tf/gld/tfgld1503s000" role="session">Finalized Transaction Details (tfgld1503s000)</Link> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="show.non.finalized.trans">
         <Header>
            <Title>Non-Finalized Transaction Lines</Title>
         </Header>
         <FuncDesc>Starts the <Link href="/baanerp/tf/gld/tfgld1508m000" role="session">Non-Finalized Transaction Lines (tfgld1508m000)</Link> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="show.non.finalized.detail">
         <Header>
            <Title>Non-Finalized Transaction Details</Title>
         </Header>
         <FuncDesc>Starts the <Link href="/baanerp/tf/gld/tfgld1501s000" role="session">Non-Finalized Transaction Details (tfgld1501s000)</Link> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="show.budgets">
         <Header>
            <Title>Budget Details</Title>
         </Header>
         <FuncDesc>Starts the <Link href="/baanerp/tf/fbs/tffbs1100s000" role="session">Budget Amount and Quantities by Year (tffbs1100s000)</Link> session.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="show.cash.flow">
         <Header>
            <Title>Cash Flow Transactions</Title>
         </Header>
         <FuncDesc>Starts the <Link href="/baanerp/tf/gld/tfgld1523m000" role="session">Cash Flow Transactions (tfgld1523m000)</Link> session.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>