Line Manager (A002) remains default approver in leave request, despite determining different agent through WF.

Hello Experts
I am facing a issue in Leave Request.
I have requirement where for a leave, HR should be the approver not Manager.
I have determined the approver through Rule, and used a FM which modifies ACTOR_TAB internal table which is passed to the Task.
When a request is raised, I can see only HR as an agent in workflow log. Thats correct.
But If I go to Manager's inbox, request is sent to Manager as well for approval.
He is not there in agent log.
But then I checked the container element "Req". It shows Manager's userid as approver.
I dont want Manager to receive any request by default. I can determine through WF.
Can anyone help me remove Manager as Default approver.
Thanks

for your scenario check your configuration in Table V_PTARQ_TPROCESS as proposed above but in this case you need to use the BADI as above refer here http://wiki.scn.sap.com/wiki/display/ERPHCM/Leave+request+Configuration+steps http://scn.sap.com/thread/1349663

Similar Messages

Mass Approval of Leave Request...need function module or any program

Hi All,
I have developed Custom Application in webdynpro java for Leave,Travel,now i got the new requirements for mass approval of Leave and Travel can any baddy provide me any input ,i don't know which functional module or program i use , help gurus...
Regards,
Pramod gupta

Refer below links to get an idea :
uwl mass Approval- Select all option
UWL Mass Approval XML changes or Custom App
Mass leave approval?
As an alternative to this service, you can use the Leave Request: Mass Approval report (RPTARQMASS_APPROVAL) in the back-end system. These reports enable you to approve multiple leave requests in batch.

Error in approve the leave request in MSS

Hello,
i m new in ESS/MSS.. right now working on maintanance project...All configuration settings are done by other guy. -
I m facing error in approving the leave request in MSS .. it open a error page as of no page found ... can any body tell me the solution of this problem.
thankz and regards,
Sumit

Hi,
Sumit Malhotra ,
Can you check with other user who is having all the roles.
This error has something to do with the roles.navigation is occuring with URL means check the roles or try with other user.
Look into permissions and also in different browser also.
Log file u have to search in OS LEVEL.
Mail meto [email protected] if it doesn,t work and we can try for other ways.
Sorry if it doesn't work.
Thanks,
Gopal.sattiraju

Leave request mail in different languages

Hello,
we are using the leave request functionality for different countries. The report RPTARQEMAIL is scheduled as a daily job, but sends the emails in english only (the schedule user is defined with language 'EN').
We changed the english text of the email (SE61) and included all languages which we need. But the email subject is still just in english. Furthermore the email is getting quite long and not really user-friendly.
We would like to send the emails always in the user's language (text and subject). Is there a way how to do this in the standard report?
Thanks for your support!
Nicole

You need to copy and modify the program to pick the user language text from SE61. This is required since the standard text is mentioned in Selection-Screen of this report will be picked always. you should also be able to change the subject line since this program sends composed mail.

Preblem for Approver in Leave request

Hi All,
   Well i am facing a problem in Create leave Request For the Approver that is selected by default based on the organisation head.I don't now how it happens but thing that i noticed thta for an employee if i maintain a head position in the org it picks up that head position of org as default.
My consulatant want this value to be picked up as we require i.e fetch a particular employee through coding on the screen itself and default on the screen.Can this be done else if any body can provide any better alternative for this solution is most welcomed.
Well we can actually send or sellect the approver what he wants but what about the approver that comes as default on screen and if there is no approver workflow will not be triggered as it gives the error
Please reply soon.

1)   go to swdd tcode,give workflow name and then click on step which finds out the approver of the employee.u will find FM which is finding approver.
now u can go an change the FM in SE37 and put ur own logic to find the approver.
suppose u want to find approver by A002 relationship of employee then u have to write followign code in the concerned FM -
DATA: ls_sobid TYPE sobid.
SELECT SINGLE sobid FROM hrp1001 INTO ls_sobid
   WHERE otype = 'S'
   and   plvar = '01'
   AND   objid = i_plans
   AND   endda >= sy-datum
   AND   begda <= sy-datum
   AND   rsign = 'A'
   AND   relat = '002'.
