Hierarchy
EA-HRCGB (Software Component) Sub component EA-HRCGB of EA-HR⤷
PA-BN-FB-XX (Application Component) General Parts⤷
PAOC_BEN_FBN (Package) Flexible Benefits System
Basic Data
| Data Element | BEN_SPLAN |
| Short Description | Secondary Plan |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BEN_PLAN | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | T5UBA |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | SecondPlan |
| Medium | 14 | Secondary Plan |
| Long | 14 | Secondary Plan |
| Heading | 5 | SPlan |
Documentation
Definition
Specifies a plan as a secondary plan when defining plan relationships for the Provider Report for Flexible Benefits GB (RPUFBN71).
Use
This data element is applied in conjunction with the data element BEN_MPLAN which is used to specify a plan as a master plan when defining plan relationships for report RPUFBN71.
You must assign plan relationships in order to merge the output data from report RPUFBN71. You use the data elements BEN_MPLAN and BEN_SPLAN to acheive this objective.
Note:
You must assign plan relationships in a specific Customising step.
You specify plans as either master plan or secondary plans in the Benefits Administration IMG step: Define Benefit Plan Releationship for Provider Report (FLEX).
Dependencies
- Secondary plans must have the same plan category as the associated master plan.
- Secondary plans cannot be specified as a master plan and also as a secondary plan for another master plan at the same time.
- Family members only must be assigned to the secondary plan.
The employee himself/herself must not be included in a secondary plan.
- If you select multiple plans as secondary plans, you must ensure that there are different family members assigned to different plans.
One family member can only be included in one secondary plan.
Example
Your organisation has implemented two Flexible Benefits health plans:
- Additional Health Check Plan with the four-character identifier SHEA .
The health plan SHEA is for employees only.
- Additional Health Check Plan with the four-character identifier AHEA .
The health plan AHEA is for an employee's spouse only.
If you do not maintain the plan relationship between these two plans in this IMG step, the Provider Report RPUFBN71 outputs three records for each enrolled employee: two records for the employee and one record for his or her spouse. This is incorrect.
Therefore, in this IMG step, you assign plan SHEA as the master plan and AHEA as the secondary plan. After this customizing, the provider report RPUFBN71 reads your customizing settings made in table V_T74_FBN14 and merges the data for these two health plans.
The overall result is that only two records for one employee are produced by report RPUFBN71: one record for the employee and one for his or her spouse.
History
| Last changed by/on | SAP | 20040302 |
| SAP Release Created in | 200 |
