Ansicht
Dokumentation

RPLAASF1 - Employer statement for the French Employment Center

RPLAASF1 - Employer statement for the French Employment Center

BAL_S_LOG - Application Log: Log header data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

The ASSEDIC statement (Association pour l'Emploi dans l'Industrie et le Commerce) is a document that the company must issue to the employee when the employment contract ends, regardless of the reason for terminating the contract.

In addition to details about the employee and the company, the statement contains information about the contract termination, the working hours and the pension funds. It also shows the development of the employee's salary over the last twelve months of employment.
SAP supplies an automated version of this statement.

As the content of the legal document is represented faithfully in the SAP version of the form, the UNEDIC (Union Nationale Pour l'Emploi Dans l'Industrie et le Commerce) assigns the agreement number 1022 to the form. The statement is an automated version of the Assedic statement and not a draft.

The automated statement has 11 frames, each corresponding to a frame in the standard statement.

Maintenance of contracts with tables T5F42 to T5F45:

  • You can use the Corporate Function (0034) infotype to fill in a status or a specific job category. If you want to create your own status or category, use the new "go to" created in the ASSEDIC Statement business phase in the implementation guide (IMG).
  • Once the T5F42 table is set to the data necessary for the identification of the CDD (fixed term contract), CDI (permanent work relationship) and special contract, it replaces the characteristics FAAS5 and FAAS6 (these are still used for all data that cannot be set in the table).
    Set the new parameters, refer to the IMG work step on ASSEDIC Statement.
  • The reasons for contract termination have been changed, and some have even been deleted. You can refer to the documentation on the FAAS1 characteristic for a current and comprehensive list of these reasons.

Prerequisites

In order to issue an ASSEDIC Statement for a given employee, the employee must:

  • have a payroll for month of leaving (month of the last day of activity)
  • be subject to:
  • a leaving action: change from an active status (stat2 = 3) to a inactive status (stat2 <> 3) in the Action (0000) infotype OR

  • another action entered in the "Other action to take into account" field.
    You are now able to make an Assedic Statement for an employee for whom you enter in the program selection screen an action of reentry the following day.

The T5F1E table also needs to be set with the addresses of the contribution funds.

Features

The information reported in the statement is taken from master and payroll data in the system, except for the codings specific to the ASSEDIC.

A certain amount of data is not available in the system and the user has to enter this manually in the selection screen.
These are:

  • the relationship of the employee to the company manager

  • the special Social Insurance registration plan (if applicable)

  • the date of the first presentation of the social plan (if applicable)

  • the dates of validity and of the employee's adherence to the F.N.E. convention (if applicable, the program checks that the employee is 55 or older before showing this line)

  • the reason for contract termination if it is different than those set by ASSEDIC

  • the reason for the difference between the usual weekly hours in the company and those worked by the employee (if applicable)

  • the reason for not paying paid leave (if applicable)

  • the periods covered by non-monthly bonuses

  • the collection of a FNGS down-payment (if applicable)

  1. Frame 1 - EMPLOYER
  • The "Business name", "Employer's address" and "Telephone number" fields are defined using the "FDDR1" characteristic and table "T536A".
  • The "SIRET Number", "APE Code" and "Agency that collected the unemployment insurance contributions" fields are filled in from the T5F1P table.
  • The field concerning the Assedic comes from the T5F1P table. "GARP" must be entered in the "Name of the Assedic" field in the T5F1P table.

  1. Frame 2 - EMPLOYEE
  • The employee's name and first name (and female employee's marital name) come from the Personal Data (0002) infotype.
  • The employee's address comes from the Addresses (0006) infotype.
  • The employee's Social Insurance number comes from the Social Data (0064) infotype.
  • The "Qualification level" code comes from the FAAS2 characteristic, according to the status and category of the employee, etc. The code is defined by the ASSEDIC, and given by the program, but the user must set the link between the status and the qualification code.
  • The employment specification "Executive/Non-executive" comes from the FACI1 characteristic, according to the status and category of the employee, or to the type of contract of your employees.
  • The "Relationship to company manager" field is supplied in the selection screen, under the tab "Special case".

  1. Frame 3 - EMPLOYEE'S ADDITIONAL PENSION FUNDS

The additional pension funds come from the employee's infotype 64. You have to fill in the new column CATEG in the T5F1A table, which gives a list of your contribution funds, and to assign the appropriate value to your pension funds.
The addresses of the pension funds are read in the T5F1E table, with the department of the establishment.

  1. Frame 4 - EMPLOYMENT
  • The employment dates of the applicant are defined according to the infotypes Contract Elements (0016), Organizational Assignment (0001) or Actions (0000).