e_objid = ls_sobid.
2) if not by A002 then u can create a new relationship say 'ZTV' and maintain this relationship for employees and find approver based on tht then as follows -
SELECT SINGLE sobid FROM hrp1001 INTO ls_sobid
   WHERE otype = 'S'
   and   plvar = '01'
   AND   objid = i_plans
   AND   endda >= sy-datum
   AND   begda <= sy-datum
   AND   rsign = 'A'
   AND   relat = 'ZTV'.
e_objid = ls_sobid.
3) reward poins if helpfull
amit

Wrong agent picked if manager not maintained for employee in leave request

Hi All
We are using std. workflow WS12300111 for leave request approval which is run from the EP side.
It is working all fine, but the problem arises when there is no manager maintained for an employee. Idealy it should have given a error message; but here the workflow runs and the agent is the manager of the previous leave request.
Is there any setting that is missing anywhere? Or there is someother reason that I can't forsee?
Please help me out in this

Hi Varsha,
who the agent is getting selected for that step of wrkflow.... r they using any rule or they are referring and org structure..
if they are referring org structure then it will take the next line manager of that employee...
so if the picking agent is next line manager then it is working fine .............
Regards Dev

Need multi level approval for Leave request workflow in ESS

Hi All,
Our requirement is for 5 levels of approvals for the leave request raised in ESS means After employee raises leave request ,it has to be approved by 5 managers one after the other. In standard system only 1 level of workflow and approval is available so please anybody suggest the solution . Thanks in advance.

in addition to the above content your workflow consultatn have to create this ask him to
refer this document
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
for multiple level of aproving the leave reqest and and orgstructure have to be well formed
ravindra

ESS leave request - Change Approver

Hi,
We have a situation in which a employees dotted line manager will approve the leave request instead of a direct manager. We have a custom relationship to establish the dotted line manager. Now, In the ESS leave request there is a Approver field which shows the Employees direct manager. Can we customize the logic using a BADI or User exit to show the dotted manager?. Please let me know which enhancement is to be used for this requirement.
Thanks in Advance for your assistance.
Ramesh

in the customizing for the definition of the processes per rule group
you set the selection for the next processor to "Manual Entry".
or for the BADI
Another way is to use the BAdI Control Processing Processes for Time
Management Web Applications (PT_GEN_REQ) and implement the methode
IF_EX_PT_GEN_REQ~FIND_RESP_AND_DEFAULT_NEXT_PRC.
Method FIND_RESP_AND_DEFAULT_NEXT_PRC of badi
PT_GET_REQ might be utilised here.
Please have a look at the method
CL_PT_REQ_SEARCH_NEXT_P~SEARCH_NEXT_PROCESSOR.
If you are implementing the badi then make sure you copy all the methods
and implement the one, as mentioned.

Manager is not able to Approve the leave

Dear Freinds,
Please help me in solving this below issues.
EE has applied for leave thro ESS. Manager have recd a confirmation from Work flow system . But the same is not reflecting in Manager MSS . Therefore he is not able to approve the same . However, Manager is able to approve the leave for others.
I cheked in PO13 and the realationship and dates are perfect. Can anyone tell me what could be the reason.
IS there any T-code to check the Email communication that both had.

Hi,
Please check the workflow log in the system using transaction SWI1 for the date on which the EE has applied for leave,
check the Agent assigned for approving the leave by clicking on the Agent button - confirm that this is the same manager.
Also this is assuming that in MSS under the UWL other employees leave requests are visible,
so as to eliminate portal side issues.
Regards,
Samson.

Leave Request Not Appearing in UWL for Manager

