Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PA-PF-DE (Application Component) Company Pension Scheme Germany⤷
P01A (Package) HR Germany: Retirement Pension Plan
IMG Activity
| ID | OHADBAV310A | Define Entitlements |
| Transaction Code | S_AHR_61012589 | IMG Activity: OHADBAV310A |
| Created on | 19990223 | |
| Customizing Attributes | OHADBAV310A | Define Entitlements |
| Customizing Activity | OHADBAV310A | Define Entitlements |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHADBAV310A |
In this step, you define all the entitlements you require for your pension plans.
Definition of Entitlements
In the Entitlements CPS detailed screen, you create the entitlement and define the following rules:
Calculation Procedure
Every claim is assigned a calculation procedure. In the case of income-orientated calculation procedures, the fields Income Identifier and Fictitious Income are also displayed. Income that forms the basis for the valuation of a claim, is regularly transferred to the CPS database and stored under the identifier specified here.
Reaction When Several Claims Collide:
When maintaining the master data, you first of all assign an employee to a pension plan in the Entitlement Group Type BAV infotype (0323). From the pension plan, there are possible entitlements that can be approved for the employee in the Entitlements CPS infotype (0202).
If you do not want an employee to be assigned two entitlements at the same time, you can use the collision check:
- Using the Collision Class field, you assign each entitlement to a collision class (01 - 20).
- In the Reaction on Collision input list, you control the system's behaviour when pension plan entitlements are simultaneously created in the Entitlements CPS infotype (0202):
W: A warning is displayed
E: An error is displayed
A: The entitlement that already exists is delimited when the new entitlement is created.
Example:
Instead of the entitlement Z500 (Retirement Pension), all employees get the entitlement Z600 (New Retirement Pension). An employee can not be assigned both entitlements at the same time. That means that when creating entitlement Z600 in the Entitlements CPS infotype (0202), a record that already exists with entitlement Z500 should be delimited. Both entitlements have collision class 1.
In this case, you maintain the input list Reaction to Collision for entitlement Z600. In position one (position 1 = collision class 1), you enter a D for delimit.
If entitlement Z600 is created in the Entitlements CPS infotype (0202) and entitlement Z500 already exists, then the data record with entitlement Z500 is delimited to the key date.
Screen Group Infotype
Using the Screen Group Infotype field, you determine which additional fields are available when maintaining the Entitlements CPS infotype (0202) for each entitlement.
Control Differing Start Date:
The employee´s entry date according to the Actions (0000) and Organizational Assignment (0001) infotypes is the entry date for the CPS (Company Pension Scheme). You can override this entry date for each entitlement, with either a date type from the Date Specifications (0041) or Contract Elements (0016) infotypes. This date type must be maintained accordingly for the employee.
Status of Entitlements
In the Entitlements CPS (0202) infotype, an entitlement status can be specified for everyentitlement. In the Entitlement Status detailed screen, you decide which statuses are permitted for an entitlement in the Entitlements CPS (0202) infotype.
Depending on the status, the entitlement is dealt with in different ways when calculating the pension (Report RPCWVSD0).
Rules for Entitlements
In the Rules for Entitlements screen, you decide how a pension benefit is paid.
In the case of a monthly pension (for example, retirement pension), payment is made using the Basic Pension Payments CPS (0201) infotype, under the wage type that you specify in the field Pension Benefit Wage Type.
In the Pension Type field, you specify the subtype of the Basic Pension Payments CPS infotype, under which the pension is grouped.
In the case of a capital payment, payment is made via the Additional Payments (0015) infotype, under the wage type that you specify in the field Wage Type Capital Payment.
You can also determine a Payment type.
Example
Requirements
Standard settings
Recommendation
Activities
- Decide which entitlements exist in your company (beyond all pension plans and institutions).
- Decide which calculation procedure (contribution-related, employment period to income, and so on) should be used to calculate each individual entitlement.
- Decide which entitlements an employee can have at the same time, which entitlements delimit one another and which entitlements exclude one another. Assign your entitlements to the collision classes accordingly and define the desired reaction in the case of collision.
- Decide which entitlements you require a different entry date for.
- Check the permitted statuses for your entitlements.
- Decide, under which wage types the pensions resulting from the entitlements should be stored in the Basic Pension Payments CPS (0201) or in the Additional Payments (0015) infotypes.
Further notes
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 |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHADBAV310A | DE | Germany |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHADBAV310A | 0 | HLA0100987 | Company Pension Scheme Germany |
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_T5DCA | C - View cluster | SM34 | 0000000000 | Primary Entitlements |
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
