Time management > DON'T USE > 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

SEEREFERTTO 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

Fields

The following fields are present on this tab :

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).
If you have limited space, you can use the short title if there is one.

  • Short title (field SHO)

Short description.
Description on 10 alphanumeric characters.

  • Enhanced leave event (field LVEENHANCE)

 

In multi-legislated folders (where the LEG activity code is active), the Legislation fields are displayed.

  • If a legislation has been set in the LEGFIL (Legislation selection filter) parameter (SUP chapter, INT group), it is used as the default but can be changed if needed.
  • If LEGFIL has no legislation set, there will not be a default, so the Legislation field will have to be entered appropriately.

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.

 

 

Close

 

Tab Management

Presentation

In this tab, define in details all the characteristics of the event.

Close

 

Fields

The following fields are present on this tab :

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:

  • Time extraction: The event date belongs to an extraction period corresponding to a whole number of weeks.
  • Calendar month: The event date belongs to the monthly period (for example: from 1st to 31th).

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.
A disabled record cannot be used (by calling its code) in other records (documents, parameters etc.) or during mass processing.
Authorizations granted for a given function can prohibit the creation of an active record. In that case, the box is disabled by default and can only be modified by an authorized user or via a signature circuit defined by Workflow.

Assign an access code to the event, so that the access to this event can then be controlled upon inquiry or modification.

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.
For example: A RTT day is imposed by the company. The "Automatic creation" case must be activated to assign the RTT event to all the employees for this date.

  • Comment mandatory (field CMTOBG)

This field makes the comment entry mandatory in time entry.

 

  • 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.
This workflow rule must be of "Time management" type and its triggering event code must be the event nature.

  • 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: defines the minimum balance.

  • 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.

 

Close

 

Tab Analytical

Presentation

In this tab, define the analytical breakdown of the event.

 

Fields

The following fields are present on this tab :

Default dimension

This default dimension initializes analytical dimensions in time entry, if the event code is entered.

  • Title (field CCEINIDES)

 

Grid Analytical dimensions

 

  • 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.
If a default dimensionis entered, the distribution is first performed according to this dimension code.

 

 

Tab Dashboard

Fields

The following fields are present on this tab :

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.

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).

Close

 

Tab Leave sub type

Fields

The following fields are present on this tab :

Grid Leave sub type

 

  • Priority (field LVESUBPRI)

 

  • Accrual (field LVEACCPRI)

 

Close

 

Reports

Menu Bar

Documentation / Paragraphs

This menu item allows access to the documentation management on the first paragraph of the documentation (if there is one) associated with the current record.

Documentation / Links

This menu item allows access to link management. It is used to define the links between the current record and other records (for example, the links between functions and parameters). These links are specific to the documentation and are used to load the generation of documentation structures.

Documentation / Generation

This menu item launches a documentation generation. You can also launch it from the Generation button at the bottom of the screen.

You can launch three types of generation one by one or simultaneously

  • The generation of the documentation structure from the dictionary (ADOCUMENT, ADOCBLB, and ADOCCLB tables)
  • The generation of the documentation from the previous tables
  • The generation of the field documentation

The range suggested by default takes into account the current record, but you can modify it at launch time.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation