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

Similar Messages

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

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

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.

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."

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

SAP Open Enrollment Error : Age group could not be determined

Hi Gurus,
We have been trying to configure Open Enrollment and when I try to go in the backend using HRBEN0001, it lists all the eligible plans and lets you complete the Open enrolllment, however in the Error List one error pops up saying "Age Group Cannot be determined". I have a spouse listed in the system, but his birthday has been entered so it should be able to calculate the age group without any issues.
When we login to the portal and try to click on the Open Enrollment tab, no plans show up but only the error "Age Group cannot be determined" shows up.
We have configured three variants for Voluntary Life and Spouse Life for the age groups 1-69, 70-74 and 75+. Could this be the reason of the error?
Has anyone encountered this error before? and if yes, can you please let me know how to resolve this?
Any suggestions will be appreciated.
Thanks
Kavita

Hi Kavitha,
Can you tell me how u resolved the issue???
Regards

ESS Open Enrollment Error message

Hello experts,
I am coming to you because I cannot figure out why we are getting this particular error message when an employee is doing open enrollment.
When an employee goes into ESS and tries to do an open enrollment for their medical/savings/insurance plans, the following error message occurred.
No entry for period parameter 30 / payroll year / payroll period
This is not happening for all of the employees within this payroll area. Just some....but enough to make it a good portion of our employee population.
I have looked at the period parameters/calendar and modifiers etc. to see if the period was set up and could find nothing wrong. We do have the period set up and the calendar goes out to 2010.
I would really appreciate help on this issue since open enrollment begins very soon for us!
Thanks,
Suparna

Hi Arun,
Yes,I have checked those tables (thank you though) and all appropriate values seem to be there.
This is the first time we are doing open enrollment. We went live with SAP in Jan 2008. At that time all employees were converted in with their respective benefit plans. We have had new hires throughout the year who have enrolled and while we had a few onesie twosie issues, nothing of this nature.
Do you think it could be in the ESS set up somewhere?
My problem is that it works for some people and not others. I am looking to see what is different on an employee that works vs one that doesn't.
Any suggestions would be most appreciated!
Thanks,
Suparna

Open vi error for report generation toolkt

Originally it works fine.
Now I upgrade to win7, LV9 and office2010.
To open the old program by 8.6.1, I reinstalled LV 8.6.1 and report generation toolkit.
But still got the error as attached.
Any suggestion, thanks.
Attachments:
ss.png ‏184 KB

1. MS Office 2010 is not yet supported, since it's still just a beta. I believe there are couple of changes that Microsoft make, and it could cause a problem.
2. LabVIEW 8.6.1, and all its toolkit is not supported on Windows 7. This could cause a problkem also.
In conclusion, you should use LabVIEW 2009, Report Generation Toolkit 2009, Windows 7, and downgrade office to XP, 2003 or 2007.
More information: http://digital.ni.com/public.nsf/allkb/C9408B9F08D711E786256F3300701D01

Installation error for iTunes 7.5 on XP: Specified path is too long

I just downloaded the most recent version of the installer, but every time I run it, I get this message midway through the "Copying new files" step:
+The specified path is too long:+
C:WINDOWSwinsxsx86Microsoft.VC80.CRT1fc8b
3b9a1e18e3b8.0.50727.762_x-ww6b128700
There's no denying that it's long, but I don't know what I'm supposed to do about that. I mean, I'm not the one who specified the path.
Clicking Retry just returns the same error endlessly, and clicking Cancel causes the installer to roll back all its changes and close itself.
What gives?

What exact version of Windows XP Pro do you have?
Is it the standard Professional edition, or is ir Professional x64 edition? Check by right-clicking on My Computer and choosing Properties.

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)

ESS Open Enrollment statement link

Hello ,
I am on NW04s and ECC6.0 and added a link on the confirmation screen for the Open Enrollment service for the Open Enrollment confirmation statement but when I click on the link I get the following error:
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: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:429)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:728)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:663)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:78)
     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:1248)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:190)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     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)
I wonder for the cause for this.
Any help would be highly appreciated.

can you please check 1068276.
also please send the dump of R/3 using st22 transaction.

Open Enrollment in ESS Senrio is disable

Hi
we installed ESS bsuiness package 60.2 on portal and backend is ECC5.0.when i logon to portal and check Employee Service-->Benifits&Payment.under "benifit" there is link called "Open Enrollment" .it is disable or glared.can anybody help me how to enable it.please help
Prasad

Hi Kaushal
i had created service as u suggested .it is giving new error called :
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:190)
     at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasons.isConsistent(InternalVcBenefitsEnrollmentReasons.java:179)
     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:413)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:179)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
     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:347)
     at com.sap.tc.webdynpro.clientserver
Thanks
Prasad

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

Control ESS Open Enrollment to use adjustment reason instead of open offer

Hi :
We would like to control open benefit enrollment with adjustment reason instead of standard open offer. Plans are configured for adjustment reason 'OPEN', IT0378 created for the ee with this reason, and open enrollment period is configured . I use
'EMPLOYEE_OPEN_ENROLLMENT_SERVICE05' as my resource.
However, it keeps bringing up plans from standard open offer as versus to plan configured for adjustment reason 'OPEN'. Debugging through, I could see that it passes enrollment type 'O' (for open) instead of 'E' (for event) in 'SELECTED_ENROLL_REASON' to function 'HR_BEN_ESS_RFC_INIT_SELECTION' which in turn would cause it to select plans from standard open period instead of plans configured for 'OPEN' adjustment reason.
What could I do to force ESS to use 'E' instead of 'O' ? I try to avoid having to create an enhancement point for the above fucntion to alter the field.
Thanks.

Double-post - closed

Open Enrollment error for US - No correct adjustment reason specified

Similar Messages

Maybe you are looking for