Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE-PS (Application Component) Public Sector⤷
P01O_ZV (Package) SP Notification Program for Public Sector Germany
IMG Activity
| ID | OHADOE_ZVMP06_000 | SP Notification Program 2006 - General Information - |
| Transaction Code | S_L7D_24000066 | (empty) |
| Created on | 20051118 | |
| Customizing Attributes | OHADOE_ZVMP06_000 | SP Notification Program 2006 - General Information - |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHADOE_ZVMP06_000 |
Use
The notification procedure for the supplementary pension in the public sector with SP notification program 2006 triggers the notification procedure via PU11.
The following explains the set up of the SP notification program 2006 in the system. First, there is an overview of the technical and system-related aspects of the supplementary pension. It aims to clarify the relationship between these two aspects.
Technical view of supplementary pension:
- The supplementary pension in the public sector consists of a company pension scheme in the form of a pension fund within the context of the Company Pension Act/BetrAVG (together with the German Income Tax Act/EStG, German Pension Reform/AVmG, and German Pension Tax Law/AltEinkG).
- As an employer, you belong to the east or west pay scale area; different assessment thresholds with regard, for example, to pension insurance or the supplementary pension apply to these two areas.
- You are a member of one supplementary pension institute (SPI) only. If you have multiple supplementary pension institutes, you act as a different employer for each one. As a member of a supplementary pension institute, you have received a membership/account number from the institute in question.
- At your supplementary pension institute, there is at least one ring-fencing (for example, for VBL there are west and east ring-fencings and for the SPF of the KVBW there are the ring-fencings I and II); as an employer, you belong to one only. The ring-fencings differ in their financing (for example, pay-as-you-go financing, combination model, or capital cover) and in their different percentage rates for the pay-as-you go contribution rate or flat contribution rate or for reorganization pay.
- Your employees are compulsorily insured at your supplementary pension institute in accordance with the ATV/ATV-K (pension agreement). Following registration with the supplementary pension institute, your employees become insured persons and receive an insurance policy number from the SPI.
- As an employer, you are connected to a computer center that automatically sends notifications on insured persons (and perhaps on insured persons who are employees of other employers) to the supplementary pension institute in accordance with the DATÜV-ZVE (General Data Transfer Regulations for Supplementary Pension Institutes). The computer center requests a license to do this from the supplementary pension institute and, once the license has been received, obtains a license number from the institute.
Example:
The Town of Walldorf (west pay scale area) is registered with the SPF of the KVBW in ring-fencing II (capital cover procedure with 4% contributions from supplemental pension-liable remuneration). Its membership number is 4711. The notifications are processed by the regional Rhein-Neckar computer center, which also sends notifications on the SPF for the City of Heidelberg and which has been given the license number 0815 by the supplementary pension institute.
That explains the technical point of view. But what happens in the system?
- An employer is defined in the system as a personnel area or subarea. For the purposes of pension insurance, this area is assigned to the pay scale area east or west (T5D0P table).
- For each membership/account number of a supplementary pension institute, you create an "employer with a supplementary pension institute" (SP employer) in the system. The corresponding supplementary pension institute, account/membership number, computer center, assessment thresholds, and SPI ring-fencings are assigned to this SP employer.
- For each supplementary pension institute of which at least one of your SP employers is a member, one (and one only!) supplementary pension institute must be created as the GPR pension fund in the system.
- For each supplementary pension institute in the system, you set up at least one ring-fencing. You then assign the percentage values for the assessment/contribution calculation.
- For each license number that you hold with an SPI, you have to create a computer center that reports to the SPI in question.
- For your employees, you later create the ABS/SPI Data infotype (0051) in the production system to make your employees liable for supplemental insurance. An SP employer is assigned on the basis of the organizational assignment (infotype 0001, personnel area/subarea) and personnel area/subarea reporting (for example, as for ELSTER electronic employment tax notification). If this assignment is not correct, the SP employer can be specified directly in infotype 0051.
Example (continued):
The Town of Walldorf is divided into two personnel areas: The Town Hall (RATH) and the building yard (BAUH). Since all employers of the Town of Walldorf are insured with the same SPF, only one SP employer (membership number 4711) is set up. For the sake of simplicity, the personnel area RATH is still used, so all employees of the building yard (BAUH) are assigned to the personnel area RATH via personnel area/subarea reporting. Membership number 4711 and later the SPI "SPF of KVBW", the computer center "Rhein-Neckar", and ring-fencing II are assigned to the SP employer RATH.
Thus, in the GPR the SPF of the KVBW is created as the supplementary pension institute in investment type PF (Pension Fund). For this SPI, a ring-fencing (ring-fencing II) is set up with a reference to the percentage table. There, a contract model is defined with the corresponding contract elements, so that 4% of the supplemental pension-liable remuneration is calculated as the employer's contribution. In addition, the regional Rhein-Neckar computer center with license number 0815 is set up for the SPF.
Note: For system-based reasons, the sequence of setting up this data is not like that in the example; instead, it follows the sequence defined in the IMG.
Overview for customers replacing the PU11 notification procedure
For a schematic depiction of the dependencies of the individual Customizing objects of PU11 and SP notification program 2006, see the file attached to SAP Note 766654.
Before setting up the SP notification program 2006, you need to have understood the Customizing for PU11 and its extremely complex dependencies in order to be able to correctly change to the new system. Unfortunately, the automatic conversion of Customizing is not possible due to the fact that in some cases there are extremely different approaches between the two Customizing incidences.
Since the supplementary pension institute is set up in SP notification program 2006 as an investment institute of the GPR, you might be able to use an existing investment institute that you created a while back for PU11 Customizing. It is most sensible to use an investment institute that you set up for voluntary insurance.
Report names
Function Old name New name
Notification generation RPCZVMD0 RPCZVMD2
Notification display Function in PU11 RPLZVMD2
Data carrier generation RPCZVDD0 RPCZVDD2
Data carrier display/comparison RPUZVTD0 RPUZVCD2
Data carrier download RPUZVTD0 RPUZVTD2
Data carrier management Not available RPUZVDD2
Contribution statement RPCZVKD2 RPCZVBD2
Determination of amounts Not available RPCZVDTAD2
Transfer of amounts RPCZVDTAD0 RPCZVDTSD2
Infotype 0051 changeover Not required RPIZVAD2
Notification deletion RPHZVCD0, RPUP2D10 RPUZVAD2
Notification status change Not available RPUZVAD2
Customizing tables
Function Old name New name
Assignment of EMP -> SP-ER VAGKY characteristic T596L
SP employer T5D5B T5DPBSZVAG
Account number of SP-ER T5D5N, DZVEX characteristic T5DPBSZVAG
Computer center of SP-ER T5D5Z, DZV04 characteristic T5DPBSZVRZ
Address of sender T536A T5DPBSZVRZ
Payroll control T5D5C T5DPBSZVPY
Assessment thresholds T5D5C T5DPBSZVBG
Percentages/contract models T5D5C T5DPBSZVPZ
Assessment taxation T5D5H T5D5H
SPI data T5D5Z T5DPBSZVZVE
SPI ring-fencing series T5D5Z T5DPBSZVAV
Accounts for transfers T5D1H, T521B T521B
Notification record format (DATÜV-ZVE) T5D5D T5DPBSZVST
Registration/record types T5D5E T5DPBSZVMTSA
Notifications to be generated T5D5E T5DPBSZVME
T5DPBSZVTY
T5DPBSZVMTSA
Valid signing off reasons T5D5E, T535V T5DPBSZVAB
Assignment of wage type to T5D5G T596G, T596I,
remuneration notification T596J
Notification tables
Table Old (PCL2, SP cluster) New (transparent&
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHADOE_ZVMP06_000 | DE | Germany |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHADOE_ZVMP06_000 | 0 | HLA0003773 | Public Sector |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20051118 |
| SAP Release Created in |