If you want a permanent employment contract following a temporary employment contract to be grouped as a single employment period, set the T5F42 table (or the characteristic "FAAS5" if the table cannot be set). In order for these two contracts to form one single employment period, the days when the employee did not work between the two contracts must be non-workdays or non-working days.
The "Last job held" field is determined (via the function module HR_FR_GET_QUALIFICATION) by the 0217 "Code INSEE" infotype or infotype 0001 according to the setting of the QUALI constant in the T511K table.
  • Notice dates are displayed only if the employee has a permanent work contract. If notice is given, the notice start and end dates must be specified in the Date Specifications (0041) infotype.
  • Code 80 corresponds to the date on which notice was given to the employer.

  • Code 81 corresponds to the notice period start date.

  • Code 82 always corresponds to the notice period end date (regardless of whether it is observed or not, or paid or unpaid).

Two other situations may arise:
- If the notice is not entirely observed, you can also enter code 42 "Last day worked" (end of the period carried out). If you do not enter this, the system will calculate this date itself.
- If part of the notice is not observed but is paid, you must enter the additional code 43 "Last day paid" (end of the period not carried out but paid).
  • Special employment category: this must be filled in according to the Corporate Function (0034) infotype.
Exception: if the employee is a casual worker, a temporary worker or an expatriate, the information comes from table T5F45 (and not from infotype 0034).
  • Concerning the duration and weekly working hours,
  • the values of the weekly and annual work duration in the company come from the characteristic FAAS4 and the payroll parameter table (T511K); if the annual work duration is not provided by the parameter, then it is calculated according to the personal data of the employee and the weekly work duration in the company.

  • the value of the employee's weekly and annual hours comes from the "Planned working time" (0007) infotype. If the employee's contractual work duration does not correspond to the work duration that comes from the 0007 infotype, this contractual duration can be entered on the selection screen in the "Contractual weekly work duration" and "Contractual annual work duration" fields.
    If the collective and individual durations do not correspond and the employee's operating rate (coming from the "Basic Pay" 0008 infotype) is different from the fixed value HACTI (in table T511K), then the system automatically displays part-time work as the reason for the difference.

  • The "Work relationship" field is supplied (via the function module HR_FR_GET_CONTRACT) by the Organizational Assignment (0001) or Contract Elements (0016) infotype, depending on whether the fixed value "CONTR" in table T511K is 1 or 0.
  • Special contracts are filled in by the new contract management (table T5F42). If this information is not available, the program uses the characteristic "FAAS6".
  • The "Special Status" selection is also filled in by the Corporate Function (0034) infotype.
  • If the employee is registered to a special Social Insurance plan, you must fill the fund and the registration number in the same field, following the note "Registration number". If the employee is not registered in a special Social Insurance plan, enter "Not applicable".

  1. Frame 5 - TOTAL UNEMPLOYMENT WITHOUT TERMINATION

The days of partial unemployment considered to be managed by the absences processing. The partial unemployment hours linked to the DDTE allowances come from the subtypes entered in the selection screen. These data are only used if an allowance for partial unemployment has been requested under the tab "Special Cases" on the selection screen.

  1. Frame 6 - REASON FOR TERMINATION
  • The multiple choice specifying the reason for termination comes from the "FAAS1" characteristic, according to the type and reason for the leaving action.
  • Data concerning the social plan have to be entered in the selection screen, under the tab "Special cases".
  • On the statement, the program only shows the frame concerning the FNE convention if the employee is older than 55. The program does not specify whether this convention exists or not.

  1. Concerning frames 7.1, 7.2, 7.3

Sums concerned (salaries, bonuses, balance of all amounts) are declared in the currency in which they are sent. There is no need for conversion.

