Hierarchy
⤷ PY-DE-PS (Application Component) Public Sector
⤷ P01O_ZV (Package) SP Notification Program for Public Sector Germany
IMG Activity
ID | OHADOE_ZVMP06_065 | SPI: Define Validity of Deregistration Reasons |
Transaction Code | S_L7D_24000074 | (empty) |
Created on | 20051118 | |
Customizing Attributes | OHADOE_ZVMP06_01 | SP Notification Program 2006 (Mandatory/Critical) |
Customizing Activity | OHADOE_ZVMP06_065 | SPI: Define Validity of Deregistration Reasons |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHADOE_ZVMP06_065 |
Use
You use this IMG activity to define the validity of deregistration reasons for each supplementary pension institute (SPI).
Standard settings
Deregistration reasons must be correctly set up at least from January 1st 2002, since the SP notification program 2006 must be able to generate notifications from this date.
Activities
To define the validity of deregistration reasons for each SPI, proceed as follows after calling up the IMG activity:
- Select an entry in the Set Up Supplementary Pension Institute table.
- Double-click Define Validity of Deregistration Reasons in the dialog structure and call the table for the selected SPI.
- Maintain the table in accordance with your requirements.
Note:
To enable the determination of the correct deregistration reason for certain events that require a deregistration followed by a registration on the next day, you have to define an SAP-specific ID for this deregistration reason in the final column (see example). - Choose Save.
Example
In the case of the VBL, if you change from ring-fencing east to ring-fencing west (or vice versa), you have to use deregistration reason 28 (Temporary End Due to Change of Ring-Fencing) in the first column. To enable the 28 to be recognized by the program, you have to enter 28 for East-West Change in the last column (SAP Deregistration Category).
Note:
If you have constellations where the automatic determination of the deregistration reason is incorrect, you can override the deregistration reason using HRPBSDE_ZV_ABMGR (BAdI for Changing Deregistration Reason). The BAdI used in the old notification program - HR_ZVK_MELDUNG_001 - could not be used because its interface is incompatible with the new program. If you have an implementation for the old BAdI for the period from January 1st 2002 to present, you also require an implementation for the SP notification program 2006. Otherwise, no implementation is required for the time being.
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | I | Valid for countries specified |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
VC_T5DPBSZVZVE | C - View cluster | SM34 |
History
Last changed by/on | SAP | 20051118 |
SAP Release Created in |