Error in accessing Leave request

Hi Guys,
We are implementing ESS - MSS. I m trying to access leave request I m getting following error.
I have maintened 105 0001 infotype. ie assigned user to the ess user. Also given Essuser to SAP_ALL authorization.
And also I maintained webmo feature for my employee and employee sub group.
this is error I m getting
A critical error has occured. Processing of the service was terminated. Unsaved data has been lost.
Contact your system administrator.
Broken delta link - object type = id = portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.13.ess.employee_self_service/com.sap.pct.erp.srvconfig.13.lea/com.sap.pct.erp.srvconfig.13.fpmapplications/com.sap.pct.erp.srvconfig.13.LeaveRequestEnhCE_13/com.sap.xss.config.fpmviews/BlockCale.
com.sap.xss.config.FPMInconsistentObjectException: Broken delta link - object type = id = portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.13.ess.employee_self_service/com.sap.pct.erp.srvconfig.13.lea/com.sap.pct.erp.srvconfig.13.fpmapplications/com.sap.pct.erp.srvconfig.13.LeaveRequestEnhCE_13/com.sap.xss.config.fpmviews/BlockCale.
     at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:64)
     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.retrieveRelatedObjects(PersistentObjectManager.java:172)
     at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:132)
     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)
It would be grate full If some body help me to resolve this issue.
Thanks in advance
Sanju.

This issue has already been resolved earlier. Take a look here:
leave application delta link
regards, Lukas

Similar Messages

Error while raising leave request

Dear all,
I am getting error while raising Leave request over ESS...Task WS12300111 locked for instantiation.
As well as in MSS manager is not getting requests for approval..can anyone tell me on workflow front what shall be done.
Regards,
Rajasekar.

check the WF is a general task ie PFTC and user has authoriation, Are you using any custom code through badi, then enusre Start_WF method is implemented.

Error message for Leave request (Related to some Old Question)

Hi Experts, 
 
We are facing an Error when only 1 employee in the company opens his Leave request page, the same page is working for others perfectly. 
 
this Error is the same as the one in the below posts: 
 
1. Link: Re: Error message for Leave request 
 
and I tried going through their solutions such as: 
 
1. Please check if you have the leave config done on ECC side under Personnel Management --> Employee Self services --> Service Specific settings --> Working time --> Leave request . 
2. At the least you should have assign the default rule to your PSG to the standard leave type given. Otherwise create your own rule groups and Specify Processing processes for type of leave set up. 
3. explicitly activate WEBMO Feature although it was activated 
 
But the Error is still coming for this specific Employee, even though his Vacation Quota is created and available for deduction. 
 
Please Help me in solving this issue. 
 
Regards, 
Abdulrahman

Index: 0, Size: 0:
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
 at java.util.ArrayList.RangeCheck(ArrayList.java:507)
 at java.util.ArrayList.get(ArrayList.java:324)
 at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:268)
 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:2549)
 at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:621)
 at com.sap.tc.webdynpro.progmodel.context.Node.setLeadSelection(Node.java:753)
 at com.sap.xss.hr.lea.form.FcForm.setLeadSelectionForSubtype(FcForm.java:700)
 at com.sap.xss.hr.lea.form.FcForm.setVisibility(FcForm.java:943)
 at com.sap.xss.hr.lea.form.FcForm.prepareCommand(FcForm.java:308)
 at com.sap.xss.hr.lea.form.wdp.InternalFcForm.prepareCommand(InternalFcForm.java:2041)
 at com.sap.xss.hr.lea.form.FcFormInterface.prepareCommand(FcFormInterface.java:116)
 at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface.prepareCommand(InternalFcFormInterface.java:1887)
 at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface$External.prepareCommand(InternalFcFormInterface.java:1983)
 at com.sap.xss.hr.lea.form.edit.VcFormEdit.onInit(VcFormEdit.java:299)
 at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onInit(InternalVcFormEdit.java:1084)
 at com.sap.xss.hr.lea.form.edit.VcFormEditInterface.onInit(VcFormEditInterface.java:165)
 at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface.onInit(InternalVcFormEditInterface.java:204)
 at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface$External.onInit(InternalVcFormEditInterface.java:280)
 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:1288)
 at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
 at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:548)
 at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:592)
 at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:864)
 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.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:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

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

