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

Similar Messages

  • FlexBens:Open Enrollment/Print form- No correct adjustment reason specified

    Hi Experts,
    Need help on Flexible benefits of UK.
    I have done all the necessary configuration, but somehow im facing the "No correct adjustment reason specified" on the ESS pages of FlexBens:Open Enrollment & FlexBens:Print Form Screen. However, im able to view Participation screen.
    Also, i have maintained 171 and 378 aswell. but still this error comes. I have used Tcode HRFBN0001 for enroll ment from R/3. Its working fine here. Also I looked in functional module HR_BEN_ESS_RFC_ENRO_REASONS. Data is shown properly.
    I doubt if this is an authorization issue. If anyone of you know what should be the portal Role to access Flexible Benefits ok UK. or if you think the reason is something else, the please share with me your thoughts.
    Regards,
    Pranitha

    Hello Bhargava,
    Please assign/ Configure General Benefits Information (Infotype 0171) for PERNER.
    Go thru this link it will help you
    [http://help.sap.com/erp2005_ehp_03/helpdata/EN/7e/8a62e6545711d1891c0000e8322f96/content.htm]
    Thankyou,
    Regards
    Vijai

  • No Correct Adjustment Reason Specified

    We are running EP7.0 and ESS/MSS on the latest patch sets.
    We are attempting to get Open Enrollment working through ESS. When opening the Benefits and Payment Area, no enrollment options are available. When I attempt to run the web dynpro on its own, it displays the error "No Correct Adjustment Reason Specified'
    Anyone have any tips or points to check to get 'Enrollment' working properly in ESS.
    Thanks,
    -Tim

    Go to the Resource: EMPLOYEE_GENERICENROLLMENT_SERVICE05
    In "URL OF PCD, make sure this is entered:
    ROLES://portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.area_benefits_payment/com.sap.pct.erp.ess.enrollment
    This points the Resource to the iView "Enrollment."

  • ESS Benefit Enrollment - No correct adjustment reasons specified

    We are in ECC 60. When testing ESS benefit open enrollment (under Content Admin - Portal Content - Content Provided by SAP - End user content - ESS - Iviews - Benefit and Payment - then either test on 'Enrollment' or 'Flex Bens Enrollment)', we keep getting error 'No Correct adjustment reasons specified' .
    I already configured 'Benefit Area Admin Paramenter' to have open enrollment period to be active for month of April (for testing), and also assigned proper role in 'URL of PCD Page' for resource key 'EMPLOYEE_GENERICENROLLMENT_SERVICE05', and yet still get the error message. Searching SDN for this issue, I see that some people also had similar issues before, but there doesn't seem to be a concrete / clear solution. Appreciate if someone can shed some light on what I'm still mising .
    Thanks.

    Hi Ted,
    Not sure if this would help.
    You can try the below thread..... It also has reference to an OSS Note.
    [Adjustment Reason;
    Good Luck !!!
    Kumarpal Jain.

  • Open Enrollment error for US - No correct adjustment reason specified

    Hi,
    We are getting this error "Open Enrollment error for US - No correct adjustment reason specified". Please help if you know the resolution to this.
    Regards,
    Anand Jalan

    I have found the solution for this.
    Maintain the Open enrollment period dates in IMG->Personnel administartion -> Benefits ->Flexible administration->Define Administrative Parameters

  • NO CORRECT ADJUSTMENT REASONS.

    Hello All,
    When we access the Benifits enrollment under ESS we are getting a message that "No Correct Adjustment Reason Specified". The ITS version of this IView is working fine, but for the WebDynpro I am getting the above message. Can somebody guide me what tasks I need to perform to get this working.
    Thanks a lot in advance for your response!
    Chakri.

    Did you check with SAP via OSS? could be WebDynpro related as can be seen from this <a href="https://forums.sdn.sap.com/click.jspa?searchID=762563&messageID=2912240">Thread</a>.
    ~Suresh

  • No adjustment Reason for Flexbens Enrolment-UK in portal

    Dear all,
    I am getting the "No correct adjustment reason specified" error for the "FlexBens: Open Enrollment" link on the Portal.
    I specified  enrollment reasons (infotype 378) for the employee assigned to the portal user
    I am working for UK Benefits in R/3 it is working fine and all the adjustment reasons/Events are coming but in EP under Flex bens Enrollment I am getting the above error.
    here I want to enrol the plans against the adjustment reasons.
    So pl. suggest me what I can do and is there any config settings require for this it is very urgent.
    Hong: can you pl. helpme out.
    Regards,
    Sushma

    Hi Barin,
    Pl find the detailed error through Portal for the same.
    <b>No correct adjustment reason specified</b>
    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.fbn.enrollmentreasons.VcFlexBensEnrollmentReasons.isConsistent(VcFlexBensEnrollmentReasons.java:206)
         at com.sap.xss.hr.fbn.enrollmentreasons.wdp.InternalVcFlexBensEnrollmentReasons.isConsistent(InternalVcFlexBensEnrollmentReasons.java:174)
         at com.sap.xss.hr.fbn.enrollmentreasons.VcFlexBensEnrollmentReasonsInterface.isConsistent(VcFlexBensEnrollmentReasonsInterface.java:183)
         at com.sap.xss.hr.fbn.enrollmentreasons.wdp.InternalVcFlexBensEnrollmentReasonsInterface.isConsistent(InternalVcFlexBensEnrollmentReasonsInterface.java:152)
         at com.sap.xss.hr.fbn.enrollmentreasons.wdp.InternalVcFlexBensEnrollmentReasonsInterface$External.isConsistent(InternalVcFlexBensEnrollmentReasonsInterface.java:228)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:507)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
         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:754)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
         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:1244)
         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(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
         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.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:215)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

  • 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 &#61664; Benefits &#61664; Basic Settings &#61664; Define Benefit Area
    Assign Currency to Benefit Area:
    In this step, you specify the currency for the benefit area
    IMG Path: Personnel Management &#61664; Benefits &#61664; Basic Settings &#61664; 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 &#61664; Benefits &#61664; Basic Settings &#61664; 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 &#61664; Benefits &#61664; Basic Settings &#61664; 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 &#61664; Benefits &#61664; Basic Settings &#61664; Plan Attributes &#61664; 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 &#61664; Benefits &#61664; Basic Settings &#61664; Plan Attributes &#61664; 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 &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; Define Employee Criteria Groups &#61664; 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 &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; Define Employee Criteria Groups &#61664; 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 &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; 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 &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; 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 &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; 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 &#61664; Benefits &#61664; Basic Settings &#61664; Define Employee Groupings &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Health Plans &#61664; Assign Health Plan Attributes
    Insurance Plans:
    In this step, you define general data for insurance plans
    IMG Path: Personnel Management &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664;
    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 &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Combined Coverage &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Combined Coverage &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Combined Coverage &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Insurance Plans &#61664; Combined Coverage &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Savings Plans &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Flexible Spending Accounts (FSAs) &#61664; 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 &#61664; Benefits &#61664; Plans &#61664; Flexible Spending Accounts (FSAs) &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; Define Adjustment Permissions &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; Define Adjustment Permissions &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; Define Adjustment Permissions &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Benefits Adjustment Reasons &#61664; Define Adjustment Permissions &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Employee Eligibility &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Employee Eligibility &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Employee Eligibility &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Participation Termination &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Participation Termination &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; Participation Termination &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Programs &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; 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:
    &#61607; The employee can be a beneficiary
    &#61607; Contingency beneficiaries can be named
    &#61607; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; 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 &#61664; Benefits &#61664; Flexible Administration &#61664; Dependent/Beneficiary Eligibility &#61664; 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 &#61664; Benefits &#61664; COBRA &#61664; 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 &#61664; Benefits &#61664; COBRA &#61664; 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 &#61664; Benefits &#61664; COBRA &#61664; 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 &#61664; Benefits &#61664; COBRA &#61664; 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 &#61664; Benefits &#61664; COBRA &#61664; 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

  • Adjustment Reason based Enrollment Issue

    My Open Enrollment ESS piece is working fine. The issue is with the Adjustment reason based ones.
    Basically our Open Enrollment service is enabled via regular Open Enrollment object in Benefits Adminsitration under Personnel Management ( and this works fine when I use the OPEN_ENROLLMENT service since it picks up the OPEN event).
    We also have another plan which is given to employees via 378 and so is based on an Adjustment Reason.
    When I try to enable the EMPLOYEE_GENERICENROLLMENT_SERVICE service, I get the first page which lists all the available plans for my user. But when I try to click on a particular plan, it takes me to a blank page.
    I have set the PCD URL for the Resource to the corresponding page and that is why I think the first page shows up - this is all good but I can't get to the actual enrollment from there. Any ideas?
    Thanks,
    BR

    Now, I am confused....
    You say that you are pointing your resource for OE to the area page of Benefits - and it is working fine.
    I cannot verify it since I am on ECC 6.0 and using all the services ending in 05.
    This is what I see in my system:
    EMPLOYEE_OPENENROLLMENT_SERVICE
    ROLES://portal_content/com.sap.pct/every_user/com.sap.pct.ess.employee/com.sap.pct.ess.roles/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.area_benefits_payment/com.sap.pct.ess.serv_benefits_payment
    EMPLOYEE_GENERICENROLLMENT_SERVICE
    ROLES://portal_content/com.sap.pct/every_user/com.sap.pct.ess.employee/com.sap.pct.ess.roles/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.area_benefits_payment/com.sap.pct.ess.serv_benefits_payment
    EMPLOYEE_BENEFITPAY_PAG
    ROLES://portal_content/com.sap.pct/every_user/com.sap.pct.ess.employee/com.sap.pct.ess.roles/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.employee_self_service/com.sap.pct.ess.area_benefits_payment/com.sap.pct.ess.area_benefits_payment
    The first two resources above are pointing to a Service page. (Page you see as "Enrollment" in the standard role)
    The third one points to the Area Page (Page you see as "Benefits and Payment" in the standard role)
    You should be using the PCD path of the Service page in your resources for OPEN enrollment and Generic Enrollment
    Anyway, to just quickly test your new Generic Enrollment service, you can edit the existing resource for OE and enter the URL parameter and see if it works...
    Try these things and let me know how it goes ...
    - Shanti

  • Enrollment Form Not Visible for Adjustment Reasons

    Hi Experts,
                      I am having an issue with the Benefits enrollment not being displayed in the ESS portals. We are using an adjustment reason based open enrollment . The link is visible if give the event name as BENP_EVENT = OPEN which points to the form with standard open enrollment form listing all plans but we want to use 'OPN' (custom reason) instead of 'OPEN'. If i change the event to BEN_EVENT= OPN, it is displaying the link but not unable to read the employee and throwing an error saying, "infotype IT0171 doesnot exist for 00000'. Listed below is my configuration.Your help is much appreciated.
    Adjustment Reason:
    Form Setup:
    Launchpad Link:
    Launchpad Config:
    Ess Page:
    Thanks,
    Vishnu

    Hi Shankar,
                       Thanks!! for the reply. The application is in active mode only. The system is only taking the event name(BENP_EVENT = OPEN). I have to create another adjustment reason with 'OPEN' name just for form purpose and keeping my 'OPN' as is for my enrollment purpose. The problem is with 'OPEN' it lists out all the plans , even the ones that we don't want to show.
    Thanks,
    Vishnu

  • Reporting Location in SAP HCM

    Hi SAP Experts,
    We have a requirement to track Reporting location of an employee in Org Management. Kindly advice if there is an option to extract Reporting location for an employee. Does SAP has such field?. What could be the reason for not having Reporting Location in SAP?
    Your response is highly appreciable.
    Regards,
    Phani Prakash
    SAP HCM Business Analyst.

    This question should be answered by the customer in your project. You cannot expect people on this forum to guess your customers requirements.
    People have given some hints based on their best estimates of what a Reporting Location could be.
    I would recommend, asking a precise definition of the requirement from your client, and then identifying the relevant SAP fields that holds that information, and going from there.

  • Overview SAP HCM country based infotypes

    Dear all,
    I am in search of an overview of all Sap HCM infotypes. Per infotype I need to know whether it is an infotype common to all countries (such as: 000,0001,0002,0003,0006,0007,0008,0009,0014,0015) or a country specific infotype (U.S. Benefits Payroll IT(0496 - 0501)).
    Is there anybody willing to share information or (ofcourse preferably) share such a list?
    Thanks in advance!
    Maarten
    (vandermeijde at hotmail.com)

    Hi Marteen,
    Info types like 0000,0001,0002,0003,0004,0005,0006,007,0008,0009,0010.......
    all infotypes are commonly used for all countries, but only thing is some countries was not require some infotypes. maintaining of info types entirely depends on Client requirement.
    For example:
    Infotype 0021 is maintained only the client want to enter details of the employee's family otherwise we don't maintain it.
    Thanks & Regards
    Sandeep

  • Configuration Guide for HCM BENEFITS

    Hi,
    Could anybody point me to Configuration guide for HCM Benefits for SAP BI or BW ? whats the documents title/number containing necessary HCM Benefit analysis configuration ?
    Thanks in advance

    Hi Raj,
    Try this link:
    http://help.sap.com/bp_hcmv1600/BBLibrary/Documentation/N06_BB_ConfigGuide_EN_US.doc
    Cheers,
    Tanish

  • SAP HCM Support Function reg

    Hi All
    I have 4 Years of Experience in SAP HCM End user support and I also got a job offer for SAP HCM Support from one of the big company.
    If I continue my career in SAP Support what will be my future career, whether is there any big career opportunities available in future for Support function.
    Please suggest your views
    Thanks

    I agree with Colleen,
    There is a general perception among many that Support project work is degrading, boring, monotonous, non-challenging, lack-of-learning-opportunities etc.
    Those who say this, have actually no real work experience or are ignorant of world they live in. A support project is as important as an Implementation or a Roll-out project. Most Implementation and Roll-out projects are a 100m dash to the finish line. No one is bothered whether you flew or limped to the finish-line - as long as you completed the run within a decent timeline. The real challenge of Support project is in fixing a hurriedly set-up system without taking into consideration future performance or sustainability. These points have been discussed many times(even recently).
    Even if the above reasons don't excite here's one more. All Implementation/roll-out projects are short term and you'll end up searching for projects within months of beginning one, whereas Support projects are long-term and hence give you more stability and reassurance of steady revenue.
    pk
    PS: And this comes from a person who's worked in Implementation/Rollout/Upgrade projects for 70% of his total SAP project experience.

  • Change BEGDA when enrolling in adjustment reason plans from ESS/HRBEN0001

    Hi Experts, ,
    Please provide your inputs/let me know if any BADI or User Exit exists, for acheiving following requirtement in ESS -
    Following a life event change or at the time of hire, eligible employees log on to ESS to adjust available benefits plans. The requiremnet is to change the effective dates (E.g. if enrolling in health plan - P0167-BEGDA) of the plans during enrollment. The idea is to have a custom table created which would hold Adjustment reason, Benefit plan and effective date calculation rule (1st day of next month, last day of month etc.. ) and derive effective date from this Ztable when employee enrolls in any plan from ESS/HRBEN001.
    Any inputs on acheiving this requirement would be of great help.

    Thanks for taking ur time and relplying to this question...
    I have seen the class and the function module being called in this class .. BEGDA is an importing parameter and hence any change done to it will not be captured .. and moreover I guess this will not trigger from HRBEN0001 ..
    any comments ?

Maybe you are looking for