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 | OHADBAV720 | Permissibility of Actions in Pension Calculation |
| Transaction Code | S_AHR_61012576 | IMG Activity: OHADBAV720 |
| Created on | 19990223 | |
| Customizing Attributes | OHADBAV720 | Permissibility of Actions in Pension Calculation |
| Customizing Activity | OHADBAV720 | Permissibility of Actions in Pension Calculation |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHADBAV720 |
In this step, you specify which processes should follow one another in pension calculation (Report RPCWVSD0).
Here, the processing status you have defined for every processing type in the step Create Processing Types, is decisive. This processing status is saved for every run of report RPCWVSD0 in the CPS database.
At this point, you can determine how pension calculation should behave when certain processing statuses collide.
Example
You have performed pension calculation for an employee with the trigger date 12/31/1998 with the processing type Individual Pension. The processing type Individual Pension has processing status 1 (pension calculation). In the transparent table Status Information (P01CST) of the CPS database, this pension calculation run is saved with processing status 1 (pension calculation).
At a later date, you once again perform pension calculation for this employee with an identical trigger date, also with the processing type Individual Pension, processing status 1 (pension calculation).
In this example, a run with processing status 1 collides with a run that already exists simultaneously that already has processing status 1.
In the standard system, a model entry is defined for this case. In the case of two simultaneous processing statuses 1, the first run is reversed. The reversal is displayed.
Requirements
Standard settings
The standard system already contains model entries that usually cover all requirements.
Recommendation
Activities
- Check if the model entries provided by SAP are sufficient to meet your requirements.
- If necessary, modify the model entries or add new entries.
Further notes
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHADBAV720 | DE | Germany |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHADBAV720 | 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 |
| V_T5DW7 | V - View | SM30 | 0000000000 | Generated Table Maintenance: V_T5DW7 |
History
| Last changed by/on | SAP | 19990223 |
| SAP Release Created in |
