<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/bc/ttf/bcttf0201m000" xml:lang="en">
   <Header>
      <Title>Migrate Mapping Scheme (bcttf0201m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to create a integration
		  mapping scheme, based on ledger accounts, dimensions, transaction types and
		  series that are defined in Baan IVc. This session makes use of the data of tables:</Paragraph>
         <List>
            <ListItem>Ledger Mapping to be migrated (bcttf005)</ListItem>
            <ListItem>Dimension Mapping to be migrated (bcttf010)</ListItem>
            <ListItem>Transaction Types (bcttf011)</ListItem>
         </List>
         <Paragraph>Data will be created in ERP Enterprise tables:</Paragraph>
         <List>
            <ListItem>Element Groups (tfgld467)</ListItem>
            <ListItem>Elements by Element Group (tfgld468)</ListItem>
            <ListItem>Ledger Mapping (tfgld469)</ListItem>
            <ListItem>Elements by Ledger Mapping (tfgld470)</ListItem>
            <ListItem>Dimension Mapping (tfgld471)</ListItem>
            <ListItem>Elements by Dimension Mapping (tfgld472)</ListItem>
            <ListItem>Mapping Schema Details (tfgld474)</ListItem>
            <ListItem>Document Numbering / Compression (tfgld477)</ListItem>
            <ListItem>Default Accounts (tfgld478)</ListItem>
         </List>
      </AimSection>
      <GeneralSection>
         <SectionTitle>Preparation</SectionTitle>
         <Paragraph>Before you can use this session:</Paragraph>
         <List>
            <ListItem>The migration of tables Ledger Mapping Base (bcttf001),
			 Ledger Mapping (Project and Service) (bcttf002), Dimension Mapping Base
			 (bcttf006) and Transaction Types (bcttf011) must be done.</ListItem>
            <ListItem>The migration of table Mapping Schemas (tfgld473) must be
			 done, or a record must be added manually in this table with session <GUIRef href="/baanerp/tf/gld/tfgld4573m000" role="session">Mapping Scheme (tfgld4573m000)</GUIRef>.</ListItem>
            <ListItem>The migration of master data must be finished.</ListItem>
            <ListItem>The session <GUIRef href="/baanerp/tc/fin/tcfin0210m000" role="session">Initialize Mapping Scheme Data (tcfin0210m000)</GUIRef> must be run.</ListItem>
            <ListItem>It is recommended to start the sessions <GUIRef href="/baanerp/bc/ttf/bcttf0105m000" role="session">Ledger Mapping (bcttf0105m000)</GUIRef> and <GUIRef href="/baanerp/bc/ttf/bcttf0110m000" role="session">Dimension Mapping (bcttf0110m000)</GUIRef> to check (and maybe change) the mapping that will be
			 generated.</ListItem>
         </List>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Execution</SectionTitle>
         <Paragraph>This session must be executed to migrate mapping scheme
		  data.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>User Interface logic</SectionTitle>
         <Note>
            <SectionTitle>Tab General</SectionTitle>
            <List>
               <ListItem>The check boxes Warehouse Issue, Warehouse Receipt,
				Warehouse Order, Adjustment Order, Cycle Counting Order and Revaluation Order
				are disabled with the value No if the package Warehouse Management is not
				implemented in the company in which the session is started in session <GUIRef href="/baanerp/tc/com/tccom0500m000" role="session">Implemented Software Components (tccom0500m000)</GUIRef>.</ListItem>
               <ListItem>The check box People is disabled with value No if the
				package People is not implemented.</ListItem>
               <ListItem>The check boxes Sales Order, Purchase Order and Purchase
				Contract are disabled with value No if the package Order Management is not
				implemented.</ListItem>
               <ListItem>The check box Production Order is disabled with value No
				if the package Manufacturing is not implemented.</ListItem>
               <ListItem>The check box Project (PCS) is disabled with value No if
				the module Project Control is not implemented.</ListItem>
               <ListItem>The check boxes Project Costs &amp; Commitments and
				Project Revenues are disabled with value No if the package Project is not
				implemented.</ListItem>
               <ListItem>The check boxes Service Order and Service Contract are
				disabled with value No if the package Service is not implemented</ListItem>
               <ListItem>The check boxes Freight Order, Freight Shipment and
				Freight Order Cluster are disabled with value No if the package Freight
				Management is not implemented.</ListItem>
            </List>
            <Paragraph>If a check box is disabled with value No, the related Tab is
			 not visible either.</Paragraph>
         </Note>
         <Note>
            <SectionTitle>Other Tabs</SectionTitle>
            <Paragraph>It is only possible to fill one ledger account for a
			 reconciliation group. For every reconciliation group, there is only one place
			 where the ledger account is enabled. If the ledger account is filled or changed
			 in this place, all other places for the same reconciliation group are also
			 changed.</Paragraph>
            <Paragraph>Example: The debit Reconciliation Group for Warehouse
			 Issue/Issue is Interim Transit/1. The credit Reconciliation Group for Sales
			 Order/Issue is also Interim Transit/1. If both the packages Warehouse
			 Management and Order Management are implemented, only the Default Account
			 (Credit) for Warehouse Issue/Issue is enabled. When this one is filled or
			 changed, automatically the Default Account (Debit) for Sales Order/Issue is
			 changed. The link between Reconciliation Groups and Transaction
			 Origin/Financial Transaction combination can be found in session <GUIRef href="/baanerp/tc/fin/tcfin0115m000" role="session">Integration Document Types by Reconciliation Group (tcfin0115m000)</GUIRef>.</Paragraph>
         </Note>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Process logic</SectionTitle>
         <GeneralSection>
            <SectionTitle>Starting the session</SectionTitle>
            <List>
               <ListItem>If session <GUIRef href="/baanerp/bc/ttf/bcttf0105m000" role="session">Ledger Mapping (bcttf0105m000)</GUIRef> is not started before this session is started, table
				Ledger Mapping to be migrated (bcttf005) is filled based on Ledger Mapping Base
				(bcttf001) and Ledger Mapping (Project and Service) (bcttf002).</ListItem>
               <ListItem>If session <GUIRef href="/baanerp/bc/ttf/bcttf0110m000" role="session">Dimension Mapping (bcttf0110m000)</GUIRef> is not started before this session is started, table
				Dimension Mapping to be migrated (bcttf010) is filled based on Dimension
				Mapping Base (bcttf006).</ListItem>
               <ListItem>When the session is started, the following defaults are
				retrieved: <List>
                     <ListItem>The check box Simulate gets the value Yes</ListItem>
                     <ListItem>The check boxes for the Transaction Origin gets the
					 default value Yes if the related package or module is implemented.</ListItem>
                     <ListItem>The default Transaction Type and the default Series on
					 tab General are defaulted from table Integration Parameters (tfgld450).</ListItem>
                     <ListItem>The ledger account for currency differences is not
					 defaulted.</ListItem>
                     <ListItem>The check box compression is defaulted by selecting
					 just one record of table Transaction Types (bcttf011).</ListItem>
                     <ListItem>The Transaction Type and Series for a Transaction
					 Origin/Financial Transaction combination are defaulted from table Transaction
					 Types (bcttf011), by selecting a transaction that is analogous to this
					 combination (or looks a lot like that). If there is not such a transaction in
					 table Transaction Types (bcttf011), the fields remain empty.</ListItem>
                     <ListItem>The ledger accounts are defaulted from table Ledger
					 Mapping to be migrated (bcttf005), where a ledger account is chosen with a low
					 priority, as this is normally the “last-option” ledger account for the
					 reconciliation group.</ListItem>
                  </List>
               </ListItem>
            </List>
         </GeneralSection>
         <GeneralSection>
            <SectionTitle>Press the Continue button</SectionTitle>
            <Paragraph>The process is doing the following steps for every
			 Transaction Origin/Financial Transaction combination:</Paragraph>
            <GeneralSection>
               <SectionTitle>Step 1</SectionTitle>
               <Paragraph>In Financials, table Document Numbering / Compression
				(tfgld477) is filled in the following way in case a transaction type can be
				found.</Paragraph>
               <List>
                  <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.mscd" role="manual">Mapping Scheme Code</GUIRef> is filled with the mapping scheme code
				  defined on the form.</ListItem>
                  <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.msvs" role="manual">Mapping Scheme Version</GUIRef> is filled with the mapping
				  scheme version on the form.</ListItem>
                  <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.idtc" role="manual">Integration Document Type</GUIRef> is filled with the
				  integration document type that is retrieved from table Integration Document
				  Type by Transaction (tcfin010) for the Transaction Origin/Financial Transaction
				  combination.</ListItem>
                  <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.ocmp" role="manual">Business Object Company</GUIRef> and field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.fcmp" role="manual">Financial Company</GUIRef> are filled with 0, which means that
				  the transaction type and series are used in every company. So they should be
				  shared or defined in every company.</ListItem>
                  <ListItem>tfgld477.sdla and tfgld477.scla remain empty.</ListItem>
                  <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.ttyp" role="manual">Transaction Type</GUIRef> is filled with the transaction type
				  defined on the form for the Transaction Origin/Financial Transaction
				  Combination. If this one is empty, it is filled with the default transaction
				  type defined on the form (tab General). If this one is also empty, no record is
				  created in table Document Numbering / Compression (tfgld477).</ListItem>
                  <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.seri" role="manual">Series</GUIRef> is filled with the series defined on the form
				  for the Transaction Origin/Financial Transaction Combination if the transaction
				  type is defined for this combination. If this one is empty, it is filled with
				  the default series defined on the form (tab General).</ListItem>
                  <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.dcot" role="manual">Compression of Debit Transactions</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.ccot" role="manual">Compression of Credit Transactions</GUIRef> are filled with
				  the value of the check box Compression of transactions on the form.</ListItem>
               </List>
            </GeneralSection>
         </GeneralSection>
         <GeneralSection>
            <SectionTitle>Step 2</SectionTitle>
            <Paragraph>Every transaction origin/financial transaction combination
			 has a reconciliation group (debit) and a reconciliation group (credit). See
			 also session <GUIRef href="/baanerp/tc/fin/tcfin0115m000" role="session">Integration Document Types by Reconciliation Group (tcfin0115m000)</GUIRef>. The following steps are done for both the
			 reconciliation groups. So they are done twice for every transaction
			 origin/financial transaction combination:</Paragraph>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>a. An element group for ledger mapping is inserted in table
			 Element Groups (tfgld467). This is only done if a mapping is available for the
			 Reconciliation Group in table Ledger Mapping to be migrated (bcttf005). This
			 means that at least one record exists for the Reconciliation Group with a
			 certain element flagged as yes (so it is applicable) and the related element
			 values are not equal to the minimum value and maximum value (strings) or not
			 equal to empty (enumerates). Example: For a certain Reconciliation Group only
			 one record is present. This record has the following data.</Paragraph>
            <TABLE width="100%" border="1" borderstyle="default"
                   space-and-orientation="indented-estimated">
               <TBODY noTR="2">
                  <TR no="1" isLast="false">
                     <TH colspan="3" rowspan="1">Warehouse</TH>
                     <TH colspan="3" rowspan="1">Project</TH>
                     <TH colspan="3" rowspan="1">Country</TH>
                  </TR>
                  <TR no="2" isLast="true">
                     <TD rowspan="1" colspan="1">V</TD>
                     <TD rowspan="1" colspan="1"/>
                     <TD rowspan="1" colspan="1">ZZZZZZ</TD>
                     <TD rowspan="1" colspan="1">V</TD>
                     <TD rowspan="1" colspan="1">PRJ1</TD>
                     <TD rowspan="1" colspan="1">PRJ!</TD>
                     <TD rowspan="1" colspan="1"/>
                     <TD rowspan="1" colspan="1">NL</TD>
                     <TD rowspan="1" colspan="1">USA</TD>
                  </TR>
               </TBODY>
            </TABLE>
            <Paragraph>This means in this case that an element group will be
			 created, because Project is flagged as yes (unlike country) and has values that
			 are not equal to the minimum and maximum value (unlike warehouse) Insert is
			 done in the following way:</Paragraph>
            <List>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4567m000#tfgld467.mscd" role="manual">Mapping Scheme Code</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4567m000#tfgld467.msvs" role="manual">Mapping Scheme Version</GUIRef> are filled like the same
				fields in table Document Numbering / Compression (tfgld477).</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4567m000#tfgld467.egcd" role="manual">Element Group Code</GUIRef> is a new generated code, based on the
				enumerate values of the Reconciliation Area (3 positions), the Reconciliation
				Sub-Area (4 positions), a defined code for the Business Object (2 positions)
				and a 0 (because it is for Ledger Mapping)</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4568m000#tfgld467.egds" role="manual">Element Group</GUIRef> is a generated description in the
				format 0 (Ledger Mapping) / Reconciliation Area / Reconciliation Sub-Area /
				Business Object Name. For instance: 0/Invoice Accrual/3/Purchase Order.</ListItem>
            </List>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>b. If a record is inserted in table Element Groups
			 (tfgld467), the elements for the element group are inserted in table Elements
			 by Element Group (tfgld468). The elements that must be inserted are selected
			 from table Ledger Mapping to be migrated (bcttf005) from the records for the
			 Reconciliation for which the related element values are not equal to the
			 minimum value and maximum value (strings) or not equal to empty (enumerates).
			 In the example above only Project will be added as element for the element
			 group. Warehouse has the minimum and maximum value and Country is not flagged.
			 Insert is done in the following way:</Paragraph>
            <List>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4568m000#tfgld468.mscd" role="manual">Mapping Scheme Code</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4568m000#tfgld468.msvs" role="manual">Mapping Scheme Version</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4568m000#tfgld468.egcd" role="manual">Element Group Code</GUIRef> are filled like the same fields in
				table Element Groups (tfgld467).</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4568m000#tfgld468.seqn" role="manual">Sequence Number</GUIRef> is the first free number. The first
				element (Project in the example) gets 1, the next element (in the example not
				present) should get 2, and so on.</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4568m000#tfgld468.elcd" role="manual">Element Code</GUIRef> is the element code that can be seen in
				session <GUIRef href="/baanerp/tf/gld/tfgld4558m000" role="session">Elements by Integration Document Type (tfgld4558m000)</GUIRef> for the integration document
				type. Example: for Purchase Order/Receipt, the element code for Project is
				211200000000.</ListItem>
            </List>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>c. If a record is inserted in table Element Groups
			 (tfgld467), the ledger mapping is inserted in table Ledger Mapping (tfgld469).
			 For the given reconciliation group, all records with the checkbox for To Be
			 Used as yes are selected from table Ledger Mapping to be migrated (bcttf005).
			 For every record an insert is done in the following way:</Paragraph>
            <List>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4569m000#tfgld469.mscd" role="manual">Mapping Scheme</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4569m000#tfgld469.msvs" role="manual">Mapping Scheme Version</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4569m000#tfgld469.egcd" role="manual">Element Group Code</GUIRef> are filled like the same fields in
				table Element Groups (tfgld467).</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4569m000#tfgld469.tcmp" role="manual">Business Object Company</GUIRef> is filled with field <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.lcmp" role="manual">Logistic Company</GUIRef>.</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4569m000#tfgld469.fcmp" role="manual">Financial Company</GUIRef> is filled with value of field <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.fcmp" role="manual">Financial Company</GUIRef>.</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4569m000#tfgld469.prio" role="manual">Priority</GUIRef> is filled with value of field <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.prio" role="manual">Priority</GUIRef>. There is one exception: there is a
				restriction in Financials that a record with priority 1 should be present
				always for a combination of Mapping Scheme Code, Mapping Scheme Version and
				Element Group. So the record in table Ledger Mapping to be migrated (bcttf005)
				with the highest priority (even if it is unequal to 1) will get priority 1 in
				table Ledger Mapping (tfgld469).</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4569m000#tfgld469.seqn" role="manual">Sequence</GUIRef> is filled with value of field <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.sern" role="manual">Sequence</GUIRef>. For the record with priority 1 there should
				always be a sequence 1 also. So in case this is not present in table Ledger
				Mapping to be migrated (bcttf005), the lowest value for field <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.sern" role="manual">Sequence</GUIRef> will be replaced by 1 in field <GUIRef href="/baanerp/tf/gld/tfgld4569m000#tfgld469.seqn" role="manual">Sequence</GUIRef>.</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4569m000#tfgld469.leac" role="manual">Ledger Account</GUIRef> is filled with value of field <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.leac" role="manual">Ledger Account</GUIRef>.</ListItem>
            </List>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>d. If a record is inserted in table Ledger Mapping
			 (tfgld469), the elements by ledger mapping must also be inserted in table
			 Elements by Ledger Mapping (tfgld470). This is done for the same records of
			 table Ledger Mapping to be migrated (bcttf005) as are used for filling table
			 Ledger Mapping (tfgld469) and is done in the following way:</Paragraph>
            <List>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.mscd" role="manual">Mapping Scheme</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.msvs" role="manual">Mapping Scheme Version</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.egcd" role="manual">Element Group</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.tcmp" role="manual">Target Logistic Company</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.fcmp" role="manual">Financial Company</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.prio" role="manual">Priority</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.seqn" role="manual">Sequence Number</GUIRef> are filled like the same fields in
				table Ledger Mapping (tfgld469).</ListItem>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.elsn" role="manual">Element Sequence Number</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.elcd" role="manual">Element</GUIRef> are filled with the same values as fields <GUIRef href="/baanerp/tf/gld/tfgld4568m000#tfgld468.seqn" role="manual">Sequence Number</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4568m000#tfgld468.elcd" role="manual">Element Code</GUIRef>.</ListItem>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.evfr" role="manual">Element Value From</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.evto" role="manual">Element Value To</GUIRef> are filled with the element value
				from and the element value to of table Ledger Mapping to be migrated
				(bcttf005). In the example above, for the element project, both fields <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.evfr" role="manual">Element Value From</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.evto" role="manual">Element Value To</GUIRef> are filled with PRJ1. If an element
				value has the maximum domain value in table Ledger Mapping to be migrated
				(bcttf005), the value will be converted to the maximum domain value of the
				element value (which is a string with length 50). Element values that are
				enumerates are inserted as the corresponding number in the domain.</ListItem>
            </List>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>e. Element groups for dimension mapping are inserted in
			 table Element Groups (tfgld467). Like the element group for ledger mapping,
			 this is done only if a mapping is available for the Reconciliation Group in
			 table Dimension Mapping to be migrated (bcttf010). This is done by dimension
			 type and business object. For a reconciliation group a maximum of 5 dimension
			 element groups are inserted by business object. The code of the element group
			 is equal to the code of the element group for ledger mapping, except for the
			 last position. For ledger mapping this is a 0, for dimension mapping this is 1,
			 2, 3, 4 or 5, dependent on the dimension type. Note: the elements for the same
			 reconciliation group and different business objects can be different for the
			 dimension element groups, as dimension mapping is not necessarily
			 balanced.</Paragraph>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>f. If a record for dimension mapping is created in table
			 Element Groups (tfgld467), records must be inserted in table Elements by
			 Element Group (tfgld468) also. This is done in the same way as for ledger
			 mapping, data is retrieved in this case from table Dimension Mapping to be
			 migrated (bcttf010).</Paragraph>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>g. If a record for dimension mapping is created in table
			 Element Groups (tfgld467), a dimension mapping must be created in table
			 Dimension Mapping (tfgld471). For the given reconciliation group and the given
			 business object, all records with the checkbox for To Be Used as yes are
			 selected from table Dimension Mapping to be migrated (bcttf010). For every
			 record an insert is done in the following way:</Paragraph>
            <List>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4571m000#tfgld471.mscd" role="manual">Mapping Scheme Code</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4571m000#tfgld471.msvs" role="manual">Mapping Scheme Version</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4571m000#tfgld471.egcd" role="manual">Element Group Code</GUIRef> are filled like the same fields in
				table Element Groups (tfgld467).</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4571m000#tfgld471.dtyp" role="manual">Dimension Type</GUIRef> is filled with value of field <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.dimn" role="manual">Dimension Type</GUIRef>.</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4571m000#tfgld471.tcmp" role="manual">Business Object Company</GUIRef> is filled with value of field <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.lcmp" role="manual">Logistic Company</GUIRef>.</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4571m000#tfgld471.fcmp" role="manual">Financial Company</GUIRef> is filled with value of field <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.fcmp" role="manual">Financial Company</GUIRef>.</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4571m000#tfgld471.prio" role="manual">Priority</GUIRef> is filled with value of field <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.prio" role="manual">Priority</GUIRef>. There is one exception: there is a
				restriction in Financials that a record with priority 1 should be present
				always for a combination of Mapping Scheme Code, Mapping Scheme Version,
				Element Group and Dimension Type. So the record in table Dimension Mapping to
				be migrated (bcttf010) with the highest priority (even if it is unequal to 1)
				will get priority 1 in table Dimension Mapping (tfgld471).</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4571m000#tfgld471.seqn" role="manual">Sequence</GUIRef> is filled with value of field <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.sern" role="manual">Sequence</GUIRef>. For the record with priority 1 there should
				always be a sequence 1 also. So in case this is not present in table Dimension
				Mapping to be migrated (bcttf010), the lowest value for field <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.sern" role="manual">Sequence</GUIRef> will be replaced by 1 in field <GUIRef href="/baanerp/tf/gld/tfgld4571m000#tfgld471.seqn" role="manual">Sequence</GUIRef>.</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4571m000#tfgld471.dimx" role="manual">Dimension</GUIRef> is filled with value of field <GUIRef href="/baanerp/bc/ttf/bcttf0110m000#bcttf010.dimx" role="manual">Dimension</GUIRef>.</ListItem>
            </List>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>h. If a record is created in table Dimension Mapping
			 (tfgld471), the elements by dimension mapping must also be inserted in table
			 Elements by Dimension Mapping (tfgld472). This is done for the same records of
			 table Dimension Mapping to be migrated (bcttf010) as are used for filling table
			 Dimension Mapping (tfgld471) and is done in the following way:</Paragraph>
            <List>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.mscd" role="manual">Mapping Scheme</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.msvs" role="manual">Mapping Scheme Version</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.egcd" role="manual">Element Group</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.dtyp" role="manual">Dimension Type</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.tcmp" role="manual">Target Logistic Company</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.fcmp" role="manual">Financial Company</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.prio" role="manual">Priority</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.seqn" role="manual">Sequence Number</GUIRef> are filled like the same fields in
				table Dimension Mapping (tfgld471).</ListItem>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.elsn" role="manual">Element Sequence Number</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.elcd" role="manual">Element</GUIRef> are filled with the same values as <GUIRef href="/baanerp/tf/gld/tfgld4568m000#tfgld468.seqn" role="manual">Sequence Number</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4568m000#tfgld468.elcd" role="manual">Element Code</GUIRef>.</ListItem>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.evfr" role="manual">Element Value From</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4572m000#tfgld472.evto" role="manual">Element Value To</GUIRef> are filled with the element value
				from and the element value to of table Dimension Mapping to be migrated
				(bcttf010). The same comments as given for fields <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.evfr" role="manual">Element Value From</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4570m000#tfgld470.evto" role="manual">Element Value To</GUIRef> are applicable here.</ListItem>
            </List>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>i. In case a default ledger account is defined on the form
			 for the Reconciliation Group, table Default Accounts (tfgld478) is filled in
			 the following way:</Paragraph>
            <List>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.mscd" role="manual">Mapping Scheme</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.msvs" role="manual">Mapping Scheme Version</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.idtc" role="manual">Integration Document Type</GUIRef> are filled like the same
				fields in table Document Numbering / Compression (tfgld477).</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.dbcr" role="manual">Debit/ Credit</GUIRef> is filled with the value Debit is this
				is the Reconciliation Group (Debit) and with Credit otherwise</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.tcmp" role="manual">Business Object Company</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.fcmp" role="manual">Financial Company</GUIRef> are filled with 0, which means that
				the default accounts are used in every company. So they should be shared or
				defined in every company.</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.leac" role="manual">Ledger Account</GUIRef> is filled with the Ledger Account
				(debit or credit) defined on the form.</ListItem>
            </List>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>j. If at least one element group (for ledger mapping or
			 dimension mapping) is inserted for the reconciliation group, a record must be
			 inserted in table Mapping Schema Details (tfgld474). This is done in the
			 following way:</Paragraph>
            <List>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.mscd" role="manual">Mapping Scheme Code</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.msvs" role="manual">Mapping Scheme Version</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.idtc" role="manual">Integration Document Type</GUIRef> are filled like the same
				fields in table Document Numbering / Compression (tfgld477)</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.dbcr" role="manual">Debit/ Credit</GUIRef> is filled with the value Debit, this is
				the Reconciliation Group (Debit) and with Credit otherwise</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.legc" role="manual">Ledger Element Group Code</GUIRef> is filled with the element group
				for ledger mapping (from step 2a) if this one is created. Otherwise it remains
				empty.</ListItem>
               <ListItem>Fields <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.deg1" role="manual">Dimension 1 Element Group Code</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.deg2" role="manual">Dimension 2 Element Group Code</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.deg3" role="manual">Dimension 3 Element Group Code</GUIRef>, <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.deg4" role="manual">Dimension 4 Element Group Code</GUIRef> and <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.deg5" role="manual">Dimension 5 Element Group Code</GUIRef> are filled with the element
				groups for ledger mapping (from step 2e), if they are created. Otherwise they
				remain empty.</ListItem>
               <ListItem>Field <GUIRef href="/baanerp/tf/gld/tfgld4557m000#tfgld474.lael" role="groupbox">Log All Elements</GUIRef> will get the value Yes.</ListItem>
            </List>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>k. For some reconciliation groups, currency differences are
			 automatically logged in the system. This can be seen in session <GUIRef href="/baanerp/tc/fin/tcfin0120m000" role="session">Reconciliation Groups (tcfin0120m000)</GUIRef>. If this is the case, the mapping for the
			 integration document type for this currency difference (which also can be seen
			 in session <GUIRef href="/baanerp/tc/fin/tcfin0120m000" role="session">Reconciliation Groups (tcfin0120m000)</GUIRef>) must also be
			 inserted. This is done in the following way:</Paragraph>
            <List>
               <ListItem>If the default transaction type is filled on the session,
				a record is inserted in table Document Numbering / Compression (tfgld477) (like
				in step 1). Field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.idtc" role="manual">Integration Document Type</GUIRef> is filled with the
				integration document type for currency differences (from session <GUIRef href="/baanerp/tc/fin/tcfin0120m000" role="session">Reconciliation Groups (tcfin0120m000)</GUIRef>), field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.ttyp" role="manual">Transaction Type</GUIRef> is filled with the default
				transaction type defined on the session and field <GUIRef href="/baanerp/tf/gld/tfgld4577m000#tfgld477.seri" role="manual">Series</GUIRef> is filled with the default series defined on
				the session. Other fields are the same as in step 1. If the default transaction
				type is not filled on the session, no record is inserted in table Document
				Numbering / Compression (tfgld477).</ListItem>
               <ListItem>For the debit side of the currency difference, a record is
				created in table Default Accounts (tfgld478). Field <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.idtc" role="manual">Integration Document Type</GUIRef> is filled with the
				integration document type for currency differences, field <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.dbcr" role="manual">Debit/ Credit</GUIRef> is filled with the value Debit and field <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.leac" role="manual">Ledger Account</GUIRef> is filled with the same ledger account
				of step 2i. All other fields are also field like in step 2i. Furthermore a
				record is inserted in table Mapping Schema Details (tfgld474). Field <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.idtc" role="manual">Integration Document Type</GUIRef> is filled with the
				integration document type for currency differences and field <GUIRef href="/baanerp/tf/gld/tfgld4574m000#tfgld474.dbcr" role="manual">Debit/ Credit</GUIRef> is filled with the value Debit. All
				other fields are filled like in step 2j.</ListItem>
               <ListItem>For the credit side of the currency difference, also a
				record is created in table Default Accounts (tfgld478). Field <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.idtc" role="manual">Integration Document Type</GUIRef> is filed with the
				integration document type for currency differences, field <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.dbcr" role="manual">Debit/ Credit</GUIRef> is filled with the value Credit and
				field <GUIRef href="/baanerp/tf/gld/tfgld4578m000#tfgld478.leac" role="manual">Ledger Account</GUIRef> is filled with the default ledger
				account for currency differences as defined on the session. The other fields
				are like in step 2i. There is no record created in table Mapping Schema Details
				(tfgld474) for the credit side of the currency difference, as in Baan IVc it was not possible to set up a mapping for currency differences.</ListItem>
            </List>
         </GeneralSection>
         <GeneralSection>
            <Paragraph>Note: the committing of a transaction is done by Transaction
			 Origin/Financial Transaction combination, if everything goes fine for that
			 combination. If something is going wrong, an error message is printed on the
			 report and the combination is skipped, so it will not be part of the Financial
			 Mapping Scheme.</Paragraph>
         </GeneralSection>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Duration</SectionTitle>
         <Paragraph>Warning: Execution of this session can take a long time. If
		  the session is started for the first time and session <GUIRef href="/baanerp/bc/ttf/bcttf0105m000" role="session">Ledger Mapping (bcttf0105m000)</GUIRef> and/or <GUIRef href="/baanerp/bc/ttf/bcttf0110m000" role="session">Dimension Mapping (bcttf0110m000)</GUIRef> are not started before, this will also take some time.
		  The next time it will be faster.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Restart</SectionTitle>
         <Paragraph>When you will restart the session, the process runs again. If
		  something is inserted that is already present, it will be skipped in the next
		  run. If something new is found that was not inserted yet, it will be inserted.
		  Note: in session <GUIRef href="/baanerp/tf/gld/tfgld4573m000" role="session">Mapping Scheme (tfgld4573m000)</GUIRef> it is possible to delete
		  the Mapping Scheme. If this is done, it is also possible to run the session
		  multiple times, until the generated mapping scheme is fine.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>General Migration Topics: <Link href="/baanerp/baaniv/tech/general/GTtfacr0003" role="manual">Fill Charge Interest (tfacr0003)</Link>
         </RelTopic>
         <RelTopic>General Migration Topics: <Link href="/baanerp/baaniv/tech/general/GTtfacr0004" role="manual">Fill Identification for Manual Sales and Interest Invoices (tfacr0004)</Link>
         </RelTopic>
         <RelTopic>General Migration Topics: <Link href="/baanerp/baaniv/tech/general/GTtfacr0005" role="manual">BUA Migration (tfacr0005)</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldGroup>
         <Title>General</Title>
         <FieldHelp>
            <Header>
               <Title>Mapping Scheme Code</Title>
            </Header>
            <FuncDesc>The code of the Mapping Scheme for which data will be
			 generated. It is possible to zoom to session <GUIRef href="/baanerp/tf/gld/tfgld4573m000" role="session">Mapping Scheme (tfgld4573m000)</GUIRef> to pick up the correct mapping scheme code.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Mapping Scheme Version</Title>
            </Header>
            <FuncDesc>The version of the Mapping Scheme for which data will be
			 generated. It is possible to zoom to session <GUIRef href="/baanerp/tf/gld/tfgld4573m000" role="session">Mapping Scheme (tfgld4573m000)</GUIRef> to pick up the correct mapping scheme
			 version.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Simulate</Title>
            </Header>
            <FuncDesc>Checkbox indicating if session runs in simulate mode (yes) or
			 update mode (no). It is advised to first run the session in simulate mode. When
			 this is done, an error report is given for things that are not going correct.
			 They can be solved in this case before running the session in update
			 mode.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Checkboxes for Transaction Origins to migrate</Title>
            </Header>
            <FuncDesc>These checkboxes indicate if the mapping must be generated
			 for a certain transaction origin. If the related package or module is not
			 implemented, the value is No and it cannot be changed. In other cases the
			 default value is Yes but it can be changed to No if it is not
			 required.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Default Transaction Type</Title>
            </Header>
            <FuncDesc>The transaction type that will be used for the mapping scheme
			 in the following cases- No transaction type is defined for the specific
			 transaction origin/financial transaction combination on one of the following
			 tabs. In this case this is the fallback transaction type- Mapping of currency
			 differences that are automatically logged in the system (as indicated on
			 session <GUIRef href="/baanerp/tc/fin/tcfin0120m000" role="session">Reconciliation Groups (tcfin0120m000)</GUIRef>).</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Default Series</Title>
            </Header>
            <FuncDesc>The series that will be used for the mapping scheme in the
			 following cases- No transaction type is defined for the specific transaction
			 origin/financial transaction combination on one of the following tabs. In this
			 case the default transaction type and also the default series are used.-
			 Mapping of currency differences that are automatically logged in the system (as
			 indicated on session <GUIRef href="/baanerp/tc/fin/tcfin0120m000" role="session">Reconciliation Groups (tcfin0120m000)</GUIRef>).</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Default Ledger Account for Currency Difference</Title>
            </Header>
            <FuncDesc>The default ledger account that will be used for the credit
			 side of currency difference posting that are automatically logged in the
			 system, as indicated in session <GUIRef href="/baanerp/tc/fin/tcfin0120m000" role="session">Reconciliation Groups (tcfin0120m000)</GUIRef>.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Compression of transactions</Title>
            </Header>
            <FuncDesc>Indicating if compression is allowed for transactions or not.
			 This value will be used for every integration document type, if the user wants
			 to have different values for different integration document types, this should
			 be changed afterwards manually in the Financial Mapping Scheme.</FuncDesc>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title>Other Tabs</Title>
         <FieldHelp>
            <Header>
               <Title>Transaction Origin</Title>
            </Header>
            <FuncDesc>The transaction origin for the transactions. Transaction
			 origins can be found in session <GUIRef href="/baanerp/tc/fin/tcfin0110m000" role="session">Integration Document Type by Transaction Origin/Financial Transaction (tcfin0110m000)</GUIRef>.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Financial Transaction</Title>
            </Header>
            <FuncDesc>The financial transaction for the transactions. Financial
			 transaction can be found in session <GUIRef href="/baanerp/tc/fin/tcfin0110m000" role="session">Integration Document Type by Transaction Origin/Financial Transaction (tcfin0110m000)</GUIRef>. Note: not all existing Transaction Origin/Financial
			 Transaction combinations that exist in ERP LN 6.1 are available on the
			 session, only the ones for which something exists that is equal to or looks
			 like a transaction in MANMAN/HP. Other transaction origins/financial transactions
			 must be set up in the financial mapping scheme manually, as they have to do
			 with functionality that does not exist in MANMAN/HP.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Transaction Type</Title>
            </Header>
            <FuncDesc>The transaction type that will be used for the integration
			 document type related to the combination of Transaction Origin and Financial
			 Transaction (see session <GUIRef href="/baanerp/tc/fin/tcfin0110m000" role="session">Integration Document Type by Transaction Origin/Financial Transaction (tcfin0110m000)</GUIRef>). If this one is not filled, the default transaction
			 type of the General Tab will be used.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Series</Title>
            </Header>
            <FuncDesc>The series that will be used for the integration document
			 type related to the combination of Transaction Origin and Financial Transaction
			 (see session <GUIRef href="/baanerp/tc/fin/tcfin0110m000" role="session">Integration Document Type by Transaction Origin/Financial Transaction (tcfin0110m000)</GUIRef>). If the Transaction Type is not filled,
			 the default transaction type and the default series of the General Tab will be
			 used.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Default Account (Debit)</Title>
            </Header>
            <FuncDesc>This is the default account that will be used for the debit
			 side of the transaction. If no ledger account can be found via the mapping,
			 this ledger account is used. So it is a “last-option” account only.</FuncDesc>
         </FieldHelp>
         <FieldHelp>
            <Header>
               <Title>Default Account (Credit)</Title>
            </Header>
            <FuncDesc>Like Default Account (Debit) but for the credit side of the
			 transaction</FuncDesc>
         </FieldHelp>
      </FieldGroup>
   </Fields>
</Session>