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

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
10 26-Nov-2021 10:22 1 KB Karen Parrott to previous
9 26-Nov-2021 10:22 1 KB Karen Parrott to previous | to last
8 26-Nov-2021 10:22 1 KB rforbes to previous | to last
7 26-Nov-2021 10:22 563 bytes jmyers to previous | to last CUSTOM WAGE RATE ==> CUSTOM WAGE RATE(System_Preference)
6 26-Nov-2021 10:22 563 bytes jmyers to previous | to last
5 26-Nov-2021 10:22 563 bytes jmyers to previous | to last
4 26-Nov-2021 10:22 527 bytes jmyers to previous | to last
3 26-Nov-2021 10:22 507 bytes jmyers to previous | to last
2 26-Nov-2021 10:22 506 bytes RForbes to previous | to last
1 26-Nov-2021 10:22 360 bytes JEscott to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed 2 lines
!System Preference
!!!CUSTOM WAGE RATE (System Preference)
__NOTE - This Preference has been Deprecated.__
\\ \\
At line 5 removed 2 lines
Values allowed: P2K_SPWAGE_PRE
At line 8 added one line
The custom wage rate logic identified in this scenario must be defined in as a function in the database which takes no parameters and returns a boolean TRUE;
At line 10 added 15 lines
This data base function has access to all the P2K_PPGENR8 package variables including complete table structures like [Pay headers|P2K_PR_PAY_HEADERS] (K_PPH), [Pay lines|P2K_PR_PAY_LINES] (K_PPL) and [Pay line details|P2K_PR_PAY_LINE_DETAILS] (K_PPLD). The output of the custom wage rate function is populated into package variables that are then used in the subsequent payroll calculation:
;P2K_PPGENR8.K_CUSTOM_WAGE_RATE:The result of the computation or manipulation. This is the new wage rate that will be used for that transaction, on the pay line detail.
;P2K_PPGENR8.K_WAGE_MESSAGE: Any diagnostic or informational messaging is populated here. This ends up in the pay line's [AUDIT_TEXT] field
Care should be taken to ensure that there are no places where the function can abort due to data problems. This is usually done with a construct at the end like
{{{
EXCEPTION
WHEN OTHERS THEN
p2k_ppgenr8.k_wage_message := p2k_pmgen.error_stack;
p2k_ppgenr8.k_wage_output := 0;
RETURN TRUE;
END;
}}}
At line 11 changed 2 lines
![Notes|Edit:Internal.CUSTOM+WAGE+RATE]
[{InsertPage page='Internal.CUSTOM+WAGE+RATE' default='Click to create a new notes page'}]
![Notes|Edit:Internal.CUSTOM WAGE RATE(System_Preference)]
[{InsertPage page='Internal.CUSTOM WAGE RATE(System_Preference)' default='Click to create a new notes page'}]