Refer to documentation Implementation
In this function, define all the characteristics of the time event, such as:
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 used by default in reports and screens (if there is enough space). |
| Short description. |
|   |
| 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. |
|   |
|   |
Close
Presentation
In this tab, define in details all the characteristics of the event.
Close
Fields
The following fields are present on this tab :
Setup
| 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. |
| 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. |
| No help linked to this field. |
| 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. |
| The event entry is performed by:
These periods are defined for a pay date in the "Extraction periods" function. |
|   |
Management
| This check box is used to activate or disable the current record without losing its contents. |
| 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. |
| Indicates if the event can be used by the "Automatic creation" function, which automatically generates events in time entry. |
| This field makes the comment entry mandatory in time entry. |
|   |
|   |
|   |
|   |
Time
| 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.) |
| No help linked to this field. |
| 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.). |
| This field conditions the entry of the activity type in time entry. |
| Triggers the workflow rule associated when the event nature is updated in entry time. |
| Prohibits event entry on a period posterior to that of the pay month. For example, the entry of a Suspension event cannot be anticipated. |
| No help linked to this field. |
|   |
| For example, the delegation hours must not appear on the calendar slip |
| This field is used for the calculation of the working time smoothing hours. |
Note required
|   |
|   |
|   |
|   |
Leave control
|   |
|   |
|   |
| Balance control: controls the balance for the current event code. |
|   |
View in holiday planning
| Groups a set of time events in order to visualize them by group on the annual leave planning. |
|   |
Close
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. |
|   |
Grid Analytical dimensions
|   |
| 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. |
|   |
Fields
The following fields are present on this tab :
Setup
| 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. |
| If this box is checked, the current event balance is visible in the Calendar and Reference plannings functions of the Sage X3 People Portal. |
| If this box is checked, the event code balance is visible in the Leave balance inquiry function of Sage X3 People Portal. |
|   |
|   |
| 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
Fields
The following fields are present on this tab :
Grid Leave sub type
|   |
|   |
|   |
Close
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.
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.
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 range suggested by default takes into account the current record, but you can modify it at launch time.