ESS- Error in Leave Request

Hi All,
I have a workset 'working Time' and in that i have 'leave request'. When i go and apply for leave(casual leave type which is type 0001) and press Review, its throws the error as" Attendance/absence type 0002 requires minimum of 3 attendance/absence days ", and if i will change the type of leave as probationary Leave, then also it throws the same error.
I need to debug it now.. where should i do this and what might be the cause for this error.
Pls help me..
Regards,
Shreya.

Hello king,
we saw that and checked but could'nt find it.. what to do next.
Pls will you tell us in more detail.. as i am learner.
Waiting for ur reply.
Regards,
Shreya.

Similar Messages

  • Error in Leave Request:ESS

    Hi All,
    I am getting a error in Leave Request Iview in ESS application.
    I am using EP 7.0.
    I have done the required settings in R/3.Created Rule group,added applciation parameter in iview,JCos are working.
    But still I am getting this error.
    If anybody has the idea on how to solve it please help.
    The initial exception that caused the request to fail, was:
    java.lang.NullPointerException
         at com.sap.xss.hr.lea.blockcale.VcBlockCale.transferFixedBcData(VcBlockCale.java:371)
         at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:262)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCale.onInit(InternalVcBlockCale.java:275)
         at com.sap.xss.hr.lea.blockcale.VcBlockCaleInterface.onInit(VcBlockCaleInterface.java:163)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface.onInit(InternalVcBlockCaleInterface.java:144)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface$External.onInit(InternalVcBlockCaleInterface.java:220)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         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:756)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
         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:1289)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
         at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
         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:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
         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:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Regards,
    Sumangala

    Hi,
    Please check whether that particular employee having all the necessary authorization or not in ECC side.
    Also mention the ECC and ESS version with SP level.
    Regards,

  • Error in ESS while Accessing Leave Request

    Dear All,
      We are having the ESS in EP 7.0 and ECC 6.0, We have deployed the ESS components. Everything working fine for one User only,But for other users we are facing problem Leave Request. This is the error we are getting:::
    com.sap.xss.config.FPMConfigurationException: Read of object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest failed.
    *     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:92)*
    *     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObject(PcdObjectBroker.java:47)*
    *     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:106)*
    *     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:80)*
    *     at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:83)*
    *     at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)*
    *     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.initializeConfiguration(FcXssPcd.java:816)*
    *     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.loadConfiguration(FcXssPcd.java:250)*
    *     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.loadConfiguration(InternalFcXssPcd.java:178)*
    *     at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.loadConfiguration(FcXssPcdInterface.java:138)*
    *     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.loadConfiguration(InternalFcXssPcdInterface.java:148)*
    *     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.loadConfiguration(InternalFcXssPcdInterface.java:240)*
    *     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcd.loadConfiguration(CcXssPcd.java:282)*
    *     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcd.loadConfiguration(InternalCcXssPcd.java:184)*
    *     at com.sap.pcuigp.xssutils.ccpcd.CcXssPcdInterface.loadConfiguration(CcXssPcdInterface.java:115)*
    *     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface.loadConfiguration(InternalCcXssPcdInterface.java:124)*
    *     at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface$External.loadConfiguration(InternalCcXssPcdInterface.java:184)*
    *     at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:205)*
    *     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)*
    *     at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)*
    *     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)*
    *     at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)*
    *     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:172)*
    *     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:731)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)*
    *     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)*
    *     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: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.wdDoRefresh(PageBuilder.java:596)*
    *     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:827)*
    *     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:299)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:683)*
    *     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)*
    *     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)*
    *     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.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest)
    *     at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:421)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1177)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1183)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1282)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1229)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:996)*
    *     at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:68)*
    *     at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:989)*
    *     at com.sap.xss.config.pcd.PcdObjectBroker.getPcdContext(PcdObjectBroker.java:305)*
    *     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:53)*
    *     ... 69 more*
    Please let me know what might be the problem, and y its not working for other ESS users.
    Expecting solution and Ideas as soon as possible as its very are in crucial time.
    Thanks
    Ravi.S

    This is a permission issue.
    Please go to Content Admin> Portal C D> ...Provided by SAP> End User C> ESS> you will see the ESS object> Right click on it and select Permission and you will see the roles present on the right hand side.
    Check it and save it.
    Regards
    Prashant

  • Java.lang.NullPointerException Error in Leave Request tab of ESS in Portal

    Hello All,
    I have configurted ESS/MSS on EP 7.01 SP03, but it is giving error in almost every tab.
    When i navigate in to Employee Self Service < Working Time < Leave Request tab it ends up with error pasted below.
    java.lang.NullPointerException
    Same error appears for other tabs like Employee Self Service < Working Time <Quote Overview/Clocl In/Out Corrections
    Any help to solve this issue will be highly appretiated.
    Thanks
    Vinit

    Full exception chanin from NWA is as below
    Exception occured during processing of Web Dynpro application sap.com/ess~lea/LeaveRequest. The causing exception is nested.
    [EXCEPTION]
    java.lang.NullPointerException
    at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290)
    at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206)
    at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173)
    at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115)
    at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124)
    at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface$External.onInit(InternalBTrackingCompInterface.java:198)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
    at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:219)
    at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:273)
    at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
    at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:198)
    at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:258)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
    at com.sap.xss.essceservices.vcceassignmentselection.VcCEAssignmentSelection.onInit(VcCEAssignmentSelection.java:235)
    at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelection.onInit(InternalVcCEAssignmentSelection.java:174)
    at com.sap.xss.essceservices.vcceassignmentselection.VcCEAssignmentSelectionInterface.onInit(VcCEAssignmentSelectionInterface.java:162)
    at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelectionInterface.onInit(InternalVcCEAssignmentSelectionInterface.java:144)
    at com.sap.xss.essceservices.vcceassignmentselection.wdp.InternalVcCEAssignmentSelectionInterface$External.onInit(InternalVcCEAssignmentSelectionInterface.java:220)
    at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
    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: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:1289)
    at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
    at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
    at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593)
    at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865)
    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: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)
    Edited by: Vinit Soni on Aug 27, 2010 7:59 AM

  • Strange error in Leave request

    Hi Experts,
    I am getting one error in production for the leave request. When one particular employee applies for the leave, he is able to apply for the leave properly. After applying leave, his leave request status changes to sent. when i checked in the report "RPTARQDBVIEW" about that particular employee's leave document, workflow was not attached to that document. This is happening everytime whenever he applies for the leave. Workflow is not getting triggered whenever he applies. Its working fine for the other employees similar to him.  
    Can you help me regarding this. This is becoming critical.
    Thanks
    Sameer
    One thing i found that, its happending for few more employees. and common thing about them is that all are getting error "Unable to send the request with this approver" while applying leave. when they go back and again apply then leave request is going. For all these employees their manager is not belongs to india org unit. And this ESS we have configured for india employees.
    Edited by: sameer dhuke on Jul 17, 2009 7:41 PM

    Hi,
    This comens when the approral is not assign to the User-ID
    Say "A" is the employee and you need set "B" is manager for "A"
    Then folloiwng things you need to do .
    in the PA30 chekh the "Org Assig" for "A".
    The org unit for "A" ( employee ) and "B" ( manager ) should be same .
    then PO10 give the Org Unit and check the following entry .
    19.02.2009     31.12.9999     B     003     Incorporat     S     50006006     056607A     0,00
    19.02.2009     31.12.9999     B     012     Is managed     S     50006006     056607A     0,00
    you can see the "50006006" is the possition ( Is managed )
    Then you need to go PO13 give the possition no and click up on 'Overview"
    19.02.2009     31.12.9999     A     003     Belongs to     O     50129078     New org unit                        0,00
    01.04.2007     31.12.9999     A     008     Holder     P     00001070     (Employee A)     100,00
    01.01.2000     31.12.9999     A     011     Cost cente     K     00002009461000     Financial As     0,00
    19.02.2009     31.12.9999     A     012     Manages...     O     50129078     New org unit     0,00
    01.01.2000     31.12.9999     B     007     Is describ     C     50015243     AdmSup     0,00
    Like this you can set the manager to employee

  • ESS/MSS: Approve Leave Request in UWL - not working

    Hi to all,
    we are using web dynpro ESS/ MSS (SAPESS07_12/ SAPMSS07_4) in portal NW04s for mySAP ERP2005 and are using UWL in order to approve leave requests. If employees are creating leave requests, everything works fine. After that the manager opens the leave request in UWL, the web dynpro application is openening succesfully and after some clicks he reaches the buttons to approve or reject the leave request. But by pushing one of them the following messages occures :
    <b>Workitem 000000000000 Cannot be read</b>
    After pushing the button again, another message comes up:
    <b>No Customizing for status typ ARQ, Status approved...</b>
    By the way, the same errors also come up when the employee wants to delete his leave request which is not approved.
    Any ideas, what can be the reason?
    Regards,
    Frank

    Hi Ashutosh,
    I have found the reason. The user <b>WF - Batch</b> in sap erp, which is using the RFC Destination for workflow, was locked. Well, it is a a little bit strange for a cummunication user that he becomes locked. Unlocked him, now all works.
    Thanks for your support.
    Regards,
    Frank

  • Critical error in leave request

    Dear All,
    Following error is getting only for some users when they click on Leave request link in E-portal. We have EP 7.
    I have searched previously posted threads for this type of issue & checked for points suggested in those threads. But everything seem to be ok.
    1. Leave request config is proper
    2. WEBMO maintained is ok.
    3. Infotype 0105 subtype 0001 is maintained & ESS role is assigned using Tcode HRUSER.
    4. Leave quota is updated in 2006.
    Error I am getting
    Critical Error
    A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
    Contact your system administrator.
           User  does not exist in this period                                 , error key: RFC_ERROR_SYSTEM_FAILURE   
           User  does not exist in this period                                 , error key:
    RFC_ERROR_SYSTEM_FAILURE:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException:      User  does not exist in this period                                 , error key: RFC_ERROR_SYSTEM_FAILURE
    For  other users entire leave request & leave approval process is happening properly. leaves are also getting updated in 2001. Then why the error is for only few users?system has gone live & people are not able to apply leaves
    Please help.
    Thanks & Regards,
    Swapnali
    Edited by: Swapnali Kamerkar on Sep 14, 2010 2:28 PM

    Hi Siddharth & Jiggar,
    Thanks for your immediate response.
    Yes, I had already checked  this scenario giving SAP_ALL authorization, same error is coming & I don't think so authorization would be the problem cause for other users entire leave request & leave approval is happening properly with assigned ESS Role.
    Also respective user Id was already created in R/3 & maintained in infotype 0105 subtype 0001 using HRUSER Transaction. Same user ID was created in portal & employee is logging-in with that Id. Validity period is also proper.
    Also I want to put one more point here that whenever I don't maintained user Id in 0105 subtype 0001 for a particular employee & if he is logging-in with that ID, Error coming is only 'User 'XY' doesn't exist in this period'. where XY is user ID.
    But for the case in qustion even if Id is maintained in 0105, error coming is 'User doesn't exist in this period ...RFC_ERROR_SYSTEM_FAILURE'.
    Also all other applications like time account,payslips, personal information are working fine for that user.
    Waiting for your replies.
    Thanks & Regards,
    Swapnali
    Edited by: Swapnali Kamerkar on Sep 15, 2010 8:36 AM

  • Team calendar Error in Leave request Page .No Views found: Missing customiz

    Hi all
    i am portal consultant , i dont know much abt HR related configuration required for ESS.
    Plz Tell me the what configuration Exactly needed for Team calender in a leave Request page.
    in R3 i have been to the the Tabel   V_PTREQ_TEAM  where i found  the below things.
    Earlier I found  Group of orgnisation for Team view mode alsp ATTEND.  i changed into ESS_LEA_EE.  and i transported it but Now use ,
    still getting the error 
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator
    No Views found: Missing customizing  
    00000001     SAP Standard     01.01.1800     31.12.9999     Approval Mode     View Group (MSS)     ATTEND
    00000001     SAP Standard     01.01.1800     31.12.9999     Administrator Mode     View Group (MSS)     ATTEND
    00000001     SAP Standard     01.01.1800     31.12.9999     Team View Mode     View Group (MSS)     ESS_LEA_EE
    Plz tell me the what are the Necessary cnfigurations Required for Team calendar ,
    what we have to maintain in this table.
    After Upgradation Team calender is not working.
    Before r it worked.
    plz help me  to solve this
    Thankyou
    swapna

    Hi,
    Check the link below:
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/108c31e7-b6a7-2d10-3692-c1a9f7a5c4dc?QuickLink=index&overridelayout=true
    Hope this helps.
    Cheers-
    Pramod

  • ESS WF WS04200009 Leave request with HTML (BP for SAP R/3 4.7))

    Hi there all,
    I hope somebody can help how to configure this scenario. I searched around on SDN and SAP Help but couldn't find a thing.
    I actually have 2 questions:
    1. is there somebody who has some how-to guides for the ESS scenarios especially about the leave request.
    2. Where are publishing the leave request in the portal. When i submit the leave request a got a pop-up with the message: you are not allowed to do this task.
    I hope somebody has some useful information.
    Thanks in advance
    Regards Maarten.

    Hi Maarten,
    These points may help you:
    1)All HTML templates should be imported into your IT Server.(ESS server)
    2)In tcode PFTC select workflow template WS04200009 and proceed to workflow builder.
    3) In workflow builder for each step select agent assignment and in the agent assignment attributes choose the general task option.
    Everything else is standard and should work fine.
    Regards,
    Rajeev

  • Error in Leave Request screen

    Hi All,
    Particular group of employess are facing problem in accessing leave request screen in the portal. They are getting the following error.
    *********Error**************
    "There are no customizing settings for absence type".
    Please guide me in resolving this.
    Thanks,
    Steffler.

    Hi,
    Can you check if the absence is correctly maintained, also make sure absence which were available earlier are customised correctly and not delimited or removed.
    Check t-code "PTARQ" .
    Hope the tasks are set to "General Task"
    SPRO> Time Management>Web Application>Leave Request(new)>Link Absence types and workflow templates.
    Regards
    Puneet

  • JCO Error in leave request.

    Dear Experts,
    When i open the leave request application, when we select date & leave type & go futhure ...i am facing below mentioned error in my portal.This is after upgradation of EHP5
    JCO$Abap Exception
    com.sap.mw.jco.JCO$AbapException: (126) NOT_FOUND: NOT_FOUND
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3486)
    at com.sap.mw.jco.JCO$Repository.execute(JCO.java:20965)
    at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:21367)
    at com.sap.mw.jco.JCO$Repository.queryFunctionInterface(JCO.java:20990)
    at com.sap.mw.jco.JCO$Repository.getFunctionInterface(JCO.java:21094)
    Regards,
    *Nisha K

    Dear Nisha,
    Hope you are doing good.
    The below link gives the reason for this issue:
    http://help.sap.com/erp2005_ehp_05/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
    Can you please download the latest patch level of the RFC library for your release as well. Please see note 413708 on how to download the RFC library.
    Make sure that the JDK being used is supported and if the issue persists, enable the below JCo trace as per:
    628962 - How to switch on the SAP JCo trace
    Then reproduce the issue and check the latest logs for more info..
    Thank you and have a nice day :).
    Kind Regards,
    Hemanth
    SAP AGS

  • ESS Auto Approval Leave Request

    Goodday all,
    I'. trying to create a WF which will have a step tp auto approve a leave request after 5 days of submission to the approver. I have made a copy of the standard WF12300011 and have included 'modeled deadline monitoring' step just before 'request approved?' step. This is where i'm stuck, once teh deadline is obsolete, i will need to create a new step to automatically change the REQ.STATUS to 'Posted' OR 'Approved'. How do i do this step? or is there a better way to do things? Thanks in advance
    Regards

    Try Like this
    1. As you said that you hvae a copy of the standard workflow so when the Modeled Deadline monitoring is reached any ways a outcome will be included in the WF template , so what you can do is in that outcome you include a Activity which uses the method of conatiner element REQ  which will have the current request instance
    REQ type is cl_pt_req_wf_attribs so in this class you hvae a method with name APPROVE so use this mehtod in the Activity that you will create in the modeled deadline monitoring outcome. this will approve the request and when ever the report RPTARQPOST is executeed the approved request will be posted into the respective infotypes.
    If you hvae any more queries plz let me know, because i also had the same issue and i fixed that in the above mentioned way.

  • Error in Leave Request

    Hi,
    We are using the standard Leave application -- HRESS_A_PTARQ_LEAVREQ_APPL and the application is working fine except for one employee. Seems like Basis issue but it must be for all the employees. PERNR is mapped and all the master data is correct, Payroll area not locked, user is also not locked. Unable to find out the issue. reply will be appreciated.
    Regards,
    Abdullah khan

    Hi,
    There is no issue of authorizations as i have checked by assigning SAP_ALL.
    Category               ABAP Programming Error
    Runtime Errors         TIME_OUT
    ABAP Program           CL_PT_REQ_ATTABS_ITEM_SELECTORCP
    Application Component  PT
    Date and Time          28.03.2014 16:34:37
    |Short text                                                                                        |
    |    Time limit exceeded.                                                                          |
    |What happened?                                                                                    |
    |    The program "CL_PT_REQ_ATTABS_ITEM_SELECTORCP" has exceeded the maximum                       |
    |     permitted runtime without                                                                    |
    |    interruption and has therefore been terminated.                                               |
    |                                                                                                  |
    |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                                                                                    |
    |    After a specific time, the program is terminated to make the work area                        |
    |    available to other users who may be waiting.                                                  |
    |    This is to prevent a work area being blocked unnecessarily long by, for                       |
    |    example:                                                                                      |
    |    - Endless loops (DO, WHILE, ...),                                                             |
    |    - Database accesses with a large result set                                                   |
    |    - Database accesses without a suitable index (full table scan)                                |
    |                                                                                                  |
    |    The maximum runtime of a program is limited by the system profile                             |
    |    parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this                 |
    |     time limit is                                                                                |
    |    exceeded, the system attempts to cancel any running SQL statement or                          |
    |    signals the ABAP processor to stop the running program. Then the system                       |
    |    waits another 60 seconds maximum. If the program is then still active,                        |
    |    the work process is restarted.                                                                |
    |How to correct the error                                                                          |
    |    Programs with long runtime should generally be started as background                          |
    |    jobs. If this is not possible, you can increase the system profile                            |
    |    parameter "rdisp/max_wprun_time".                                                             |
    |                                                                                                  |
    |    Depending on the cause of the error, you may have to take one of the                          |
    |    following measures:                                                                           |
    |    - Endless loop: Correct program;                                                              |
    |    - Dataset resulting from database access is too large:                                        |
    |      Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table                      |
    |      (for example);                                                                              |
    |    - Database has unsuitable index: Check index generation.                                      |
    |                                                                                                  |
    |    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:                                                                                     |
    |                                                                                                  |
    |    "TIME_OUT" " "                                                                                |
    |    "CL_PT_REQ_ATTABS_ITEM_SELECTORCP" or "CL_PT_REQ_ATTABS_ITEM_SELECTORCM008"                   |
    |    "SEL_REQS_BY_INFOTYPE_DATA"                                                                   |
    |                                                                                                  |
    |    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.         

  • ESS Leave request screen giving a critical Error in production server

    Friends,
    We are in a critical face of ESS implemetation.
    We are doing an ESS MSS implementation for country grouping 99.
    When we moved our changes to production server after succesful testing in quality, getting the following Critical error for Leave Request Screen.
    java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
         at java.util.ArrayList.RangeCheck(ArrayList.java:512)
         at java.util.ArrayList.get(ArrayList.java:329)
         at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:272)
         at com.sap.aii.proxy.framework.core.AbstractList.get(AbstractList.java:230)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCList.get(DynamicRFCList.java:281)
         at com.sap.tc.webdynpro.progmodel.context.Node$ModelElementList.getElement(Node.java:2543)
         at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:621)
    Other areas like personal Info & who is who are working fine.
    Leave request was working fine in Development and Quality servers and it never worked in Production server.
    It worked fine with same config, with same master data and same employee & org structure in quality server.
    We tried the following things:
    1. Checked and confirmed the sequence of transports for configs and Developments to Quality and Production.
    Even compared the table level entries and ABAP codings B/n dev and Production. All are same.
    2. Moved the workflow changes to production and activated the same. No change found after that.
    3. Gave SAP all authorization in R/3 and full authorization from portal side as well.
    4. Assigned the userid to different employees and checked the masterdata of employees.
    5. Checked the note 1388426.Every thing mentioned in the note is there in the system.
    6. Verified Rule groups and WEBMO feature are correct and same as in quality.
    As our go live date is very near, request your help .Thanks in advance for your help.
    Regards,

    Customisation of Leave request is mising in your system, please check the rule group using PTARQ.

  • ECC 6.0 - Leave request show duplicate entries one with ERROR status

    Dear All,
    We have implemented standard Leave request process, we are facing the issue as mentioned below, Its not happening for all the time, however we want to what scenario   this problem will arrives.
    Problem description:
    E.g. Staff applied annual leave on 10.06.2010, the leave request will sent for approval , after the approval of the leave ,every 30 min. we have scheduled a job which will execute standard program RPTARQPOST to post a leave request to IT2001.
    After the approval when staff go into ess and see leave request details under "Show Overview of Leave" and its shows as 2 records for the same period one with APPROVED and another one with ERROR.
    Type of Leave   From         TO                    Status                      Used
    Annul

    Hi Annul,
    Please check SAP Note 986003 - ESS LEA: Incorrect ERROR status for records in RPTARQPOST.
    May be relevant for your case.
    Regards,
    Dilek

Maybe you are looking for