|
Sun4 To Sun5 Data Migration |
|
|
|
|
Sun Documentation -
System Implementation
|
|
Page 9 of 9
Manual Corrections to be made to the SunSystems 5.1 Database after Migration
If, when migrating, the SunSystems 4.2 business unit name is different to the SunSystems 5.1 business unit name manual adjustments are required, as Data Migration cannot convert the Business Unit codes that are held on the following static data; Allocation Targets (ALT) and (FA) Consolidation. Users must amend the business unit codes held on these rows manually using the associated Static Data Maintenance function.
If you are going to be using memo accounts with journal types created in SunSystems 4.2, you must amend the journal type using Journal Types Setup (Posting Overrides) (JTX). On the Security tab the Memo Post Rule Override field is set to 0-Undefined, amend it to the required setting.
If you do not amend this field when using ledger import to import memo amounts the values are set to zero regardless of what you have changed the business unit to. Journal types set up in SunSystems 5 are created according to what is set on the business unit.
Payment Terms Update
It is also necessary to run Payment Terms Update (PTU) for all your account codes after migrating 4.2 data.
This enables the system to calculate and store the due dates of your migrated transactions.
Note: In the following circumstances, Due Dates are not migrated:
- If the Due Date is not present in the SALF-XXX.BAK.
- If the Account Code is of the following types: Memo, Balance Sheet or P&L.
- If the Allocation Marker is of the following types: Correction, Reconciled, Allocated or Paid.
|
Only registered users can write comments.
Please login or register.
|
Sun Documentation 
