Nature of events
All the time spent by an employee is divided into a succession of activities called events. Events constitute the basis of the employees' time entry. The event valuation will be used to populate pay and time variables.
Prerequisites
Refer to documentation Implementation
Screen management
In this function, define all the characteristics of the time event, such as:
- The valuation type of the time event (numbers of hours or days)
- Its category (time worked or not)
- Its base (work days, working days, calendar days)
- The management automatisms it benefits from
- ts analytical distribution.
Header
Code (field COD) |
Event code with three characters identifying the nature of the time spent. The time entry is performed on these event codes. |
Description (field DES) |
Description used by default in reports and screens (if there is enough space). |
Short title (field SHO) |
Short description. |
Enhanced leave event (field LVEENHANCE) |
Legislation (field LEG) |
In multi-legislated folders (where the LEG activity code is active), the Legislation fields are displayed.
If a legislation is entered in the record header, other fields entered must follow any rules applicable to the legislation. If a legislation is not entered in the record header, it might be deduced from another element (such as the company, site, or employee) and again, other fields entered must follow any rules applicable to the legislation. If a multi-legislation group of companies is selected, other fields entered must follow any rules applicable to the legislation of at least one company in the group. Example If you select a group of British (BRI) and French (FRA) legislation companies, you cannot enter a value in a field that is only applicable to the South African (ZAF) legislation. In single legislation folders (where the LEG activity code is not active), the Legislation fields are not displayed. |
Company (field CPY) |
Site (field FCY) |
Tab Management
In this tab, define in details all the characteristics of the event.
Setup
Entry type (field DAYDAC) |
This field defines the unit in which the event duration will be entered in days or hours. In both cases, the other unit will be automatically deduced from the calendar. |
Event valuation (field VLTEVT) |
Used in the portal entry of absences, this parameter calculates the legal start and end dates of the leave. For RTT, start and end dates must be a work day. For paid leaves, the start date is a day worked and the end date is the day before work is resumed. |
Category (field CATTIM) |
No help linked to this field. |
Valuation in days (field DAYTYP) |
This field defines how the default value of the event's number of days (or hours depending on the case) will be evaluated based on the start and end dates of the event. Depending on the choice, the system will propose the number of working days, work days or calendar days according to the employee's planning. |
Entry period (field MONDAC) |
The event entry is performed by:
These periods are defined for a pay date in the "Extraction periods" function. |
Cost type (field CSTTYP) |
Management
Active (field ENAFLG) |
This check box is used to activate or disable the current record without losing its contents. |
Access code (field ACS) |
Assign an access code to the event, so that the access to this event can then be controlled upon inquiry or modification. |
Declaration (field CODDDS) |
The event nature code must be associated with a code expected by the standard for N4DS and DSN legal declarations (French legal declarations). The correspondence between event codes and codes expected by the standard is managed in the 344 miscellaneous table - Specific situation. You can access this table from the field. |
Automatic creation (field GNRAUT) |
Indicates if the event can be used by the "Automatic creation" function, which automatically generates events in time entry. |
Comment mandatory (field CMTOBG) |
This field makes the comment entry mandatory in time entry. |
Population (field POP) |
Filter (field FILTRE) |
Reason mandatory (field RSNMAN) |
SS limit contribution (field CLGPPNSSC) |
Time
Working time (field WRKTIM) |
The event traces an activity of "working time" or "other" type. This distinction is the calculation basis for certain time variables (time off in lieu, adjustable working hours, etc.) |
Time off in lieu (field REPFLG) |
No help linked to this field. |
Day/night management (field NGTDAY) |
The event traces a day or night "working time" activity. This distinction is the calculation basis for certain time variables (day basket, night basket, etc.). |
Activity type entry (field TYPDAY) |
This field conditions the entry of the activity type in time entry. |
Workflow (field WRKEVT) |
Triggers the workflow rule associated when the event nature is updated in entry time. |
Prior entry forbidden (field CTLDAC) |
Prohibits event entry on a period posterior to that of the pay month. For example, the entry of a Suspension event cannot be anticipated. |
Activity nature entry (field NATACT) |
No help linked to this field. |
Time slot entry (field PLGHOR) |
To be excluded from the calendar slip (field PRNCAL) |
For example, the delegation hours must not appear on the calendar slip |
Paid absence WT smoothing (field ABSPAY) |
This field is used for the calculation of the working time smoothing hours. |
Note required
Number of days (field NBRDAY) |
Count nonbusiness days (field NONBUS) |
Before nonbusiness or public holiday (field BFRNON) |
After nonbusiness or public holiday (field AFTNON) |
Leave control
Insufficient leave option (field LVEINSOPT) |
Maximum credit (field LVEMAXCRE) |
Max credit option (field LVEMAXOPT) |
Balance control (field FLGBLC) |
Balance control: controls the balance for the current event code. |
Minimum balance (field BLCMIN) |
View in holiday planning
Type (field PLNGRP) |
Groups a set of time events in order to visualize them by group on the annual leave planning. |
Statutory pay category (field SXPCAT) |
Tab Analytical
In this tab, define the analytical breakdown of the event.
Default dimension
Default dimension (field CCEINI) |
This default dimension initializes analytical dimensions in time entry, if the event code is entered. |
Title (field CCEINIDES) |
Grid Analytical dimensions
Dim type code (field DIE) |
Input (field CCEDAC) |
Dimension on which the analytical distribution of the dimension type is posted. This dimension can be modified in time entry if the dimension type is enterable. |
Analytical dimension (field CCE) |
Tab Dashboard
Setup
Enterable on portal (field AUZPRH) |
If the field is set to Yes, the current event code can be used in the holiday request entry function of the client server and portal. |
Design code (field DESIGN) |
The design code is used to define the graphical representation of the current event code in the Calendar and Reference plannings functions of Sage X3 People Portal. |
Display on calendar (field AUZCAL) |
If this box is checked, the current event balance is visible in the Calendar and Reference plannings functions of the Sage X3 People Portal. |
Display on balance (field DSPSLD) |
If this box is checked, the event code balance is visible in the Leave balance inquiry function of Sage X3 People Portal. |
Justifying (field JUSTIF) |
Display sub types (field DSPSUBTYP) |
Display code superimposed on calendar (field OVERWR) |
Check this box if you want to display the code of nature of event in the calendar, in addition to the design code (the design code corresponds to the background color used for the code of nature of event). |
Tab Leave sub type
Grid Leave sub type
Leave sub type (field LVESUBTYP) |
Priority (field LVESUBPRI) |
Accrual (field LVEACCPRI) |