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
Similar Messages
-
Dear Team,
I am facing one issue in ESS, in that only one service(Employee Search) showing critical error.
Please check attachment once
Thanks,
SrinivasHi Srivas,
And also ask your portal consultant to check the RFC destinations was created or not and also check the ping test for RFC.
Regards,
Anil -
ESS Leave request Visual Parameters for the Tasks
Dear All,
I have a basic dought about ESS Leave request Workflow process.
We have used WS9100004 TS12300097 for this Visual Parameters are
Visual Parameters Visual Parameter Value
APPLICATION LeaveRequestApprover
PACKAGE com.sap.xss.hr.lea.appl
For Task TS12300116
Visual Parameters Visual Parameter Value
APPLICATION com.sap.xss.hr.lea.appl
PACKAGE LeaveRequest
In the same way I have to use another workflow for canceling the leave request
Workflow number is WS12400005 in which I have used
TASKS TS 12400028, TS04200011, TS04200007, TS01000162, TS04200008
For above tasks what are the visual parameters I need to maintain.
Visual Parameters Visual Parameter Value
APPLICATION ?
PACKAGE ?
Please suggest me on this.
Regards,
Kishorekumar.RHi Siddharth Rajora,
With you r help i was able to resolve the issue. Thanks for the information.
Regards,
kishore. -
ESS Leave Request error when launched from the portal
Hi guys
When i try to launch the Leave request from ESS tab in portal i am getting the following error
I have checked the backend and i can process a leave request from there. It is failing on the portal side.
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
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)This error occurs due to the following customisaton, Please
check this :
Check the Feature WEBMO is activated or not?
Is the pernr assigned correctly?
Please can you check if the Pernr used
has correct information like It0105 etc, also the rules are
correctly defined.
For the Employee, First of all check the Period Work Schedule also
the Quotas of the pernr needs to maintained in 2006, Please do
this customisation and it should solve the issue.
Maintain the absence quota in the IT2006 and then try once.
Also make sure that the Settings in Webmo and PTARQ etc all is done
The pernr belongs to the a Rule and have absences defined for him. -
Team Calendar in ESS Leave Request (Error)
Hello,
we are configuring the Leave request in ESS and MSS in the portal (EP 7.0, ECC 6.0, latest release). The Leave Request process and application, Time accounts and Workflows all working fine and the customizing is done in the IMG.
Only under ESS -> Leave Request -> Team Calendar we are getting this Error:
java.lang.Exception: No Views found: Missing customizing
at com.sap.xss.ser.tecl.fc.FcTeamCalendar._checkData(FcTeamCalendar.java:799)
at com.sap.xss.ser.tecl.fc.FcTeamCalendar._getData(FcTeamCalendar.java:751)
at com.sap.xss.ser.tecl.fc.FcTeamCalendar.initialReadData(FcTeamCalendar.java:385)
at com.sap.xss.ser.tecl.fc.wdp.InternalFcTeamCalendar.initialReadData(InternalFcTeamCalendar.java:319)
at com.sap.xss.ser.tecl.fc.FcTeamCalendarInterface.initialReadData(FcTeamCalendarInterface ....etc.
I have maintained the Customzing in IMG for Team Calendar as the following:
00000001 SAP Standard 01.01.1800 31.12.1999 Approval Mode View Group (MSS) MSS_LEA_EE
00000001 SAP Standard 01.01.1800 31.12.1999 Attendance Overview View Group (MSS) MSS_LEA_EE
00000001 SAP Standard 01.01.1800 31.12.1999 Administrator Mode View Group (MSS)
00000001 SAP Standard 01.01.1800 31.12.1999 Request Mode View Group (MSS) ESS_LEA_EE
00000001 SAP Standard 01.01.1800 31.12.1999 Team View Mode View Group (MSS)
Would you please help?
Many Thanks and Regards,
NazihHi Bryan,
1. First of all make sure that the Internet Graphic Server is activated + up and running on your SAP ERP System (see also SAP Note 704604)
2. Then you have to set the Customizing Parameters for the Team Calendar in IMG (SAP ERP System):
a. Tcode: PTARQ -> Customizing
b. Working Time -> Team Calendar
c. Node Create Rule Group -> Example: 00000001 (SAP Standard)
d. Node Adjust WEBMO Feature -> Assign all Nodes to your Rue Group
e. Node Spec. Absecne to be displayed -> Here i assume you have set up the Leave Request Process and WF already, so you only need to assign this to your Rule Group:
Example.
00000001 SAP Standard 01 0100 Leave 01.01.1800 31.12.9999
f. Node Select Employee -->
Here you need to set the Group of your Employee which should be displayed in the team calendar:
Example.
00000001 SAP Standard 01.01.1800 31.12.9999 Approval Mode View Group (MSS) MSS_LEA_EE
00000001 SAP Standard 01.01.1800 31.12.9999 CATS Approval View Group (MSS) MSS_LCA_EE
00000001 SAP Standard 01.01.1800 31.12.9999 Attendance Overview View Group (MSS) MSS_LEA_EE PPOME_P
00000001 SAP Standard 01.01.1800 31.12.9999 Administrator Mode View Group (MSS) MSS_LEA_EE PPOME_P
00000001 SAP Standard 01.01.1800 31.12.9999 Request Mode View Group (MSS) ESS_LEA_EE
00000001 SAP Standard 01.01.1800 31.12.9999 Team View Mode View Group (MSS) MSS_LEA_EE PPOME_P
---> Tipp: Check all Settings and Leave Types also with an HR Consultant before maintaing these in the ESS Customizing...
Regards,
Nazih -
ESS Leave Request - Error while creating a leave record
Hi Friends,
Some of the ESS leave request(not workflow) has gone into error when the system tryies to create a leave record in background. I can view these error request using the report RPTARQDBVIEW. This happens when the background program(PTARQPOST) tries to create a leave record. In some cases the status of the leave request is set to error(the status attribute of the container element(Req) has the value Error),but we are not able to find what is actual error.Is there any log where we can check what is the problem? Please advice.May be
Internally the pernr might not be locked or some one may be maintaing the pernr for whom you are trying to post. -
Hi Experts,
We have implemented ESS in our organisation.
In the leave request view i am getting the following error.
For ex : If the leave request pending is 10.
If i approved 1 it should reduce to 9 .....Its getting refreshed as 9 in R/3end but in the portal page its remains the same(Showing pending request : 10)
Can anyone pls throw some light on this issue.
Thanks in Advance,
DharaniHello,
Please, I have the same issue!
How did you resolve this problem?
Thanks in advance -
ESS Leave request: specify processing process for an auto approval presence
Hi experts,
My client wants to use a type of presence in ESS (Mobile working) to be requested by the employee without any worklow approval. I just need them to automatically stay on status approved.
I was trying to configure this requirement but system does not allow me to uncheck box "Requests have to be approved". (See links).
http://screencast.com/t/iGblIQ9DKy
http://screencast.com/t/f4PgbmDvq
Any suggestions?
Thanks in advance.
Best,
ASyeah there is a bug for this, implement the note 1451738 to fix it
requests to be approved, should be unchecked for automatic approval as you said is correct of achiveing your requirement!
Edited by: Siddharth Rajora on Nov 3, 2011 4:51 PM -
Does the SCOM 2012 agent "look back" in the logs before the service was started?
Does the SCOM 2012 agent "look back" in the logs before the service was started?<o:p></o:p>
We raised this question to our Microsoft rep back when we migrated to SCOM 2007. We wanted to know if SCOM would alert on errors generated before the Heath Service started. For example, errors
logged before the service is started on reboot (which is when some critical errors are logged). We also wondered what happens when the service is restarted...would errors during the same window be missed?
If I remember correctly the MS response was that the agent looks back on startup/restart based on a timestamp of some kind. We did some testing that seemed to confirm this information. I've
recently encountered several instances of errors generated while the service was stopped (primarily during boot up) where SCOM failed to alert on the error.
Can anyone confirm how the SCOM 2012 agent deals with errors generated before the service starts on boot and during service restarts?I would suspect it's with watermarks as it has been in the past. What you should look into is if these alerts you were expecting are event based, and if there are rules set to alert for these conditions. If so, and you don't get an alert,
then you can bring that up with your msft rep. However, they should be caught.
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.
There is a watermark. If the agent has been down for a significant period of time, the watermark may not apply, as the log would have rolled - but the entire log will still be processed regardless of what has already been discarded in the log. This may cause
some problems if a monitor picks up an unhealthy state, and the healthy state log entry has already been flushed. In this case, you need to reset health on that particular monitor, or just flush the cache on the agent to start anew.
Jonathan Almquist | SCOMskills, LLC (http://scomskills.com) -
ESS leave request workflow WS04200009...error-u r not one of the possible a
hi all
i m working on ESS leave request workflow WS04200009....but when i create a leave request from user's A/c i got an error at that leave req create screen that's-- u r not one of the possible agent of the task...
pls do help if anyone no solution.
thanks in advance .
RajTry making this task a General Task..use tcode PFTC and change the attribute of this task to a general task. That might help solve the issue.
-
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 moreI 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. -
A critical error has occured. Processing of the service had to be terminate
When manager wants to approve the employee leave request its giving following 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.
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.
Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE
Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE:com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Access via NULL object reference not possible., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
at com.sap.xss.hr.lea.form.FcForm.getCustomizing(FcForm.java:1020)
at com.sap.xss.hr.lea.form.FcForm.onInit(FcForm.java:417)
at com.sap.xss.hr.lea.form.wdp.InternalFcForm.onInit(InternalFcForm.java:2053)
at com.sap.xss.hr.lea.form.FcFormInterface.onInit(FcFormInterface.java:184)
at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface.onInit(InternalFcFormInterface.java:1911)
at com.sap.xss.hr.lea.form.wdp.InternalFcFormInterface$External.onInit(InternalFcFormInterface.java:2007)
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.hr.lea.worklist.VcWorkList.onInit(VcWorkList.java:267)
at com.sap.xss.hr.lea.worklist.wdp.InternalVcWorkList.onInit(InternalVcWorkList.java:363)
at com.sap.xss.hr.lea.worklist.VcWorkListInterface.onInit(VcWorkListInterface.java:164)
at com.sap.xss.hr.lea.worklist.wdp.InternalVcWorkListInterface.onInit(InternalVcWorkListInterface.java:144)
at com.sap.xss.hr.lea.worklist.wdp.InternalVcWorkListInterface$External.onInit(InternalVcWorkListInterface.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.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(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Access via 'NULL' object reference not possible., 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_Customizing_Get(LeaveRequestAdaptiveModel.java:392)
at com.sap.xss.hr.lea.model.Pt_Arq_Customizing_Get_Input.doExecute(Pt_Arq_Customizing_Get_Input.java:137)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
... 47 more
kindly help ASAP,Hi,
Did you give enough authorizations to the user at the beack end.
Just Try giving SAP_ALL authorizations and check.
Regards,
Santhosh -
Error after second level approval in ESS leave request
Hi Experts
I am using custom workflow for Ess Leave request process which is copied from WS21500001.
I have added custom class methods to change status from approved to sent.
Then another method i have set next appovaer.
The problem i m facing is that I am getting an error on portal after second approval approves the request.
i.e Field syomol has not been assigned yet.
from st22 i found its generating from
Include LPT_ARQ_REQUEST_UIAF06 - Form execute_approver_update
By debugging i found that Its not getting next approval with status T as there is only first approval with status 'A'
This results in unassigned field symbol. and then error.
Please help me resolve this issue.
Please confirm why next approver is not found in method.Hi All
Thanks for your reply.
I checked why it was giving a dump.
This execute_approver_update subroutine takes approval data from table ptreq_approver .
I filled this with resp actor id after request is approved and status is changed to sent.
For every emp its unique actor id is saved in ptreq_actor table agaist his pernr.
SELECT SINGLE actor_id FROM PTREQ_ACTOR INTO actor_id WHERE objid = nextApprover_pernr.
wa_appr-mandt = sy-mandt.
wa_appr-request_id = Request_ID. "Req.requestID ( from Workflow )
wa_appr-version_no = version_no. "Req.Version ( from Workflow )
wa_appr-seqnr = seqnr. "Same as version no but in char
wa_appr-approver_ins = actor_id. "Employee actor id from ptreq_actor
wa_appr-status = 'T'. "Manual
append wa_appr to it_appr.
INSERT PTREQ_APPROVER FROM TABLE it_appr .
commit work and wait.
This resolved my issue.
Thanks -
Hi
In ESS when the User is trying to click on Leave request - Error displayed as below :
error displayed as : "A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost. Please contact your system administrator. User HPSAPHR4 does not exist in this period User HPSAPHR4 does not exist in this period: com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User HPSAPHR4 does not exist in this period at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111) at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:121) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:203) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:181) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:229) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:183) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:243) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:774) at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:261) at
siriIn addition to checking if employee is active etc,, you need to check that the user is connected to an employee. This happens in Infotype 0105 subtype 0001. The easiest way to check this may be via SE16N. Check table PA0105 and the usernam in field USRID.
BTW - the eror you describe will also happen if the user tries to access own data in portal.
The most usual error is the missing of IT0105 in my experience.
/Kirsten -
ESS: Leave Request - How to use a custom Leave Workflow?
Hi Experts,
I am implementing ESS 1.0 for mySAP ERP05. I have a custom workflow for Leave Request which I want to use for the ESS Leave Request. Can someone tell me what are the configuration steps required for this?
I have already performed the following activity:
SPRO --> Personnel Information --> ESS --> Service Specific Settings --> Working Time --> Leave Request --> Specify Processing Processes for Types of Leave
Here I have defined the WF ID of New Request as the custom Workflow ID.
Now when I trigger the Leave Request from EP-ESS, the message comes that the request was sent successfully.
But in the backend no workflow gets triggered. I even tried to write an implementation for the BADI PT_ABS_REQ to trigger the custom workflow event, but still no activity in the ECC workflow upon submitting thwe portal request.
Can some one please advise.
Thanks,
ShobhitOhh.. So the standard WF also doesnt get triggered??
Are you sure u have done SWU3 config??
If u have, Try using SWU_OBUF to refersh the workflow buffer.
Try swi1 to check what is happening with ur WF.
Try login to requesters login ... SBWP ... check the outbox. Is there a WF with Error here.
Cheers!!
Ashutosh
Maybe you are looking for
-
I had an icloud account in 2009. We set it up as a family plan because my family had just changed from PC to Mac. We never used it and let the plan expire in 2010. My ical will not sync with my new iphone because it is linked to the family plan accou
-
Updating hybrid configuration failed - Kerberos authentication: The network path was not found
I'm configuring Exchange 2010 SP3 as a Hybrid server with Exchange Online. This is a single server running Exchange roles Mailbox, Client Access, Unified Messaging and Hub Transport. When I run the Manage Hybrid Configuration, I receive the following
-
Java.lang.NoSuchMethodError when try to use RDBMS WLI adapter sp2
Hi, We have encountered a problem when trying to use the latest version of the WLI RDBMS adapter downloaded from the website. This adapter comes as an ear file of size 4026K. Has anyone been able to get this version to work?? Was using the earlier ve
-
Any hopes for isync 3.0 connect 5310 through usb?
bluetooth is darn slow >!!
-
How to user Drill through URL ?!
Dear All , We are on EPM 11.1.2.1 3 tiers production servers . We applied ERPi path 11.1.2.1.501 with ODI 11.1.1.5 . Integration between ERPi , Hyperion planning and EBS R12 Everything is working OK . When I loaded data and enabled drill thought . Wh