Forecasted plan
The training plan is elaborated by taking into account the training requests of the employees and managers, and by taking into account provisional actions, even if the attendees and training periods are not identified or defined yet.
The costs are deducted depending on:
- The training period costs defined in the Training period function
- The salary costs of the trainee
- The average salary costs by 2483 category if the trainee is not identified
Asessioncan be included in two budget periods. The training costs of the session are determined for a single budget period. The value of the CTLBUR - Session end date parameter (chapter FRT, group MIS) specifies whether the costs are defined for the budget of the first year or of the second year.
Prerequisites
Refer to documentation Implementation
Screen management
Header
The training plan is elaborated by period for the whole folder, by company or exceptionally by site. You can create several successive versions of the plan before finally validating it.
When the Final checkbox is selected (version communicated to the works council), you cannot generate other versions of the plan over this period.
Identifier
Chart code (field YEAPLF) |
Training plan code When the plan is final (the Final checkbox is selected), the plan code, the start date and the end date automatically populate the training requests (GESDEM) linked to the training plan. |
field LIBFILT |
Legislation (field LEGPLF) |
Company (field CPYPLF) |
Provisional plans can be defined by company. |
Site (field FCYPLF) |
Provisional plan can be defined by site. |
Version (field VERPLF) |
Version of the plan over the period (10 characters authorized). |
Final (field FLGCLO) |
Several versions of the training plan can be created for the same period. The plan with the Final checkbox selected is the plan that is is transmitted to the works council. Once a final training plan has been created for a period, it is no longer possible to generate other versions for this period. When a plan is final (the Final checkbox is then selected), the plan code, the start date and the end date automatically populate the training requests. The training requests considered for this plan can no longer be modified. These requests are no longer taken into account in the simulation of new provisional plans. You can remove the final status of a plan at any time. In this case, the training requests can once again be modified. |
Start date (field STRDAT) |
If the plan code already exists in the Budget guideline function (GESBUR), the Start date and End date fields are automatically populated with the dates entered in the reference budget. You cannot modify these dates. If you create a new plan code without linking it to a reference budget, you can enter any date. When a plan is final, the plan code, the start date and the end date automatically populate the training requests. |
End date (field ENDDAT) |
Total cost of plan
Budget (field AMTBUDREF) |
This field displays the reference budget corresponding to the current element, that is to say, the period, the company and the site. The displayed amount is either:
|
Total (field TOT) |
No help linked to this field. |
Chargeable (field IPT) |
Plan/budget (field PRCPLFBUD) |
field PRC |
Tab Plan
You can enter the plan manually in the Plan entry grid or click Proposal to preload the plan. To facilitate the entry, use the Request picking selection list.
For each line entered, the detailed costs of the training period or session (if the training request is linked to a session) are displayed in the Provisional costsgrid..
The salary costs of the trainees are valued according to the 2483 category of the attendees, in case of a non-nominative training request. Otherwise, salary costs are valued according to the payroll plan headings set up in the following parameters:
- Chargeable employer hourly rate - TXHRPAT
- Total employer hourly rate - TXHRPAT2
- Chargeable employee hourly rate - TXHRPAT
- Total employee hourly rate - TXHRPAT
The total cost of the plan is displayed in the header.
You can value training actions, even when the training period is not defined. In that case, the training period code to be used is the one defined as dummy in the Training periods function. The same fields are available for entry.
For example:
As part of the HR policy, the manager knows that some actions will be taken for a group of employees. The terms have not been defined yet, but a global budget has been allocated. In that case, the action is added to the plan by using the dummy training period code and it can provide all the available information on the category, the system, etc.
You can isolate the calculations on some lines of the plan for simulation purposes before confirming that a plan is final (the Calculation column is set to No).
Grid Plan entry
Calculation (field CLCFLG) |
This allows you to assess the impact of a plan line deletion on the costs and on their distribution before a permanent deletion. A plan cannot be final (check box not accessible) when there are lines with the value 'No' in the Calculation field. The user has to make a choice:
|
No. (field NBREMP) |
Number of employees selected to participate in the training period. |
Training period (field STG) |
Training period to be integrated in the training plan. |
Priority (field PIO) |
Information initialized by the request or the entry. |
Domain (field DOM) |
Theme (field THM) |
Gender (field SEX) |
Age (field AGE) |
Source (field ORI) |
Pro period (field FLGPRO) |
Date (field DAT) |
Standard job (field JOBPOT) |
Position (field POT) |
Fiscal nature (field NATFIS) |
Action category (field CATACN) |
Request (field DEMNUM) |
Status (field STA) |
Employee ID (field EMP) |
If there is only one participant, it is possible to enter the ID of the employee. The request is nominative. |
First name (field SRN) |
Contract (field CTRNUM) |
Contract of the employee. . |
Site (field FCY) |
Site to which the training period participants must be attached. |
Category (field CATFRT) |
Category of employees selected to participate in the training period. A warning message is displayed if the entered category is not the one concerned by the training period. |
Department (field SRV) |
Service to which the training period participants must be attached. |
Grid Provisional costs
Cost (field TYPCRG) |
This table details the cost of each line of the training plan. If a request is added manually to the training plan, the cost lines are marked as ‘automatic’. The values will come from the training period. The costs in the training period are applied, and if there is a training cost distribution associated with the training period, then the distribution rules will be applied where appropriate. If a cost is added manually to the grid, the values will not come from the training period and. no training cost distribution will be applied. The costs (salary and charges) of the participants, or the trainer, are calculated automatically, according to the payroll headings defined in the parameters. If the costs are defined in the cost distribution from the training period, the same rules are applied automatically. If the payroll module is not available, or the training requests are not for named people, the costs are calculated according to their categories. Miscellaneous table 453 – Categories contains the hourly rates that are applied. |
Cost type (field TYPCST) |
If the line was generated from a proposal this field will be set to ‘Automatic’ otherwise, if the line was added manually it will be set to ‘Manual’. If you amend one of the two ‘Automatic’ lines linked to a cost distribution, they both become ‘Manual’. If you delete one of the two ‘Automatic’ lines linked to a cost distribution, you will be warned that the line will be recreated if the plan is revalued. This field cannot be amended. |