ESS/MSS Leave Request Issue
Hello All Experts
We have implemented ESS/MSS. Everything is working fine except the Leave Request approval. The approval request comes to the approver's inbox.When we try to open the approval request, the webdynpro application is getting but there is no data in the same. I mean the webdynpro application which is launched is blank.
Could anyone please try to help me how to make this webdynpro application up and running ?
We are using EP 7.0 with ECC 5.0
TIA,
Vivek
Hi Chuckie/Ton Groot,
As mentioned in post by Ton Groot,
I navigated to System Administration --> System Configuration --> Detailed Navigation --> Universal Worklist Workflow à Universal Worklist - Administration
I get a list of
Universal Worklist Systems
System Alias Connector Type Action Activate
AdHocSystem | AdHocWorkflowConnector | | Deactivate
SAP_ITS_XSS | WebFlowConnector | Re-Register | Deactivate
ActionInbox | ActionInboxConnector | | Deactivate
When I click on Re-Register button under Action, I get the following message
Item type registration was successful for the following systems:
- SAP_ITS_XSS (WebFlowConnector)
I have also cleared the cache by navigating to Cache Administration Page
Still the issue remains.
TIA,
Vivek
Similar Messages
-
ESS: UWL Leave request issue
Hi folks,
We are on EP 7.0 SP13 wit ESS/MSS 600 SP11 (for ERP2005) .
We configured ESS Leave request and facing the below issue.
When an employee takes leave with the leave request application and the manager rejects/approves this leave request,
a work item is send in the UWL Inbox of the employee. Processing this work item leads to the following error:
Application error occurred during request processing.
Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'com.sap/ess~lea' and application 'LeaveRequest' are not deployed on the server. Please check the used URL for typos.
Exception id: [0018FE28A06E006500000070000032B50004463FEC45E404]
I've checked the SWFVISU transaction and changed the package name of workflow task 'TS12300116' to 'sap.com/esslea', initially, it was 'com.sap/esslea'. Though i make this change and re-register the UWL system, i still get the error when opening the task from UWL Inbox
All ESS/MSS services/webdynpros are deployed without errors.
Does any body have an Idea ??
Thanks
KarthikHi Karthik,
The error is because in SWFVISU transaction, where the Workflow task is linked with the Leave request approver application ,the package name is wrong.
The task for approval process is TS12300097.
In SWFVISU,
Application name is : LeaveRequestApprover
Package : com.sap/ess~lea
If you notice,the package name mentioned here would be com.sap.xss.hr.lea.appl. Please correct it to com.sap/ess~lea.
You can also check out note 779075
Hope this solves it.
Regards
Reshma -
I am working ESS/MSS, we are deployed all the Business packages in the portal and once we open Leave request application
"There are no Customizing settings for absence type"
The above Error displayed,is there any configuration is required for R/3. if yes, can any one please help me
Regards,Hi,
Have you configured the basic settings in TM like Absences, Attendances, AQ types. To achieve the absence types in ESS, you need to configure the absence types in R/3.
Good Luck
Om
Reward it, if u feel helpful. -
hi ppl,
I am working on ESS Cancel leave request work flow
can anyone tell the Abap class and event for triggering this work flow.
Regards,
S.DheepakHi jayanthi,
I have already checked all the confugurations steps in PTARQ, this navigates us to the path below as you mentioned
ESS -> Service Specific Settings -> Working Time -> Leave Request -> Processing process-> specify processing process for types of leave
in that Process request using workflow
1)WF ID of New Request
2)WF ID of Cancellation Request
3)WF ID of Change Request
The value assigned
1)New Request: 12300111
2)Cancellation Request:01000109 <> 1000109(one more thing i found whenever i give entry 01000109 for cancel the value is saved as 1000109. )
New Request working fine using ws12300111.
change working fine using ws12300111.
Cancellation of leave which is not approved also working fine using ws12300111.
Hi jayanthi,
I have already checked all the confugurations steps in PTARQ, this navigates us to the path below as you mentioned
ESS -> Service Specific Settings -> Working Time -> Leave Request -> Processing process-> specify processing process for types of leave
in that Process request using workflow
1)WF ID of New Request
2)WF ID of Cancellation Request
3)WF ID of Change Request
The value assigned
1)New Request: 12300111
2)Cancellation Request:01000109 <> 1000109(one more thing i found whenever i give entry 01000109 for cancel the value is saved as 1000109. )
New Request working fine using ws12300111.
change working fine using ws12300111.
Cancellation of leave which is not approved also working fine using ws12300111.
when i delete a approved leave request unable to do.
thanks in advance
Dheepak -
ESS leave request issue?
Hi Gurus,
I have an requirement where in which if employee enters (Employee total working hours is 8 hours per day) 4 hours in the hours column of the ESS leave request page.
He has to get 0.5 days in the no of days column in the ESS leave request page.
Then if employee choose the leave type as Sick Leave (It will be generic in standard ESS) he has to get the column where in which he can enter the reason for the same.
EP 7.0 and backend is ECC6.0 and am using ESS/MSS 60.2 business package.
Is there any patch is avaiable to incorprate the above requirement into standard ESS/leave request page.
Higher points will be rewarded for valuble inputs.......
This is very urgent requirement............
Thanks in Advance,
DharaniHi,
Please check this blog:
Follow your leave request in Duet
Please refer to this document:
[Doc deleted 87 Nov 2012]
Please check this thread for leave request from ESS:
Leave request from ESS
Please check this wiki link for validation of leave request:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erphcm/validations%2bfor%2bess%2bleave%2brequest
Hope this helps.
Regards,
Mona -
Component Usage error in MSS Leave Request approval
Hi All,
We are getting the below mentioned error only for few users while approving the leave request in MSS.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
... 41 more
Kindly share your views on the same.
Thanks and Regards,
Vivek.Hi Anup,
Please find the complete Trace below.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; MS-RTC LM 8)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20080611120129.0000 (release=NW04S_13_REL, buildtime=2008-09-11:17:05:50[UTC], changelist=42127, host=pwdfm114), build date: Wed Nov 19 19:21:28 CET 2008
J2EE Engine 7.00 patchlevel 109044.44
Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation
Operating system AIX, version: 5.3, architecture: ppc64
Session & Other
Session Locale en
Time of Failure Sat Jan 02 12:26:56 CET 2010 (Java Time: 1262431616916)
Web Dynpro Code Generation Infos
sap.com/ess~lea
SapDictionaryGenerationCore 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/pcui_gp~xssutils
SapDictionaryGenerationCore 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pcui_gp~xssfpm
SapDictionaryGenerationCore 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
sap.com/pcui_gp~tecl
SapDictionaryGenerationCore 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:43[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0011.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:02:51[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0010.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:40:44[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:25[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:39[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0010.20061002105432.0000 (release=645_VAL_REL, buildtime=2006-10-21:15:41:32[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0011.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:00:20[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0011.20061227101814.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:05:13[UTC], changelist=431317, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
SapWebDynproGenerationCore 7.0011.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:08:35[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0011.20070125102926.0000 (release=645_VAL_REL, buildtime=2007-01-31:20:21:35[UTC], changelist=434634, host=pwdfm101)
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetFPMConfigurationUsageInterface(InternalFPMComponent.java:245)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.changeToExceptionPerspective(FPMComponent.java:861)
at com.sap.pcuigp.xssfpm.java.MessageManager.handleException(MessageManager.java:258)
at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:103)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModelInternal(BackendConnections.java:323)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.initBackend(BackendConnections.java:256)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.connectModel(BackendConnections.java:154)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.connectModel(InternalBackendConnections.java:237)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.connectModel(FPMComponent.java:841)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.connectModel(FPMComponent.java:1071)
at com.sap.pcuigp.xssfpm.wd.BackendConnections.init(BackendConnections.java:141)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalBackendConnections.init(InternalBackendConnections.java:233)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:182)
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:150)
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: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)
Thanks and Regards,
Vivek. -
ESS/MSS leave approve view is diaplaying as error
Hi All,
We are using ESS/MSS for leave request and approval process.
We did neccessary configuration for the same. I have created leave request in ESS successfully and the same request displayed as item in UWL/Task. When try to approve, by clicking the link, it throws an error.
The error details are : 503 Service not available
Error: -6
Version: 7000
Component: J2EE Server
Date/Time: Mon Jan 16 14:31:49 2012
Module: http_j2ee_mt.c
Line: 820
Server: eppilot_KHE_11
Error Tag:
Detail: Cannot reach external Application Server on eppilot:51111
When i try to preview the Iview 'leave reuqest approval' as a stand alone(from Content administration), its shows the approval view perfectly . even i tried to approve from their , its approving perfectly. But the Leave request approval view is not displaying when manager click the link to approve in UWL/Task.
Kindly help.
Thanks,
VenkatHi Andy,
Thanks for your reply.
As per the SAP Note 779075,
I have changed in SWFVISU same as below.
TS12300097 WebDynpro Java
APPLICATION LeaveRequestApprover
DYNPARAM wi_id=${item.externalId}
PACKAGE sap.com/ess~lea
TS12300116 WebDynpro Java
APPLICATION LeaveRequest
DYNPARAM wi_id=${item.externalId}
PACKAGE sap.com/ess~lea
The application "LeaveRequestAdmin" is not released. Use transaction SWFVISU to delete the following entry:
TS12300104 WebDynpro Java
APPLICATION LeaveRequestAdmin
PACKAGE sap.com/ess~lea
1.After that , in Universal Worklist configuration, I have selected the row..system alias 'SAP_WedDYnpro_XSS' Connector type 'Web flow connector, clicked the re-register button. I got the folowing message :
Item type registration was successful for the following systems:
- SAP_WebDynpro_XSS (WebFlowConnector
2. After that i have cleared the cache.
But still i am getting the same error message, when i click the leave request item. Kindly help.
Thanks in advance. -
Error in ESS Szenario leave request after rejecting leave
Hi folks,
we getting an error in the ESS leave request application with using the workflow (WS12300111).
We have EP7 SP11 wit ESS/MSS 600 SP7 (for ERP2005) . All ESS/MSS services/webdynpros are deployed without errors.
If an employee takes holiday with the leave request and the manager rejects this leave request, a work item is created in the UWL box of the employee. Processing this work item leads to the following error:
Application error occurred during request processing. Details:
com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'com.sap/ess~lea' and application 'LeaveRequest' are not deployed on the server. Please check the used URL for typos.
Exception id: [C0000A7D0192002A0000000400000B7E000431AA883F1DCE]
But the application is ready deployed (the employee take this appl- to create the leave request
In the ERp2005 / HCM customizing, transaction SWFVISU the approval task TS12300097 uses application "LeaveRequestApprover" is working fine.
TS12300116 uses application "LeaveRequest" leads to this error... :-(((
Does any body have an Idea ??
Please help!
Thx marioHi Mark,
yes something like that - we solved this with a tipp from OSS/ SAP..
Using transaction SWFVISU, check the following entries and correct
these
where required:
TS12300097 Java WebDynpro
APPLICATION LeaveRequestApprover
---> CHECK THESE PACKAGE sap.com/ess~lea
TS12300116 Java WebDynpro
APPLICATION LeaveRequest
>CHECK THESE PACKAGE sap.com/ess~lea
The WF item who was running o.k. (check leave request) had the wrong entries :
TS12300097 Java WebDynpro
APPLICATION LeaveRequestApprover
---> CHECK THESE PACKAGE sap.com/ess~lea -> was com.sap ...
After changing this to sap.com -> the other service who had the error
runs now O.K. !! This problem was only on the EP7 system SP12 and
ESS/MSS SP8..other Portal system with NW7SP11 ESS/MSS SP6 had this
error not...
regards
mario -
Hi all,
I was trying to make some small changes in the leave request application when i got stuck up in an issue. In the Leave Request, underneath the Roadmap, there is an option to "Show time accounts". I just want to change its text to "Show ******". How can i achieve this?
Thanks,
ShyamHi shyam,
I am also working on <b>ess`lea</b> <b>leaverequest</b> modifications.
Can you please share your work with me,means can you guide me how to add new fields in leave request application.I think we should add new fields in VcFormEdit component --> EditView .
It will be very greatfull to you.
Regards,
Rajesh.N
[email protected] -
MSS-Leave Request Approval Error
Hello All,
We have implemented UWL within our organisation and we are using it for approving Leave request.The leave requests are appearing in the task list but when a user clicks on it he gets a error message as below.We are on EP7 sp12.
Application error occurred during request processing.
Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'com.sap/ess~lea' and application 'LeaveRequestApprover' are not deployed on the server. Please check the used URL for typos.
Exception id: [0017087D873900490000001F0000139000044508CF7E13ED]
We have checked 'com.sap/ess~lea' and they are working fine.
Has anybody encountered this message.
Regards
AjeyAre you able to run com.sap/ess~lea' and application 'LeaveRequestApprover'
from Content Adminustrtor -> WebDynpro -> Application
for the same user..
If this is Dev/Test system then assign Content admin roles and see if they are working for this user....
If answer is yes, then look for WAS properties of the system which you have used to register in UWl. If that is directing to WD applicatino server. If no, then please maintain the entries.
Hope this helps.
Rgds, -
ESS/MSS leave reques Enhancement
Hi,
I am trying to do some enhancement to ESS/MSS Development Component in the NWDS, but it is not getting reflected. can someone help me out to resolve this issue..??
Thanks
AngshumanHi Praveen,
Extended notifications for SAP Business Workflow notify users by e-mail or SMS about work items that need to be processed. Notifications are sent to the relevant user in the form of messages. At present, e-mail messages (HTML or text-only) and SMS messages are supported.
Well I would say its not the base for all mails but surely for notifications.You can send mails even without configuring it.You can try it out in dev by creating a simple workflow with mail step.For mails you need to maintain the SCOT settings and evn that is done by BASIS guys so...u need not worry about it.
Also , for extended notifications i would suggest you to go through this link
Link:[http://help.sap.com/erp2005_ehp_04/helpdata/DE/d5/581ee8d56f1247bf34cfcd66d16d81/frameset.htm] -
ESS LEA: Leave request, RPTARQPOST
Hi,
I read on some forum posts that the program (SE38) - RPTARQPOST has to be scheduled in order to update the status of leave requests and post to PA2001 after they have been approved.
I have not scheduled it, but in our system, when manager approves a leave request, it gets updated in PA2001 (PA30). I understand from our workflow consultant that table prarq_header is being updated with the status (sent, approved, rejected) through a step in the workflow.
Wondering if it is still necessary to schedule RPTARQPOST
Appreciate any advice.
Thank you,
Brgds,
Zubair
info:
Using ESS BP ERP1.0 on Enterprise Portal 7.0, backend ECC6
workflow template WS12300111Honestly speaking, I at my place have scheduled PTARQ for all the activities to be done. But you have done it through workflow. May be its a different way of doing. Really not able to say whether right or wrong.May be the Workflow consultant at your place is the right person to judge
-
Leave Request Issue in SAP Portal
Hi ,
We are using standard Leave Request Application for UK and Belgium.
In Edit Screen Sickness Leave text we have a drop down to select the type of leave.
In Edit screen its working perfectly, the type of leave which we have selected in dropdown box, these text is not getting passed to the to the Review screen.
We are using the same iView for UK and Belgium.For UK its working fine . The 'type of leave" text is passing to the review screen. This issue is only for Belgium users.
Can any one please let me know any country specific settings i have to do for this in SPRO.
Thanks
AlexiIs the text available in T554s,Please can you check this for these absences or
in v_t554s_web -
Any ESS Multilevel Leave Request
hi friends
I am working on Multilevel ESS Leave Request Workflow. Is there any standard workflow for multilevel approvals. I know the standard workflow WS12300111 but its only one level approval. I want to have multilevel approval.
Regards
vijayhi mike
Thanks for your reply.
I have developed multilevel leave request workflow. Am facing the problem in dynpro screen. As am using standared task TS12300097 used for approval. when i used this task the 1st approver get's the workitem in portal. After approval the workitem is moviing to the second approver. but when i come and check in the 1st approver's UML i can find the approved list in the dash board am again able to approve the leave. Is this a bug in standard screen?. Do we need to go for new customized dynpro screen development?.
waiting for your reply.
Regards
vijay -
In ESS/ MSS Leave should update w.e.f leave applied date
Hi All,
My client requirement is.....
Employee applied (on 30th April 2014) for future date i.e 20th May 2014 to 23rd May 2014.
Employee applied on 30th April 2014
Manager approved on 1st May 2014.
Once Manager approved it should not update IT2006 - Absence Quota.
It should update on 20th May 2014. After Planned work schedule,
Can we configure or not. (Standard SAP not support I knew this)
If Yes......tell me the a few configuration map.
Regards
AnokuIn standard there is no functionality to post the only current day leaves which are in APPROVED status.
Once this RPTARQPOST run in back ground it will post all APPROVED status records in IT 2001 / 2002.
In your case, you nee to make RPTARQPOST to Z and modify the code to include your business logic for posting only current day leave i.e begin date <= sy-datum leaves.
check the report in RPTARQPOST debug mode at below code lines.
IF ign IS INITIAL.
* Get requests having status APPROVED and ERROR
PERFORM get_requests
USING
c_arq_reqtype
CHANGING
req_tab.
ELSE.
* Get only requests having status APPROVED
PERFORM get_approved_requests
USING
c_arq_reqtype
CHANGING
req_tab.
ENDIF.
PERFORM process_all_requests
USING
cl_pt_arq_const=>c_app_id.
In above code line you can remove the records in table req_tab with your validations before calling the PERFORM process_all_requests.
Maybe you are looking for
-
Datas from info record should not overwrite BAPI_PO_CREATE parameters
Hi, I intend to pass the netprice value while posting PO through BAPI_PO_CREATE. but the values from info record overwriting the parameters supplied. Please guide me how to avoid this overwritting. Thanks, Vempalli
-
Version 3.6.18. Running on Windows XP Pro. (kept current) This happens on a variety of pages. I get the little Loading thing in the tab, with the circle moving. So I X out (to exit Firefox). When I go to restart I get the error message "Another versi
-
Grouping issue- LiveCycle Designer 7.0
Hello, We are trying for the past few days to create a dynamic PDF that uses an XML Data source to parse and display grouped information, We have taken a look at the samples but none of them seem to be helpful in this case. For ex. If we have a XML d
-
Sideloaded Amazon Kindle - where's the app on my PB?
Hi there, I downloaded Amazon Kindle from Good E Reader. Went fine, opened on my PB after download. However, I'm afraid to close it, as there is no app anywhere! Yes, I've scrolled up, down, left and right, and nothing. How do I find it? Where could
-
Nexus 7K F2 modules Multicast support
I have some questions related to F2 multicast support: Cisco multicast configuration guide says that "F2 modules do not support any form of IPv4 or IPv6 tunnels" what dose it means? Are they referring to MDF and GRE tunnels? I know PIM-BiDir is not s