Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PA-BN (Application Component) Benefits⤷
PBEC (Package) Benefits - Customizing
IMG Activity
| ID | OHBEN0313 | Define Benefit Adjustment Reasons |
| Transaction Code | S_AHR_61002170 | IMG-Aktivität: OHBEN0313 |
| Created on | 19981221 | |
| Customizing Attributes | BEN_00_AD_1_1_E0103 | Administration - mandatory - critical - all countries but JP |
| Customizing Activity | BEN_00_T74HA | View V_T74HA |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OHBEN0313 |
In this step, you define adjustment reasons to control changes to employee enrollments according to company policy.
The adjustment reason types that you define here are assigned as subtypes of Adjustment Reasons records (infotype 0378) in HR Master Data. Since a record can only have one subtype, a new record must be created for every adjustment reason an employee experiences.
According to the adjustment concept, an employee can only make changes to her enrollments if she has an Adjustment Reasons record (infotype 0378) with the required adjustment reason as a subtype. The only exceptions to this are if changes are made during an open enrollment period or if an anytime adjustment reason is assigned to the plan type.
In addition to defining adjustment reasons for certain events that can trigger changes, you may also want to define a special adjustment reason to allow changes to plans at any time.
Example
An employee adopts a child and wants to include the child in her health plan coverage. The following adjustment reason is defined:
CHLD - New child
The employee is allowed to include the child in all health plans as a dependent, but must do so within 3 months of the adoption.
Requirements
Standard settings
Recommendation
- To ensure that the Adjustment Reasons infotype is created for any relevant changes, SAP recommends that, wherever possible, you include the Adjustment Reasons infotype in appropriate personnel actions in Personnel Administration. To do this, you should consider which of your personnel actions permits an adjustment to benefits, and assign the infotype to the associated info groups.
If the personnel action experienced by an employee would also mean her benefit area, first and second program grouping values need to be created or will change, the General Benefits Information record (infotype 0171) must also be included in the relevant personnel action and created before the Adjustment Reasons record.
If you do not have a corresponsing personnel action for an adjustment reason, you must ensure that the Adjustment Reasons infotype and any other relevant infotypes, for example, Family/Related Person (infotype 0021), are created manually as required.
For more information on personnel actions, see the section Actions in the Customize Procedures section of the Personnel Administration IMG.
- SAP advises that you monitor the validity dates that you define here on a regular basis to ensure that they remain valid for your processing purposes.
Activities
- Decide which adjustment reasons are required by your organization.
- Choose New entries.
- Enter a four-character identifier and description for each adjustment reason.
- Define the timeframe for changes to enrollments.
- In the field Total time allowed for adjustments, you can enter the time within which changes must be made. In the field Time allowd for adjust. after initial choice you can then enter a shorter time period during which changes are allowed after an employee has communicated her initial choice.
- Select Changes anytime if you want to allow changes to enrollments at any time, regardless of whether or not an employee has an Adjustment Reason record (infotype 0378) for the adjustment reason in question. If you define an adjustment reason as "anytime", you therefore do not need to define any time restrictions.
- Enter the validity dates for benefit plan records created by adjustment processing.
- If you transfer plan data to a provider by means of an IDoc, enter the American Standard code to denote the adjustment reason.
- Save your entries.
- Choose Next entry and repeat steps 2 to 7 for each adjustment reason.
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 |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | OHBEN0313 | 0 | HLA0006759 | Administration |
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_T74HA | V - View | HRBEN0041 |
History
| Last changed by/on | SAP | 20000117 |
| SAP Release Created in |
