Stage 5: Assisting Migration of Blank- Bank Sub Codes, Asset Diary Codes and Transaction Analysis Codes.
1. Create a record in the PARAM-ZZZ.DAT file, to indicate the default bank sub-code in SunSystems 5 that replaces the default i.e. blank bank sub-code in SunSystems 4.2.
2. Characters 1-4 must be ‘BANK’.
3. Characters 5-9 must indicate the default sub-code for SunSystems 5, that replace the default (blank) Blank sub-code that existed in SunSystems 4.2. All alpha characters must be in upper case.
4. Create a record in the PARAM-ZZZ.DAT file to indicate the default Asset Diary Note Code in SunSystems 5, that replaces the default (blank) Asset Diary Note Code that existed in SunSystems 4.2.
5. Characters 1-5 must be ‘ASSET’.
6. Characters 6-10 must indicate the default Asset Diary Note Code for SunSystems 5. This replaces the default (blank) Asset Diary Code that existed in SunSystems 4.2. Any alpha characters must be in upper case, you need only supply a default Asset Diary Note Code if you are serialised for Asset Register in SunSystems 5.
7. To cater for the very occasional instances of corrupt data, i.e. where a ledger transaction has been found with no account code it is necessary for the user to supply the error suspense account so that Data Migration can substitute this for any corrupt account codes it finds during migration. All transactions changed in this way are reported to the LDGREP_ZZZ.log.
8. Create a record in the PARAM-ZZZ.DAT file to indicate the error suspense account code in SunSystems 5.
9. Characters 1-6 must be LEDGER.
10. Characters 7-16 must indicate the error suspense account for SunSystems 5. Data Migration checks that this is a valid account code in the version 5 Chart of Accounts table. This implies that you must run Static data migration before running the ledger transaction migration or set the account up manually in SunSystems 5.

Discuss in forum