<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tf/fam/tffam8470m000" xml:lang="en">
   <Header>
      <Title>Print Accumulated Depreciation by Location (tffam8470m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to provide a summary of <Link href="/baanerp/tf/glossary/glossary#000109" role="glossary">acquired</Link>, <Link href="/baanerp/tf/glossary/glossary#000147" role="glossary">transferred</Link>, <Link href="/baanerp/tf/glossary/glossary#000119" role="glossary">disposed</Link>, and fully
		  depreciated <Link href="/baanerp/tf/glossary/glossary#000149" role="glossary">asset-related transactions</Link> and <Link href="/baanerp/tf/glossary/glossary#000114" role="glossary">asset books</Link> for a specified
		  range of periods. Only <Link href="/baanerp/tf/glossary/glossary#000129" role="glossary">depreciated</Link> values will
		  appear.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/basictasks/000006" role="manual">To use From and To fields</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <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="loc1.f">
         <Header>
            <Title>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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>Dummy Label</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="screen.hcur">
         <Header>
            <Title>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>
         <SimpleSection>
            <Paragraph>From the Tools menu, choose Rotate Currency to switch home currencies.</Paragraph>
         </SimpleSection>
      </FieldHelp>
   </Fields>
</Session>