This page (revision-8) was last changed on 26-Nov-2021 10:22 by JEscott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
8 26-Nov-2021 10:22 4 KB JEscott to previous
7 26-Nov-2021 10:22 3 KB JEscott to previous | to last
6 26-Nov-2021 10:22 3 KB JEscott to previous | to last
5 26-Nov-2021 10:22 2 KB JEscott to previous | to last
4 26-Nov-2021 10:22 1 KB JEscott to previous | to last
3 26-Nov-2021 10:22 1 KB JEscott to previous | to last
2 26-Nov-2021 10:22 1 KB JEscott to previous | to last
1 26-Nov-2021 10:22 1 KB JEscott to last

Page References

Incoming links Outgoing links
ORDER OF CONVERSION
ORDER OF CONVERSION

Version management

Difference between version and

At line 3 changed one line
Since the data that is being loaded into the environment builds on each other, the tables need to be loaded in a specific order so that the data validation that occurs during the conversion process will find the needed records. The order that the records need to be loaded in are basically the same that the records need to be keyed in, if they were being entered by hand through the application screens.
Since the data that is being loaded into the [{$applicationname}] environment builds on each other, the tables need to be loaded in a specific order so that the data validation that occurs during the conversion process will find the needed records. The order that the records need to be loaded in are basically the same that the records need to be keyed in, if they were being entered by hand through the application screens.
At line 5 changed 70 lines
The chart, shown below, can be used as a guideline for converting records into the application. The first column shows the order number that the table will need to be loaded in. If the number does not contain a whole number (IE 0.1 for USERS), then the table does not have a conversion process associated to it. These records will have to be keyed into the application using the appropriate screen. The entries in this table with whole numbers (IE 1 for LOCATIONS, or 2 for ENTITIES), can be loaded in. However, if the table only contains a small quantity of data and the data does not need to be reloaded after being refreshed from PILOT, this data can be keyed into the appropriate screen. If this data is keyed into the PILOT database, this data will be taken to the CONV/PROD database during the EXPORT/IMPORT process.
||Sequence|| Conversion Area||Table
|0.1| USERS |
|0.2| WORK_STATUS |
|0.3| CHANGE_REASONS |
|0.4| TERMINATION_REASONS |
|0.5| GEO |
|0.6| LEXICONS |
|1| LOCATIONS |[INF_CV_LOCATIONS]
|1.1| CALENDARS |
|1.2| GLCOMPANIES |
|2| ENTITIES |[INF_CV_ENTITIES]
|3| BANKS |[INF_CV_BANKS]
|3.1| PAYROLLS |
|3.2| HOLIDAYS |
|4| AUTHORIZATIONS |[INF_CV_AUTHORIZATIONS]
|5| DEPARTMENTS |[INF_CV_DEPARTMENTS]
|5.1| ORG_LEVEL_TYPES |
|6| ORGLEVELS |[INF_CV_ORGLEVELS]
|7| WORKRULES |[INF_CV_WORKRULES]
|8| SCALES |[INF_CV_SCALES]
|9| RANGES |[INF_CV_RANGES]
|10| GLSEGMENTVALUES |[INF_CV_GLSEGMENTVALUES]
|11| UNITS |[INF_CV_UNITS]
|12| GROUPS |[INF_CV_GROUPS]
|12.1| PREMIUM_TYPES |
|13| PREMIUMS | [INF_CV_PREMIUMS]
|14| JOBS |[INF_CV_JOBS]
|15| POSITIONS |[INF_CV_POSITIONS]
|16| PERSONALS |[INF_CV_PERSONALS]
|17| EMPLOYMENTS |[INF_CV_EMPLOYMENTS]
|18| ASSIGNMENTS |[INF_CV_ASSIGNMENTS]
|19| PROPERTIES |[INF_CV_PROPERTIES]
|20| CDNPAYRULES | [INF_CV_CDNPAYRULES]
|21| USPAYRULES |[INF_CV_USPAYRULES]
|22| MILITARIES |[INF_CV_MILITARIES]
|23| CONTACTS |[INF_CV_CONTACTS]
|24| PAYMENTRULES |[INF_CV_PAYMENTRULES]
|25| DISTRIBUTIONS |
|25.1| REVIEW_CATEGORY |
|26| REVIEWS |[INF_CV_REVIEWS]
|26.1| PAYPOINTS |
|26.2| GLACCOUNTS |
|26.3| USERVARS |
|26.4| USPAYCATEGORIES |
|26.5| PAYCOMPONENTS |
|26.6| STATCOMP |
|26.7| FREQUENCIES |
|26.8| PAYCALENDARS |
|27| STATISTICS |[INF_CV_STATISTICS]
|28| SUNDRYLINES |[INF_CV_SUNDRYLINES]
|29| TODATES |[INF_CV_TODATES]
|30| EXPERIENCES |[INF_CV_EXPERIENCES]
|31| MATRICES |[INF_CV_MATRICES]
|31.1| LEAVE_TYPES |
|32| ACCRUALS |[INF_CV_ACCRUALS]
|33| LEAVELINES |[INF_CV_LEAVELINES]
|34| ENROLLMENTS |[INF_CV_ENROLLMENTS]
|35| RECIPIENTS |[INF_CV_RECIPIENTS]
|36| PAYRUNS |[INF_CV_PAYRUNS]
|37| PAYHEADERS |[INF_CV_PAYHEADERS]
|38| PAYLINES |[INF_CV_PAYLINES]
|39| PAYPCAMOUNTS |[INF_CV_PAYPCAMOUNTS]
|40| DISBURSEMENTS |[INF_CV_DISBURSEMENTS]
----
![Notes|Edit:Internal.ORDER+OF+CONVERSION]
[{InsertPage page='Internal.ORDER+OF+CONVERSION' default='Click to create a new notes page'}]
The chart, shown below, can be used as a guideline for converting records into the application. The first column shows the order number that the table will need to be loaded in. If the number does not contain a whole number (IE 0.1 for USERS), then the table does not have a conversion process associated to it. These records will have to be keyed into the application using the appropriate screen within [{$applicationname}]. The entries in this table with whole numbers (IE 1 for LOCATIONS, or 2 for ENTITIES), can be loaded in. However, if the table only contains a small quantity of data and the data does not need to be reloaded after being refreshed from PILOT, this data can be keyed into the [{$applicationname}] screen. If this data is keyed into the PILOT database, this data will be taken to the CONV/PROD database during the EXPORT/IMPORT outlined in another section of this manual.
This page (revision-8) was last changed on 26-Nov-2021 10:22 by JEscottTop