| Ledger Mapping (bcttf0105m000) |  |
| Use this session to view the additional fields from Baan IVc (= elements in ERP LN 6.1 ) that are used to define the Ledger Account. This session can also be used to change the Ledger Account that will be used in the financial mapping scheme. The Ledger Account can be changed on each view. Through view “Reconciliation Group, Companies, Priority, Sequence, To be Used” it is possible to change the indicator To be Used. At the first form the data about the originating bcttf020.tror and Financial Transaction is visible. At the next forms the elements (i.e. Item and Warehouse) are visible that are used to determine the Ledger Account. This maintain session prepares the input for session Migrate Mapping Scheme (bcttf0201m000). Dependent on the filled additional fields of Baan IVc, the element groups and the elements by element groups of ledger account mapping are generated. Preparation Not applicable. Execution It is strongly advised to start this session to judge the ledger accounts and the indication ‘To be Used’ before running session Migrate Mapping Scheme (bcttf0201m000). Process logic If this session is started for the first time then the data from interim tables Ledger Mapping Base (bcttf001) and Ledger Mapping (Project and Service) (bcttf002) is copied to table Ledger Mapping (bcttf005). First data of table Ledger Mapping (Project and Service) (bcttf002) is copied to table Ledger Mapping Base (bcttf001). Based on the table Ledger Mapping Base (bcttf001) the fields Priority and Sequence are filled without gaps. Lines with the same Priority having other elements will get a new Sequence. This is done according to the similar functionality used in the integration mapping scheme. Per reconciliation group, companies, Priority and Sequence one line will be flagged with To be Used = Yes. The other lines (flagged with To be Used = No) of the same group have overlapping values in the elements. It is mandatory that only one line in the group be flagged with Yes. If the indicator To be Used of another line is manually changed into Yes, the old indicator ‘Yes’ is switched into ‘No’. Note Note that no overlapping values are allowed in the elements of one reconciliation group, companies, Priority and Sequence because the debit postings and credit postings must result in the same ledger account. For example purchase order / receipt books debit on ledger account ‘Interim Transit’ and warehouse receipt / receipt books credit on the same account. Only one ‘set of elements’ and one ledger account must be used to generate the mapping. Therefore (through To be Used ) a choice is made between the different financial transactions that are related to each other. Session Migrate Mapping Scheme (bcttf0201m000) generates the same elements for the reconciliation groups that must be ‘cleared’. The generated debit and credit mapping will contain the same elements (=elements of Baan IVc, for example “Item” and “Item Group”). Dependent on the reconciliation group the elements that can be used in ERP LN 6.1, are marked as ‘Yes’. Some elements can be filled with data from Baan IVc but can be marked with ‘No’ if this element is not longer available in ERP LN 6.1. In session Migrate Mapping Scheme (bcttf0201m000) the lines with indicator To be Used = ‘Yes’ are selected to fill the integration mapping scheme. The other lines with To be Used = ‘No’ are ignored. Duration Warning: Execution of this session takes some time if it is started for the first time. The next time it will be faster. Restart Not applicable. Related topics General Migration Topics: To migrate the Integration Mapping Scheme (Overview) (tfgld0004) General Migration Topics: To migrate ledger accounts to integration mapping scheme (tfgld0001)
Fields | Description
Ledger Mapping
Reconciliation Group | The reconciliation group is determined based on the Transaction Origin and Financial Transaction where the mapping data is defined. Related topics General Migration Topics: To migrate ledger accounts to integration mapping scheme (tfgld0001)
Logistic Company | 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.
Financial Company | 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.
Priority | The priority of the mapping. A low number is found first in the mapping process.
Sequence | The sequence of the mapping is used to define different mappings (not overlapping within one priority).
Transaction Origin | 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.
Financial Transaction | 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.
Additional Type | 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.
Debit/Credit | The indicator whether the mapping is used for the debit or for the credit side of the financial transaction.
To be used | This flag indicates whether the line originating from Baan IVc will be used during generation of the mapping scheme.
Ledger Account | This ledger account is used to map the financial transactions that originate from the several packages.
General
Financial B.P. Group (A/P) | This element is filled with the supplier group of Baan IVc. 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.
Financial B.P. Group (A/R) | The financial business partner group (accounts receivable) is show here.
Warehouse | The warehouse element is shown here.
Item | The item element is shown here.
Item Group | The Item Group element is shown here.
Project Package Linked | The Project Package Linked element is shown here.
Project | The Project element is shown here.
Main Project Package Linked | The Main Project Package Linked element is shown here. Note that this field indicates whether a mapping is applicable for PCS or for Project or for all types of projects.
Main Project | The Main Project element is shown here.
Item Cost Component | The Item Cost Component element is shown here.
Cost Component Type | The Cost Component Type element is shown here.
Country | The Country element is shown here.
Reason Code | The Reason Code element is shown here.
Transaction Type | The Transaction Type element is shown here.
TP Project
Cost Component (TP) | The cost component for Project element is shown here.
Cost Type (TP) | The cost type for Project element is shown here.
Task | The task for Project element is shown here.
Equipment | The equipment for Project element is shown here.
Subcontracting | The subcontracting for Project element is shown here.
Sundry Cost | The sundry cost for Project element is shown here.
Result Type | The result type for Project element is shown here.
Contract Execution | The contract execution for Project element is shown here.
Category | The category for Project element is shown here.
Agreement Type | The agreement type for Project element is shown here.
Service
Service Contract Type | The service contract type for Service element is shown here.
Cost Type (TS) | The cost type for Service element is shown here.
Cost Type Group | The cost type group for Service element is shown here.
Cost Analysis Type | The cost analysis type for Service element is shown here.
Commissions and Rebates
Customer | The cost analysis type for Commission and Rebated element is shown here.
Relation | The relation for Commission and Rebated element is shown here.
Relation Type | The relation type for Commission and Rebated element is shown here.
Agreement Group | The agreement group for Commission and Rebated element is shown here.
Commission/Rebate Group | The commission or rebate group for Commission and Rebated element is shown here.