Error when opening leave request task in UWL

Hi,
I have a manager role and when I want to proceed the leave request tasks in the UWL, I get the following error message:
Error:     -6
Version:     7000
Component:     J2EE Server
Date/Time:     Thu Jun 10 17:58:01 2010
Module:     http_j2ee.c
Line:     820
Server:     erpqalas1_QE1_00
Error Tag:     {00015518}
Detail:     Cannot reach external Application Server on localhost:50000
I have no idea where the problem comes from and no idea how I can solve it. I have no access to the serve but I can ask the administrator to check a few points for me.
Can anyone give me a hand on that problem ?
Thanks in advance fir your help.
Thibault

Please check this: http://help.sap.com/saphelp_nw2004s/helpdata/en/20/d0f83b4a91ce5ce10000000a11402f/frameset.htm
It might be helpful.
Edited by: Saud Shaikh on Jun 14, 2010 2:22 PM

Error while approving Leave request

Hi,
I am facing an issue while approving the attendance request of an employee via MSS. The error message comes for the leave request further in the queue.
Error Message : No read authorization for infotype 2001/5006(Annual Leave) for employee number between 07.06.2010 and 07.06.2010
Hoping for the early response.
Thanks!

I guess there is problem with the managers ID and the authorizations.
Try to check in SU53 and speak to security team to run the trace and provide the necessary authorizations

Error while approving Leave request from UWL

Hi Experts,
We are getting following error while manager clicks on Universal Worklist to approve Leave Request. On system we have assigned ess id to employee no. 43 in IT 105-0001 but it gives error message about employee no. 167 which has nothing to do with this leave request.
Please go through following ST22 error log..
Short text of the error message:
"No data exists in this period for infotype 0105 and employee 00000167."
Trigger Location of Runtime Error
 Program SAPLPT_ARQ_REQUEST_U
 Include LPT_ARQ_REQUEST_UIAF
 Row 186
 Module type (FORM)
 Module Name DUMP_IF_ERRORS
Source Code Extract
Line SourceCde
156 ENDCASE.
157
158 IF lock_indicator = 'X'. "ANK Note962342
159 status_ui = c_req_sent.
160 status_ui_text = 'gesendet'(s04).
161 endif. "ANK Note962342
162
163 ENDFORM. " set_request_status_ui_text
164
165 &----
166 *& Form dump_if_errors
167 &----
168 * text
169 ----
170 * -->MESSAGES text
171 ----
172 FORM dump_if_errors
173 USING
174 messages TYPE ptarq_uia_messages_tab.
175
176 FIELD-SYMBOLS:
177 <message> TYPE bapiret2.
178
179 LOOP AT messages ASSIGNING <message>.
180 IF <message>-type EQ c_message_error.
181
182 *Note 1168656 begin
183 * MESSAGE x999(53) WITH
184 * <message>-message
185 * <message>-type. "#EC *
>>>>> MESSAGE <message>-message type 'X'.
187 *Note 1168656 end
188 ELSEIF <message>-type EQ c_message_abend.
189 *Note 1168656 begin
190 * MESSAGE a999(53) WITH
191 * <message>-message
192 * <message>-type. "#EC *
193 MESSAGE <message>-message type 'A'.
194 *Note 1168656 end
195
196 ENDIF.
197 ENDLOOP.
198
199
200 ENDFORM. " check_errors
201
202 *&----
203 *& Form prepare_customizing_attibs
204 *&----
205 * text
Would really appreciate kind guidance to resolve the same.
Thanks.
Aashish

