Hierarchy
⤷ PA-BN-FB-XX (Application Component) General Parts
⤷ PAOC_BEN_FBN (Package) Flexible Benefits System
IMG Activity
ID | OHFBNFA02 | Define Corequisite Insurance Plans Consistency (FLEX) |
Transaction Code | S_PLN_62000237 | (empty) |
Created on | 20040301 | |
Customizing Attributes | OHFBNFA02 | Define Corequisite Insurance Plans Consistency (FLEX) |
Customizing Activity | OHFBNFA02 | Define Corequisite Insurance Plans Consistency (FLEX) |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | OHFBNFA02 |
Define Corequisite Insurance Plans Consistency (FLEX)
Use
In this step you:
- Define the master-slave relationship between two insurance plans, where the cost calculation is different in each of the plans.
- Determine whether the Provider Report For Flexible Benefits (RPUFBN71) will merge the cost of two plans together or generate a separate cost for each plan.
Requirements
- The two insurance plans you are defining must have same configuration except for their respective cost rules. This is because the Flexible Benefits system must control two benefits plan enrolled with the same benefits plan options.
- Only a strict one-to-one relationship between master and secondary plan options are is permitted in the system. Therefore, it is not permissable:
- For a master plan to have multiple secondary plans
- For one secondary plan to be linked in a relationship to more than one master plan
- No recursive relationships are permitted between master and secondary plans. For example, Plan B cannot be the secondary plan of Plan A and also be the master plan for Plan A at the same time.
See also documentation for the IMG step Define Benefits Plan Relationship for Provider Report (FLEX).
Standard settings
This IMG step relates only to GB FlexBens Insurance Plans. You customize here to allow for the situation where an employee wishes to enrol an insurance plan that covers him/herself and any spouse or partner, but where the cost calculation and policy coverage upper limit is different between employee and his/her spouse or partner.
In this situation, you must set up two separate insurance plans. In this IMG step, you define the relationship between these two insurance plans and determine how report RPUFBN71 handles cost reporting.
Activities
For each of your insurance plans with differing cost calculations and policy coverage for employee and partner/spouse, you must:
- Configure two insurance plans, one as a master plan and another as a secondary plan.
- Set the allowable plan options level for the secondary plan.
- Maintain the indicator Secondary Plan Exist.
During Flexible Benefits enrolment , when an employee enrols a master insurance plan, the system checks whether the secondary insurance plan assigned to this master plan must also be enroled at the same time.
If you set the Secondary Plan Exist indicator, the assigned secondary insurance plan must also be enroled.
If you do not set the Secondary Plan Exist indicator, it is not mandatory that the assigned secondary insurance be enroled.
- Maintain the indicator Merge Cost .
If you set this indicator, the costs of the master and secondary insurance plans will be merged together when you run the Provider Report For Flexible Benefits (RPUFBN71). If you do not set this indicator, the costs of the two plans will be processed separately by report RPUFBN71.
- Save your entries.
Example
You implement a GB FlexBens Critical Illness Insurance Plan for your employees, with an upper coverage limit for the employee of GBP 500,000 and GBP 50,000 for the partner respectively. You calculate the cost of the plan as follows:
Cost = Coverage level selected by employee x provider factor/1000
Example 1A: Female Employee with Annual Salary of GBP 25,000
Employee is aged 36 - Factor used by provider to calculate cost of plan is 2.25
Partner is male, aged 38 - Factor used by provider to calculate cost of plan is 1.87
The employee chooses Critical Illness cover of 2x salary for herself and her partner (GBP 50,000). The cost of this selection is therefore calculated as follows:
Cost for employee: 50,000 x 2.25 / 1000 = 112.50
Cost for partner: 50,000 x 1.87/ 1000 = 93.50
Total cost of plan to employee = 206.00
Example 1B: Female Employee with Annual Salary of GBP 25,000
Employee chooses Critical Illness cover of 4x salary for herself and her partner (GBP 100,000). The cost of this selection is therefore calculated as follows:
Cost for employee: 100,000 x 2.25 / 1000 = 225.00
Cost for partner: 50,000 x 1.87/ 1000 = 93.50 (GBP 50,000 coverage limit for partner applies)
Total cost of plan to employee = 318.50
Example 2: Male Employee with Annual Salary of GBP 30,000
Employee is aged 28 - Factor used by provider to calculate cost of plan is 0.78
Partner is female, aged 33 - Factor used by provider to calculate cost of plan is 1.75
The employee chooses Critical Illness cover of 3x salary for himself and his partner (GBP 90,000). The cost of this selection is therefore calculated as follows:
Cost for employee: 90,000 x 0.78 / 1000 = 70.20
Cost for partner: 50,000 x 1.75/ 1000 = 87.50 (GBP 50,000 coverage limit for partner applies)
Total cost of plan to employee = 157.70
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | I | Valid for countries specified |
Customizing Attributes | Country Key | Country Name |
---|---|---|
OHFBNFA02 | GB | United Kingdom |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | OHFBNFA02 | 0 | PLN0000014 | Great Britain |
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_T74_FBN15 | V - View | SM30 |
History
Last changed by/on | SAP | 20040301 |
SAP Release Created in |