Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PY-DE-NT-NI (Application Component) Social Insurance⤷
P01S (Package) HR Germany: Social Insurance
IMG Activity
| ID | OHADSVB32 | Activate Use of AI Membership Key |
| Transaction Code | S_L7D_24002729 | (empty) |
| Created on | 20110421 | |
| Customizing Attributes | OHADSVB32 | Activate Use of AI Membership Key |
| Customizing Activity | OHADSVB32 | Activate Use of AI Membership Key |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHADSVB32 |
Use
The subapplication BGHV (Determine Maximum Annual Earned Income WCA from Membership Key) specifies the payroll year as of which the AI membership key is used to determine the AI data of the company.
Activating the subapplication BGHV has the following consequences:
- Inclusion of the maximum annual earned income for each membership key
The membership key is saved in the payroll result.
In contrast to the payroll without membership key, the maximum annual earned income limit is now taken into consideration in the full amount within a year for each membership key (combination of AI carrier and membership number). That is, if the membership key changes within a year, the maximum annual earned income limit with its annual value is taken into consideration for the AI carrier belonging to the new key. This can result in a WCA gross amount that exceeds the maximum annual earned income limit.
- Determination of responsible AI carrier for specified periods for the data module DBUV in the DEUEV notification
With the introduction of DSME version 02 in DEUEV notifications, you can now report multiple responsible AI carriers in the module DBUV (Accident Insurance).
However, when you create the DEUEV notifications using report RPCD3VD0, the old logic is still used. meaning that only the last valid AI carrier is reported for as long as the subapplication BGHV is not activated.
Only for notification periods in which the subapplication BGHV is activated are multiple AI carriers reported in module DBUV. This is to prevent the system from canceling DEUEV notifications that were already created.
Requirements
The subapplication BGHV can only be activated on January 1 of a year. Otherwise, the maximum annual earned income limits are incorrectly calculated in the payroll, as a new maximum annual earned income limit is set when a membership key occurs for the first time, irrespective of whether the WCA gross amount has already been calculated.
When the subapplication BGHV is activated, the company data for each membership key must be maintained as of this date (see section Maintain AI Data of Company) and the membership keys have to be assigned to the company (see section Assign Membership Key to Company).
Standard settings
In the standard system (example Customizing in view V_T596D), the subapplication BGHV is activated as of January 1, 2012.
Activities
Decide the payroll year as of which you want to activate the subapplication BGHV.
Recommendation: Apply the default setting (activation as of January 1, 2012) and maintain the company data for each membership key as of January 1, 2012.
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
| Customizing Attributes | Country Key | Country Name |
|---|---|---|
| OHADSVB32 | DE | Germany |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHADSVB32 | 0 | HLA0003753 | Social Insurance |
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_T596D | V - View | SM30 |
History
| Last changed by/on | SAP | 20110421 |
| SAP Release Created in |