The values in frame 7 are calculated according to the payroll wage types that you specify in the selection screen and the payroll result clusters.

  1. Frame 7.1 - SALARIES OF THE 12 COMPLETE CALENDAR MONTHS PRECEDING THE LAST DAY WORKED AND PAID
  • The date of the last day worked and paid is the end date of the Actions(0000) infotype, whis is changed in the event of employee absence, whether compensated or not
    However, if you want to change the date of the last worked day because it does not correspond to the end of work contract (in case of notice not carried out, leave without pay or end of career), then you must enter the date 42 in the 'Date Specifications' (0041) infotype. The system will look for the last 12 months preceding the entered date.
  • The payroll period dates correspond to the payroll results clusters dates.
  • The payment date corresponds to the payroll calculation date (Cluster RF table VERSC).
  • The column "Number of worked hours" is calculated according to the wage types entered in the "Number of worked hours" field on the selection screen.
  • Concerning the management of absences, a distinction must be made:
  • Enter every unpaid absence other than illness in the "Absences, unpaid days" field (under the tab "Salary elements") on the selection screen.

  • In the case of illness, the number of days that have not been fully paid is determined by posting the days of grace, the days of absence without continued pay ("Continued" indicator in table T5F2A) and the days of absence based on the quotas specified in the "Partial salary quotas" field on the selection screen.

  • The monthly gross salary is calculated according to the payroll wage types in the "Gross salaries" field.
  • In the standard version, the cumulation wage type /118 allows you to set the amount of the gross salary to be displayed in this statement. This is a specific gross, in which every sum corresponding to the usual remuneration is included, i.e. the basic monthly salary and the compensation and bonuses with the same periodicity only.
    If you want to use an existing cumulation wage type (and do not want to create the wage type /118 corresponding to this definition of the gross), you can enter a gross including every bonus, even those with a periodicity different from the monthly salary, in the "Gross salary" field (tab "Salary elements"). You will then need to enter the special bonuses in the corresponding field in frame 7.2 before checking the box "Bonuses to be deducted from the gross".
  • The amount of the ASSEDIC payroll deduction is calculated according to the payroll wage types specified in the "Gross salaries" field.

  1. Frame 7.2 - BONUSES AND COMPENSATIONS
  • Bonuses and compensations with a periodicity different to the salaries that are not mentioned in the column "Monthly gross salaries" correspond to the wage types entered in the "Bonuses or compensations" field on the selection screen.
  • The dates corresponding to the period covered by the compensation or the bonus are displayed if the wage type entered in the selection screen is set in the view V_T5FPER.
  1. Frame 7.3 - BALANCE OF ALL AMOUNTS
  • The dates of payroll periods correspond to the dates of the last payroll result cluster, provided that it is not a full month.
  • The payment date corresponds to the payroll calculation date (Cluster RF table VERSC).
  • The gross salary is calculated according to the payroll wage types entered in the "Gross salary" field. The wage types entered in the "Comp. included in the gross salary" field are deducted.
  • The "Compensation for notice" field is calculated according to the wage types entered in the corresponding field of the selection screen.
  • The "Compensation for paid leave" field is calculated according to the wage type (containing the number of working days of compensated leave) entered in the corresponding field on the selection screen under the tab "Balance of all amounts".
  • The "Total statutory compensations" field is calculated according to the statutory compensations filled in the selection screen:
  • Statutory compensation for dismissal

  • Additional compensation for dismissal

  • Compensation for end of temporary work contract

  • Compensation for end of mission

  • Retirement compensation

  • Special compensation for dismissal

  • Compensation due to journalists

  • Customer compensation

  • Compensation due to civil aviation flight personnel

  • Other statutory compensations

The system automatically calculates the total of the statutory sums.

  • For sums already paid, you must specify the wage types in the "Effective sums total" field on the selection screen (under the tab "Balance of all amounts").
  • The "Transactional compensation total" and "Conventional compensation total" fields are displayed according to the wage types entered in the selection screen.
  • You also need to specify, by checking the box, if a transaction is pending.

  1. Frame 8 - NATIONAL FUNDS FOR SALARY GUARANTEE

This information is entered in the selection screen under the tab "Special cases".

  1. Frame 9 - EMPLOYER'S STATEMENT

All information is filled in the selection screen, under the tab "Signatory".

Output

The program generates the list of the chosen employees for the copy of the statement. In this list, each line corresponds to the data of one employee.
By double-clicking on the line of the employee concerned, you generate an Assedic statement for them.
This statement is printed via SAPscript, 1 page per employee. In order to access a print preview, you need to set a printer that supports the Postscript format.

A button allows you to launch the generation of Assedic statements for all the employees on the list.

Using the screen for the list in question, another button allows you to print the list of error messages, showing the personnel number followed by the errors that appeared for that personnel number during the program execution.

Integration

For further information, you can consult the documentation for the following characteristics
FDDR1
FAAS2
FACI1
FAAS6
FAAS5
FAAS1
FAAS4






Addresses (Business Address Services)   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 21509 Date: 20240601 Time: 173323     sap01-206 ( 416 ms )