<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tf/fam/tffam1402m000" xml:lang="en">
   <Header>
      <Title>Print FAS 109 Deferred Tax Report (tffam1402m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to print a report
		  indicating the deferred tax component created by the timing difference between <Link href="/baanerp/tf/glossary/glossary#000114" role="glossary">asset books</Link>. You must specify one financial type book and one other comparison
		  tax book ( <Link href="/baanerp/tf/glossary/glossary#000155" role="glossary">Federal Tax-U.S</Link> or <Link href="/baanerp/tf/glossary/glossary#000157" role="glossary">Other Tax-U.S</Link>). You must enter the tax rate on the Options form.</Paragraph>
      </AimSection>
      <GeneralSection/>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000163" role="manual">Reporting</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000082" role="manual">Financial - U.S. Books</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000083" role="manual">Federal Tax - U.S.</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000084" role="manual">Other Tax - U.S.</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="book2">
         <Header>
            <Title>Tax 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="tax.rate">
         <Header>
            <Title>Tax Rate</Title>
         </Header>
         <FuncDesc>The tax percentage for each tax code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="agrp.f">
         <Header>
            <Title>Asset Group</Title>
         </Header>
         <FuncDesc>A broader level of grouping than an asset category. Used to
		classify your organization's assets for reporting and inquiry.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="agrp.t">
         <Header>
            <Title>Asset Group Code</Title>
         </Header>
         <FuncDesc>A broader level of grouping than an asset category. Used to
		classify your organization's assets for reporting and inquiry.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ctgy.f">
         <Header>
            <Title>Category</Title>
         </Header>
         <FuncDesc>Used to classify an asset and provide data entry defaults
		during asset entry. Categories have associated subcategories, which are
		assigned by default.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ctgy.t">
         <Header>
            <Title>Category</Title>
         </Header>
         <FuncDesc>Used to classify an asset and provide data entry defaults
		during asset entry. Categories have associated subcategories, which are
		assigned by default.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="sctg.f">
         <Header>
            <Title>Subcategory</Title>
         </Header>
         <FuncDesc>Subcategories provide additional classification of assets
		within a category. For each category, you enter one or multiple subcategories.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="sctg.t">
         <Header>
            <Title>Subcategory Code</Title>
         </Header>
         <FuncDesc>Subcategories provide additional classification of assets
		within a category. For each category, you enter one or multiple subcategories.</FuncDesc>
      </FieldHelp>
      <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="screen.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>
      </FieldHelp>
      <FieldHelp ID="dim1.f">
         <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="dim1.t">
         <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="dim2.f">
         <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="dim2.t">
         <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="dim3.f">
         <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="dim3.t">
         <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="dim4.f">
         <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="dim4.t">
         <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="dim5.f">
         <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>
      <FieldHelp ID="dim5.t">
         <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>
      <FieldHelp ID="loc1.f">
         <Header>
            <Title>Location 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 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 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 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 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 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 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 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 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>