|
Sun4 To Sun5 Data Migration |
|
|
|
|
Sun Documentation -
System Implementation
|
|
Page 5 of 9
Stage 6: Data Migration
1. Log in to SunSystems 5 as the SuperUser and use Navigation Manager to access Data Migration (DM).
Click here to see the screenshot
The following fields are displayed on the Data Migration form:
Business Unit Code 4.2
Leave blank when migrating system data, otherwise enter the business unit code for SunSystems 4.2.
Note: The databases created in 4.2 versions, using the function DB=Database Definition, are now referred to as business units in SunSystems 5.
Business Unit Code 5.1
Leave blank when migrating system data, otherwise enter the business unit code for SunSystems 5.1.
System
Indicates the number of table rows migrated and not migrated after the System data migration
button has been clicked.
Static/Payment Terms
Indicates the number of table rows migrated and not migrated after the Static data migration button has been clicked. The number of Payment Terms table rows is also displayed.
Transaction
Indicates the number of table rows that were successfully migrated after the Trans data migration button has been clicked.
Archive
Allows you to enter specific, or a range of, years before clicking the Archive data migration button.
Data Check button
Checks for invalid dates in the Ledger backups and for lower/mixed case codes in the Static and Ledger backups and validates bank and asset entries, and analysis code lengths to ensure they are not longer than the SunSystems 5 analysis dimension they are migrated to and address/account relationships.
Apply RI button
This enables referential integrity to be applied to the specified business unit tables and system tables.
Note: After you have migrated the data, you must run the Payment Terms Update (PTU) utility. This ensures that all the due dates in the ledger file are updated.
|
Sun Documentation 
