ESS PZ14 Enrollment error

EP 6.0, ESS 50.4, ITS 6.20, ERP 4.72
No longer supported by SAP
When the Enrollment Detail (PZ14) screen is opened in the portal, the dropdown boxes for Health Plan Option and Dependent Coverage are not in the correct place on the page.
I have tried to change the file, SAPLHRBEN00ENROLLMENT101CORE_ACC but could not find the correct place to move the dropdown box code.
Has anyone else had this problem?

Thanks for your information.
Instead of making these changes, we forced the Enrollment 101 screen to open with the accessibility file.
Then in the accessibility file, which is written to display correctly, we added some style tags to force the font to the correct size.

Similar Messages

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

ESS Benefit Enrollment Critical Error

We are getting a Crtical Error when we try to save ESS Benefit Enrollment in ESS Portal
The error says:
Field Symbol has not yet been assigned, error key: RFC_ERROR_SYSTEM_FAILURE.
Please advice

Amr,
It could possibly be related to your patch level. Check this [thread|"Field symbol has not yet been assigned" Error on Family data iview; out.
Good Luck!
Sandeep Tudumu

ESS Leave Request error - Processing of the service was terminated.

Dear All,
I am getting the below error on the leave request page in ESS
A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
Contact your system administrator.
Index: 0, Size: 0
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
let me know what could be the reason for this error?
Thanks

Suresh,
Please search in scn this has been discussed many times
Thanks
Bala Duvvuri

ESS Bank Key Error Message

Hello All,
I want to customize ESS Bank application error message.Whe we don't enter input for routing number it gives the following message "Enter the bank key". I wanted to customize that error message. I could not locate it in WebDynpro DC. Any input on this highly appreciated.
Thanks
VJ

Hi,
the error is coming from the Bapi, there will be a strandard error node in the bapi that will give the wd application to display the error, request the RFC developer to change in the back end,
find out the node erroreturn in the model, and pass the information of RFC to the abap developer,
otherwise, if you want to customize in WD application, you have to go to perticular method which is throughing the error and you can change there by calling ur own message from message pool.
Cheers,
Apparao.

UAG Certificate Enrollment Error, Logon Failure.

Hi All,
I have been configuring UAG with the help of TLG provided online. On one machine I have to enroll
IP-HTTPS listener certificate. For that i have followed following steps.
Run > mmc > files > Add/Remove snap-in > certificate
on the new window I select computer account then next
then Local Computer Then Finish.
Now, Right Click on the details Pane All Tasks > Request New Certificate > AD Enrollment policy
Now After Clicking Next I am getting Error
Enrollment Error
Logon Failure : Unkown Username or Bad Password.
Recently I have change only this system's password (System Name UAG2SERVER)
Can anyone please help.

Hi,
have you created a rule in the TMG console to allow all traffic to your CA? Otherwise the cert enrollment will fail.
I don not understand what you mean with that you have changed the system password. Are you logged in with an domain account?
regards,
Lutz

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

ESS Open Enrollment Issue

Hi,
We have recently implemented EP 6.0 on ECC 5.0. In the Open Enrollment service (Benefits & Payment workset), a link 'Print New Plan Selection' appears when the plan selection has been submitted. We do not want this link to appear. In the ITS version, we just did not set up the form type 'B2' in Benefits IMG and PZ14 service took care of disabling it.
However, with WebDynpro ESS I am getting a critical error stating 'Form type B2 does not exist'. We do not have to give this option of printing confirmation form after enrollment. Points will be rewarded for relevant answers.
Regards,
Abhijeet.

Please access:
SAP Customizing Implementation Guide > Personnel Management > Benefits > Flexible Administration > Form Setup > Assign Templates to Form Types (V_T74HL)
Set
Form Type: B2 Confirmation form
ADOBE FORM: HR_BEN_CONF
And SAVE
fyi
Marcelo Casaca
Business Consultant
NorthgateArinso
Alameda Madeira, 53
Conjunto 52, Andar 5 Alphaville
06454-010 Barueri-São Paulo
BRAZIL
Phone: +55 11 3028-8910
Fax: + 55 11 3028-8911
URL: www.northgatearinso.com

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.

ESS Open enrollment - Hide Plans

Hi Gurus,
We are implementing Open enrollment for ESS. The problem is when we run the Enrollment iView, it is pulling all the benefit plans, despite us having the Adjustment reason "OPEN". Even when I disable the adjustment reason, it is pulling all the plans with out any error. So, I believe the iView is not looking at the Adjustment reason at all.
I have set the URL parameter in the resource "Z_EMPLOYEE_OPENENROLLMENT_SERVICE05" as "TRACKING_ID=OPEN&INITIATOR_ROLE=HRASRD&EVENT=OPEN". Also I have tried setting the Application Parameter in the Enrollment iView as "EVENT=OPEN". Are there some other parameter that needs to be set?
Thanks,
Sudhir

Also, What is the difference between the Open Enrollment Service, FlexBens Enrollment, and Generic Enrollment?
I am using the service Z_EMPLOYEE_BENEFITPAY_OPEN_ENROLLMENT05. Am I using the wrong service?
thanks,
Sudhir
Edited by: Sudhir Avirneni on Aug 18, 2008 6:50 PM

ESS- Open Enrollment quick link - no plan selections

I've enabled the Open Enrollment Quick link in Benefits and Payment. When I execute it, I get the error message
"No plan selections could be prepared for the specified enrollment reason. Contact your Benefits Administrator for assistance"
R/3 and ITS both display the enrollment plan choices without an adjustment reason of OPEN. Why can't the Portal ESS find them?

This is pretty old but still for the people who will be visiting to this thread just like I did.
We had a same issue... I have checked Web Dynpro java application for benefits enrollment and it shows this message when it has ZERO plans to show in open enrollment.
Then I did debugging in ECC Function modules and found why it is not sending any benefit plans even though user has them in Info type 168 (insurance plans).
It could be any reason for plans not to populate, our reason was user have Vol Spouse Life insurance and Voluntary Child Life Insurance but they dont have Spouse and/or Child records in Info type 21.
So, this error will show up when there are ZERO plans / records to show in portal. Find your issue why by debugging.
-Pradeep

Generic Enrollment error

Hello,
    I am trying to set up ESS. When I click on ESS --> Overview --> Generic Enrollment, I am getting the following error:
The initial exception that caused the request to fail, was:
   java.lang.StringIndexOutOfBoundsException
at java.lang.String.substring(String.java:1067)
    at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasons.setLeadSelectionFromURLParam(VcBenefitsEnrollmentReasons.java:255)
    at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasons.onBeforeOutput(VcBenefitsEnrollmentReasons.java:184)
    at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasons.onBeforeOutput(InternalVcBenefitsEnrollmentReasons.java:182)
at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasonsInterface.onBeforeOutput(VcBenefitsEnrollmentReasonsInterface.java:129)
... 53 more
Could anybody please guide me as what could be wrong with the ESS configuration?
We are on EP 7.0, ECC 6.0, ESS SP 11.
Thanks much for you information in adavnce!!
~~~LB

Hello Naga -
   Thanks for your information. I talked to our functional team and they said, they are able to manually do this through the HRBEN0001 transaction. So, they do not think anything is wrong with the value of the adjustment reason.
Could it be anything related to the Webdynpro program that executes this?
Here is the detailed exception information:
The initial exception that caused the request to fail, was:
java.lang.StringIndexOutOfBoundsException
*     at java.lang.String.substring(String.java:1067)*
*     at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasons.setLeadSelectionFromURLParam(VcBenefitsEnrollmentReasons.java:255)*
*     at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasons.onBeforeOutput(VcBenefitsEnrollmentReasons.java:184)*
*     at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasons.onBeforeOutput(InternalVcBenefitsEnrollmentReasons.java:182)*
*     at com.sap.xss.hr.ben.enrollmentreasons.VcBenefitsEnrollmentReasonsInterface.onBeforeOutput(VcBenefitsEnrollmentReasonsInterface.java:129)*
*     at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasonsInterface.onBeforeOutput(InternalVcBenefitsEnrollmentReasonsInterface.java:132)*
*     at com.sap.xss.hr.ben.enrollmentreasons.wdp.InternalVcBenefitsEnrollmentReasonsInterface$External.onBeforeOutput(InternalVcBenefitsEnrollmentReasonsInterface.java:208)*
*     at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)*
*     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)*
*     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(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:313)*
*     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)*
Please trhow in some light on this.
Tahnks for your suggestion in adv,
~~~LB

