<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/bc/ttf/bcttf0110m000" xml:lang="en">
   <Header>
      <Title>Dimension Mapping (bcttf0110m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view the additional
		  fields from Baan IVc (=Elements in ERP LN 6.1) that are used to define the value on field <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.dimx" role="manual">Dimension</GUIRef>. This session can also be used to change
		  the <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.dimx" role="manual">Dimension</GUIRef> that will be used in the integration
		  mapping scheme. The fields <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.dimx" role="manual">Dimension</GUIRef> and <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.used" role="manual">To be Used</GUIRef> can be changed on each view. At the first form the data about
		  the originating <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.fitr" role="manual">Financial Transaction</GUIRef> is visible. At the next forms
		  the elements (i.e. item and warehouse) are visible that are used to determine
		  the <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.dimx" role="manual">Dimension</GUIRef>.</Paragraph>
         <Paragraph>This maintain session prepares the input for session <GUIRef href="/baanerp/bc/ttf/bcttf0201m000" role="session">Migrate Mapping Scheme (bcttf0201m000)</GUIRef>. Dependent on the filled additional fields of Baan IVc, the element groups and the elements by element groups of
		  dimension mapping are generated.</Paragraph>
      </AimSection>
      <GeneralSection>
         <SectionTitle>Preparation</SectionTitle>
         <Paragraph>Not applicable.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Execution</SectionTitle>
         <Paragraph>It is strongly advised to start this session to judge the
		  dimensions and the indication ‘To be Used’ before running session <GUIRef href="/baanerp/bc/ttf/bcttf0201m000" role="session">Migrate Mapping Scheme (bcttf0201m000)</GUIRef>.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Process logic</SectionTitle>
         <Paragraph>If this session is started for the first time then the data
		  from interim table bcttf006 is copied to the table bcttf010. A new field <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.bona" role="manual">Business Object Name</GUIRef> is filled based on the
		  reconciliation group and the financial transaction. For example the Transaction
		  Origin = Purchase will be connected to the ‘Purchase Order’. This <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.bona" role="manual">Business Object Name</GUIRef> is used to group the same
		  elements in a priority. The <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.prio" role="manual">Priority</GUIRef> is filled with an increasing value per
		  reconciliation group, companies, <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.dimn" role="manual">Dimension Type</GUIRef> and <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.bona" role="manual">Business Object Name</GUIRef>.</Paragraph>
         <Paragraph>In contrast with the ledger account mapping (session <GUIRef href="/baanerp/bc/ttf/bcttf0105m000" role="session">Ledger Mapping (bcttf0105m000)</GUIRef>) all lines will be flagged with <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.used" role="manual">To be Used</GUIRef> = Yes. The reason is that dimension mapping can have
		  overlapping ranges. The second reason is that it is not mandatory that
		  dimensions of the debit and the credit postings that are ‘clearing’ interim
		  accounts are the same.</Paragraph>
         <Paragraph>Dependent on the reconciliation group the elements that can be
		  used in ERP LN 6.1, are marked with ‘Yes’. Some elements can be filled with data
		  from Baan IVc but can be marked with ‘No’ if this addition is
		  not longer available in ERP LN 6.1. For example: For sales orders the elements Order Series, Item,
		  Item Group, Statistic Group, Warehouse, Item Cost Component, Project, Customer,
		  Financial B.P. Group (A/R), Employee, Trade Group, Country, Area, Line of
		  Business, Order Type can be used.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Duration</SectionTitle>
         <Paragraph>Warning: Execution of this session takes some time if it is
		  started for the first time. The next time it will be faster.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Restart</SectionTitle>
         <Paragraph>Not applicable.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>General Migration Topics: <Link href="/baanerp/baaniv/tech/general/GTtfgld0002" role="manual">To migrate dimensions to integration mapping scheme (tfgld0002)</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldGroup>
         <Title>Dimension Mapping</Title>
         <FieldHelp>
            <Header>
               <Title>Reconciliation Group</Title>
            </Header>
            <FuncDesc>The reconciliation group that is determined based on the <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.tror" role="manual">Transaction Origin</GUIRef> and <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.fitr" role="manual">Financial Transaction</GUIRef> where the mapping data is
		  defined.</FuncDesc>
            <RelatedTopics>
               <SectionTitle>Related topics</SectionTitle>
               <RelTopic>General Migration Topics: <Link href="/baanerp/baaniv/tech/general/GTtfgld0002" role="manual">To migrate dimensions to integration mapping scheme (tfgld0002)</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Business Object Name</Title>
            </Header>
            <FuncDesc>The business object name is filled based on the reconciliation
		  group, <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.tror" role="manual">Transaction Origin</GUIRef>, <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.fitr" role="manual">Financial Transaction</GUIRef> and <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.adtp" role="manual">Additional Type</GUIRef>.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Dimension Type</Title>
            </Header>
            <FuncDesc>The dimension type indicates which of the five types belongs to
		  the <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.dimx" role="manual">Dimension</GUIRef>.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Logistic Company</Title>
            </Header>
            <FuncDesc>The logistic company for which the mapping will be used. If
		  this field is filled with zero, then the mapping is applicable for all logistic
		  companies.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Financial Company</Title>
            </Header>
            <FuncDesc>The financial company for which the mapping will be used. If
		  this field is filled with zero, then the mapping is applicable for all
		  financial companies.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Priority</Title>
            </Header>
            <FuncDesc>The priority of the mapping. A low number is found first in the
		  mapping process.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Sequence</Title>
            </Header>
            <FuncDesc>The sequence always has the value ‘1’.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Transaction Origin</Title>
            </Header>
            <FuncDesc>The origin of the transaction for which the mapping will be
		  used. Note that the values of this field are taken over from Baan IVc. In ERP LN 6.1 other values are applicable for this field.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Financial Transaction</Title>
            </Header>
            <FuncDesc>The financial transaction for which the mapping will be used.
		  Note that the values of this field are taken over from Baan IVc. In ERP LN 6.1 other values are applicable for this field.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Project Transaction</Title>
            </Header>
            <FuncDesc>This field indicates whether the dimension originates from
		  project specific mapping in Baan IVc.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Additional Type</Title>
            </Header>
            <FuncDesc>This field contains an additional value to separate a mapping
		  within one combination of transaction origin and financial transaction. The
		  first 8 values of this field are taken over 1:1 from Baan IVc (Invoice Totals, Late Payment Surcharge, Order Discount, Material
		  Costs, Operation Costs, Revenues, Rebate, Commission). The other values are new
		  defined ones for example to separate between transactions that are split in ERP LN 6.1.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Debit/Credit</Title>
            </Header>
            <FuncDesc>The indicator whether the mapping is used for the debit or for
		  the credit side of the financial transaction.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>To be used</Title>
            </Header>
            <FuncDesc>This flag indicates whether the mapping – line will be used
		  during generation of the mapping scheme.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Dimension</Title>
            </Header>
            <FuncDesc>This dimension is used to map the financial transactions that
		  originate from the several packages.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>General</Title>
         <FieldHelp>
            <Header>
               <Title>Item</Title>
            </Header>
            <FuncDesc>This element Item is filled from the mapping by element or the
		  mapping by range of Baan IVc, see session <GUIRef href="/baanerp/tf/gld/tfgld4121m000" role="session">Maintain Options by Integration Element (tfgld4121m000)</GUIRef>. The ‘Yes/No’ flag indicates
		  whether this element is available in ERP LN 6.1. Also a From and a To value is show. Note that for elements that
		  are not used for mapping, the minimum and the maximum value are
		  filled.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Item Group</Title>
            </Header>
            <FuncDesc>The element Item Group is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Statistic Group</Title>
            </Header>
            <FuncDesc>The element Statistic Group is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Warehouse</Title>
            </Header>
            <FuncDesc>The element Warehouse is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Project</Title>
            </Header>
            <FuncDesc>The element Project is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Item Cost Component</Title>
            </Header>
            <FuncDesc>The element Item Cost Component is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Work Center</Title>
            </Header>
            <FuncDesc>The element Work Center is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Order Series</Title>
            </Header>
            <FuncDesc>The element Order Series is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Order Type</Title>
            </Header>
            <FuncDesc>The element Order Type is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Country</Title>
            </Header>
            <FuncDesc>The element Country is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Area</Title>
            </Header>
            <FuncDesc>The element Area is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Line of Business</Title>
            </Header>
            <FuncDesc>The element Line Of Business is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Employee</Title>
            </Header>
            <FuncDesc>The element Employee is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Trade Group</Title>
            </Header>
            <FuncDesc>The element Trade Group is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Transaction Type</Title>
            </Header>
            <FuncDesc>The element Transaction Type is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Reason Code</Title>
            </Header>
            <FuncDesc>The element Reason Code is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Container</Title>
            </Header>
            <FuncDesc>The element Container is shown here.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>Business Partner</Title>
         <FieldHelp>
            <Header>
               <Title>Supplier</Title>
            </Header>
            <FuncDesc>The element Supplier is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Financial B.P. Group (A/P)</Title>
            </Header>
            <FuncDesc>The element Business Partner Group Accounts Payable is shown
		  here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Customer</Title>
            </Header>
            <FuncDesc>The element Customer is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Financial B.P. Group (A/R)</Title>
            </Header>
            <FuncDesc>The element Business Partner Group Accounts Receivable is shown
		  here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Financial B.P. Group (A/R) PCS Project</Title>
            </Header>
            <FuncDesc>The element Business Partner Group Accounts Receivable of the
		  PCS Project is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Financial B.P. Group (A/R) Service Contract</Title>
            </Header>
            <FuncDesc>The element Business Partner Group Accounts Receivable of the
		  service contract is shown here.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>Production</Title>
         <FieldHelp>
            <Header>
               <Title>Main Item</Title>
            </Header>
            <FuncDesc>The element Main Item is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Main Item Group</Title>
            </Header>
            <FuncDesc>The element Main Item Group is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Main Warehouse</Title>
            </Header>
            <FuncDesc>The element Main Warehouse is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Main Work Center</Title>
            </Header>
            <FuncDesc>The element Main Work Center is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Machine</Title>
            </Header>
            <FuncDesc>The element “Machine” is shown here.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>Service</Title>
         <FieldHelp>
            <Header>
               <Title>Service Contract</Title>
            </Header>
            <FuncDesc>The element Service Contract is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Service Contract Type</Title>
            </Header>
            <FuncDesc>The element Service Contract Type is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Warranty</Title>
            </Header>
            <FuncDesc>The element Warranty is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Service Order Type</Title>
            </Header>
            <FuncDesc>The element Service Order Type is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Cost Type (TS)</Title>
            </Header>
            <FuncDesc>The element Cost Type of Service is shown
		  here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Cost Type Group</Title>
            </Header>
            <FuncDesc>The element Cost Type Group is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Service Car</Title>
            </Header>
            <FuncDesc>The element Service Car is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Cluster</Title>
            </Header>
            <FuncDesc>The element Cluster is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Service Area</Title>
            </Header>
            <FuncDesc>The element Service Area is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Installation</Title>
            </Header>
            <FuncDesc>The element Installation is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Installation Type</Title>
            </Header>
            <FuncDesc>The element Installation Type is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Cost Analysis Type</Title>
            </Header>
            <FuncDesc>The element Cost Analysis Type is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Package Part</Title>
            </Header>
            <FuncDesc>The element Package Part is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Servicing</Title>
            </Header>
            <FuncDesc>The element Servicing is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Service Package</Title>
            </Header>
            <FuncDesc>The element Service Package is shown here.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>TP Project</Title>
         <FieldHelp>
            <Header>
               <Title>Element</Title>
            </Header>
            <FuncDesc>The element Element is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Cost Component</Title>
            </Header>
            <FuncDesc>The element Cost Component of Project is shown
		  here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Category</Title>
            </Header>
            <FuncDesc>The element Category is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Financing Method</Title>
            </Header>
            <FuncDesc>The element Financing Method is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Acquisition Method</Title>
            </Header>
            <FuncDesc>The element Acquisition Method is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Task</Title>
            </Header>
            <FuncDesc>The element Task is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Equipment</Title>
            </Header>
            <FuncDesc>The element Equipment is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Subcontracting</Title>
            </Header>
            <FuncDesc>The element Subcontracting is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Sundry Cost</Title>
            </Header>
            <FuncDesc>The element Sundry Cost is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Revenue Code</Title>
            </Header>
            <FuncDesc>The element Revenue Code is shown here.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>Commissions and Rebates</Title>
         <FieldHelp>
            <Header>
               <Title>Commission/Rebate Group</Title>
            </Header>
            <FuncDesc>The element Commission or Rebate Group is shown
		  here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Relation</Title>
            </Header>
            <FuncDesc>The element Relation is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Agreement Group</Title>
            </Header>
            <FuncDesc>The element Agreement Group is shown here.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>Transportation</Title>
         <FieldHelp>
            <Header>
               <Title>Transport Means Group</Title>
            </Header>
            <FuncDesc>The element Transport Means Group is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Means of Transport 1</Title>
            </Header>
            <FuncDesc>The element Means of Transport 1 is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Means of Transport 2</Title>
            </Header>
            <FuncDesc>The element Means of Transport 2 is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Standard Route</Title>
            </Header>
            <FuncDesc>The element Standard Route is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Transport Type</Title>
            </Header>
            <FuncDesc>The element Transport Type is shown here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Employee (Transportation)</Title>
            </Header>
            <FuncDesc>The element Employee of Transportation is shown
		  here.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Employee Department</Title>
            </Header>
            <FuncDesc>The element Employee Department is shown here.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
   </Fields>
</Session>