Hi Ashish,
Short text of the error message:
"No data exists in this period for infotype 0105 and employee 00000167
This clearly suggests that the employee data is not up to date.
Go to Tcode : PC00_M40_CLSTR
here 40 is the country coding or the Molga value for India. Like wise which ever country you work for, enter the country code there instead of 40.
Enter the pernr as 00000167 and you would find till which date the payroll for 167 has been run successfully.It has to be in green color.
If the payroll is not run till the period in which you are getting the error ( which obvisouly is what the error means) try running the payroll by going to the Tcode : PC00_M40_CALC or you can ask your HR team to run this payroll for you and you are good to go.
Good Luck!
Sandeep Tudumu

Intreperter Failed ERROR while cancelling leave request in ESS

Hi all,
We are facing this issue. When a person goes to ESS and tries to delete a wrongly raised leave request by pressing on trash button. We get a confirmation screen. In that after pressing on " Delete leave request" we get the following error
INTERPRETER FAILED
THE INTERNET TRANSACTION SERVER FAILED TO GENERATE THE RESPONSE FOR CURRENT REQUEST.
PLEASE CONTACT THE SYSTEM ADMINISTRATOR.
INTERNAL ERROR CODE: 0X2101
NOTE : This issue is only with certain employees.
Can anybody guide what should be done so as to resolve the above said issue.
Thanks in advance.
Gowri Shankar.

Hi,
This means 'no such input', I assume the Business HTML interpreter is
searching for a template that does not exist...
If you are using the internal ITS you will find information in the related trace
file, for the stand alone ITS in the agateX_sapjulep.trc.
Alternatively you want to set ~generatedynpro temporarily in order to see
which screen should be processed.
regards
Tobias

User unable to access Leave Request in Portal

Hello guys,
A user can't access the leave request via Enterprise Portal 7.0 - the view works perfectly with the other users thus the issue seems to be isolated to this particular user. IE version being used is IE 6.0 - so that shouldn't be the cause of the problem. Also, the roles have been cross-checked and synchronized with the other users who are able to access the Leave Request function. Yet, it appears the roles are correctly assigned
Could it be possible that this is a problem with the user's data? Which component should I also look into?
Thank you in advance!
Regards,
Jan

As for the IE patch problem, we're conducting an http-trace to check with this. But I see this as very unlikely, since the user also tried accessing it via a different workstation but the problem persists.
The 'resolution' for similar cases was to recreate a user account - even just a direct copy of the same user works. This could be an SAP application bug perhaps? The target is for a long term fix to the problem.
Thanks!
Regards,
Jan

Error in ess leave request

Hi Experts,
Please find the below error and guide me in this, as the employee has applied leave request and it is approved and posted in 2001 but the employees has an Option in ess to change his approved leave also but when he is trying to change the leave getting the error
The leave must not start before 22.04.2009
please help me in this.
waiting for your response..
Regards,
Shilpa

Hi,
GO to SPRO .
IMG Path:
Personnel Management  Personnel Administration  Personnel Data  Employee self service  Service Specific settings  Working Times  Leave Request  Processing Process  specify processing process of leaves types
Select one leave
in that "Start Date in the Past"
select 1st RADIO button "Processing Permitted to the recalculation Limit"
Save ...and check

Error in creating leave request

Hi ,
I am new to HR and i am working on Leave management.
When i am trying to crate a leave request workflow, i am getting the below error msg:
'Absence type 100 was not found in Customizing for 21.10.2010'
What could be the reason?\
Thanks,
Krish.

Hello Kishore,
You don't have the absence type created on either one of the two following tables.
T554S - This one is for the Absence creation on the backend in IT2001.
T554S_Web - This one is to show on the frontend framework of the Leave Request.
Regards,
Bentow.

500 internal error while approving leave request

