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 | OHADOEG02 | Legacy Data Transfer for SP Reporting |
| Transaction Code | S_L7D_24000001 | (empty) |
| Created on | 20060529 | |
| Customizing Attributes | OHADOEG02 | Legacy Data Transfer for SP Reporting |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHADOEG02 |
Use
Legacy data transfer for SP reporting
This section provides information on things to take into account for a system changeover with regard to SP notifications in the SAP system.
Only use the SP reporting activated with the sub-application ZVMP (see SAP Note 766654). Reporting via transaction PU11 is obsolete.
When changing the payroll system, we recommend that you inform the affected supplementary pension institutes.
As a general rule, a distinction is made between two changeover options:
- A deregistration is sent to the SPI on the day before the system change in the old system and a registration is sent on the productive start day in the SAP system.
- The SPI does not want to receive any notifications regarding a system changeover.
In both cases, the following applies with regard to the transfer of master data and the payroll results from the legacy system for times prior to production startup:
- Master data:
The ASB/SPI Data infotype (0051) must be created from the day of production startup in the SAP system. There is no infotype record prior to production startup.
- Payroll results:
If payroll results from the legacy system are to be transferred for times prior to production startup (partial annual totals in CRT, income threshold deficits etc.), no VBL table may be contained in the payroll results.
1. Deregistration in legacy system, registration in SAP system
This is the more simple scenario: In the legacy system, insurance periods are formed from the payroll results and are communicated to the SPI.
In the SAP system, registrations are communicated to the SPI for each insured person on the day of production startup. The annual notification insurance periods are generated in the SAP system the following year between the day of production startup and the end of the year.
This makes life a lot easier particularly if the production startup is in the middle of the year, since the annual notification for the year of production startup only needs to be generated for the part of the year since the production startup, and thus only with the payroll results from the SAP system. The part of the year prior to the production startup will already have been reported via the insurance periods communicated upon deregistration.
2. No notification to SPI at production startup
If your SPI does not want to receive a notification of deregistration from your legacy system or a notification of registration from the SAP system, extra efforts are required on the part of the employer. The employer must proceed as follows for each person who is compulsorily insured with an SPI on the date of the production startup:
- Define a date type for the technical date IDs 32 (actual start of SP insurance) and 36 (actual start of work relationship) in the Date Specifications infotype (0041).
- Select the "Do Not Transfer Notifications to SPI" indicator in the ASB/SPI Data infotype (0051) for the month of the production startup only. As a result, (at least) two infotype 0051 records exist for the personnel case: The first comprises the complete month of the production startup (first day of the month to last day of the month); the second exists from the first day of the month following the production startup month and ends on 31/12/999 unless you want to restrict it to an anticipated leaving date.
Exception: If the person concerned leaves during the month of production startup (whether on the last day of the month or on another day) or if the person concerned only joins the company during the month of the production startup, the field in question in infotype 0051 should not be selected.
The notification generation program (RPCZVMD2) is to be started in the month of production startup. Then, you use the status converter (RPUZVAD2) to change the status of all registrations of persons who leave during the month of production startup (from "New" to "Manual"). Do not change the status of deregistrations; otherwise, they will not be sent to the data carrier. Also, you must not change the status of persons who join the company during the month of production startup. Following the start of the data carrier generator (RPCZVDD2), only the deregistrations of persons leaving the company in the month of production startup and the registrations of persons joining the company in the month of production startup should be sent to the data carrier. With this procedure, name and address changes during the month of production startup are not communicated automatically. You have to report them manually.
If the month of production startup is January, you have to carry out the annual notification run for the previous year using the legacy system. If the month of production start is a month other than January (that is, during the year), you have to combine the payroll results from the legacy system with the payroll results from the SAP system for the annual notification in order to submit one annual notification only for each insured person. This cannot be supported by the SAP standard system. If production startup takes place during the course of the year, the first described scenario (deregistration in the legacy system and registration in the SAP system) is therefore the preferred option.
Business Attributes
| ASAP Roadmap ID | 254 | Transfer 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 |
|---|---|---|
| OHADOEG02 | DE | Germany |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHADOEG02 | 0 | HLA0003773 | Public Sector |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20060529 |
| SAP Release Created in |