ESS Leave Request - Error while creating a leave record

Hi Friends,
Some of the ESS leave request(not workflow) has gone into error when the system tryies to create a leave record in background. I can view these error request using the report RPTARQDBVIEW. This happens when the background program(PTARQPOST) tries to create a leave record. In some cases the status of the leave request is set to error(the status attribute of the container element(Req) has the value Error),but we are not able to find what is actual error.Is there any log where we can check what is the problem? Please advice.

May be
Internally the pernr might not be locked or some one may be maintaing the pernr for whom you are trying to post.

ESS Persoanl Data Error(Screen output without connection to user)

Hi All,
        When i am trying to Save my data in my ESS----->Personal Info -
>Personal Data, i am getting below error, any body know how to resolve this issue, please let me know.
Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE:
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.per.fc.persinfo.FcPersInfo.save(FcPersInfo.java:440)
     at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfo.save(InternalFcPersInfo.java:770)
     at com.sap.xss.per.fc.persinfo.FcPersInfoInterface.save(FcPersInfoInterface.java:186)
     at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface.save(InternalFcPersInfoInterface.java:275)
     at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface$External.save(InternalFcPersInfoInterface.java:435)
     at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNavi.onEvent(VcPersInfoReviewNavi.java:213)
     at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNavi.onEvent(InternalVcPersInfoReviewNavi.java:171)
     at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNaviInterface.onEvent(VcPersInfoReviewNaviInterface.java:115)
     at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNaviInterface.onEvent(InternalVcPersInfoReviewNaviInterface.java:124)
     at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNaviInterface$External.onEvent(InternalVcPersInfoReviewNaviInterface.java:200)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:533)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseSaveEvent(FPMComponent.java:951)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseSaveEvent(FPMComponent.java:1114)
     at com.sap.xss.per.vc.reviewnavi.VcPersInfoReviewNavi.next(VcPersInfoReviewNavi.java:227)
     at com.sap.xss.per.vc.reviewnavi.wdp.InternalVcPersInfoReviewNavi.next(InternalVcPersInfoReviewNavi.java:175)
     at com.sap.xss.per.vc.reviewnavi.ReviewNaviView.onActionNext(ReviewNaviView.java:153)
     at com.sap.xss.per.vc.reviewnavi.wdp.InternalReviewNaviView.wdInvokeEventHandler(InternalReviewNaviView.java:173)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     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:321)
     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.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1299)
     at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:868)
     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:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     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:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     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(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Screen output without connection to user., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.xss.per.model.mac.HRXSS_PER_MAC.hrxss_Per_Save(HRXSS_PER_MAC.java:478)
     at com.sap.xss.per.model.mac.Hrxss_Per_Save_Input.doExecute(Hrxss_Per_Save_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 64 more
and after that i went to ST22 Transaction Code in my ECC System i found two types of DUMP errors,
the below are those details.
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exception              CX_SY_REF_IS_INITIAL
Date and Time          09/09/2008 08:19:16
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLHRXSS_PER_MAC" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
"SAPLHRXSS_PER_MAC" or "LHRXSS_PER_MACU04"
"HRXSS_PER_CLEANUP"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"HRXSS_PER_CLEANUP" "(FUNCTION)", or its possible occurrence must be declared
in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "ERPDEV01"
Network address...... "10.88.1.6"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "ERPDEV01"
Database type..... "MSSQL"
Database name..... "DE1"
Database user ID.. "de1"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 23 2007 00:33:51"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 133
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 4189840
Heap.... 0
Page.... 0
MM Used. 1229856
MM Free. 2957360
User and Transaction
Client.............. 210
User................ 937048
Language Key........ "E"
Transaction......... " "
Transactions ID..... "68211f907e6911ddbfef005056833439"
Program............. "SAPLHRXSS_PER_MAC"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "########"
Database Release.... 645
Kernel Release...... 645
Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. "###"
User................ "############"
Transaction......... " "
Call Program........." "
Function Module..... "HRXSS_PER_CLEANUP"
Call Destination.... "<unknown>"
Source Server....... "ERPDEV04"
Source IP Address... "10.88.1.9"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "SAPLHRXSS_PER_MAC" - in
"HRXSS_PER_CLEANUP".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 13
of the (Include) program "LHRXSS_PER_MACU04".
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", but it was neither handled locally
nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPLHRXSS_PER_MAC "; its source code begins in
line
1 of the (Include program "LHRXSS_PER_MACU04 ".
Source Code Extract
Line
SourceCde
1
FUNCTION hrxss_per_cleanup.
2
3
""Local interface:
4
*" EXPORTING
5
*"     VALUE(MESSAGES) TYPE BAPIRETTAB
6
7
8
CALL METHOD mac_adapter->cleanup
9
   IMPORTING
10
     messages = messages.
11
12
TRY.
>>>>>
CALL METHOD xss_adapter->cleanup
14
15
CATCH CX_HRPA_VIOLATED_ASSERTION .
16
ENDTRY.
17
18
ENDFUNCTION.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
2
SY-TABIX
0
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080909
SY-UZEIT
081916
SY-XPROG
SAPLHRXSS_PER_MAC
SY-XFORM
HRXSS_PER_CLEANUP
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
4 FUNCTION     SAPLHRXSS_PER_MAC                   LHRXSS_PER_MACU04                      13
HRXSS_PER_CLEANUP
3 FORM         SAPLHRXSS_PER_MAC                   LHRXSS_PER_MACU04                       1
HRXSS_PER_CLEANUP
2 FORM         SAPMSSY1                            SAPMSSY1                               85
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
%_RFC_START
Chosen variables
Name
Val.
No.       4 Ty.          FUNCTION
Name HRXSS_PER_CLEANUP
MESSAGES
Table[initial]
%_DUMMY$$
2222
0000
0000
0000
No.       3 Ty.          FORM
Name HRXSS_PER_CLEANUP
SYST-REPID
SAPLHRXSS_PER_MAC
5454455555545544422222222222222222222222
310C82833F052FD1300000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
%_%_MESSAGES
Table[initial]
No.       2 Ty.          FORM
Name REMOTE_FUNCTION_CALL
%_DUMMY$$
2222
0000
0000
0000
SY-REPID
SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SYST-REPID
SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
HEADER
000000000000
000000000000
TYPE
3
0000
3000
SY-XPROG
SAPLHRXSS_PER_MAC
5454455555545544422222222222222222222222
310C82833F052FD1300000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
RC
0
0000
0000
SY-XFORM
HRXSS_PER_CLEANUP
455555545544444552222222222222
82833F052F3C51E500000000000000
000000000000000000000000000000
000000000000000000000000000000
%_SPACE
2
0
0
0
No.       1 Ty.          MODULE (PBO)
Name %_RFC_START
%_PRINT
000                                                                                0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RFCTYPE_INTERNAL
3
0000
3000
Internal notes
The termination was triggered in function "method_call_iref"
of the SAP kernel, in line 2207 of the module
"//bas/700_REL/src/krn/runt/abmethod.c#8".
The internal operation just processed is "METH".
Internal mode was started at 20080909081916.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App       : disp+work.EXE (pid=3864)
When      : 9/9/2008 8:19:16.162
Threads   : 2
Computer Name       : ERPDEV01
User Name           : SAPServiceDE1
Number of Processors: 4
Processor Type: AMD64 Family 15 Model 65 Stepping 2
Windows Version     : 5.2 Current Build: 3790
State Dump for Thread Id d90
FramePtr         ReturnAd         Param#1          Function Name
0000000007d1bb20 0000000077d704bf 000000003879a800 ntdll!ZwWaitForSingleObject
0000000007d1bbc0 0000000001722981 0000000000000180 kernel32!WaitForSingleObjectEx
0000000007d1be10 00000000006110c5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
0000000007d1be40 0000000000af8e9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
0000000007d1be90 0000000000afe0c0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7091)]
0000000007d1c870 000000000081768a 0000000001adae28 disp+work!ab_rabax [abrabax.c (1231)]
0000000007d1c8d0 0000000000830b12 0000000000000000 disp+work!method_call_iref [abmethod.c (2215)]
0000000007d1ca50 0000000000a0bac7 0000000000000008 disp+work!ab_extri [abextri.c (554)]
0000000007d1caa0 0000000000ac830c 0000000000000008 disp+work!ab_xevent [abrunt1.c (281)]
0000000007d1cb30 000000000066f348 0000000000000008 disp+work!ab_dstep [abdynpro.c (492)]
0000000007d1ccb0 0000000000672f1d 000007fe571fc890 disp+work!dynpmcal [dymainstp.c (2403)]
0000000007d1cd40 000000000067291a 000007fe571414a0 disp+work!dynppbo0 [dymainstp.c (543)]
0000000007d1cdf0 00000000006320d5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
0000000007d1fc30 00000000004d7393 0000000000000003 disp+work!dynpen00 [dymain.c (1629)]
0000000007d1feb0 000000000042d5a6 000000000a595080 disp+work!TskhLoop [thxxhead.c (4470)]
0000000007d1fee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1121)]
0000000007d1ff10 00000000019c7dd1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
0000000007d1ff70 0000000077d5964c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
0000000007d1ffa0 0000000000000000 00000000019c7c60 kernel32!BaseProcessStart
State Dump for Thread Id 1e0c
FramePtr         ReturnAd         Param#1          Function Name
000000000edffe40 0000000077d5f691 0000000007d86460 ntdll!NtFsControlFile
000000000edffeb0 00000000018ae00f 0000000000000000 kernel32!ConnectNamedPipe
000000000edfff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
000000000edfff70 0000000077d6b6da 0000000077d6b6a0 msvcrt!endthreadex
000000000edfffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
SAPMSSY1
0
04/11/2005
09:27:15
22528
E
1
Prg
SAPLSYST
1
02/13/2005
17:31:56
35840
E
2
Prg
SAPLHRXSS_PER_MAC
2
07/03/2008
12:14:05
58368
E
3
Prg
CX_SY_REF_IS_INITIAL==========CP
3
07/05/2005
13:10:16
10240
E
4
Typ
SCX_SRCPOS
0
05/18/2004
14:07:11
2048
5
Prg
CX_DYNAMIC_CHECK==============CP
5
07/05/2005
13:10:16
10240
E
6
Prg
CX_ROOT=======================CP
6
02/06/2008
15:43:48
11264
E
7
Prg
CX_NO_CHECK===================CP
7
07/05/2005
13:10:16
10240
E
8
Prg
CX_SY_NO_HANDLER==============CP
8
07/05/2005
13:10:16
10240
E
9
Typ
SYST
0
09/09/2004
14:18:12
31744
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program SAPMSSY1
SYST                                       / /       : :     00004612
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
243
FUNC
03
001F
LHRXSS_PER_MACU03
1
244
PAR2
02
0000
001F
C000
LHRXSS_PER_MACU03
1
246
FUNC
13
0003
LHRXSS_PER_MACU03
1
247
PAR2
01
0000
0014
C001
LHRXSS_PER_MACU03
1
249
FUNC
FF
0000
LHRXSS_PER_MACU03
1
250
ENDF
00
0000
LHRXSS_PER_MACU03
1
251
00
0000
LHRXSS_PER_MACU03
1
252
STCK
02
C001
LHRXSS_PER_MACU03
1
253
CPOP
00
0000
LHRXSS_PER_MACU03
1
254
00
0000
LHRXSS_PER_MACU03
1
255
FUNP
3E
0000
0014
8000
0000
8000
0000
0000
LHRXSS_PER_MACU04
1
259
FUNP
80
0000
0000
0000
0000
0000
0000
0000
LHRXSS_PER_MACU04
1
>>>>>
METH
03
0000
0000
8006
0000
0000
0000
0000
LHRXSS_PER_MACU04
13
267
PAR2
00
0000
0001
0000
LHRXSS_PER_MACU04
13
269
FUNE
00
0000
LHRXSS_PER_MACU04
18
270
00
0000
LHRXSS_PER_MACU04
18
271
PERP
00
0000
LHRXSS_PER_MACU04
1
272
FUNC
03
E844
LHRXSS_PER_MACU04
1
273
FUNC
03
0020
LHRXSS_PER_MACU04
1
274
FUNC
13
0003
LHRXSS_PER_MACU04
1
Second Dump
Runtime Errors         DYNPRO_SEND_IN_BACKGROUND
Date and Time          09/09/2008 08:19:15
Short text
Screen output without connection to user.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSTRD" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
During background processing, the system attempted to send a
screen to a user.
Current screen: "SAPLSTRD " 0351.
How to correct the error
If the error occurred in your own ABAP program or in an SAP
program you modified, try to remove the error.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DYNPRO_SEND_IN_BACKGROUND" " "
"SAPLSTRD" or " "
"SYSTEM-EXIT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "ERPDEV01"
Network address...... "10.88.1.6"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "ERPDEV01"
Database type..... "MSSQL"
Database name..... "DE1"
Database user ID.. "de1"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 23 2007 00:33:51"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 133
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 12569520
Heap.... 0
Page.... 131072
MM Used. 8307376
MM Free. 4259072
User and Transaction
Client.............. 210
User................ 937048
Language Key........ "E"
Transaction......... " "
Transactions ID..... "68211f907e6911ddbfef005056833439"
Program............. "SAPLSTRD"
Screen.............. "SAPLSTRD 0351"
Screen Line......... 0
Information on caller of Remote Function Call (RFC):
System.............. "########"
Database Release.... 645
Kernel Release...... 700
Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Nam

