WS12300111: Leave Request Approval - Multiple Approvals
Hello.
I am part of a project, trying to implement ESS/MSS at a large international NPO Customer, and have encountered a problem.
I plan to use the WS12300111 Workflow for the approval process of Leave Requests, but since the customer in some situations require more than one approval, I have to enhance the workflow. At first glance it seems simple just to repeat the approval process, but since the request will be marked as approved at the first approval step, that will not work.
We are required to keep the implementation as close to SAP Standard as possible, so the portal guys tell me, that it is not really an option to make changes to the approval functions.
I have considered making the first approval a simple workflow task, that doesn't update the request itself, but since a rejection should update the request and trigger the Process Leave Request by Employee task, I really don't see that working either.
Any thoughts on the subject, or maybe even a solution, will be greatly appreciated.
Best regards
Poul Steen Hansen
Denmark
Hi dude,
Well, I might not be able to give you the coding, but I can explain it how to do this. Check the procedure.
Create a new BOR and create a new method - CHANGESTATUS.
Add one and only IMPORT parameter REQUEST of type PTREQ_HEADER-REQUEST_ID.
In the coding part, firstly lock your request using the FM - ENQUEUE_EPTREQ.
Then create an instance using the static method ca_pt_req_header=>agent->get_request which takes the REQUEST number as input and gives us the instance as OUTPUT.
Having the instance in hand, we can use the method initiate_state_transition to change the status of this method. Pass the SEND status as INPUT and get the new updated status as OUTPUT.
Unlock the leave request using the FM - DEQUEUE_EPTREQ.
Implement and release this method in your BOR.
And please make sure that your method is INSTANCE INDEPENDENT METHOD.
In your template create a Standard background task after your first approval step which calls this method.
Regards
<i><b>Raja Sekhar</b></i>
Similar Messages
-
Team Calendar in Read-Only Mode in Leave Request Approver Screen
Hi,
After lots of interaction and inputs in my previous thread,
Customization Done for 2 level approval of leave in ESS but Facing Problems
Our Team had decided to make the Team Calendar in Leave Request Approval Screen in Read-Only Mode (more precisely modus=TeamView)
My question is, is it possible to achieve the same, because instead of adding custom validations using Custom RFC, If it is possible to make the Team Calendar as Read-Only than it will help us to achieve our goals. Please do let us know that is it possible? and, if Yes, How to achieve it?
On leave request approval screen, we want Approver to take any action via "Show Worklist" and No User Action allowed on Team Calendar (Disabled but not InVisible).
Thanks,
Regards,
Tushar Shinde.This is the note 1484853 but as i said you cant see it unless you raise a Message for SAP , We have to add yout company to the note.
these are the steps
Symptom
In LeaveRequestApprover application, a higher level manager can
approve/reject a leave though he/she is not the owner of the approval
workitem (TS12300097). It happens when a higher level manager clicks on
the leave in the TeamCalendar launched from the LeaveRequestApprover
application.
Other terms
LeaveRequestApprover, TS12300097, prepare_select, WorkList,
LPT_ARQ_REQUEST_UIAF07
Reason and Prerequisites
Reason:- This is caused because the approve/reject button were not
restricted based on the logged in user.
Prerequisites:- IT105 entries for the backend PERNRs should be correctly
maintained.
You can check here
Object REPS LPT_ARQ_REQUEST_UIAF07
Object Header FUGR PT_ARQ_REQUEST_UIA
FORM PREPARE_SELECT
the note is meant for few customers only -
Problem in changing label in leave request approval screen
Hi All,
I have followed the SAP note 1234273 to change labels in our Leave request iViewin ESS and could do it successfullybut I could not able to know how to change the labels in Leave request approval screen because I have created a custom role and assigned Universal work list to it and assigned it to manager to view the leave requests applied. I navigated to Leave request approval screen via that role but ctrl + right click is not working on that page. Please suggest meCheck your uwl config, normally it is configured to directly call concerned(leave req approval) application hence your iview may not be getting called. You can try changing the uwl config to call PCD page instead of direct wdp application call.
~cheers
avadh -
UWL Leave Request Approval and Page Not Found
Hello Everyone,
We are in the process of implementing leave request with EP 70 ECC 6.0 and I am trying to implement the approval portion in the UWL. The workflow is appearing correctly in the UWL; however, when I click on the request in the UWL, I get a pop up with an error message that has "Page Not Found or Not Available." Does anyone know what could be causing this? I have read some of the other messages and transaction SWFVISU has been mentioned, but I am not sure how to set this up or if this would even resolve my problem.
Also, one of the reasons I have decided to go the UWL route is because the Leave Request Approval Web Dynpro has too many steps. Our users will not like having to click Approve, then Review, then Approve Request. If set up correctly, would the UWL have this many steps? I would imagine so if it is calling the same Web Dynpro, but I thought I would ask. Ideally I would like to have our Approvers select the Leave then choose approve and that be all they do.
Please let me know what you think.
Best Regards,
ScottDear Scott,
I am having this problem as well.
I did 2 things to fix this problem.
Firstly, please go to SWFVISU and check the visualization parameter for the below task.
TS12300097
TS12300104
TS12300116
Make sure it is package value is sap.com/ess~lea. It is not com.sap. Then re-register your UWL and it should be workin.
Let me know if it still does not and you may need to check your WAS setting.
Rewards point if useful
Regards,
Bryan -
How to create iView for Leave Request Approval for ESS Tab in Portal
Hello ,
I am new to Enterprise portal. I got a requirement for creating iViews.
How to create iView for Leave Request Approval for ESS Tab in Portal.??
Please give me clearly or provide any document.
Thanks
RishaHi Risha,
is it customized application ?
If so in SWFVISU transaction maintaain the entry .
Use transaction SWFVISU to prepare standard setting for your Workitem in the UWL. --Parameters for Work Item Visualization in the UWL.
Have a look at below link
http://help.sap.com/saphelp_nw2004s/helpdata/en/59/d516690e854c7090ae15bf492a869f/content.htm -
Dear All,
In the portal the manger will have to go through 4 steps in order to approve a leave request, can we eliminate some of the steps to decrease the amount of time required for a leave approval.
is it related to guided procedures ?
appreciate if someone can point me to the righ direction..Hi,
Please have a look at report RPTARQAPP .
This report will give u a list of pending approvals for a manager.
U can copy the code and use it in a BAPI, Create a new simple WD application to list out all the pending requests..
Then whats left ... approve... Thats very simple..call following code..
CALL METHOD cl_pt_req_badi=>initiate_state_transition
EXPORTING
im_request = request
im_event = event
IM_RET_VALUE = 0
IMPORTING
ex_new_status = me->status.
where status = 'APPROVED'.
U can develop a simple web dynpro application using this code.. its easy and u can give multiple approvals option also.
Have a look at RFCs listed here as well
http://help.sap.com/saphelp_erp2005vp/helpdata/en/73/8eaf40a90c952ae10000000a155106/content.htm
U should be ready for development for this... its simple and easy ... no JDI no importing of ESS MSS business package.. easy to maintain code!!
Cheers!!
Ashutosh -
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. -
Java.lang.NullPointerException in Leave Request Approver.
Hi,
When i try to click the redio button under the UWL to approve the Leave Request, i'm getting following errors.... Any idea ....???
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
at com.sap.xss.hr.lea.form.edit.VcFormEdit.setReadOnlyApprover(VcFormEdit.java:467)
at com.sap.xss.hr.lea.form.edit.VcFormEdit.onInit(VcFormEdit.java:269)
at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onInit(InternalVcFormEdit.java:700)
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:158)
... 37 more
java.lang.NullPointerException
at com.sap.xss.hr.lea.form.edit.VcFormEdit.setReadOnlyApprover(VcFormEdit.java:467)
at com.sap.xss.hr.lea.form.edit.VcFormEdit.onInit(VcFormEdit.java:269)
at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onInit(InternalVcFormEdit.java:700)
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:158)
at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface$External.onInit(InternalVcFormEditInterface.java:234)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:466)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$1300(FPMComponent.java:71)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseSelectionChangeEvent(FPMComponent.java:795)
at com.sap.xss.hr.lea.worklist.VcWorkList.select(VcWorkList.java:178)
at com.sap.xss.hr.lea.worklist.wdp.InternalVcWorkList.select(InternalVcWorkList.java:163)
at com.sap.xss.hr.lea.worklist.VcWorkList.selectFromList(VcWorkList.java:274)
at com.sap.xss.hr.lea.worklist.wdp.InternalVcWorkList.selectFromList(InternalVcWorkList.java:187)
at com.sap.xss.hr.lea.worklist.WorkListView.onActionSelectFromList(WorkListView.java:166)
at com.sap.xss.hr.lea.worklist.wdp.InternalWorkListView.wdInvokeEventHandler(InternalWorkListView.java:211)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanks
AliFailed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
at com.sap.xss.hr.lea.form.edit.VcFormEdit.setReadOnlyApprover(VcFormEdit.java:467)
at com.sap.xss.hr.lea.form.edit.VcFormEdit.onInit(VcFormEdit.java:269)
at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onInit(InternalVcFormEdit.java:700)
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:158)
... 37 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; MS-RTC LM 8)
Version
DOM version
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: 6.4018.00.0000.20060915154217.0000 (release=630_REL, buildtime=2006-09-15:21:06:29[UTC], changelist=417774, host=PWDFM027)
J2EE Engine 6.40 patchlevel 105424.313
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: amd64
Other
Session Locale en_US
Time of Failure Thu Mar 06 04:22:59 CST 2008 (Java Time: 1204798979911)
Web Dynpro Code Generation Infos
sap.com/ess~lea
SapDictionaryGenerationCore 6.4018.00.0000.20060413100453.0000 (release=630_VAL_REL, buildtime=2006-07-27:20:17:05[UTC], changelist=399179, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4018.00.0000.20060413100453.0000 (release=630_VAL_REL, buildtime=2006-07-27:20:17:17[UTC], changelist=399179, host=PWDFM026.wdf.sap.corp)
SapGenerationFrameworkCore 6.4018.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2006-07-27:20:09:33[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4018.00.0000.20060706112634.0000 (release=630_VAL_REL, buildtime=2006-07-27:20:27:21[UTC], changelist=409560, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon 6.4018.00.0000.20060119123849.0000 (release=630_VAL_REL, buildtime=2006-07-27:20:10:34[UTC], changelist=385565, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore 6.4018.00.0000.20060119123849.0000 (release=630_VAL_REL, buildtime=2006-07-27:20:10:25[UTC], changelist=385565, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary 6.4018.00.0000.20060119123716.0000 (release=630_VAL_REL, buildtime=2006-07-27:20:14:08[UTC], changelist=385561, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro 6.4018.00.0000.20060706112048.0000 (release=630_VAL_REL, buildtime=2006-07-27:20:22:55[UTC], changelist=409544, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4018.00.0000.20060726153907.0000 (release=630_VAL_REL, buildtime=2006-07-27:21:03:58[UTC], changelist=412327, host=PWDFM026)
SapWebDynproGenerationCore 6.4018.00.0000.20060706112634.0000 (release=630_VAL_REL, buildtime=2006-07-27:20:27:50[UTC], changelist=409560, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4018.00.0000.20060726153907.0000 (release=630_VAL_REL, buildtime=2006-07-27:21:03:58[UTC], changelist=412327, host=PWDFM026)
sap.com/pcui_gp~xssutils
SapDictionaryGenerationCore 6.4017.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-06-21:20:49:38[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4017.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-06-21:20:49:50[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapGenerationFrameworkCore 6.4014.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-09-08:19:59:29[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4017.00.0000.20060530202640.0000 (release=630_REL, buildtime=2006-06-21:20:59:47[UTC], changelist=405182, host=PWDFM027.wdf.sap.corp)
SapMetamodelCommon 6.4017.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-06-21:20:42:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelCore 6.4017.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-06-21:20:42:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelDictionary 6.4017.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-06-21:20:46:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
SapMetamodelWebDynpro 6.4017.00.0000.20060530202218.0000 (release=630_REL, buildtime=2006-06-21:20:55:02[UTC], changelist=405174, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4017.00.0000.20060530202355.0000 (release=630_REL, buildtime=2006-06-21:21:18:15[UTC], changelist=405176, host=PWDFM027)
SapWebDynproGenerationCore 6.4017.00.0000.20060530202640.0000 (release=630_REL, buildtime=2006-06-21:21:00:17[UTC], changelist=405182, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4017.00.0000.20060530202355.0000 (release=630_REL, buildtime=2006-06-21:21:18:15[UTC], changelist=405176, host=PWDFM027)
sap.com/tcwddispwda
No information available
sap.com/pcui_gp~xssfpm
SapDictionaryGenerationCore 6.4017.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-06-21:20:49:38[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4017.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-06-21:20:49:50[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapGenerationFrameworkCore 6.4014.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-09-08:19:59:29[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4017.00.0000.20060530202640.0000 (release=630_REL, buildtime=2006-06-21:20:59:47[UTC], changelist=405182, host=PWDFM027.wdf.sap.corp)
SapMetamodelCommon 6.4017.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-06-21:20:42:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelCore 6.4017.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-06-21:20:42:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelDictionary 6.4017.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-06-21:20:46:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
SapMetamodelWebDynpro 6.4017.00.0000.20060530202218.0000 (release=630_REL, buildtime=2006-06-21:20:55:02[UTC], changelist=405174, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4017.00.0000.20060530202355.0000 (release=630_REL, buildtime=2006-06-21:21:18:15[UTC], changelist=405176, host=PWDFM027)
SapWebDynproGenerationCore 6.4017.00.0000.20060530202640.0000 (release=630_REL, buildtime=2006-06-21:21:00:17[UTC], changelist=405182, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4017.00.0000.20060530202355.0000 (release=630_REL, buildtime=2006-06-21:21:18:15[UTC], changelist=405176, host=PWDFM027)
sap.com/tcwdcorecomp
No information available
sap.com/pcui_gp~tecl
SapDictionaryGenerationCore 6.4017.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-06-21:20:49:38[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4017.00.0000.20060530191647.0000 (release=630_REL, buildtime=2006-06-21:20:49:50[UTC], changelist=405154, host=PWDFM027.wdf.sap.corp)
SapGenerationFrameworkCore 6.4014.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-09-08:19:59:29[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4017.00.0000.20060530202640.0000 (release=630_REL, buildtime=2006-06-21:20:59:47[UTC], changelist=405182, host=PWDFM027.wdf.sap.corp)
SapMetamodelCommon 6.4017.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-06-21:20:42:46[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelCore 6.4017.00.0000.20060302125746.0000 (release=630_REL, buildtime=2006-06-21:20:42:36[UTC], changelist=392271, host=PWDFM027.wdf.sap.corp)
SapMetamodelDictionary 6.4017.00.0000.20060302125547.0000 (release=630_REL, buildtime=2006-06-21:20:46:39[UTC], changelist=392265, host=PWDFM027.wdf.sap.corp)
SapMetamodelWebDynpro 6.4017.00.0000.20060530202218.0000 (release=630_REL, buildtime=2006-06-21:20:55:02[UTC], changelist=405174, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4017.00.0000.20060530202355.0000 (release=630_REL, buildtime=2006-06-21:21:18:15[UTC], changelist=405176, host=PWDFM027)
SapWebDynproGenerationCore 6.4017.00.0000.20060530202640.0000 (release=630_REL, buildtime=2006-06-21:21:00:17[UTC], changelist=405182, host=PWDFM027.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4017.00.0000.20060530202355.0000 (release=630_REL, buildtime=2006-06-21:21:18:15[UTC], changelist=405176, host=PWDFM027)
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
at com.sap.xss.hr.lea.form.edit.VcFormEdit.setReadOnlyApprover(VcFormEdit.java:467)
at com.sap.xss.hr.lea.form.edit.VcFormEdit.onInit(VcFormEdit.java:269)
at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEdit.onInit(InternalVcFormEdit.java:700)
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:158)
at com.sap.xss.hr.lea.form.edit.wdp.InternalVcFormEditInterface$External.onInit(InternalVcFormEditInterface.java:234)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:466)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:354)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$1300(FPMComponent.java:71)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseSelectionChangeEvent(FPMComponent.java:795)
at com.sap.xss.hr.lea.worklist.VcWorkList.select(VcWorkList.java:178)
at com.sap.xss.hr.lea.worklist.wdp.InternalVcWorkList.select(InternalVcWorkList.java:163)
at com.sap.xss.hr.lea.worklist.VcWorkList.selectFromList(VcWorkList.java:274)
at com.sap.xss.hr.lea.worklist.wdp.InternalVcWorkList.selectFromList(InternalVcWorkList.java:187)
at com.sap.xss.hr.lea.worklist.WorkListView.onActionSelectFromList(WorkListView.java:166)
at com.sap.xss.hr.lea.worklist.wdp.InternalWorkListView.wdInvokeEventHandler(InternalWorkListView.java:211)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)
at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) -
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, -
Webdynpro - Leave Request Approval
Hi Colleagues,
We have implemented the mysaperp2005 ESS business package on EP7. Portal is working, leave request is working, workflows trigger and open in UWL, UWL looks OK.
However the button to execute the workflow, "Launch Webdynpro", launches the wrong URL for Leave Approval.
It gets the Port wrong using 8032
http://ourserver.com:8032/webdynpro/dispatcher/sap.com/ess~lea/LeaveRequestApprover
Should be port 53300
http://ourserver.com:53300/webdynpro/dispatcher/sap.com/ess~lea/LeaveRequestApprover
Cannot find where 8032 is comming from, can can't find any config for this in the LeaveRequestApprover iView properties or anywhere else. Checked every property of the LeaveRequestApprover versus LevaeRequest iView: identical.
Regards,
Jimmy.Thanks Sebastian,
icm/server_port_0 is not set up.
I have only icm/server_port_<xx>
Do you thing I should I set up icm/server_port_0?
Regards,
Jimmy.
Param. Name
icm/server_port_<xx>
Short description(Engl) ICM server specification
Appl. area Internet Communication Manager
ParameterTyp Character String
Changes allowed Change permitted
Valid for oper. system All operating systems
DynamicallySwitchable
Same on all servers
Dflt value
ProfileVal
Current value -
Error: You are not a receiver of the work item in Leave Request Approval
Hi all,
I have copied the standard leave request workflow and done the customization as per my requirement.
Agent assignment for all the tasks are General Tasks.
We are facing below error when we are trying to approve the leave request from MSS UWL.
"You are not a receiver of the work item.".
This started happening after implementing the note 1501377 which is for clearing the approved leave request
workitems from UWL .
i have gone through the threads related to this issue and tried given solution but no success .
Please let me know if anything else is missing since its happening after implementing the note.
Thanks,
SantoshAble to resolve the issue :-).
i was using Fork since my workflow is a two level process.
so the workflow was travelling to both branches one was in ready state another was in waiting state(48hours deadline)
having different agents.
i debugged the 1501377 note code when leave is approved it is looking at last workitem of the request which is waiting state workitem in my case and I was trying to approve the leave from user who is in ready state. then it throws the error.
So i have changed the design of workflow. i have done below things for two level process.
i will have requested end for approval task with outcome in that branch i kept second level approver. My questions
1) i am planning to do write below code to post the entries into infotypes after approval by managers. is it ok or any suggestions?
CALL METHOD cl_pt_arq_processor=>post
EXPORTING
im_request =
RECEIVING
ret_value = retrun
2) how to complete the WF if the 1st manager misses the deadline and WF goes to second manager?
Please let me know.
Thanks,
Santosh -
HELP: Customizing ESS Leave Request for multiple entries in one submission
Hi experts,
I appreciate help on this urgent problem. We're on ECC6 with EP7. My customization requirements are below:
1) Allow multiple leave entries to be submitted at one go. Standard ESS only allows one date range entry per submission. We've customized the Webdynpro Leave request form to allow multiple entries in table form.
Assuming there's 3 requests:
R1 ~ 01-Oct-2007
R2 ~ 03-Oct-2007
R3 ~ 05-Oct-2007
Whenever user clicks 'New Entry' button, Webdynpro will call bapi PT_ARQ_REQUEST_PREPARE to generate a new request ID.
When user clicks on 'Review' button, I will loop at the requests internal table and check each of the entries, which is an individual request, via BAPI PT_ARQ_REQUEST_CHECK. Am I doing correctly so far?
The checks return no error. Next comes the problem. When I click the 'Send' button, I will loop at the request IDs (in ascending order) into BAPI PT_ARQ_REQUEST_EXECUTE. I will get a dump, saying that the object cannot be found. Debugging shows that it cannot find the first request ID (R1) in the memory. I found that if I sort the request IDs in descending order, it will be able to find the last request (R3) and could process it. However, when it comes to the 2nd last request (R2), it will give me the same dump saying that object can't not found. Both R1 and R2 cannot be found whereas only R3 can be found.
In overview, the logic we adopted is like this:
1) PT_ARQ_REQUEST_PREPARE-CREATE (R1)
2) PT_ARQ_REQUEST_CHECK (R1) upon clicking 'New Entry' Button
3) PT_ARQ_REQUEST_PREPARE-CREATE (R2)
4) PT_ARQ_REQUEST_CHECK (R2) upon clicking 'New Entry' Button
5) PT_ARQ_REQUEST_PREPARE-CREATE (R3)
6) PT_ARQ_REQUEST_CHECK (R1, R2, R3) upon clicking 'Review' Button
7) Loop PT_ARQ_REQUEST_EXECUTE ( R3 - Returns OK, R2 - Returns object not found and terminates, R1 - not processed because execution terminated by R2).
Can anyone please advise me how I should go about changing the BAPIs? Or are the CLASSes/BADIs to be changed?
<b>Points will be rewarded for helping with this urgent requirement.</b> Thank you.
Regards,
DamienHi Kiran,
Thanks for replying. My guess initially was also that the requests are overwritten.
I heard of another company's implementation who did the same concept and was able to do it. Unfortunately, I'm unable to get any information from them.
Initially, my frontend programmer and I thought of adopting the 'dummy checks' methodology. i.e. Do dummy checks when clicking 'New entry' or 'Review' button. This is to ensure that the entries were entered correctly at front end. Only when the user clicks on the 'Send' button, my BAPIs take in a table of request entries and perform the Request_Prepare&Request_Check&Request_Execute one at a time.
This may be expensive as there will be double the processing needed. One set for dummy checks and one set for the actual backend processing.
Is there any way that I can create multiple requests in 'transcient' state so that it won't be overwritten and I can still find it when I call the BAPI PT_ARQ_PREPARE_EXECUTE? PT_ARQ_PREPARE_EXECUTE only takes in request IDs instead of request structures.
Thanks again, Kiran, for replying. Have a good weekend.
Regards,
Damien -
ESS Leave Request Approval Not working
Hi All,
We here have ESS1.0, ECC 6 and EP 7 on NW2004s.
Problem which i am facing is in Leave Request.
An employee enter his leave details and send it to its boss.
and the boss check the same in his UWL uptil this its working fine.
But when the boss click on the Leave request in UWL to approve or reject the same then error comes.
The error is "<u><b>Application error occurred during request processing.
Details: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Wrong WebDynpro-URL: no application name specified
Exception id: [001125C556F8005400000500000B2052000432CAF4C7A0CF]</b></u>"
Kindly help me out on how can i resolve this issue.
Regards,
Sidhartha ChatterjeeHi Sidhartha,
proove, if you use the following things:
In the portal under "Universal Worklist - Administration" you must fill out the parameter "Web dynpro launch system" for the binded ECC system you use. Use a portal system (the alias name for the portal system you have created) which links to the Web Application Server where you have deployed(!) your application (if web application server and portal is the same you also must create a portal system with the local web application data). In general, you create and named a portal system like SAP_WebDynpro_XSS and bind it as parameter.
If you do not use this system the Web Dynpro for Approve/ Reject leave request generates a wrong URL with the Web application data from ECC, not for web dynpro.
More information:
Configuring The Business Package For Employee Self Service (ESS)-mySAP ERP 2004
(to create the system SAP_WebDynpro_XSS)
http://help.sap.com/saphelp_nw04/helpdata/en/92/a88931f2dd4631b9e8d530697d89c9/content.htm
(to bind it into UWL)
Hope that helps,
Regards,
Frank -
Leave Request Approval Application
Hello Everyone,
I get the following error when clicking a leave request in the UWL to approve:
Service cannot be reached
What has happened?
URL http://cicerpaio.cice.ae:8015/webdynpro/dispatcher/sap.com/ess~lea/LeaveRequestApprover call was terminated because the corresponding service is not available.
Note
The termination occurred in system ERD with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:cicerpaio_ERD_15-v:0-s:404-r:Notfound
HTTP 404 - Not found
Your SAP Internet Communication Framework Team
How can I fix this? Is this a configuration issue?
Best Regards,
MotazHi,
1. Navigate to System Administration->System COnfiguration->Universal Worklist Administration
2. Locate the WebFlow connector which is pointing to the R3 System for Leave Request task
3. Click on Edit and in Web Dynpro Launch system enter SAP_LocalSystem
Save and retest.
Thanks
Prashant -
We have implemented ESS/MSS with EP 7.0 and ERP2005.
We are logged in as an ESS User and have select to raise a 'Leave Request' then we want to select a different approver from the approver that defaults.
After selecting the drop down icon, next to the defaulted approver, the Advance Search appears and you have the option search for another approver.
However, when searching for the another approver, you do not get another choice other than the user logged on i.e. the current ESS User.
Is this a know fault?
Has anybody encountered this problem before and if so how did they solve it?
Thankshi,
Are u using Leave request application from SAP Business package ,if you r using this the approver list is loaded from your companies Organisational Assignment data in ECC.
regards,
M.Arunkumar
Maybe you are looking for
-
All the music used to play but not anymore please can i have some help??
-
Adobe CC installer fails to initialize in Windows 8.1
I tried cutting and pasting the opm.db file to the desktop as recommended in one thread. Still the CC installer fails to initialize. Any one found a fix yet?
-
Adobe 9 crashes or faults on Windows Vista Business
Running Vista Business, keeps getting these when opening PDF's. I have all the updates for my OS and for Adobe 9. Log Name: Application Source: Application Error Date: 9/30/2008 1:28:26 AM Event ID: 1000 Task Category: (100)
-
Read_Network resulting Java Error " Table or view does not exists"
Hello Gurus, I tried loading a Oracle Network (Oracle 11g) under the same user where i created the Network Tables. But still i am getting "table or view does not exists" . What could be the issue here ? Please help. begin SDO_NET_MEM.NETWORK_MANAGER.
-
Help: OIM 10G Server With Weblogic
Hello all, I've running 9102 version of OIM on weblogic. I've to apply 9102 BP15 patch and also include some heavy JSP changes into xlWebApp.war. Here is what i've done - (1) installed BP15 patch as per the README in patch guide. (included the xlweba