Staff departures - Implementation

Prerequisites

Activity codes

The following activity codes (sorted by type) may have an impact on the way the function operates :

Dependent activity codes

These codes are never entered in folder management, because their value is calculated :

 FHRPA (Presence of HCM or HRA), FKSPA (Payroll localisation for RSA), FPAY (Presence of the Payroll module), KGZA (Global Sage ZA localization), KMIEA (Middle-Eastern localization), NFR (Absence - Training).

Functional

 FRT : Training management

Localization

 KAE : Arab Emirates localization

 KQA : Qatar localization

 KSA : Saudi Arabia localization

 KUK : Localization united kingdom

 KZA : South-African localization

General parameters

The following general parameters may change the way the function is working :

Payroll-X3P

 SLDTTCPT (defined at level Legislation) : Full settlement

 TYPCP (defined at level Site) : Holidays management - Working dys

Time management-X3P

 HOUMAXYEA (defined at level Site) : Max number of hours/year

 HOUWEKLEG (defined at level Site) : Company weekly hours

Authorizations

This function is object managed. The creation, modification, anddeletion operations can be activated or deactivated for a given user.Filters by rolescan also be associated with this function.

As data is linked to a site, a filter per site can be activated.

Miscellaneous pre-requisites

This function only manages the outgoing staff (redundancy, end of contract, resignation, etc.). The final departure of an employee being the only event that can trigger the generation of a record. Consequently a departure date needs to be entered in the personal file.

Tables used

The following tables are implemented by the function :