|
Sun4 To Sun5 Data Migration |
|
|
|
|
Sun Documentation -
System Implementation
|
|
Page 3 of 9 Stage 4: Assisting Migration of Analysis Categories and Codes
1. Log out of SunSystems and log in again using the Operator Id you created at Stage 3.
Note: Before undertaking the following you need to have decided and planned how you want to analyze the data in SunSystems 5.
2. Use Navigation Manager to access Analysis Dimensions Setup (ND).
3. Create as many Analysis Dimensions for your new business unit as you need to transfer your 4.2 Analysis Categories. For each Analysis Dimension that you create, make a note of the Analysis Dimension Id that the system automatically allocates.
4. Use Navigation Manager to access Analysis Structure Setup (NS) and then define how you want to analyze your data.
5. You have a choice of Analyzable Entities to which you can attach the Analysis Dimensions that were created earlier:
Analyzable Entity Table Description
Table 1 Item
Table 122 Warehouse
Table 132 Employee
Table 138 Address
Table 142 Sales Invoice Line
Table 148 Supplier
Table 150 Customer
Table 152 Account
Table 177 Purchase Invoice Line
Table 191 Sales Order Line
Table 192 Quotation Line
Table 204 Asset
Table 214 Purchase Order Line
Table 233 Movement Order Line
Table 901 Ledger Transaction Line
6. Create a flat text file for each of your Database Codes called PARAM-ZZZ.DAT, where ZZZ is your SunSystems 4.2 Database Code and each record has a maximum of 19 characters. For each record:
- The first two characters must indicate the 4.2 Analysis Category that you want to migrate, for example A0, A1 etc.
- The next two characters must indicate the Analysis Dimension Id that the 4.2 Analysis Category is to become in SunSystems 5.
- The next 15 characters must indicate the default Analysis Code for SunSystems 5, which replaces the default (blank) Analysis code that existed in previous versions of SunSystems. This code must be in uppercase.
|
Note: You must ensure that you only have default entries for analysis categories that have a ‘spaces‘ analysis code in your v4.2 backup. Setting defaults for codes that do not exist in your 4.2 ssrf backup will cause errors to be reported in the error log produced during Data Check within Stage 6 and, if left uncorrected, will cause the migration to fail. There is no comma delimitation in this file. Do not leave any extra spaces or lines at the end of the file.
7. You must create a record for each 4.2 Analysis Category you want to migrate to SunSystems 5 - Account Analysis Category A0 to A9
- Analysis Category Asset F0 to F9
- Transaction Analysis Category T0 to T9
- Movement Analysis Category M0 to M9
- Item Analysis Category I0 to I9
- Address Analysis Category C0 to C9
|
8. Once the file PARAM-ZZZ.DAT file is created, copy it into your SunSystems 5 backup folder. The backup folder can be the default folder (_back), or the folder you specified in Operator Setup (OS). |
Sun Documentation 