Hi,
We have a strange issue where leave requests are not appearing in the UWL for a specific manager. We have checked with other managers and the leaves are appearing in their UWLs and they are able to process their employee's leaves without any issue.
For the manager not seeing the leave in their UWL, I have confirmed the following:
1) Proper manager defaults in 'approver' field in ESS and employee is able to send leave request without issue
2) Manager receives email to process employees leave request after RPTARQEMAIL program runs
3) Leave is reaching the manager's business workplace in R/3 so this verifies workflow is working and the leave is being directed to proper manager for approval
4) Proper roles have been assigned to manager and verified in PRD
*Also, the leaves were appearing in the manager's UWL at one point but no longer appearing. This makes it more confusing!
Does anyone have any suggestions/ideas as to what may have happened?
Any feedback would be greatly appreicated!
Regards,
Brian

Hi:
We transported our ESS/MSS changes from the DEV client to STG client. I have verifiied the follwoing settings in STG:
1) SWU3 - all connections are green.
2) Workflow template and tasks - all are assigned as general task with agents assigned
3) Configuration in SAP contains the correct WF template for leave processing
4) UWL has been regenerated
I am able to submit a leave request under ESS user. I check workflow and it shows leave has been submitted and waiting for Manager to approve step.
However, under MSS user the leave request is not showing up in the UWL. All configuration on backend and the items noted above have been verified.
Is there configuration or a connection on the portal side that I need to check? Or anywhere else? Any input would be greatly appreciated.
Regards,
Brian

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

How to change approver for a leave request in ESS

Hi Team,
When person employee A requests for leave it goes to Employee B being the manager in Org assignment.
But when CEO applies for leave as no body is there on top of him , I want to make HR Director as the agent to approve the leave request.
could you please tel me if any BADI or anywhere I can do the changes to set the agent I want to make to approve the request.
Please help.
Thanks,
Sourya prkash.

Hi,
There are two BADi's which can help you to deal with ESS leave requests PT_GEN_REQ and PT_ABS_REQ. just try to check out the above two badi's . There is a method in the default implementation class with name FIND_DEFAULT_AND_RESP_ACTOR..
Regards
Pavan

Reg : Getting error while approving leave request

Hello Experts,
Manger is getting and error message u2018Work item 000000000000 cannot be readu2019 while
Approving the leave request of one his reportee. This error is triggering for only one
Reportee.
Experts please kindly help us.
Regards,
Raj

Hi Raj,
There are a number of issues that could cause this. Can you share your scenario (where is manager approving the request - via SAPGUI, ESS, MSS?) Are you using an SAP standard workflow?
Plus, there are lots of threads in SCN on this topic. Have you checked any of these?
Good luck,
Sue

Exception in approving Leave Request

Hi All,
When ever a manager is trying to click on launch webdynpro to approve Employees Leave Request, is throwing an Exception in new portal window.
Exception condition "IT0008_NOT_FOUND" raised., error key: RFC_ERROR_SYSTEM_FAILURE:
We have cross checked with infotype 0008 for Employee and Manager. These details have been maintained. But still the problem exists.
Please suggest a solution
Regards,
Kishore.
Edited by: kishore kumar on Aug 4, 2009 9:19 AM
Edited by: kishore kumar on Aug 4, 2009 9:21 AM

Hello,
Could you pls let us know what was the solution for the above.
Thanks & Regards.

Second level Manager Unable to view the leave request

Hello Experts
We are using three levels approval leave request, first level manager able to approve successfully, when second level manager approving the leave request is unable to see any contents inside the request, its showing blank.
Kindly help me on this.
Thanks
Neelima.

Hi,
I have a requirement in which I have to sent Leave Workflow to three approvers. For that I maintain the approvers in a customising table. What I did is, I took a copy of the standard Leave WF and added a step in loop (to read the table maintained, through a bor method). For the last approver, he has to get the standard leave approval task and for that reason i looped my custom bor for 2 times and put the standard leave approval task outside the loop.
Now the issue is that, eventhough the first approver gets the workitem and approves that, the next approver is not getting the workitem for him. Workflow is going into an error state stating that the successor node is not found.
Please tell me whether my approach for customising leave workflow is correct. And if correct, what could be the reason for the error that I get.
Regards,

Line Manager (A002) remains default approver in leave request, despite determining different agent through WF.

Similar Messages

Maybe you are looking for