Ansicht
Dokumentation

RPLSPPS2 - SPP monthly insurance events

RPLSPPS2 - SPP monthly insurance events

Vendor Master (General Section)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report is an enhancement to the existing SPP monthly insurance events report (RPLSPPS0), and it creates the ALECTA report on white collar employees who are 18 years or older. This is a monthly report generated for reporting employee related events, registered during the reporting period to Alecta. The report obtains the relevant information from Information needed to be reported to Alecta database table (T5SPP).

The report generates information on the following employee related events:

  • IN - Entry to ALECTA ,
If there is any entry to ALECTA, the system reports the IN event.
  • FK - Organizational Reassignment / Change of company within group
In case of organizational reassignment or change of company within group due to which the Organizational number or Cost center (in view V_T5S0P_ALL) changes, the system reports the FK event.
  • LO - Change in earnings (positive and negative)
  • For employees enrolled into ALECTA department 1, the system reports LO event every month with the monthly actual gross salary(paid). In case when there is a Juper change (change in legal entity) due to change in organizational assignment / change of company within group for an employee, two LO events will be reported if the month is the same as the reporting period.

  • For employees registered with ALECTA Department 2, the following apply:

The system reports LO event whenever the annual salary is changed, the annual earnings for wage waiver are created in the current period, or the latter amount is changed as compared to the previous period. To determine whether such creation or change occurred, the system compares the value of the T5SPP-MRSAL field in previous periods to the value in the current payroll result.
If the annual earnings for wage waiver is changed so that it becomes equal to regular annual salary, that is, the amount of wage waiver is reduced to zero, an LO event is reported with the amount zero (in the wage waiver field). If, in subsequent periods the wage waiver remains zero, the LO event will be reported with no value.
If there are two or more salary records within the same month, the system reports the latest salary.
  • Even if the salary is changed in the middle of the month, the system reports it as if the change was valid from the first day of the month.

  • AV - Termination from Alecta
When you terminate an employee from ALECTA, the system reports the AV event with the termination date.

Note

  • You typically generate this report only once in a month, and after the normal payroll run.
  • For an employee hired after the payment date, the report will generate the employee ALECTA information in the next month.

Integration

Prerequisites

  • Customers newly entering into Alecta need to update a form in the system with information about all the wage types relevant to Alecta reporting. A model Form ALEC is available that you can copy and update with the wage type information. For more information, refer to the IMG under Payroll Sweden -> Pensions -> Alecta.
Note
Ensure that you do not include the wage types SPB0 to SPB5 in this form.
  • Customers who were previously reporting to Alecta using the SPP monthly insurance events report (RPLSPPS0) must note that along with ALECTA monthly insurance eventsreport (RPLSPPS2), Form ALEC is used.
Note
You must update Swedish org. structure - ALLtable view (V_T5S0P_ALL) with the following:
  • Current identification number to ALECTA under Pension

  • ALECTA Department 1 Pension Plan identifier

  • ALECTA Department 2 Pension Plan identifier

  • This report is valid for customers who were earlier reporting to Alecta using the SPP monthly insurance events report (RPLSPPS0), and for customers wishing to recreate Bonus and Compensation values for previous years from a legacy system.
  • You have processed the normal payroll run. Ensure that there are no master data changes between the periods when the payroll was run and the execution of the conversion report.
  • You must maintain the relevant Date types for Percentage of Absence, Reason for Leaving and Alternative pension solution at previous employer in Date Types view (V_T548Y).
  • You must maintain the date types in Sweden functionality based customizing entries feature (SFUNC). This feature must be maintained for Functionality Identifier ALEC and salaried/white-collar employees. Note that these date types should be same as the date types relevant to Alecta maintained in Date Types view (V_T548Y). The order of date types in the return value table is important.
  • 1st entry => 25% Absence

  • 2nd entry => 50% Absence

  • 3rd entry => 75% Absence

  • 4th entry => Long trm parental leave

  • 5th entry => Leave of absence

  • 6th entry => Retired with pension

  • 7th entry => Alternative pension solution at previous employer

  • You must maintain the Percentage of Absence, reported with the IN, FK, and LO events, in Date Specificationsinfotype (0041) with the date for date type before or in the reporting month.
The relevant Date types are:
  • SA (25% Absence)

  • SB (50% Absence)

  • SC (75% Absence)

If the absence percentage is not valid anymore, you must remove the entry of the respective date type from the Date Specific infotype (0041) record. Note that more than one Date type for Absence percentage should not be present at any given time. This would lead to incorrect reporting of Absence percentage.
Also, if you maintain Absence percentage for an employee, the employee is not fit for work. By default, any employee is fit for work.
  • You must maintain the Reason for Leaving which is reported with the AV event (on termination from ALECTA ) Date Specifications infotype (0041) with the date type same as the date of termination from ALECTA. The relevant Date types are:
  • SD (Long term parental leave (Valid only for employees enrolled in to ALECTA department 2))

  • SE (Leave of absence)

  • SF (Retired with pension)

If none of the above reasons are maintained in Date Specific infotype (0041) and Sweden functionality based customizing entries feature (SFUNC), the system defaults the Reason for Leaving to Termination of Employment.
  • You must maintain the relevant Date type in Date Specifications infotype (0041) with the same Date type date as the date of entry to ALECTA if the employee has had an Alternative pension solution at previous employer, which is reported with IN event for employees belonging to Alecta Department 2.
    The relevant Date type is SG (Alternative pension solution at previous employer).

Features

Selection

Standard Variants

Output

Activities

  1. Enter the relevant selection criteria.
  • Payroll Period - Specify the last executed payroll period. The conversion records then get the last date in the payroll period as reporting date.

  • ALECTA information from current system - You can generate the report based on factors such as Organizational number, ALECTA Benefit Plan type or according to what is customized in a customer specific feature.

  • To report the negative Change in Salary event, select Annual Salary Decrease.

Note
As per legal changes 01.10.2007, the existing benefit plan SPPP is used as ALECTA Department 2. Additionally, ALECTA Department 1 (ALE1) is created.
  1. Select the Divide Variable Payment by 3 checkbox if you want the system to divide the variable payments by 3 (years) regardless of the number of years of employment or number of years with variable payment.
  2. To generate the report in a test mode, select Test run. In this case, the report will not update the database table SPP information needed to be reported to Alecta (T5SPP).
  3. Enter an Address Key to identify the name of the company that must be printed in the header of the TemSe file. You can configure the same using the table view Addresses (T536A).

Example






BAL_S_LOG - Application Log: Log header data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 11449 Date: 20240520 Time: 130834     sap01-206 ( 165 ms )