SAP HR Benefits

Hi all ,
I need the documents on SAP HR-Benefits.
Regards
santosh .

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
heck this one and let me know if there is anything else even arun has also given nice response so if u have any query pls revert back
6

Similar Messages

  • How Benefits is maintained where SAP HR Benefits not implemented?

    Hello folks,
    Just wondering how Benefits / Benefits config is maintained where SAP HR Benefits is not implemented. How this works out in SAP and out side SAP i.e. outsourcing etc.. Please explain.
    Thanks a ton..
    JEss..

    If your client has decided to outsource Benefits admin to a third party, you will most probably have to :
    1. Send employee status files with the data stored in PA. Ex Active, Termed, DOB, Dependents etc..... The spec for this will be provided by the 3rd party.
    2. Open Enrollment will be handled via online or mail.
    3. All queries regarding benefits will be handled by the 3rd party unless it is a master data issue.
    Depending on the size of the org, you may want to promote using SAP for benefits as it had many advantages.
    thanks,
    Tariq Khan

  • SAP HCM Benefits: No correct adjustment reason specified

    Dear All,
    We are implementing Benefits through portal.I do have error whicle enrolling a pernr even though entires are maintained in IT0171 & ITo378.
    The corresponding FM "hr_ben_ess_rfc_enro_reasons" is called and executed without having any entries under the internal table "ERROR_TABLE". After the FM is executed, the portal dump is displayed which is shown below.
    Kindly help me trace from where we get this error message.
    "No correct adjustment reason specified"   
      No correct adjustment reason specified:com.sap.pcuigp.xssfpm.java.FPMRuntimeException: No correct adjustment reason specified
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)
         at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasons.isConsistent(VcBenefitsEnrollmentReasons.java:218)
         at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasons.isConsistent(InternalVcBenefitsEnrollmentReasons.java:190)
         at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasonsInterface.isConsistent(VcBenefitsEnrollmentReasonsInterface.java:173)
         at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasonsInterface.isConsistent(InternalVcBenefitsEnrollmentReasonsInterface.java:152)
         at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasonsInterface$External.isConsistent(InternalVcBenefitsEnrollmentReasonsInterface.java:228)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:508)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener  
    Thanks in Advance
    Nazia

    Dear Nazia,
    This error looks like configuration mapping of iViews. Please check with the portal team, whether the correct iView is configured for the country specific setting. In general, for any particular pernr if the error comes, Please check whether the particular pernr as any Unicode issue (like junk character).
    Thanks,
    Ganesh R K

  • SAP HR Benefits and Payroll Integration

    Hi All,
            This is the first time i am posting in HR, i am new to HR Benefits, i need to configure the Benefits and Payroll Integration in my client. I don't know how to do that one, if any body have configuration steps or any article please share with me.
    It  really great help.
    Thanks in Advance.
    Thanks and Regards,
    Abhi.

    Hi,
    Under SPRO -> Payroll -> Country Payroll -> Benefits, are the options u must configure.
    Be sure to create wage types copying the standard ones.
    In this case is better that you copy wage types from the standard option
    In table V_T512Z, select infotype 0167 to see permitted wage types, your new wage type must be in this group.
    Value of the wage type will be automatically taken from the benefits cost configuration.
    You must assign a wage type for a plan.
    Hope this helps,
    Daniel

  • How to make pre-requisite plans as mandatory in SAP Hr Benefits sub-module?

    I have a request to make all the pre-requisite plans (health plans, insurance plans, savings plans, etc) as mandatory in system in benefits module.
    Can anybody guide me how to do that?

    I have to configure the following scenario.
    There are 2 health plans into the system like
    a) BCBS with plan options: Basic & Special
    b) Mediservice with plan options: Basic & Supplementary.
    currently both the plans with all the corresponding plan options are available for hourly employees.
    Changes in configuration required isthat: Hourly employees are eligible only for BCBS-Basic plan and Mediservice-Basic plan.
    How do I make these changes in the system?
    Kindly help
    Thanks

  • Outsourcing of Benefits to 3rd Party

    Hello... we are currently using the SAP HR Benefits module, but will soon be outsourcing our HR Benefits administration to a 3rd party.    The 3rd party will be sending us the benefits deductions via an interface, so that we may incorporate them into our SAP Payroll run.   My question is the following:   is it better to store the benefits deductions on infotype 14, or does it make sense to continue to configure SAP HR Benefits and store the deductions on the benefits infotypes utilizing the 'alternative cost' field?    Opinions welcome...thanks.

    Hello Linda,
    Since the third party will be sending you the benefits deductions via an interface, it would seem logical to me to transfer them directly into IT0015, every pay or every month(according to your needs).
    As for the configuration of Benefits in SAP, you could keep it in place and comment out functions P0167 and P0168 in your schema.  If you want to be able to generate reports on enrollments, it would be preferable if the information could be maintained in SAP (perhaps an other interface).
    Sorry for the late answer but I just noticed your thread.
    And for SapUser1204, you should identify your needs (requirements) before trying to define the interface parameters.
    When you have identified these needs, please open your own thread.

  • SAP Benefits_Claims

    Hi Experts,
    This is regarding SAP Claim Benefits related to Asia region.
    1) My query is we enter and process claims and after that see and check the entitlement and claim details in the EASY ACCESS. I actually want to know I'm processing claim for 01/01/2007 - 31/12/2007, hence it is showing me details about the entitlements and claim detials for the year 2007. Now when I'm in 2008, the plan beginning year would be 2008 then, then if i want to see the details about the past year (say 2007 for example), how can i see that.
    2) If I'm adding some addtional texts while entering the claims, how can i see that in any report. Currently I can only see that in the Claim entry screen
    3)  How can I delete (if at all i should) for the past years Claim entries which are showing up in the entry screen.
    4) What are the concerned reports which can be generated from standard SAP related to Claims.
    Thanks & regards,
    Sumali.

    Hi sarika
    Thanks for the tips. I found that the cause is in one of the config steps. It's under PM>BN>Plans>Claims>define Claim Variant for Plan.
    There are two tabs in this step: One for "Claim rule criterion", another for "Claim limit parameter".
    The message is caused as I do not put any option under Miscellaneous Details/Overclaim (Tab "Claim limit parameter". )
    However, since this is a warning message, I can proceed by just ignoring it. Is there any way that I can skip the message? It's kinda irritating for client every time they access the function.
    Many thanks.
    Rgds
    Chia

  • Java to SAP career prospects

    Hi Experts,
    I need small suggestion from you all regarding my Career . I  am a programmer in Java having around 6 years of experience. I want to step into SAP for better career prospects and survival in volatile market condition. Will it be worthwhile to learn any SAP module and will there be any better prospects because of that. I worked on Java, JSP, EJB, Struts.. etc, in financial domain. Which module in SAP should I get into. I have also come to know about Enterprise Portal. Would it be better to learn EP or to switch to some module in SAP and what would be the career prospects if I learn some SAP module.
    I would also like to know what would be the career prospects for Java Professionals ?
    Would learning of some SAP module benefits me ?
    Thanks in advance. Waiting for your valuable suggestions.
    Regards,
    Vishnu Priya

    Hi Vishnu Priya ,
    I wonder u asking this question who is holding 258 posts and 22 points as well & well versed in dialog programming???
    Regards
    sas
    Ps: Already abap 6.0 flooded with oops concepts and u gyes from java making abapers life more complicated:-) Best of luck ...If u post in CC u will recieve like this answers...u can see suggestions category...

  • SAP Script: Printing the signature on main window at the end

    Hi,
    I am working on a SAP Script (Benefits enrollment form HR_BEN_ENRO).  I copied the HR_BEN_ENRO into ZHR_BEN_ENRO and making the necessary changes without modifying the driver program.
    The problem I am facing is as follows:
    In the main window there are so many Text elements.  At the end of the main window, after the last text element, I have put some text using Include statement.  The last text element is getting triggered for some employees and hence the text underneeth that is printing, but for some employees the last element is not triggering and hence nothing is printing underneeth that.
    Is there any solution to print the this text at the end of main window after printing all the remaining information.
    I also tried using BOTTOM & ENDBOTTOM. But in this case I don't know how to check that I am in last page of the main window.  I tried the following way:
    /: BOTTOM
    /: IF &PAGE& = SAPSCRIPT-FORMPAGES&
    SIGNATURE:__________   Date:__________
    /: ENDIF
    /: ENDBOTTOM
    In this case the value I am getting for &SAPSCRIPT-FORMPAGES& is 0 (zero).
    Any solution..please.
    Appreciate.

    How to link the ZHR_BEN_ENROL instead of HR_BEN_ENRO?
    I mean when I execute the TCODE: HRBEN0001 and select particular employee and click on Print form under Offer Selection area. Then standard program calls HR_BEN_ENRO. How to replace it with Zform?
    Thanks in advance.
    Regards,
    Krishna

  • Cbih82 "Accident details" - How to make older entries not editable

    Hello Experts,
    Is there a way in CBIH82 to set the "Accident details" long text field (under involved tab) in order that older entries cannot be modified?
    What I'd like would be like in maintenance notifications. No Changes to Existing Long Text.
    When someone add characters to the long text field, system automatically add a log line (a timestamp containing user + date + hour) before text and make the text unchangeable by anyone after saving. However, the long text can be supplemented, the older entries would be greyed out.
    Is there a key in IMG or any other way to make the system behave that way? I want to prevent people erasing previous text enterred in that field.
    Thanks,
    Francois

    Hi Francois,
    This seems to be a genuine requirement, and even more when it can be seen available in the case of maintainance notifications. But, unfortunately this functionality is not available for "Accident details" long text.
    The most you may do as an alternative is to utilize "Documents" functionality. The documents uploaded in this tab has inherent SAP DMS benefits, whereby you can track changes made to a particular DIR (administrative details). You may also make the documents password-protected for unintended access, However, you can not make older entries grayed out obviously.
    Regards,
    Pavan

  • Any body have below mentioned document will u send it to me

    HR050 SAP HR Human Resources Essentials
    HR051 SAP HR Human Resources Essentials 1
    HR052 SAP HR Human Resources Essentials 2
    HR053 SAP HR Human Resources Essentials 3
    HR100 SAP HR Essentials of Human Resources
    HR110 SAP HR Essentials of Payroll
    HR120 SAP HR Essentials of Personnel Development
    HR130 SAP HR Essentials of SAP Enterprise Portal in HCM
    HR250 SAP HR Employee Self-Service
    HR260 SAP HR Manager Self Services in HCM
    HR270 SAP HR SAP Learning Solution Overview
    HR290 SAP HR System Configuration for ESS/MSS
    HR305 SAP HR Configuration of Master Data
    HR306 SAP HR Configuration of Time Recording
    HR307 SAP HR Configuration of HR System
    HR308 SAP HR Time Managers Workplace
    HR310 SAP HR Time Evaluation With Clock Times
    HR311 SAP HR Time Evaluation Without Clock Times
    HR315 SAP HR Recruitment
    HR316 SAP HR E-Recruiting
    HR325 SAP HR Benefits Administration
    HR350 SAP HR Programming in HR
    HR390 SAP HR Introduction to Payroll
    HR400 SAP HR Payroll Configuration
    HR490 SAP HR Incentive Wages
    HR505 SAP HR Organizational Management
    HR506 SAP HR Advanced Organizational Management
    HR510 SAP HR Personnel Development
    HR515 SAP HR Training and Event Management
    HR520 SAP HR Shift Planning
    HR530 SAP HR Technical Topics in HR
    HR540 SAP HR Compensation Management
    HR550 SAP HR Personnel Cost Planning and Simulation
    HR580 SAP HR Reporting in Human Resources
    HR940 SAP HR Authorizations in HR
    HR990 SAP HR Technical Tips and Tricks in HCM

    Hi Vinay,
    Check the link it would be helpful.
    http://www.easymarketplace.de/online-pdfs.php
    Br/Manas

  • Talent Management Enhancement pack 4  Business Function HCM_TCM_CI-1

    This business function contains some new job architecture functionality that we would like to utilize.  These new object types are functional name (FN) and job family (JF).  We do not plan to configure any of the talent management functionality because we will not be using it at this time.  Activating this business function also activates a functionality called Embedded Search which requires TREX 7.1.  We do not plan to do any of the configuration for the embedded search functionality either at this time as we don't think we will need it.
    My question is, is anyone aware of any issues that might arise  or what other SAP functionality that might be impacted by moving this business function into our Production environment without doing any of the configuration.  We have implemented SAP Payroll, Benefits, Org management, Personnel Administration, eRecruiting and Learning.
    Thanks in advance for any advise you can provide.

    Hi Kathy:
    In a nutshell, you shouldn't run into any issue.  You're just going to get a host of new web dynpro apps, OM data, and infotypes for the Central Person (the 74XX infotypes).  If you don't use them, then that's fine, it won't hurt anything.
    You should be just fine using the HRP1001 450 relationships from JF to FN and C to help drive your job architecture.  You would potentially need to use transaction HRTMC_PPOM to manage your job family/functional area relationships, but you won't negatively impact anything you have already implemented.
    If you're not going to use any of the Talent Mgmt functionality, you also don't need to worry about enterprise search or TREX.  I'm assuming you aren't using Succession Planning in eRecruiting, right?  If you do ever consider using the Talent Management functionality you've now implemented, you will have to migrate data over from the old eRecruiting version of Succession Planning.  Other than that, you should be good to go.
    Hope that helps!
    Thanks,
    Chris

  • Messages logged in Claims Processing

    Hi guys
    I am implementing HR Benefits module. After completing all the settings in IMG, i enrolled a personnel through SAP Menu "Benefits>Enrollment" (Tx code: HRBEN0001). This is OK.
    I then proceed to SAP Menu "Benefits>Claims (Asia)>Enrollment" (Tx code: HRCLM0020). to enroll the option. This is OK too.
    Lastly I proceed to approval via SAP Menu "Benefits>Claims (Asia)>Approval" (Tx code: HRCLM0002). After the record is added (status "To be accounted"), I hit warning message as below:
    Text for domain fixed value  of domain CLM_OVRCL does not exist
    Message no. HRBEN00FMODULES138
    Can anyone help me on this?

    Hi sarika
    Thanks for the tips. I found that the cause is in one of the config steps. It's under PM>BN>Plans>Claims>define Claim Variant for Plan.
    There are two tabs in this step: One for "Claim rule criterion", another for "Claim limit parameter".
    The message is caused as I do not put any option under Miscellaneous Details/Overclaim (Tab "Claim limit parameter". )
    However, since this is a warning message, I can proceed by just ignoring it. Is there any way that I can skip the message? It's kinda irritating for client every time they access the function.
    Many thanks.
    Rgds
    Chia

  • How does the production system take the benefit from user-exits.

    How does the production system take the benefit from user-exits.

    and it is not the production system that benefits. its the company and the people working with SAP that benefits from the user exits which allow SAP to be altered for the company specific situations.

  • How does the PRODUCTION SYSTEM take the benifit from the USER EXITS?

    how does the PRODUCTION SYSTEM take the benifit from the USER EXITS?
    please explain

    and it is not the production system that benefits. its the company and the people working with SAP that benefits from the user exits which allow SAP to be altered for the company specific situations.

