Skip to Content
avatar image
Former Member

ESS Timesheet Error

Hi,

We are having ESS application, 'Timesheet/Request Time off'. If I keep the application ideal for some time and after sometime when I try to go through it, it is throwing the following error. when I go to backend and relese the locks, still the error persists for some time. Can anyone let me know where I am getting the problem?

The following ABAP Exception occurred: PERNR_NOT_LOCKED:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:98)

at com.sap.xss.hr.cat.record.blc.RfcManager.rfcExecute(RfcManager.java:468)

at com.sap.xss.hr.cat.record.blc.RfcManager.init(RfcManager.java:822)

at com.sap.xss.hr.cat.record.blc.wdp.InternalRfcManager.init(InternalRfcManager.java:248)

at com.sap.xss.hr.cat.record.blc.FcCatRecordInterface.onInit(FcCatRecordInterface.java:344)

at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface.onInit(InternalFcCatRecordInterface.java:234)

at com.sap.xss.hr.cat.record.blc.wdp.InternalFcCatRecordInterface$External.onInit(InternalFcCatRecordInterface.java:484)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)

at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendar.onInit(VcCatCalendar.java:251)

at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendar.onInit(InternalVcCatCalendar.java:194)

at com.sap.xss.hr.cat.record.vac.calendar.VcCatCalendarInterface.onInit(VcCatCalendarInterface.java:162)

at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface.onInit(InternalVcCatCalendarInterface.java:146)

at com.sap.xss.hr.cat.record.vac.calendar.wdp.InternalVcCatCalendarInterface$External.onInit(InternalVcCatCalendarInterface.java:222)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)

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

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

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

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

at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:222)

at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1280)

at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)

at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:552)

at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:191)

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)

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.doApplicationProcessingStandalone(ClientSession.java:746)

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

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

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)

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

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

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

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

Caused by: com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFC_Fault_Exception:

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:274)

at java.lang.Class.newInstance0(Class.java:308)

at java.lang.Class.newInstance(Class.java:261)

at com.sap.aii.proxy.framework.core.JcoMarshaler.unmarshalException(JcoMarshaler.java:429)

at com.sap.aii.proxy.framework.core.JcoProxy.send(JcoProxy.java:78)

at com.sap.aii.proxy.framework.core.AbstractProxy$JcoProxyHelper.send(AbstractProxy.java:173)

at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:141)

at com.sap.xss.hr.cat.general.model.slim.CatsModelSlim.hrxss_Cat_Wd_Record(CatsModelSlim.java:221)

at com.sap.xss.hr.cat.general.model.slim.Hrxss_Cat_Wd_Record_Input.doExecute(Hrxss_Cat_Wd_Record_Input.java:137)

at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)

... 66 more

Thanks & Regards,

Raj.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • May 31, 2007 at 12:23 AM

    Hi Raj,

    It's failing at this BAPI Hrxss_Cat_Wd_Record, try testing with some data to replicate this issue then maybe that will explain why it's throwing that error.

    Raj

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Silvio Marcos Galery dos Santos

      Hi there.

      I also experienced this problem. It has to do with the fact that the user is locked in the back-end.

      I solved it by going to SM04 and removing the session of the currently logged in user.

      I am busy investigating a long term solution

      Hope this helps!

  • avatar image
    Former Member
    May 02, 2008 at 06:34 PM

    We are also experiencing this error -- intermittently for no apparent reason. The person's timesheet is not locked in the backend. We also experienced this when performing a 'playback' of LoadRunner recordings for single employees. Enqueue traces of a single time entry session show multiple enques and dequeues. Maybe multiple user sessions are opened and they are competing for the CATS_ENQUE lock?

    Certainly, we can delete sessions in SM04 and delete lock entries in SM12. But we need to find the root cause and implement a solution that will prevent this from happening (except when the timesheet is really locked).

    Has any one found a solution to this issue?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 23, 2008 at 06:03 PM

    Here's how you recreate the error: PERNR_NOT_LOCKED

    1 - Start Internet Explorer, via Start menu

    Login to portal and navigate to time sheet WD application, i.e. you have to see the small boxes with step 1->2->3

    2 - Start a second Internet Explorer, via Start menu (not via Ctrl-N in IE)

    Login to portal and navigate to time sheet WD application, i.e. you have to see the small boxes with step 1->2->3

    You now have to separate IE/portal sessions accessing the same users timesheet.

    The second window will show PERNR_NOT_LOCKED.

    I don't know why this is the behaviour, but the problem can be avoided by user not accessing the same timesheet from multiple machines or IE windows.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 08, 2008 at 06:45 AM

    Dear Friend

    Really need ur help as we are upgrading from 4.7 to ECC6.

    Our client want to implement tiem sheet. Request you to provide gudiance wheher CATS i.e CATSRegular orESS timesheet would be useful.

    if would be great if u could provide a kind of advantages adn disadvantages of both.

    Suitable points would be rewarded

    Sam

    Add comment
    10|10000 characters needed characters exceeded