<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tf/fam/tffam8407m000" xml:lang="en">
   <Header>
      <Title>Print Transaction Summary (tffam8407m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to print
		  a <Link href="/baanerp/tf/glossary/glossary#000149" role="glossary">transaction</Link> 
            <Link href="/baanerp/tf/glossary/glossary#000158" role="glossary">inquiry</Link> after specifying
		  information in the selection range fields. By specifying ranges of data in the
		  selection range fields, you can filter the print results.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000095" role="manual">Transaction Inquiry Process</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="acct.f">
         <Header>
            <Title>Ledger 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="acct.t">
         <Header>
            <Title>Ledger 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="dim1.f">
         <Header>
            <Title>Dummy Label</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="dim1.t">
         <Header>
            <Title>Dummy Label</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="dim2.f">
         <Header>
            <Title>Dummy Label</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="dim2.t">
         <Header>
            <Title>Dummy Label</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="dim3.f">
         <Header>
            <Title>Dummy Label</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="dim3.t">
         <Header>
            <Title>Dummy Label</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="dim4.f">
         <Header>
            <Title>Dummy Label</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="dim4.t">
         <Header>
            <Title>Dummy Label</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="dim5.f">
         <Header>
            <Title>Dummy Label</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="dim5.t">
         <Header>
            <Title>Dummy Label</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="book.f">
         <Header>
            <Title>Asset Book</Title>
         </Header>
         <FuncDesc>Identifies the book associated with the asset. Book codes
		permit you to define the books used by assets to record transactional data.
		Each asset must have at least one asset-book relationship.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="book.t">
         <Header>
            <Title>Book Code</Title>
         </Header>
         <FuncDesc>Identifies the book associated with the asset. Book codes
		permit you to define the books used by assets to record transactional data.
		Each asset must have at least one asset-book relationship.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="form.sumb">
         <Header>
            <Title>Summarize by</Title>
         </Header>
         <FuncDesc>Summarize <Link href="/baanerp/tf/glossary/glossary#000149" role="glossary">transaction</Link> by selecting
		  period or year.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="form.hcur">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>One of a company's base currencies in which LN 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>
         <SimpleSection>
            <Paragraph>From the Tools menu, choose Rotate Currency to switch home currencies.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="loc1.f">
         <Header>
            <Title>Location Code 1</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc1.t">
         <Header>
            <Title>Location Code 1</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc2.f">
         <Header>
            <Title>Location 2</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc2.t">
         <Header>
            <Title>Location Code 2</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc3.f">
         <Header>
            <Title>Location 3</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc3.t">
         <Header>
            <Title>Location Code 3</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc4.f">
         <Header>
            <Title>Location 4</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc4.t">
         <Header>
            <Title>Location Code 4</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc5.f">
         <Header>
            <Title>Location 5</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc5.t">
         <Header>
            <Title>Location Code 5</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc6.f">
         <Header>
            <Title>Location 6</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc6.t">
         <Header>
            <Title>Location Code 6</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc7.f">
         <Header>
            <Title>Location 7</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc7.t">
         <Header>
            <Title>Location Code 7</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc8.f">
         <Header>
            <Title>Location 8</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="loc8.t">
         <Header>
            <Title>Location Code 8</Title>
         </Header>
         <FuncDesc>A location defines the physical site of an asset. A location
		consists of up to eight segments, each of which further defines the precise
		site of an asset.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>