Skip to Content
0
Former Member
Apr 19, 2010 at 01:20 PM

ESS clock in/out approve error

38 Views

Hi all:

We are using ESS 1.41 / ECC EHP4. We use the standard workflow template WS12300111 for clock in/out.

We are able to send cor request and start the workflow correctly, but when the manager click the work item to see the request, the webdynpro application got dumped.

The exception is like below:

-


java.lang.NullPointerException

at com.sap.xss.hr.lea.form.edit.VcFormEdit.setVisibilityOfWorkItem(VcFormEdit.java:633)

at com.sap.xss.hr.lea.form.edit.VcFormEdit.setVisibleFields(VcFormEdit.java:491)

at com.sap.xss.hr.lea.form.edit.VcFormEdit.onBeforeOutput(VcFormEdit.java:332)

at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onBeforeOutput(InternalVcFormEdit.java:1092)

at com.sap.xss.hr.lea.form.edit.VcFormEditInterface.onBeforeOutput(VcFormEditInterface.java:135)

at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface.onBeforeOutput(InternalVcFormEditInterface.java:192)

at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface$External.onBeforeOutput(InternalVcFormEditInterface.java:268)

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:782)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:302)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)

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:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

-


I also find out that this error only happen when the manager only has COR request to approve. If the manager has some other leave request in his inbox, he can open the approve list, but he can not see the COR request in the list. It seems that the COR request can't be read by the approve application. Anyone can help me out here?

Best regards!

wayne

Edited by: Wayne Lou on Apr 19, 2010 3:21 PM