Maybe you are looking for

  • I am syncing my ipod but it comes up with a error saying itunes could not backup the ipod because the backup was corrupt or not compatible with the ipod, what do i do?

    i am syncing my ipod but it comes up with a error saying itunes could not backup the ipod because the backup was corrupt or not compatible with the ipod, what do i do?

  • Ipod nano 6G error 9006

    After several months I found my Ipod Nano again. In the meanwhile, I switched from Android to Iphone 5s and got quite common with ITunes. ITunes does find the Ipod, but states, that he is in "maintenance mode" and needs to be restored by ITunes - don

  • Dynamic field in select query

    Hi Team, I have to select dynamic fields from database table GLT0. This depends on period value given on screen. If period is 01 then fields will be hsl01. If period is 02 then fields will be hsl01 and hsl02. If period is 03 then fields will be hsl01

  • Web.xml + jsp deployment problem

    Hi people, I have an eclipse project that has 1 servlet and 1 jsp page. I'm having problem in deployment. The servlet works fine but jsp is not accessible. The structure of my web.xml file is as follows: <?xml version="1.0" encoding="UTF-8"?> <web-ap

  • Feedback: Elements Panel + div hirarchy

    Hello, selecting multiple divs (Strg or Shift+Left Mouse Button) within the Elements Panel would be a great enhancement in workflow. When building a responsive grid as a base for e.g. Drupal with divs having height auto and no content, it's difficult