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

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

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
9 26-Nov-2021 10:22 1 KB rforbes to previous
8 26-Nov-2021 10:22 1 KB rforbes to previous | to last
7 26-Nov-2021 10:22 1 KB rforbes to previous | to last
6 26-Nov-2021 10:22 1 KB rforbes to previous | to last
5 26-Nov-2021 10:22 1 KB rforbes to previous | to last
4 26-Nov-2021 10:22 1 KB rforbes to previous | to last
3 26-Nov-2021 10:22 1 KB rforbes to previous | to last
2 26-Nov-2021 10:22 1 KB rforbes to previous | to last
1 26-Nov-2021 10:22 1 KB rforbes to last

Page References

Incoming links Outgoing links
P 2 K_PU.EID
P2K_PU.EID

Version management

Difference between version and

At line 14 changed one line
* {{__EEM_ID-''nn''__}} - Will return the ID of the [P2K_HR_EMPLOYMENTS] record that has the most future hire date for the [employment type|EMPLOYMENT_TYPE] identified by ''nn''. If no employment type is provided (i.e. the parameter is just "EEM_ID-" (with the hyphen)) then the most future hire dated employment ID will be returned, regardless of employment type.
At line 29 added 4 lines
{{P2K_PU.EID(~,'EEM_ID-01')}} - Using Identity ID as the first parameter (~)
;:Will return the ID of the ''current'' employment ID for employment type = 01 (Employee). Note that this does not restrict to active records - the employee may be terminated on this record. This can be used in a qualification record to compare if the EEM_ID retrieved is equal to this ''most current'' record.
This page (revision-9) was last changed on 26-Nov-2021 10:22 by rforbesTop