Hello Abhiram,
Please i request weather you have assign 0105 - Communication infotype to ESSuser and
check the following JCos has been configured.
SAP_R3_Financials
SAP_R3_Financials_Metadata
SAP_R3_HumanResources
SAP_R3_HumanResources_MetaData
SAP_R3_SelfServiceGenerics
SAP_R3_SelfServiceGenerics_MetaData
SAP_R3_Travel
SAP_R3_Travel_MetaData
SAP_R3_SelfServiceGenerics_MetaDataFIN
SAP_R3_SelfServiceGenericsFIN
let me know this
points if problem solved
please close thread if problem solved
thanksyou,
regards
Vijai

ESS SP11 upgrade error in travel request

Dear All,
We have recenlty up graded to ESS-SP11 package, The intial travel request is coming. But When I click on "dditional destination" or "Review" button , The following dump is coming.
The same is happening in travel expense as well.
The error is:
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   com.sap.aii.proxy.framework.core.DataAccessException: Type conversion error, field TAX_PER_DIEMTAX, complex type class com.sap.xss.tra.tre.model.expenses.Ptrv_Web_General_Data_Int
    at com.sap.aii.proxy.framework.core.JcoBaseTypeData.propagateJcoException(JcoBaseTypeData.java:130)
    at com.sap.aii.proxy.framework.core.JcoBaseTypeData.setElementValue(JcoBaseTypeData.java:751)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClass.setAttributeValue(DynamicRFCModelClass.java:482)
    at com.sap.tc.webdynpro.progmodel.context.GenericModelClassCopyHelper.setAttributeValue(GenericModelClassCopyHelper.java:69)
    at com.sap.tc.webdynpro.progmodel.context.CopyService.copyCorresponding(CopyService.java:55)
    ... 66 more
See full exception chain for details.
Any quick help would be surely awarded with good points.
Sandeep Kulkarni.

Probably, your backend is not compatible anymore with your Portal.
You may need to upgrade your SAP_HR and EA_HR support packages.

ESS PZ14 Enrollment error

Similar Messages

Maybe you are looking for