Benefits

Benefit Administration:
This section of the Implementation Guide (IMG) is where you set the SAP Benefits Administration component.
Here you enter in the system all the details of the benefit plans offered by your company.
Benefit Area:
Benefit areas allow you to have separate administration of different benefit plan pools. This division is primarily for administrational purposes and would not normally be used for eligibility
IMG Path: Personnel Management  Benefits  Basic Settings  Define Benefit Area
Assign Currency to Benefit Area:
In this step, you specify the currency for the benefit area
IMG Path: Personnel Management  Benefits  Basic Settings  Assign Currency
this step, you enter the providers of the benefit plans you offer.
This could be the Insurance company, or Health Maintenance Organization that receives the benefit plan costs
IMG Path: Personnel Management  Benefits  Basic Settings  Define Benefit Providers
In this step, you set relevant benefit area for your Customizing activities
If you have more than one benefit area to set up, you must set up each independently. After you have set up all the plans in one area, you must return to this view, set the next current benefit area and work through the IMG again, setting up the new benefit area.
IMG Path: Personnel Management  Benefits  Basic Settings  Set Current Benefit Area
Benefit Plan Types:
In this step, you enter the benefit plan types that you require for the plan categories predefined in the system.
The following plan categories are provided by MSD:
• Health Plans
o Medical
o Dental
o Vision
• Insurance Plans
o Basic Life
o Supplemental Life
o Accidental Death & Dismember
• Savings Plans
o 403B
o 457
o PERS (Public Employees retirement Scheme for CP Benefit Plan) & TRS
(Teachers Retirement Scheme for TP Benefit Plan)
• Flexible Spending Accounts
o Health care
o Dependent care
IMG Path: Personnel Management  Benefits  Basic Settings  Plan Attributes  Define Benefit Plan Types
Define Benefit Plan Status:
It is important that you assigning statuses in order to be able to control the availability of plans with a minimum of effort. For example, you can control whether or not employees can enroll in a plan simply by changing its status
IMG Path: Personnel Management  Benefits  Basic Settings  Plan Attributes  Define Benefit Plan Status
Benefit Plan Status:
In this step, you define parameter groups. You decide which groups you require in two stages:
1. You consider which costs, credits, coverage and employee and employer contributions for your plans vary according to the age, salary and/or seniority of employees (or possibly the age of the employee's spouse).
2. You determine the different ways in which you need to divide your employees according to different value ranges for these criteria.
It is not possible to define overlaps of ranges for a criterion within a single parameter group. Therefore, if you require different employee groupings for different plans, you need to create a separate parameter group.
For each unique combination of criteria and their values, you need to define a parameter group.
In this step, you simply create the parameter groups to which you assign groups for the individual criteria in the following steps. You later refer to the parameter groups, where applicable, in the individual rule variants for plans. Since one parameter group can be referenced by multiple plans, Customizing effort is kept to a minimum. In the plan variant, you also have the flexibility of being able to specify that you only want to use certain criteria values belonging to a parameter group, for example, age ranges
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Criteria Groups  Define Parameter Groups
Age Groups:
In this step, you define the age groups for the parameter groups that you defined in a previous step.
Depending on your needs, you may find for some parameter groups, you can leave out this step, if for example there is no requirement to differentiate between employees based on age
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Criteria Groups  Define Age Groups
Age Groups under Parameter grouping “PAR1”
Cost Groupings:
In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, job classification, marital status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying costs for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Cost Groupings
Coverage Groupings:
In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, employment contract, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying coverage for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Coverage Groupings
Employee Contribution Groupings:
In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Contribution Groupings
the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employer Contribution Groupings
the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Employer Contribution Groupings
the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Options for Health Plans
Dependent Coverage Options:
In this step, you define the dependent coverage that are used in health plans.
Define all possible variations that you need, because this view is not specific to any plan or plan option
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Dependent Coverage Options
Number of Dependents:
In this step, you can restrict participation in a health plan under a dependent coverage option to certain types of dependent, as determined by the subtypes of the Family/Related Persons infotype (0021). You can also define a minimum and maximum number of persons of a particular type that can be covered. During enrollment, the system only includes those dependent coverage options in the benefit offer for which the appropriate dependents are available
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Minimum and Maximum Number of Dependents
Define Cost Variants:
In this step you define cost variants to determine which factors influence the cost of a health plan for an employee. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual costs in this step. You simply define how costs vary according to:
• Plan
• Option
• Dependent coverage
• Employee data
Before you start to define cost variants, you need to do the following:
1. Determine how often costs vary for all the combinations of option and dependent coverage that you have defined in each plan.
This indicates how many cost variants you need. You can use the same cost variant more than once, for example, if costs are always identical for the dependent coverages 'employee only' and 'employee plus family' within a plan, regardless of the plan option
2. Determine how costs vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Variants
Cost Rules:
You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Rule
Health Plan Attributes:
In this step, you bring together all the definitions relevant to the health plan that you have made in the previous steps.
You assign to each health plan:
• Its options
• Relevant dependent coverages
• The cost variants for the combination of options and dependent coverages
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Assign Health Plan Attributes
Insurance Plans:
In this step, you define general data for insurance plans
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Insurance Plan General Data
Coverage Variants:
In this step, you define coverage variants to determined which factors influence the coverage an employee is entitled to in a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual coverage in this step. You simply define how coverage varies according to:
• Plan
• Coverage option
• Employee data
Before you start to define coverage variants, you need to do the following:
1. Determine how often coverage varies for different coverage options.
This indicates how many coverage variants you need. Note the following:
• If a plan has set coverages (including salary multiples), you need a
coverage variant for each.
• If a plan allows employees to choose any amount of coverage within a
range, you need only one coverage variant.
• If a plan has options, you will need a coverage variant for each option.
2. Determine how coverage varies according to employee data.
This determines how you need to set up your variants using employee groupings. For each variant, you can specify a parameter group and coverage grouping to determine coverage
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans 
Coverage Rules:
In this step, you define the actual coverages for a plan.
You need to define coverage for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
Coverage can be defined as a flat amount or as a factor of salary
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Coverage Rules
Cost Variants:
In this step you define cost variants to determine which factors influence the cost of an insurance plan for an employee. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual costs in this step. You simply define how costs vary according to:
• Plan
• Coverage option
• Employee data
Before you start to define cost variants, you need to do the following:
1. Determine how often cost varies for different coverage options:
• If an insurance plan has set flat coverage options and flat costs, you need
to define a cost variant for each flat cost.
• If you have set flat coverage options and the flat costs are directly
proportional to the coverage stated in the flat cost, you need only one
cost variant.
• If an employee can choose any amount of coverage within a range and the
cost of the coverage is directly proportional to the coverage, you need
only one cost variant.
2. Determine how costs vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Variants
Cost Rules:
You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Rules
Insurance Plan Attributes:
In this step, you bring together all those parts of an insurance plan, that you have already defined in the previous few steps.
You define the insurance plan options, then associate to each insurance plan:
• Cost variant
• Coverage variant
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Assign Insurance Plan Attributes
Combined Coverage Limits:
When you define coverages for plans such as insurance, you can set limits on the coverage amount. This is often used when the coverage is an amount dynamically calculated when the employee chooses her coverage.
However these limits apply only to one plan and yet you might need to define limits which combine the coverages of more than one plan.
In this chapter, you define these combined limits as follows:
1. The limit that might span 2 or more plans is reduced to a mathematical equation, where there is an amount on one side and plan coverages on the other side. The two sides of this equation are then DIVIDED BETWEEN the two views in this chapter.
2. The first view defines the limit in monetary terms which is one side of the equation. It also defines the operator (equals, is greater than, and so on).
3. The second view defines the other side of the equation in terms of the plan coverages
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Combined Coverage
Combined Coverage Limit Expressions:
In this step, you enter the second half of the equation, as discussed in combined coverage
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Define Combined Coverage Limit Expressions
Imputed Income for Selected Benefits:
In this section of the IMG, you define the criteria needed to calculate Imputed Income.
Imputed Income is based upon benefits paid for by the employer and calculated using rates set by the Internal Revenue Service (IRS). This value is then treated as taxable income for the employee
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Age Groups for Imputed Income
Review Calculation Factors for Imputed Income:
In this step, you check that the Imputed Income Rate Table entries are correct.
The imputed income age groups are associated with the rates/factors set by the IRS
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Calculation Factors for Imputed Income
Savings Plans:
In this step, you define general data for savings plans.
You have defined the relevant type, status, and provider for each plan in the Basic Settings section of the Benefits IMG
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Savings Plan General Data
Employee Contribution Variants:
In this step you define employee contribution variants to determine which factors influence the permitted employee contribution to a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual contributions in this step. You simply define how contributions vary according to:
• Plan
• Option (only for plans in the plan category Miscellaneous)
• Employee data
Before you start to define variants, you need to do the following:
1. Determine how often employee contributions vary for plans and any plan options.
This indicates how many contribution variants you need.
2. Determine how employee contributions vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and employee contribution grouping to determine employee contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Variants
Employee Contribution Rules:
In this step, you define the employee contribution limits for each plan.
You need to define employee contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
You can define minimum and maximum employee contribution in the following ways:
• As a fixed amount
• As a percentage of salary
• As a contribution unit
In Payroll, the total employee contribution is the sum of these amounts
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Rules
Employer Contribution Variants:
In this step you define employer contribution variants to determine which factors influence the contribution the employer makes to a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual contribution in this step. You only define how contributions vary according to:
• Plan
• Option (only for plans in the plan category Miscellaneous)
• Employee data
Before you start to define variants, you need to do the following:
1. Determine how often employee contributions vary for plans and any plan options.
This indicates how many contribution variants you need.
2. Determine how employee contributions vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and employer contribution grouping to determine employer contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Variants
Employer Contribution Rules:
In this step, you define limits for the contributions made by the employer to employee plans. You so this for each employer contribution variant for each plan.
You need to define employer contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
You can define the employer contribution and the contribution limit in either of the following ways:
• As a fixed amount / as an amount per unit contributed by the employee
• As a percentage of employee base salary or employee contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Rules
Assign Savings Plan Attributes:
In this step, you complete the definition of savings plans by bringing together the relevant elements that you have already defined:
• EE contribution variant
• ER contribution variant
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Assign Savings Plan Attributes
Flexible Spending Accounts (FSAs):
In this step, you define general data for flexible spending accounts (FSAs).
Requirements
You have created the appropriate plan type , plan status, and benefit provider in the preceding steps
IMG Path: Personnel Management  Benefits  Plans  Flexible Spending Accounts (FSAs)  Define Spending Account General Data
Assign Spending Account Attributes:
In this step, you enter the details of your flexible spending accounts including contribution limits, an employer contribution variant (if required), and rules for the reimbursement of claims
IMG Path: Personnel Management  Benefits  Plans  Flexible Spending Accounts (FSAs)  Assign Spending Account Attributes
Flexible Administration:
In this chapter, you define the flexible aspects of your Benefits administration. You define the availability of plans to your employees, in terms of the plans themselves. You also define aspects of the enrollment process.
you enter parameters that apply to processing within an entire benefits area, including:
• Open enrollment period dates
• Default validity dates for adjustment/standard plan records
• Advance availability of future plans
• Dependent age limits
IMG Path: Personnel Management  Benefits  Flexible Administration  Define Administrative Parameters
Benefit Adjustment Groupings:
In this step, you define adjustment groupings. These groupings allow you to specify different adjustment permissions for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Benefit Adjustment Groupings
Benefit Adjustment Reasons:
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
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Benefit Adjustment Reasons
Adjustment Permissions:
In this section, you assign adjustment permissions to each benefit plan type for an adjustment reason and any adjustment grouping that you have defined.
Note that the elements for which you can define permissions are automatically determined by the system, dependent on the plan category
Health Plans:
In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Health Plans
this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Insurance Plans
Savings Plans:
In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Savings Plans
Spending Accounts:
In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Spending Account
Programs:
In this section of the IMG, you define benefit programs and the eligibility restrictions and termination conditions for the plans within these programs.
Within a program, eligibility for plans can be determined on two levels:
• Program groupings control eligibility on a high level (macro-eligibility) by allocating an employee a defined program, depending on his/her organizational and employment data.
• Eligibility rules are optional and control eligibility on a low level (micro-eligibility) by determining whether an employee can participate in a plan within the relevant program. An employee must fulfill the conditions defined in the rule in order to be able to enroll. Eligibility rules are assigned to plans in programs by means of an eligibility variant.
First Program Grouping:
In this step, you define first program groupings. Later, you define programs for a combination of first and second program groupings.
Identical attributes are available for the setup of both the first and second program groupings, and they are therefore interchangeable. The fact that you determine macro-eligibility for a program using two dimensions means that you are able to make finer distinctions between groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define First Program Grouping
Second Program Grouping:
In this step, you define second program groupings. Later, you define programs for a combination of first and second program groupings.
Identical attributes are available for the setup of both the first and second program groupings, and they are therefore interchangeable. The fact that you determine macro-eligibility for a program using two dimensions means that you are able to make finer distinctions between groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define Second Program Grouping
Employee Eligibility:
In this section of the IMG, you define the criteria according to which you control eligibility for individual benefit plans within a benefits program (definition of micro-eligibility). You perform the following steps to set up eligiblity requirements:
• You define eligibility grouping to identify groups of employees for whom
certain eligibility criteria apply.
• You create eligibility variants, which you later use to link eligibility
rules to programs.
• If necessary, you define dynamic eligibility conditions relating
specifically to actual hours worked/length of service, or zip codes.
• You bring your definitions together in the eligibility rule, where you
can also specify further conditions for enrollment.
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Groupings
Eligibility Variants:
In this step, you define eligibility variants. These consist simply of an identifier and a description
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Variants
Eligibility Rules:
In this step, you define eligibility rules for the benefit plans offered by your organization. You define these rules for combinations of eligibility grouping and eligibility variant, thereby determining the eligibility conditions that will apply for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Rules
Participation Termination:
In this section of the implementation guide you define criteria for the termination of benefit plans
Termination Groupings:
In this section of the implementation guide you define criteria for the termination of benefit plans
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Groupings
Termination Variants:
In this step, you define termination variants. These consist simply of an identifier and a description
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Variants
Termination Rules:
In this step, you define termination rules. You define these rules for every combination of termination grouping and termination variant, thereby determining the coverage continuation periods and termination day that will apply for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Rules
Define Benefit Programs:
In this step, you define termination rules. You define these rules for every combination of termination grouping and termination variant, thereby determining the coverage continuation periods and termination day that will apply for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define Benefit Programs
Dependent/Beneficiary Eligibility:
In this step, you define family member groupings and determine how family members are allocated to these groupings
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Family Member Groupings
Dependent Eligibility Rule Variants:
In this step, you define the dependent eligibility variants to which you want to assign dependent eligibility rules. You also specify whether you wish to use a family member grouping in the associated eligibility rule to restrict eligibility to types of family members with certain characteristics
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Dependent Eligibility Rule Variants
Dependent Eligibility Rules:
In this step, you define dependent eligibility rules to determine which types of family member are eligible as dependents. You then assign your rules to the appropriate plans by means of a rule variant in the step Assign Eligibility Rule Variant to Plan
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Dependent Eligibility Rules
Beneficiary Eligibility Rule Variants:
In this step, you define the beneficiary eligibility variants to which you assign beneficiary eligibility rules in the next step. You also specify the following:
• Whether you want to use a family member grouping in the associated eligibility rule to restrict eligibility to types of family members with certain characteristics
• Whether the following apply for plans to which the variant is assigned:
 The employee can be a beneficiary
 Contingency beneficiaries can be named
 Spouse approval is required if beneficiaries other than the spouse are to be amed (the system only takes this setting into consideration for plans of the category avings)
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Beneficiary Eligibility Rule Variants
Beneficiary Eligibility Rules:
In this step, you define beneficiary eligibility rules to determine which types of family member are eligible as beneficiaries. You then assign your rules to the appropriate plans by means of a rule variant in the step Assign Eligibility Rule Variant to Plan
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Beneficiary Eligibility Rules
Assign Eligibility Rule Variant to Plan:
In this step, you assign dependent eligibility variants and beneficiary eligibility variants to plans, thereby assigning the eligibility rules associated with these variants
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Assign Eligibility Rule Variant to Plan
COBRA Plans:
In this step, you specify which health plans that you have already defined in the system are COBRA-relevant.
When a clerk collects COBRA-qualified beneficiaries, the system only considers employee enrollments in the plans you select here as legitimate cases where COBRA must be offered to the employee
IMG Path: Personnel Management  Benefits  COBRA  Choose COBRA Plans
this step, you determine for which flexible spending accounts (FSAs) you will offer continuation of coverage under COBRA. You need to do this for each benefit area separately
IMG Path: Personnel Management  Benefits  COBRA  Choose COBRA Spending Accounts
Qualifying Event Coverage Periods:
In this step, you define the events that qualify individuals for COBRA coverage, and the periods of permitted coverage continuation for each qualifying event type. COBRA legislation states the following regarding coverage continuation periods:
• In the case of Termination of employment and Reduction in working hours, only 18 months coverage must be provided. If qualified beneficiaries are determined to be disabled within 60 days of the COBRA event, they are entitled to a further 11 months of coverage, as are the other qualified beneficiaries who experienced the original event.
• For all other qualifying events except Bankruptcy of employer, a qualified beneficiary is entitled to 36 months continuation coverage, and there is no extension provision for disability.
• In the case of the event Bankruptcy of employer, the coverage continuation period is the life of the retired employee or retired employee's widow/widower. You therefore do not need to define a continuation period in this case.
IMG Path: Personnel Management  Benefits  COBRA  Define Qualifying Event Coverage Periods
Assign COBRA Events to Personnel Actions:
In this step, you define how the system recognizes COBRA-qualifying events from employee personnel actions (infotype 0000) records. You do this by creating a link between the two.
The only COBRA-qualifying event types that you assign to personnel actions are:
• Termination
• Death of employee
• Reduction in hours
You need to assign these COBRA-qualifying event types since they are based on customizable entries in your HR master data and therefore cannot be delivered as standard.
When the system collects COBRA-qualified beneficiaries, it considers employee records within the date range you specify in two stages as follows:
1. The system searches for employee personnel action (infotype 0000) records. The COBRA qualifying events assigned to any personnel actions found are collected.
2. The system checks other employee infotype records for specific information which corresponds to COBRA-qualifying event types
IMG Path: Personnel Management  Benefits  COBRA  Assign COBRA Events to Personnel Actions
Notification and Payment Intervals:
In this step, you define details of COBRA administration for those states where state law concerning COBRA differs from federal law.
Federal regulations are reflected in the state settings for the District of Columbia, which is also the system default.
If you must comply with state regulations that differ from the federal regulations, you should create a new state entry. Otherwise, you can use the DC version for all employees, regardless of which state they reside in
IMG Path: Personnel Management  Benefits  COBRA  Define Notification and Payment Intervals

Thanks alot
Best Regards

Similar Messages

  • Step by Step document on Guided Procedures for Benefits.......Help Needed..

    Hello Gurus,
    We are in process of implementing Benefits and for which we are using Guided Procedures, want to have understanding of the process can you please provide the step by step documentation and an example process that will be of great help.
    Appreciate your help.
    Thanks in advance for your time.
    Kind Regards,
    Pramod

    Hi Pramod,
    Please have a look at the below links. You will probably get some help.
    First of all, see the following thread, see the answer by shen peng in the end, explained CAF in very simple terms:
    https://www.sdn.sap.com/irj/sdn/thread?threadID=470956&tstart=0
    Now have a look at the following links for understanding about CAF, :
    <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4277f37b-0601-0010-0597-89e792177e2b">Creating Composite Applications with SAP CAF</a>
    <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84df3e36-0301-0010-be9d-b99aad8c81e6">Composite Application Framework in SAP NetWeaver</a>
    <a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1122">CAF training material online</a>
    <a href="https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1231">Additional CAF Training material online</a>
    See the following links for understanding CAF GP in detail:
    <a href="https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0b1c2eda-0c01-0010-b597-b107502cdc71">CAF Guided Procedures Overview</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/39/198141f906040de10000000a1550b0/frameset.htm">CAF Guided Procedures</a>
    <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/c7/984942da51690de10000000a155106/frameset.htm">Concepts of the Guided Procedures Framework</a>
    Lastly, see the following links for CAF GP Wiki Home Page and CAF Tutorial Center:
    <a href="https://wiki.sdn.sap.com/wiki/display/BPX/Guided+Procedures">CAF Guided Procedures Wiki Home Page</a>
    <a href="https://www.sdn.sap.com/irj/sdn/nw-composition?rid=/webcontent/uuid/d8dbd703-0801-0010-c9bf-c04bc52f562f">Composite Application Framework Tutorial Center</a>
    You can also have a look at the following thread, you can drill down into many more links:
    https://www.sdn.sap.com/irj/sdn/thread?threadID=405517&tstart=0
    https://www.sdn.sap.com/irj/sdn/thread?threadID=314804&tstart=50
    Bye
    Ankur

  • Benefits of SAP Business Warehouse Reporting compared with the Query-tools?

    Hello experts,
    I've been creating reports with SAP Query tools, but been faced with few problems. First of all, there are restricted possibilities in terms of joining tables, and thus I cannot include all the data required for the report.
    One solution for this would have been to create separate queries and join the data together in Excel. The problem with this is that there exists no common field that would make sense as for a selection criterion. If the selection criterion is different in different queries, there is the danger of combining false data together, which would eventually result with distorted data. 
    So I was wondering, could anyone briefly tell me if SAP Business Warehouse reporting would solve these problems? And what other benefits would it provide compared with the SAP Query? I'd urgently need to know if it would be a beneficial investment for the company, since I haven't found solutions for the problems occurred in the creation of reports.
    Thank you in advance for you help!
    Maria

    The answers are yes - and thousands of companies have gone down this route
    Puttingin BW is a strategic aim of the comapny and not to be thought about and discussed in a BI forum such as this
    The costs of implementation and hardware will no doubt make your eyes water.
    To be quite honest SAP BI is a "no brainer" as most of the new e-SOA and new R3 modules reply on BW for their reporting needs

  • UK Payroll (Year End HMRC Return - Taxable Benefits)

    Hi Payroll Experts,
    Please look in to below issue any ideas and solutions plz revert back to me ASAP.
    On the employees expenses and benefits form P11D, section F, which is cars and fuel is not calculating right.  It seems to be tided up with the amount paid by employee for private use of the car.  Some the figure does not appear and others it's taking off the lump sum payments from the lease car payments, which it should not.  Lump sum payment seems to calculating right under section E.
    Ex:
    The numbers are as follows
    1111    (xxxx)    Lease deduction of £490.83 not appearing in box  (amount paid by employee for private use)
    Therefore the cash equivalent of each car amount is wrong  it should read  £174.
    2222    (yyyy)   Lease deduction of £721.04 not appearing in box  (amount paid by employee for private use)
    It is showing  £438.04   It seams that the lease deduction has been reduced down by the lump sum payment.  (721.04-283.00  = 438.04)
    Therefore the cash equivalent of each car amount is wrong  it should read  £1288
    Thanks & Regards
    Githa
    Edited by: PGVani on Jun 13, 2009 11:34 AM
    Edited by: PGVani on Jun 13, 2009 11:58 AM

    HI Gita,
    Let us start from the beginning.
    1) Is Company Car Infotype maintained for the two employees? Company Car INfotype is 0442. It used to be 222 earlier. If you are using anything newer than 4.5 B, this is likely to be 0442 in your case?
    2) If yes, is the following field maintained - "Regular Payments". This field is found in the "Price and Benefit" tab of IT 0442.
    3) If the field is maintained, is this payment being processed in Payroll? If you are not the person who built this system, you must ask the person who did or refer to any documentation such as BUsiness Blueprint or Configuration Document to identify this wagtype. You can also simulate a payroll and look into the log to identify which wagetype is being used. A simple  way is to glance through the RT and find a wagetype with the exact amount entered in this field. You will need to confirm by running various tests by changing the value etc.
    4) If you find the wagetype, can you please check in table v_512w_d to see whether Cumulation Class 34 is flagged for this wagetype.
    All the above will help find out what is wrong, but to rectify it may be slightly difficult at this stage as you have very little time before the due date for submission of P11D. Depending on what you find, it may be necessary to run a payroll to fully rectify. Do you have time to run another payroll before July 19th?

  • UK flex Holidays/PTO paid benefits

    Has anyone done worked with sap Benefits on configuring where EE can sell and buy certain number of the days? requirement is An employee with 25 days holiday will be eligible now for 33 days holiday (25 + 8). they can buy up to a total of 40 days off or sell down to 32, but they have to take 32 days as holiday, and canu2019t take more than 40, total. They can either buy 8 or have 40 days off. OR they can sell 8 days but not lower than 32 days off. Payroll is in ADP and time management is in sap. We have quota types and absence type configuired for this benefit plan....any information onactual configuration will be valuable as I have already started the configuration....Thanks already

  • I have a rMBP that needs to be backed up.  The Wi-Fi in my house is poor and I do not have an Ex. Hard Drive.  I want to get the new Airport Time Capsule, but can you accomplish it's benefits wirelessly?

    So...
    I have a modem across the house and my room is at the opposite side.  I believe that you have to connect the Airport Time Capsule via modem cable in order for you to appreciate the benefits of the boosted up Wi-Fi.  However, I want the airport time capsule in my room, without having any extra cables plugged into it AND also benefit from the Wifi boosts, as well as back it up wirelessly.
    Is there any way to do this?  I was reading up on it and there are search queries bringing up "bridges" and all that stuff, but I haven't found a clear answer on it.
    So, to recap:
    I want the Airport Time Capsule to not only back up my rMPB and help my wifi signal out, but to do all of this with no additional cables having to be plugged in.
    Thanks.

    Trust me when I say this coming from 20 years of experience.
    Get a powered external drive, format it 1 Partition Option: GUID and OS X Extended Journed as the format in Disk Utility.
    Download and install Carbon Copy Cloner, clone internal drive to external drive.
    Set a schedule to remind you to do it at least once a week, keep it near your charger.
    When you plug your charger in, do plug the clone and power the machine up, set the display to sleep only,
    CCC will do the rest.
    If you want to boot from it, hold the option/alt and select it Startup Manager.
    I've seen many TimeMachine and TimeCapsule nightmares and so far haven't seen a problem from anyone using a bootable clone.
    It's simple, it's easy, it's more reliable and more powerful than what Apple does and it only takes plugging in a extra cable.
    Make as many clones as you want, keep them time seperated, off site etc. etc.
    Cables don't have network issues, clones can be verified in seconds merely by booting from them.
    Clones protect your productivity, your up in seconds on a clone despite even the hard drive dying.
    Software problem? No sweat, boot of the clone and reverse clone your problems away.
    If you want to fuss and muss with half implemented TimeMachine and TimeCapsule network headaches then prepare to suffer.
    I don't like to suffer, I bought a Mac not to suffer, but it appears you do with TimeMachine and TimeCapsule.
    Most commonly used backup methods

  • API to populate default benefits in OAB

    Hi All,
    We have configured OAB in a way that the benefits also include the Employer portion automatically when an employee is enrolled for a benefit. For example, if employee is enrolled for Medical Employee only benefit, the entry for Employer Match will also be added in the benefits. When I am doing it manually in the form, it works fine but when I use API to convert the benefits, it takes only I get in datafile and pass it to the API. Is there any way I can populate all default enrollments for an employee? Or I need to derive the default benefits based on what is entered and need to run API against it?
    Appreciate your reply.
    Thanks,
    CAH

    Hi Gaurav,
    Thanks for your reply.
    No we did not create a plan for employer contribution. It is an option in the same plan which will be added to the benefits when Employee election is entered. For example, for Employee Medical, the plan name is "Standard Plan" and option is "Employee Only" or "Employee + 1" or "Employee + 2 or more". When any of these option is added, a respective options for Employer Match will be added to employee benefits. The employer Match options are "Employer EE only", "Employer EE + 1" and "Employer EE + 2 or more". And it works the same way for other Medical, Dental and Vision plans.
    How do we program Default Enrollment Process(Which API and parameters should be used)?
    Hope this makes things more clear. Please let me know if you want more clarification on a particular matter.
    Thanks,
    CAH

  • Benefits of using SAP CAR compared to SAP BW on HANA

    Hi
    I' like to understand the benefits of using SAP Customer Activity Repository. How is it better than SAP BW on HANA? What extra functions does the customer get?

    Hi Waldemar (wow, I remember E.A.Poe...)
    take a look to this document...
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ad0a4b07-0301-0010-5095-ef7615676fc0
    Hope it helps !
    Bye,
    Roberto

  • Confirmation of Benefits letter as SMARTFORM

    Hi All,
         I have created a smartform for the confirmation of benefits form letter and would like to use this instead of the standard SAPScript(TCODE = HRBEN0015). Is there a way to redirect it to the smartform?
    Please advise.
    Kind Regards,
    Daniel A. La Mendola

    Daniel,
    Yes, you can go to IMG -> Personnel Management ->Benefits -> Flexible Administration -> Form Set up ->Assign Templates to Form Types. There you`ll find place for Adobe form as above mentioned by Ted.
    Here is the link for Adobe form configuration:  https://wiki.sdn.sap.com/wiki/display/ABAP/SAPInteractiveForms-PDF-BasedPrintForms#SAPInteractiveForms-PDF-BasedPrintForms-Whatarethestepstogenerateaform%3F
    Regards,
    David

  • Function Modules for Benefits Upload

    Hi,
        I am working on ECC 6.0 with HR 6.00
        My requirement is to Create/Maintain
    1) Benefits Savings Plan information (IT0169)
    2) Family members/Dependents for this savings plan (IT0021)
       Please let me know if there are any HR-BAPI function modules or HR function modules to achieve this.
       Also can you please send me detailed information on the parameters for these function modules.
    Thanks and Regards,
    Aditya

    Hi Kum,
               I just checked HR_BEN_CREATE_SAVINGS_PLAN. This will definitely create a savings plan.
               I need a function module to edit the savings plan also (preferably standard function module). Do let me know if one exists
    Thanks and Regards,
    Aditya

  • I want to buy an Apple TV device but I need to be sure of its benefits. I have contracted a Satellite TV. Is it true that if I connect Apple TV to system, I can watch TV through IPad wherever by using wireless and App Remote

    I want to buy an Apple TV device but I need to be sure of its benefits. I have contracted a Satellite TV. Is it true that if I connect Apple TV to system, I can watch TV in my IPad wherever by using wireless and App Remote??

    If you have an iPad 2 you can wirelessly mirror it to your TV via the ATV device. If you have an iPad 1 then you can use airplay but not all apps are enabled to push video, as the developer needs to do this.
    You can also view all local content from iTunes or your iPad, pushed via airplay/home-sharing.
    The other services available are iTunes movie rentals, TV shows (past purchases viewable from the cloud), Photo Stream, Netflix, Vimeo, Podcasts, Youtube, Sports etc.
    More info
    http://www.apple.com/appletv/

  • Business case or Business benefits of BW Upgrade from 3.5 to 7.0

    Hi All,
    Could you please let me know or point me to any brochure that explains  the business case or business benefits of Upgrading BW 3.5 to 7.0 ?
    I am able to find lot of docs/info explaining the technical benefits and advantages with upgrading BW 3.5 to 7.0, and all the new features in BI 7.0.
    But what I am specifically looking for is, Sales proposal type info, Business Case of Upgrading from BW 3.5 to 7.0.
    Thanks
    KPK

    Hi,
    Go through this SAP Note : 928729
    -Vijay

  • Error while Terminating the Benefits Participation

    Hi Frieds,
    Our system is behaving veri differently. While terminating the Benefits participation we get an error "Organizational Assignment infotype does not exist for 07/01/2011".
    While in Qulaity server this is succesfuly processed. All the master data is same both in QAS & PRD.
    The long text for the same is given below.
    Please provide the solution if any one came across such issue.
    "Organizational Assignment infotype does not exist for 07/01/2011".
    Message no. PG259
    Diagnosis
    A record of infotype 0001 Organizational Assignment does not exist on 07/01/2011 for this personnel number.
    System Response
    The system response depends on the infotype and is determined by the No org. assignment field in infotype table T582A.
    The system displays either a warning or an error.
    Procedure
    Check that your entry is correct and meaningful, and then continue
    Regards
    Moosa

    Hi Moosa,
    This error message seems to indicate that the employee does not have an IT0001 record valid at the time of the benefit termination. Please make sure that IT0001 has not been delimited for this employee. You should always have a valid IT0001 record as it has time constraint 1.
    Best regards
    Sarah

  • What are the benefits of Apple TV as compared to streaming video via a MacBook Pro?

    What are the benefits of Apple TV as compared to streaming video via a MacBook Pro?

    Sorry, I don't quite understand your question. Amongst other things that's exactly what the Apple TV does, is streaming video from a computer.

  • What are the benefits of buying an iPad 2 with wi-fi, or with 3G when I already have an iPhone 4 with 3G?  My plan with was to go for wi-fi and connect to the internet through my iPhone 4.  Am I missing out on anything by not getting 3G?

    What are the benefits of buying an iPad 2 with wi-fi, or with 3G when I already have an iPhone 4 with 3G?  My plan with was to go for wi-fi and connect to the internet through my iPhone 4.  Am I missing out on anything by not getting 3G?

    James9901 wrote:
    I tried the tethering and hated it. The connection breaks every time I get > 25 feet from it and it's a pain to reestablish the connection. I suppose if I had to choose between breaking connections every now and then or paying another $100 + $25/month I'd do the tethering.
    Or just carrying the phone in your pocket? Just saying.....

Maybe you are looking for