| Migrate Mapping Scheme (bcttf0201m000) |  |
| 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: Ledger Mapping to be migrated (bcttf005) Dimension Mapping to be migrated (bcttf010) Transaction Types (bcttf011) Data will be created in ERP LN tables: Element Groups (tfgld467) Elements by Element Group (tfgld468) Ledger Mapping (tfgld469) Elements by Ledger Mapping (tfgld470) Dimension Mapping (tfgld471) Elements by Dimension Mapping (tfgld472) Mapping Schema Details (tfgld474) Document Numbering / Compression (tfgld477) Default Accounts (tfgld478) Preparation Before you can use this session: 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. The migration of table Mapping Schemas (tfgld473) must be done, or a record must be added manually in this table with session Mapping Scheme (tfgld4573m000). The migration of master data must be finished. The session Initialize Mapping Scheme Data (tcfin0210m000) must be run. It is recommended to start the sessions Ledger Mapping (bcttf0105m000) and Dimension Mapping (bcttf0110m000) to check (and maybe change) the mapping that will be generated. Execution This session must be executed to migrate mapping scheme data. User Interface logic Tab General 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 Implemented Software Components (tccom0500m000). The check box People is disabled with value No if the package People is not implemented. The check boxes Sales Order, Purchase Order and Purchase Contract are disabled with value No if the package Order Management is not implemented. The check box Production Order is disabled with value No if the package Manufacturing is not implemented. The check box Project (PCS) is disabled with value No if the module Project Control is not implemented. The check boxes Project Costs & Commitments and Project Revenues are disabled with value No if the package Project is not implemented. The check boxes Service Order and Service Contract are disabled with value No if the package Service is not implemented The check boxes Freight Order, Freight Shipment and Freight Order Cluster are disabled with value No if the package Freight Management is not implemented. If a check box is disabled with value No, the related Tab is not visible either. Other Tabs 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. 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 Integration Document Types by Reconciliation Group (tcfin0115m000). Process logic Starting the session If session Ledger Mapping (bcttf0105m000) 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). If session Dimension Mapping (bcttf0110m000) is not started before this session is started, table Dimension Mapping to be migrated (bcttf010) is filled based on Dimension Mapping Base (bcttf006). When the session is started, the following defaults are retrieved: The check box Simulate gets the value Yes The check boxes for the Transaction Origin gets the default value Yes if the related package or module is implemented. The default Transaction Type and the default Series on tab General are defaulted from table Integration Parameters (tfgld450). The ledger account for currency differences is not defaulted. The check box compression is defaulted by selecting just one record of table Transaction Types (bcttf011). 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. 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. Press the Continue button The process is doing the following steps for every Transaction Origin/Financial Transaction combination: Step 1 In Financials, table Document Numbering / Compression (tfgld477) is filled in the following way in case a transaction type can be found. Field Mapping Scheme Code is filled with the mapping scheme code defined on the form. Field Mapping Scheme Version is filled with the mapping scheme version on the form. Field Integration Document Type 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. Field Business Object Company and field Financial Company 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. tfgld477.sdla and tfgld477.scla remain empty. Field Transaction Type 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). Field Series 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). Field Debit and Credit are filled with the value of the check box Compression of transactions on the form. Step 2 Every transaction origin/financial transaction combination has a reconciliation group (debit) and a reconciliation group (credit). See also session Integration Document Types by Reconciliation Group (tcfin0115m000). The following steps are done for both the reconciliation groups. So they are done twice for every transaction origin/financial transaction combination: 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.
Warehouse | Project | Country
--- | --- | ---
V |  | ZZZZZZ | V | PRJ1 | PRJ! |  | NL | USA
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: Fields Mapping Scheme Code and Mapping Scheme Version are filled like the same fields in table Document Numbering / Compression (tfgld477). Field Element Group Code 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) Field Element Group 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. 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: Fields Mapping Scheme Code, Mapping Scheme Version and Element Group Code are filled like the same fields in table Element Groups (tfgld467). Field Sequence Number 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. Field Element Code is the element code that can be seen in session Elements by Integration Document Type (tfgld4558m000) for the integration document type. Example: for Purchase Order/Receipt, the element code for Project is 211200000000. 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: Field Mapping Scheme Code, Mapping Scheme Version and Element Group Code are filled like the same fields in table Element Groups (tfgld467). Field Logistic Company is filled with field Logistic Company. Field Financial Company is filled with value of field Financial Company. Field Priority is filled with value of field Priority. 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). Field Sequence Number is filled with value of field Sequence. 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 Sequence will be replaced by 1 in field Sequence Number. Field Ledger Account is filled with value of field Ledger Account. 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: Fields Mapping Scheme Code, Mapping Scheme Version, Element Group Code, Logistic Company, Financial Company, Priority and Sequence Number are filled like the same fields in table Ledger Mapping (tfgld469). Fields Element Sequence Number and Element Code are filled with the same values as fields Sequence Number and Element Code. Fields Element Value From and Element Value To 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 Element Value From and Element Value To 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. 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. 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). 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: Fields Mapping Scheme Code, Mapping Scheme Version and Element Group Code are filled like the same fields in table Element Groups (tfgld467). Field Dimension Type is filled with value of field Dimension Type. Field Logistic Company is filled with value of field Logistic Company. Field Financial Company is filled with value of field Financial Company. Field Priority is filled with value of field Priority. 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). Field Sequence Number is filled with value of field Sequence. 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 Sequence will be replaced by 1 in field Sequence Number. Field Dimension is filled with value of field Dimension. 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: Fields Mapping Scheme Code, Mapping Scheme Version, Element Group Code, Dimension Type, Logistic Company, Financial Company, Priority and Sequence Number are filled like the same fields in table Dimension Mapping (tfgld471). Fields Element Sequence Number and Element Code are filled with the same values as Sequence Number and Element Code. Fields Element Value From and Element Value To 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 Element Value From and Element Value To are applicable here. 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: Fields Mapping Scheme, Mapping Scheme Version and Integration Document Type are filled like the same fields in table Document Numbering / Compression (tfgld477). Field Debit/Credit Indicator is filled with the value Debit is this is the Reconciliation Group (Debit) and with Credit otherwise Field Logistic Company and Financial Company 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. Field Ledger Account is filled with the Ledger Account (debit or credit) defined on the form. 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: Fields Mapping Scheme Code, Mapping Scheme Version and Integration Document Type are filled like the same fields in table Document Numbering / Compression (tfgld477) Field Debit/ Credit is filled with the value Debit, this is the Reconciliation Group (Debit) and with Credit otherwise Field Ledger Element Group Code is filled with the element group for ledger mapping (from step 2a) if this one is created. Otherwise it remains empty. Fields Dimension 1 Element Group Code, Dimension 2 Element Group Code, Dimension 3 Element Group Code, Dimension 4 Element Group Code and Dimension 5 Element Group Code are filled with the element groups for ledger mapping (from step 2e), if they are created. Otherwise they remain empty. Field Log All Elements will get the value Yes. k. For some reconciliation groups, currency differences are automatically logged in the system. This can be seen in session Reconciliation Groups (tcfin0120m000). If this is the case, the mapping for the integration document type for this currency difference (which also can be seen in session Reconciliation Groups (tcfin0120m000) ) must also be inserted. This is done in the following way: 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 Integration Document Type is filled with the integration document type for currency differences (from session Reconciliation Groups (tcfin0120m000) ), field Transaction Type is filled with the default transaction type defined on the session and field Series 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). For the debit side of the currency difference, a record is created in table Default Accounts (tfgld478). Field Integration Document Type is filled with the integration document type for currency differences, field Debit/Credit Indicator is filled with the value Debit and field Ledger Account 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 Integration Document Type is filled with the integration document type for currency differences and field Debit/ Credit is filled with the value Debit. All other fields are filled like in step 2j. For the credit side of the currency difference, also a record is created in table Default Accounts (tfgld478). Field Integration Document Type is filed with the integration document type for currency differences, field Debit/Credit Indicator is filled with the value Credit and field Ledger Account 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. 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. Duration Warning: Execution of this session can take a long time. If the session is started for the first time and session Ledger Mapping (bcttf0105m000) and/or Dimension Mapping (bcttf0110m000) are not started before, this will also take some time. The next time it will be faster. Restart 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 Mapping Scheme (tfgld4573m000) 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. Related topics General Migration Topics: Fill Charge Interest (tfacr0003) General Migration Topics: Fill Identification for Manual Sales and Interest Invoices (tfacr0004) General Migration Topics: BUA Migration (tfacr0005)
Fields | Description
General
Mapping Scheme Code | The code of the Mapping Scheme for which data will be generated. It is possible to zoom to session Mapping Scheme (tfgld4573m000) to pick up the correct mapping scheme code.
Mapping Scheme Version | The version of the Mapping Scheme for which data will be generated. It is possible to zoom to session Mapping Scheme (tfgld4573m000) to pick up the correct mapping scheme version.
Simulate | 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.
Checkboxes for Transaction Origins to migrate | 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.
Default Transaction Type | 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 Reconciliation Groups (tcfin0120m000) ).
Default Series | 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 Reconciliation Groups (tcfin0120m000) ).
Default Ledger Account for Currency Difference | 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 Reconciliation Groups (tcfin0120m000).
Compression of transactions | 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.
Other Tabs
Transaction Origin | The transaction origin for the transactions. Transaction origins can be found in session Integration Document Type by Transaction Origin/Financial Transaction (tcfin0110m000).
Financial Transaction | The financial transaction for the transactions. Financial transaction can be found in session Integration Document Type by Transaction Origin/Financial Transaction (tcfin0110m000). 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.
Transaction Type | The transaction type that will be used for the integration document type related to the combination of Transaction Origin and Financial Transaction (see session Integration Document Type by Transaction Origin/Financial Transaction (tcfin0110m000) ). If this one is not filled, the default transaction type of the General Tab will be used.
Series | The series that will be used for the integration document type related to the combination of Transaction Origin and Financial Transaction (see session Integration Document Type by Transaction Origin/Financial Transaction (tcfin0110m000) ). If the Transaction Type is not filled, the default transaction type and the default series of the General Tab will be used.
Default Account (Debit) | 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.
Default Account (Credit) | Like Default Account (Debit) but for the credit side of the transaction