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

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,

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

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

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

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

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.

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

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.

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 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 while trying to delete leave request

Dear All,
When trying to delete a leave request via ESS Portal, system is displaying the following error message:
"No Customizing for status type ARQ, status Posted and transition event Delete."
In the workflow log, Document Status is POSTED and Workflow Status is COMPLETED.
Kindly let me know if any other information is required.
Any pointers to resolve the above issue will be highly appreciated.
Regards,
Rahul

Hi Rahul,
Please check the below threads which may help you.
Re: Cancellation Leave request
Re: Leave request deletion problem
Thanks & Regards,
Sandip Biswas.

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

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

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

In ESS-Leave Request -A critical error has occured.

In ESS when tried to enter the Leave which is under Leave request the below error occured:
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.
CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.hr.lea.blockcale.FcBlockCale.getBcData(FcBlockCale.java:232)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCale.getBcData(InternalFcBlockCale.java:250)
     at com.sap.xss.hr.lea.blockcale.FcBlockCaleInterface.getBcData(FcBlockCaleInterface.java:135)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface.getBcData(InternalFcBlockCaleInterface.java:224)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface$External.getBcData(InternalFcBlockCaleInterface.java:276)
     at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:261)
     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:150)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java: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:150)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:219)
     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.aii.proxy.framework.core.BaseProxyException: CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.pt_Arq_Eecale_Get(LeaveRequestAdaptiveModel.java:434)
     at com.sap.xss.hr.lea.model.Pt_Arq_Eecale_Get_Input.doExecute(Pt_Arq_Eecale_Get_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 60 more

I found out the solution and solved this issue.
Deleted the leave request which was created with error i.e: from the custom table zxx_vacr noted down the id initiater ( which had error) and in the Test Environment for Leave request (PTARQ) gave the PERNR and deleted the documents ( gave the id iniater in the document status ).
To check the error work flow go to SWIA and check for that Workflow (Leave) raised by the PERNR at that duration ( check in IT2001 for the duration) and give it here.
After deleting it check in the portal for the leave request.

JCO Error in leave request.

Similar Messages

Maybe you are looking for