Hi All,
One of my user when trying to approve leave request, he is getting the following error. it was working previously but suddenly thsi error has come
500 internal server error
Application error occurred during request processing
Details: com.sap.tc.webdynpro.services.sal.core.Dispatcher exception: The requested deployable object 'sap.com/ess~lea' and application 'leaverequestapprove' are not deployed
Can anyone advise on this error please!!!
Thanks!
Swarnaprakash

Dear Swarnaprakash,
Hope you are doing good.
Do make sure that all ESS related applications/services are running.
Please try to restart the applications this way:
1. start the telnet admin tool
telnet <hostname> 5<instnum>08
2. logon using the J2EE Admnistrator user
3. lsc (to list the available servernodes)
4. jump <servernode> (usually jump 0)
5. add deploy
6. start_app -all
Please have a look at the below for more information:
[http://wiki.sdn.sap.com/wiki/display/TechTSG/(JSTSG)(Telnet)DeployController+Commands]
and
[http://help.sap.com/saphelp_nwpi711/helpdata/en/45/0ad8e787652d6ae10000000a11466f/frameset.htm]
If the issue still persists, please check if all the SDAs have been deployed for ESS (SCA->SAP ESS and Business packages)
Thank you and have a nice day :).
Kind Regards,
Hemanth

Reg : Getting error while approving leave request

Hello Experts,
Manger is getting and error message u2018Work item 000000000000 cannot be readu2019 while
Approving the leave request of one his reportee. This error is triggering for only one
Reportee.
Experts please kindly help us.
Regards,
Raj

Hi Raj,
There are a number of issues that could cause this. Can you share your scenario (where is manager approving the request - via SAPGUI, ESS, MSS?) Are you using an SAP standard workflow?
Plus, there are lots of threads in SCN on this topic. Have you checked any of these?
Good luck,
Sue

MSS - Error while approving leave request

Hi,
I am facing an issue while approving the attendance request of an employee via MSS. The error message comes for the leave request further in the queue.
Error Message : No read authorization for infotype 2001/5006(Annual Leave) for employee number between 07.06.2010 and 07.06.2010
Hoping for the early response.
Thanks!
Edited by: Abhijit Chitale on Jun 2, 2010 6:52 AM
Edited by: Abhijit Chitale on Jun 2, 2010 6:53 AM

Hi,
This is an authorization issue which needs to be adjust in the ERP system. Please ask your basis administrator to help you. The authorization object is: P_ORGIN

Error raising new Leave Request

Hi guys,
Some of our users are trying to raise a leave request in ESS and getting an error
Use the input help to select an approver.
The only change that has happened is that we recently upgraded from ECC 5.0 to ECC 6.0. Other than that there has been no new development for our ESS/MSS.
There are only few users that are affected by this problem. The only thing different that I can see about these users is that in our org structure, the position that they're reporting to is not filled (no holder for that position), so they report to the next manager/approver above that position. This has never been a problem in past. ESS was able to get the next approver without any problems before the upgrade but now it seems like SAP only checks one level and since there's no holder of that position it gives this error. For any employees that report to a position that's filled don't have any issues.
I'm an SAP ABAP developer. Not too familiar with ESS/MSS or SAP config so please help me understand if this is a config issue or there's something else that needs to be done?
Thanks for your help.
Edited by: Mohammad Zeeshan on Aug 15, 2011 8:58 PM

Go to transaction PTARQ and check if you are able to determine the correct approver for these employees.
Also, from transaction PTARQ - Customizing :
Employee Self Service - Service Specific Settings - Working time - leave request - Processing Processes - Determine processing processes for each rule group
There is a configuration for "Determine Next Agent". This should be either "Line Manager" or "Last Agent, then Line Manager" (Refer to the field help for more information)
Also, you can utilize BADI PT_GEN_REQ for handling any special cases.
Thanks,
Shanti

Error in accessing Leave request

Similar Messages

Maybe you are looking for