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
CONVERTING SUNDRY LINES
CONVERTING SUNDRY LINES

Version management

Difference between version and

At line 17 changed one line
|PC_CODE_HEADER| NOT NULL| NUMBER(4)| Must be a valid PC Code from the [IPPC] screen
|PC_CODE_HEADER| NOT NULL| NUMBER(4)| Must be a valid [PC Code|PC_CODE] from the [IPPC] screen
At line 29 changed one line
|ASSIGNMENT_CODE| | NOT NULL| VARCHAR2(16)| Used to derive link to ASSIGNMENT record
|ASSIGNMENT_CODE| NOT NULL| VARCHAR2(16)| Used to derive link to ASSIGNMENT record
At line 34 changed one line
|TIME_ENTERED| | NUMBER(18,6)| Value associated to the PC Code of this Sundry Line
|TIME_ENTERED| | NUMBER(18,6)| Value associated to the [PC Code|PC_CODE] of this Sundry Line
At line 39 changed one line
|PC_CODE_DETAILS| | NUMBER(4)| Must be a valid PC Code from the IPPC screen
|PC_CODE_DETAILS| | NUMBER(4)| Must be a valid [PC Code|PC_CODE] from the [IPPC] screen
At line 42 added 25 lines
|ELEMENT_CODE| |VARCHAR2(16)|
|USER_VARIABLE_CODE | |VARCHAR2(16)|
|PC_CALC_METHOD| | VARCHAR2(30)| Must be a valid lexicon entry. Typically 00 or 'EV: Entered Value'
|DESCRIPTION| | VARCHAR2(50) |
|WAGE_RATE| |NUMBER(18,6)| A valid is only needed if this is not the employees prime assignment value
|WAGE_RATE_OVERRIDE | | NUMBER(18,6)|
|RATE_BASIS | | VARCHAR2(30)| A valid is only needed if this is not the employees prime assignment value
|RATE_BASIS_OVERRIDE | |VARCHAR2(30)|
|AMOUNT | |NUMBER(18,6)| Value associated to the [PC Code|PC_CODE] of this Sundry Line Detail
|AMOUNT_OVERRIDE | |NUMBER(18,6)|
|USER_VARIABLE_OVERRIDE| |NUMBER(18,6) |
|DISTRIBUTION_DR_MASK | |VARCHAR2(50) |
|DISTRIBUTION_CR_MASK | |VARCHAR2(50)|
|PC_RATE_SOURCE | |VARCHAR2(30)|
|HIGHER_OF_RATE | |VARCHAR2(4)|
|USER_FIELD_VALUE_01| |VARCHAR2(2000)|
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 High Line FTP server, or is included on the application installation CD.
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.
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.
The two records for the same employee and the same [PC_CODE] Header will create one record in the [P2K_PR_SUNDRY_LINES]. However, these two records will create two separate records in the [P2K_PR_SUNDRY_LINE_DETAILS]. Both of these records can be seen in the [IPSN] screen of the application after they have been converted by selecting the Details tab in the lower right side of the screen.
This page (revision-12) was last changed on 26-Nov-2021 10:22 by jmyersTop