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

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
5 26-Nov-2021 10:22 1002 bytes Karen Parrott to previous FTE_CHECKING_ROUTINE (System Preference) ==> FTE_CHCK_ROUTINE (System Preference)
4 26-Nov-2021 10:22 965 bytes kparrott to previous | to last
3 26-Nov-2021 10:22 966 bytes rforbes to previous | to last
2 26-Nov-2021 10:22 839 bytes rforbes to previous | to last
1 26-Nov-2021 10:22 773 bytes rforbes to last

Page References

Incoming links Outgoing links
USER EXIT...nobody

Version management

Difference between version and

At line 3 changed 8 lines
A) [User Calcs|USERCALC] - This is a end-user oriented mechanism of inserting specific logic at various points in Benefits or Attendance processing, in the Payroll Cycle
B) Reactive [Workflow|WORKFLOW] - This is logic that is called just before the record being inserted / updated / deleted is committed to the database.
C) Specific Logic points that are configurable, but require a PL/SQL function to be defined
* This is generally controlled with a function level preference so that different screens may have different logic.
**[FTE_CHECKING_ROUTINE|FTE_CHECKING_ROUTINE (System Preference)|FTE_CHCK_ROUTINE (System Preference)] - for posting based screens like IRPO to validate/set FTE values
**[DPS_AVAIL_EXIT|DPS_AVAIL_EXIT (System Preference)] - for posting based screens like IRPO to control if a position is valid for selection
* [User Calcs|USERCALC] - This is a end-user oriented mechanism of inserting specific logic at various points in Benefits or Attendance processing, in the Payroll Cycle or in a [Work Flow|WORKFLOW]
* Specific Logic points that are configurable, but require a PL/SQL function to be defined
** This is generally controlled with a function level preference so that different screens may have different logic.
***[FTE_CHECKING_ROUTINE|FTE_CHECKING_ROUTINE (System Preference)] - for posting based screens like IRPO to validate/set FTE values
***[DPS_AVAIL_EXIT|DPS_AVAIL_EXIT (System Preference)] - for posting based screens like IRPO to control if a position is valid for selection