Unable to approve leave request in ESS

Hi
    While trying to approve leave in ESS/MSSm getting the following error
    After clicking the link in SAP inbox / Universal Work List in MSS an error is encountered.
    In R3 we have analysed the error in ST22 transaction which says--
The current application triggered a termination with a short dump.
There is no data for infotype 0105,personnel no. 0 E .
Kindly suggest what to do..???

hi,
check the Infotype 105 subtype 0001 in Transaction PA30 for the Personnel no.
Regards,
Boobalan.

Similar Messages

Unable to Approve Leave Request

Hello guys, when trying to approve a leave request, this error was produced:
Please help. Is there an OSS Note to address this?
#1.5 #8AA34245D50201030000015B000A40B6000484C0320697E6#1271860914721#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#G22705#410961#####SAPEngine_Application_Thread[impl:3]_122##0#0#Fatal#1#/Applications/Xss#Java###null
[EXCEPTION]
#1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Message type   is unknown., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit(ModelHandler.java:206)
     at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit(InternalModelHandler.java:429)
     at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber(FcXssMenu.java:583)
     at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit(FcXssMenu.java:291)
     at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit(InternalFcXssMenu.java:455)
     at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit(FcXssMenuInterface.java:165)
     at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface.onInit(InternalFcXssMenuInterface.java:388)
     at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenuInterface$External.onInit(InternalFcXssMenuInterface.java:545)
     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.navi.FcNavigation.onInit(FcNavigation.java:313)
     at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigation.onInit(InternalFcNavigation.java:358)
     at com.sap.pcuigp.xssutils.navi.FcNavigationInterface.onInit(FcNavigationInterface.java:145)
     at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface.onInit(InternalFcNavigationInterface.java:142)
     at com.sap.pcuigp.xssutils.navi.wdp.InternalFcNavigationInterface$External.onInit(InternalFcNavigationInterface.java:282)
     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.roadmap.VcRoadmap.onInit(VcRoadmap.java:188)
     at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmap.onInit(InternalVcRoadmap.java:162)
     at com.sap.pcuigp.xssutils.roadmap.VcRoadmapInterface.onInit(VcRoadmapInterface.java:153)
     at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface.onInit(InternalVcRoadmapInterface.java:144)
     at com.sap.pcuigp.xssutils.roadmap.wdp.InternalVcRoadmapInterface$External.onInit(InternalVcRoadmapInterface.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.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: Message type   is unknown., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.pcuigp.xssutils.xssmenu.model.MenuModel.hrxss_Ser_Getmenudata(MenuModel.java:172)
     at com.sap.pcuigp.xssutils.xssmenu.model.Hrxss_Ser_Getmenudata_Input.doExecute(Hrxss_Ser_Getmenudata_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 76 more

Jan,
when the manager is trying to approve the leaves of his subordinate, he click on the single line approval request entry, and the RFC gets triggered. We usually think that the RFC will only run the particular leave request record and open the same for us. But internally the RFC reads all the pending leave request with the manager and then only displays the clicked record. When the RFC is triggered, if it finds some problem with some other record then it will fail and give the message as system faliure.
Even we had faced the same problem, In our case this employee had a leave request pending with him which belonged to some deleted employee code. As a result there was a system failure message. We deleted the workflow item from the list and the RFC was successfull.
This we check in T Code PTARQ, if u have full rights to this transaction then you can deleted the Workflow item from this list which is creating the problem.
but anywasy you can always check PTARQ for any Leave request related problems
Thanks n regards
Vedashree

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

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

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

Unable to process leave request due to WORKFLOW Status in ERROR in ESS Portal.

Dear Experts,
I'm facing an issue with the leave request of an user. The user has applied leave a week ago but still it has not got auto approved.While analyzing the database of leave request in PTARQ, it has been found that the WORKFLOW STATUS is in ERROR and the DOCUMENT STATUS is in SENT condition.
Kindly help me in this case.
Please refer the screenshot below.
Thanks & Regards,
Surendhar

Hi surendha,
That particular leave request might have gone into error because of worklfow issue at the point of time.
You can simply check with workflow if any issue with workflow was there in that tenure , leave request was being raised,
Now solution is to delete the leave request from PTARQ which is in SENT status and workflow is errored out.
Also take that work item id and get it deleted by workflow consultant (T code SWI5).
Once that leave request/work item got deleted , ask user to again apply leave and it would go to manager for approval.
Once leave request is approved, leave request would be in Posted status and will get updated in IT 2001.
Hope it helps you,
Thanks.
Priya

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

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

Error - While changing existing leave request from ESS

We are trying to use the standard leave request application in ESS/MSS. The basic required standard configurations are done. Since we wanted custom notifications, the related workflow is copied into custom workflow and we have included required custom notifications. The custom workflow is also configured properly.
Now, the standard functionalities like making leave request, triggering notifications, approving leave request and posting information into backend are working fine from the ESS/MSS.
When the employee tries to change the existing leave request (before approval) from ESS, at the 2nd step (Review and Send), it is displaying one error message General task: can be edited by all users. But, it still allows submitting the records.
Once it is submitted, the system throws one java error at the final step (after pressing SEND button) u2013 Failed to process request. Please contact your system administrator. - java.lang.NullPointerException. The complete error information is provided in the attached word document. Even though, it throws error the submitted data is getting saved into the backend.
Please help to solve this issue.
Thanks,
Prabhu
Edited by: Prabhu T on May 18, 2011 1:53 PM
Edited by: Prabhu T on May 18, 2011 1:54 PM

What custom notifications you require in leave request? We have all available in standard using Rptarqemail
First of all, the WF task should be set as
General task: can be edited by all users, which you have done presumably under task classification
Now, for checking purposes, can you check with standard WF in table v_t554s_web for one absence only?
ie WS12300111.
Please test this and let us know if you have errors
Also please check your custom WF whether it is working correctly or not?

Work flow for Leave request without ESS

Dear All,
For one of our client, we have configure workflow for leave request, first is it possible to do tht?
If so how to do it?, here we dont have ESS/MSS. Is there any standard workflow available?
Thanx

There is standard workflow task which give by SAP to approve leave request i.e. 12300111.
But I am not sure this workflow task will work with out Portal or not.

BSP error while applying a Leave request in ESS

Dear Friends,
Reposting an issue which I posted earlier in ESS Forum as I didn't get solution there and the issue is more technical and moved towards Netweaver applications.
While applying a leave request in ESS portal, I am getting an error page saying Business Server Page error.
Checked related SPRO Nodes: Both ESS UI5 and ESS (Java) nodes. They are maintained. Being HCM Functional Consultant, this error I am not able to analyze anyway. So asking Portal /Netweaver experts here.
Error screen attached-
My earlier thread posted in ESS forum
http://scn.sap.com/thread/3675714
Expecting a quick solution for this as I am stuck in this issue for last 4-5 days .
Regards,
Niladri

Sorted out . Detail can be seen in the Referal link. Closing this thread
Regards,
Niladri

UWL Filter causing error while approving Leave Request

Hi Guys,
We recently applied MSS SP17 and we changed our UWL filter BADI to SWK1 Function group - SWK_LOCAL_INBOX_GET.
The filter works fine, but when we try to approve leave request, it somehow calls this piece of code again and does not allow (DUMPS) BADI to set the filter saying - this field is not modifiable.
Has anybody seen this before. Can anybody let me know how to resolve the issue?
Regards,
SC

We added a code that if leave request calls this code...skip it.

While raising Leave Request on ESS: getting warning message displayed

Hi All,
When i am trying to raise a leave request from ESS i am getting the warning message displayed on the page as follows:
"Customizing for employee 00001153 does not exist"
I want this message to be removed.
Is this problem from R/3 end or any configuration needs to be done on ESS ?
Pls let me know how to remove this message.
Regards
Vijay

this message ensues when there is a missing customisation for the pernr, For example :
message is being displayed due to rule group customizing is missing
for a leave '0560' for which a leave record exists on the date
'14th March 2008'.
One possible solution would be to create a record in the customizing or delete the record from the application.
So please check the customisation of the absences, Quotas, rule group etc for this particular employee

Issue in Deletion of approved leave request using ws12300111

We are using Std workflow 12300111 and its working fine for new leave request and change leave request but when raise request for deletion of approved leave request the workitem created and info type updated automatically without seeking approval from manager. When you check the workflow log the agent determination happend and updated the info type 2001. This issue is in production system , At the same time if we tested the same scenario in QAS its working fine, ie its asking approval from Manager.
Pl help on this issue.
Regards,
Muthu

This is correct and intended functionality, NO WF IS triggered.
Let me explain, There is no WF triggered when APPROVED (NOT POSTED)
absence is deleted. This is standard, You can trigger a mail
which You had already done so. But there will be no WF triggered.
So if you notice
when the leave request is in status POSTED, it calls the workflow,
but if the leave request is not POSTED yet, it is doesnt call the
workflow.
There is no standard Workflow triggered when the Approved leave request
has been deleted by the employee!
This step should be configured by the customers as when to trigger a
mail to the Admin or Supervisor, when deletion or cancellation happens.
The workflow template is a simple template, You can modify
to suit their needs.

Multiple Approval Leave Request in Fiori

Hello,
Do we have multiple approval Leave request in Fiori and how do we enable it.
In EHP7 portal we have multiple approval and Fiori app should be in synch with the same. However, I could not find any option to enable the multi-level approval for leave request in Fiori.
Regards,
Divya

Hi Divya,
Are you talking about, multiple levels of approval in approve leave requests app in Fiori.
This totally depends on the workflow template you are using. If the workflow you use in your portal handles multiple approval, your approve leave request should allow the same too. Make sure you are getting the workitems in your sap inbox.
Let us know if this is not what you are asking for.
Regards,
Tejas

Approval Leave request for Wave2

hello guys:
For approval Leave Request for Wave 1, we need to define an Approval Scenario on the gateway side. Just want to know for Wave 2, where should we define the workflow task id ? should we define it on the ERP side ?
thanks
tony

Hi Tony,
The Workflow id definition remains same as wave 1.
On the gateway system.
regards,
Meghna

Can anyone Guide me Leave Request via ESS

Hi Experts
I am New to HR .Can anyone Giude me How to create Leave Request via ESS .I dont know anything about ESS.

http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
have a look.

Unable to approve leave request in ESS

Similar Messages

Maybe you are looking for