Training requests
Use this function to register the training requests coming from the employees or their managers. The training requests populate the training plan and the training actions via the open sessions.
The training requests can be individual: in this case, the ID of the employee concerned is specified.
The training requests can be more general when they come from a supervisor or a HR manager. In this case, the request can be made for several employees with a specific theme. You can enter the session or the training period at this level when they are known.
Prerequisites
Refer to documentation Implementation
Screen management
Workflow rules
Training request
For every new training request created, an email is sent to the Human Resources manager for each employee.
This concerns the requests for which:
- the status is 'Entered',
- the employee and the contract are specified.
The message sent to the manager contains the following information:
- the name of the person who made the request,
- the number and the date of the request, the training period and potentially the session,
- the participant (first name, name, ID),
- a line to validate the request and a line to reject the request.
The workflow rule is DEMSTG.
The rejection rule is DEMSTGREG.
The visa rule is DEMSTGVIS.
The associated data model is DEMSTG.
The associated workbench is DEM.
Header
You can enter the request number. If you do not enter this number, a number is automatically assigned to the request when you create it.
Request (field DEMNUM) |
Sequence number identifying each request. If this zone is left blank, an order number will be automatically assigned on request creation. |
Legislation (field LEG) |
Training period (field STG) |
Training period the training request(s) is related to. |
Request date (field DATDEM) |
This field displays the date on which the request is made. This date is mandatory and can be modified. When creating a request, this date is initialized with the date of creation. For the existing requests, the field is initialized with the date of creation if this date is not already specified. |
Tab Characteristics
Some characteristics of the request are retrieved from the session if the session is specified, or from the training period if the training period is specified.
The employee can make a training request, or a manager can enter the training requests for their employees.
A request cannot be modified if it is part of the final training plan or if it has generated a registration.
General
Priority (field PIO) |
This field can take the following values:
When creating a request, the value of this field is set to 'Normal' by default. |
Request origin (field ORIDEM) |
This field can take the following values:
When creating a request, the value of this field is set to 'Entered' by default. |
Program code (field CODCSI) |
If the source of the request is 'Individual program', the code of the program is specified and the "Professionalization period" check box is selected or not depending on the parameters of the program. |
Professionalization period (field FLGPRO) |
If this check box is selected in the individual program, it will be specified in all the training process that the training concerned comes from the professionalization scheme. |
Request origin
Source (field ORI) |
The request can be:
|
Requester ID number (field REFNUM) |
The employee ID is specified when requesting a nominal training request. |
Last name and first name (field NAM) |
Request issuer contract (field CTR) |
When the training request is nominal and the employee has several contracts, those contracts are suggested and one of them must be selected. |
Session
Session (field SES) |
The training request can specify the session the participants want to attend. |
Domain (field DOM) |
The training request may be for a specific domain. If the training period is entered, this field is initialized. |
Theme (field THM) |
The training request may be for a specific theme. If the training period is entered, this field is initialized. |
Requested period from (field DATSTR) |
Period during which the training period can take place. If the session is entered, these fields are initialized. |
Requested period to (field DATEND) |
Provisional training plan
Outside of plan (field FLGPLF) |
Check "Outside of plan" if you do not want the training request to be included in a training plan. |
Chart code (field YEAPLF) |
The code of the training plan and the start and end dates of the training plan are automatically displayed if the training request is created for a final training plan (when the Final check box is selected in the Training plan function). They cannot be modified. |
Start date (field STRDAT) |
End date (field ENDDAT) |
Classification
Fiscal nature (field DESNATFIS) |
Enter or select a fiscal nature. |
Action category (field DESCATACN) |
The actions of the training plan are classified into three categories, each of them belonging to a specific scheme. Enter or select an action category. |
Comments
field CMT |
Tab Participants
If the source of the request is 'Individual' (in the Characteristics tab), the ID of the employee is displayed in the Participants table.
If the source of the request is 'Hierarchy', it is possible to enter nominal requests and non-nominal requests.
- To enter nominal requests: enter 1 in the Number column and select the employee.
- To enter non-nominal requests: enter the number of participants in the Number column and enter at least a value in the Category column.
If the request is hierarchical, several lines are available for entry.
The requests have two types of tracking: a manual tracking and an automatic tracking.
- Use the manual tracking to know the status of the request ('Entered', 'Denied', 'Accepted', and so on). This tracking can be configured.
- Use the automatic tracking to know if:
- the request has been accepted in the final training plan (Plan),
- the request has led to the registration of the employee for the training period (Registration),
- the training of the employee is over and the session is closed (Completed).
Grid
Status (field STA) |
The status of the line can take the Firm or Planned value. Only the delivery requests with the status Closed will be suggested for the delivery (see the Delivery documentation). However all lines can be viewed, independently of their status, using the delivery request inquiry (see the Delivery request inquiry documentation). |
Tracking (field FLGINS) |
This field is automatically updated by the system:
|
No. (field NBREMP) |
Number of employees concerned by the training request. The training request can combine both nominal requests (for one employee) and global requests (for N employees). |
Employee (field EMP) |
Enter the ID of the employee if the training request is nominal. |
Last name (field NAM) |
First name (field SRN) |
Contract (field CTRNUM) |
The contract number of the employee corresponds to one of his contract sequence number.
|
Site (field FCY) |
Enter a site if the training request only concerns the employees of a site. The site is automatically updated if an employee is entered. |
Category (field CATFRT) |
Category of employees concerned by the training request. The category is automatically updated if an employee is entered. |
System (field DESTYPFRT) |
Specify the framework of the training request:
|
Type (field TYPFIN) |
Type of funding for the cost nature. |
Organization (field ORGFIN) |
Funding organization. The funding organization entered must be active. Click the Selection icon icon in order to open the list of active organizations. |
Department (field SRV) |
Enter a department if the training request only concerns the employees of a department. The department is automatically updated when an employee is entered. |
Gender (field SEX) |
In collective requests, the gender and age fields are available for entry. |
Age (field AGE) |
Standard job (field JOBPOT) |
The "Standard job" and "Position" columns are:
|
Position (field POT) |
Refusal reason (field RENREF) |
The "Refusal reason" column is available for entry if the status of the line is 'Refused' and if the user has the appropriate rights. |
Rejection letter |
Reports
By default, the following reports are associated with this function :
FICDEM : Training requests
LISTDEM : Track training requests
This can be changed using a different setup.
Specific Buttons
Total generation
Click the Total generation button to mass generate the following requests:
A final log file details the requests created. You can launch those mass generations from the Processing menu. Filters
|