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

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
12 26-Nov-2021 10:22 7 KB jmyers to previous
11 26-Nov-2021 10:22 7 KB jmyers to previous | to last
10 26-Nov-2021 10:22 7 KB RForbes to previous | to last
9 26-Nov-2021 10:22 7 KB RForbes to previous | to last
8 26-Nov-2021 10:22 7 KB JEscott to previous | to last
7 26-Nov-2021 10:22 7 KB JEscott to previous | to last
6 26-Nov-2021 10:22 7 KB JAiken to previous | to last
5 26-Nov-2021 10:22 7 KB JEscott to previous | to last
4 26-Nov-2021 10:22 7 KB JEscott to previous | to last
3 26-Nov-2021 10:22 7 KB JEscott to previous | to last
2 26-Nov-2021 10:22 7 KB JEscott to previous | to last
1 26-Nov-2021 10:22 3 KB JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 59 changed one line
If needed a custom script can be used to populate some of the field in the INF_CV_SUNDRYLINES table based on the setup of the [PC Code|PC_CODE] and the employee’s primary assignment record. The FIX_SUNDRYLINES.SQL script will set the [UNIT_CODE], [GROUP_CODE], [JOB_CODE] and [POSITION_CODE] on the INF record if these fields are loaded with a NULL value. It will also look up the [PAY_POINT_TYPE] value from the Pay Rules section of the [IPPC] screen for the [PC Code|PC_CODE] in the [PC_CODE] Header column and set this in the record. This script can be downloaded from the support FTP server, or is included on the application installation CD.
If needed a custom script can be used to populate some of the field in the [INF_CV_SUNDRYLINES] table based on the setup of the [PC Code|PC_CODE] and the employee’s primary assignment record. The FIX_SUNDRYLINES.SQL script will set the [UNIT_CODE], [GROUP_CODE], [JOB_CODE] and [POSITION_CODE] on the INF record if these fields are loaded with a NULL value. It will also look up the [PAY_POINT_TYPE] value from the Pay Rules section of the [IPPC] screen for the [PC Code|PC_CODE] in the [PC_CODE] Header column and set this in the record. This script can be downloaded from the support FTP server, or is included on the application installation CD.
At line 61 changed one line
Simple records in the INF_CV_SUNDRYLINES table will only have one record. An example of this type of sundry line would be United Way deductions or uniform allowances. Since this type of record will cause the same value to be processed by payroll, there is no need for any other PC Codes to track information of the transaction. These single record sundry lines will have the same [PC Code|PC_CODE] in both the [PC_CODE] Header and [PC_CODE] Detail columns.
Simple records in the [INF_CV_SUNDRYLINES] table will only have one record. An example of this type of sundry line would be United Way deductions or uniform allowances. Since this type of record will cause the same value to be processed by payroll, there is no need for any other PC Codes to track information of the transaction. These single record sundry lines will have the same [PC Code|PC_CODE] in both the [PC_CODE] Header and [PC_CODE] Detail columns.
At line 63 changed one line
More complex sundry lines, such as garnishments, will require additional records to track the additional information in order to make the correct calculations. For example, a garnishment deduction will need to track the amount to be taken each pay period as well as the current balance of the deduction. In this example the INF_CV_SUNDRYLINES will need to have two records loaded for these two values. The first record will have the [pay component|PAY COMPONENTS] in the [PC_CODE] Header and [PC_CODE] Detail columns set to the deduction [PC Code|PC_CODE], while the second record will have the [PC_CODE] Header set to this same [PC Code|PC_CODE] and the [PC_CODE] Detail will be set to the declining balance [PC Code|PC_CODE]. The first record will have the amount of the pay period deduction entered into the [AMOUNT] column and the second record will have the balance at the time of the conversion in its [AMOUNT] column.
More complex sundry lines, such as garnishments, will require additional records to track the additional information in order to make the correct calculations. For example, a garnishment deduction will need to track the amount to be taken each pay period as well as the current balance of the deduction. In this example the [INF_CV_SUNDRYLINES] will need to have two records loaded for these two values. The first record will have the [pay component|PAY COMPONENTS] in the [PC_CODE] Header and [PC_CODE] Detail columns set to the deduction [PC Code|PC_CODE], while the second record will have the [PC_CODE] Header set to this same [PC Code|PC_CODE] and the [PC_CODE] Detail will be set to the declining balance [PC Code|PC_CODE]. The first record will have the amount of the pay period deduction entered into the [AMOUNT] column and the second record will have the balance at the time of the conversion in its [AMOUNT] column.
At line 67 added 9 lines
[{If var='loginstatus' contains 'authenticated'
----
![Discussion|Edit:Internal.CONVERTING+SUNDRY+LINES]
[{InsertPage page='Internal.CONVERTING+SUNDRY+LINES' default='Click to create a new discussion page'}]
}]