...
Example migration using configuration packages:
Package Name | Rapid Package | Tables/Tables Included | Data entities | Note |
SIM_CONTACT
| 18 Customer 5050 Contact 5051 Contact Alt. Address 5054 Contact Business Relation | Customer Contact Contact Address Contact and Customer Relation | Contract Client Migration | |
SIM_0_DIM_VALUE | 349 Dimension Value | Contract Numbers to Table Dimension Values | Prerequisita before contract migration; Dimension No. 2 must be set before import Contract | |
SIM_1_CONTRACT | 4026397 API Financing Contract Header | Contract Headers | Both the order and the use of validations of individual fields are important here | |
SIM_2_OBJECT | 4026560 API Financed Object | Financed Objects for Contract Headers | Both the order and the use of validations of individual fields are important here | |
SIM_3_CALCINP | 4026450 API Contract Calculation Input | Calculation Inputs – Contract Value Data | Value data in calc. inputs must match the values from the header of the contract or other migrated data | |
SIM_4_GUARANTEE | 4026447 API Contract Guarantee | Contract Guarantee | Data is not mandatory | |
SIM_5_LICENSE_PLATE | 4026584 API License Plate History | License Plate History | Data is not mandatory | |
SIM_6_MIGR_POSTED_P | 4046950 API Migration - Posted Payment | Flags that contract payment calendar lines have already been posted | The data is not mandatory, it is an adjustment of the data generated by the system when activating contracts (payment calendars) based on the posting status of payments in the periods before the migration date |
...
File Type | Directory | Note | |||||
Exported Configuration PackageOneCore |
| Status as of 15.10.2022 | |||||
Exported Excel fileOneCore |
| Status as of 15.10.2022 |
Note 2: under certain circumstances (e.g. changes in the table), the order of columns in the field list of the migrated table may be changed – the changed request is renumbered according to the sequential field numbers; The order is is an integral part of the package definition and must be used exactly as defined in the package, or in the Excel spreadsheet that was created from the package, and not according to this default setting.
...
Note: Due to the fact that the recalculation will overwrite the fields on the contract header, which may have contained the original payment amounts from the migration, it is necessary to combine the original data (e.g. the migration input data to migration) and the resulting data after the recalculation when comparing the payment amount before and after the recalculation.
...