ESS leave request workflow WS04200009...error-u r not one of the possible a

hi all
i m working on ESS leave request workflow WS04200009....but when i create a leave request from user's A/c i got an error at that leave req create screen that's-- u r not one of the possible agent of the task...
pls do help if anyone no solution.
thanks in advance .
Raj

Try making this task a General Task..use tcode PFTC and change the attribute of this task to a general task. That might help solve the issue.

Similar Messages

  • Error: You are not one of the possible agents of task 'WS99900032'

    Hi frnds,
        I have copied the std leave request workflow WS12300111 into WS99900032 and assigned in the SPRO setting. The approvers are determined using the workflow rule (PFAC) and its not determined from Org Management. But when i tried to apply leave, its throwing me the error You are not one of the possible agents of task 'WS99900032'.
    Can anyone give me solution to solve it?
    thanks,
    Suganya.

    You are not one of the possible agents of task 'WS99900032'
    You need to refresh the  organizational environment and then execute the workitem
    1. First make the workflow tempalte as General task and then
    Goto PFTC ---> enter the workflow tempalte number by selecting workflow template  ---> open in display mode and on menu Addtional Data ---> agent assignment  ---> Maintian ---> select General task
    2. Goto SBWP  -
    > Seetings  -
    >workflow settings -
    > refresh ornozational environment and then try to execute the workitem

  • ESS- Leave : You are not one of the possible agent for the task ws9021212?

    Hi ,
    I have copied the standard workflow template wa12300111 and assigned the new template in the customizing. When i apply leave from ESS working time , it says an error " You are not one of the possible agent for the task ws9021212? " .
    The similar kind of Error i have solved before in by making the workflow as GENERAL TASK in PFTC as follows.
    PFTC -> Choose "Workflow Template" from the drop down -> Enter the workflow template id "ws9021212" in the text box -> now click on "change" button -> Now goto the menu addional data -> agent assignment -> maintain -> select the task text -> and set it as general task.
    i have cleared the buffer also!
    BUT STILL I AM GETTING THE ERROR ?
    Please help me !
    Richard A

    hi Richard
    Try to do this way.  IN the workflow builder there is a button with hat. that is basic data. click on that and  it will go to another screen and u can find a apple button that is agent assignment for a task click that.
    It will open maintain agent assignment screen. click the text below that and click the attribute button and click the genral task. i think this will solve ur issue.
    If helpful kindly reward points
    Regards
    vijay

  • ESS leave request workflow -WS12300111

    Hello Experts
    I need to develop ESS leave request workflow by making copy from WS12300111. We are using SAP 4.7 and EP 6.0. And ESS and MSS is not yet deployed in EP.I tried to open this workflow in Workflow builder. Its saying that the task 12300111 does not exist. I have seen this workflow in ECC 6.0.
    Is WS12300111 not available in SAP 4.7? or after deploying ESS,will it be available in SAP 4.7?
    Please help me out...
    Thanks&Regards,
    Hemalatha

    hi Hemalatha
    I think in 4.7 you can't get that workflow. In ECC6 you can see the workflow. In EP you can't the visual see the workflow like that ECC6. i have developed multileve ESS workflow. take the copy of the standard workflow ws12300111 and do the customization according to your need. Check with the support pack with the portal and basis team. ESS will support only more that sp18 i guess. check with your basis team.
    Regards
    vijay

  • ESS Leave request workflow : ws12300111 : Customizing

    Dear experts,
    I need to customoze ESS leave request workflow WS12300111.
    Can you please tell me do I need to Copy this to a NEW workflow generating a new WF no or can I simply generate a new version for this only ? What is ideal ?
    1. Can anyone tell me step by step process(config) in ESS leave application workflow?.(SWFVISU????)
    2. Is workflow WS12300111, the only workflow that I need to look for leave application ?.
    3. If it is WS12300111 I don’t see any start event for this workflow. So how is it getting triggered?
    4. For the approval task TS12300097, agent determination is done by expression ‘&Agent_0001.Agents&’. How does it interact with Org.Structure.
    5. In my scenario, approver should be supervisor of the employee applying for leave. If it is pending with this approver for 5 days it should go to the next up level manager.
    For identifying first level approver is ‘&Agent_0001.Agents&’ enough.? For identifying 2nd level approval do I need to write a rule ?
    Kindly help.

    Hi Sourav,
    Try this step by step process(config) in ESS leave application workflow.
    ESS Scenario
    Workflow Process 20000081 u2013 Create Leave Request with HTML
    Steps for triggering the workflow:
    1) The employee logs with his user name in the ESS web page.
    2) The employee creates a leave request with an optional note and sends it to the appropriate approver (usually his supervisor). The approveru2019s name is automatically displayed in the leave request form and the employee can replace him with another if such a change is needed.
    3) The approver (us approver) logs on to sap system or to ESS
    web pages and reads his mails in the SAP Business Workplace. The employeeu2019s leave request form appears in the workflow inbox with approve and reject options.
    A) If the us approver approves the leave request, he pushes the
    button approve from his mailbox (processing status A with
    approve). A screen is appeared with a box (Table entry: 0001)
    and the approver must push the button continue in order that
    the workflow is continued. Then the form is sent to the
    employeeu2019s mailbox in Sap. When the employee opens his mails, he receives a note in his inbox that u201Cthe absence from u2026. To u2026..has been approved byu2026.u201D.After that the absence is
    automatically created in the sap system. Then the approver gets a mail (notification of completion & Return u2026u2026).
    B) When the approver cancels a leave request, he pushes the
    button reject and the processing status changes to u201CRu201D.
    Then the same form appears
    Realative OSS Notes:588262, 480103, 717560, 452841, 359197, 321439, 428394, 321439, 693368, 451998 (ITS), 197746 (ITS), 419297 (ITS)
    ITS - ESS stand-alone solution for 4.7
    This solution allows customers to schedule the 4.6C or 470
    install / upgrade independently from the Enterprise Portal or
    mySAP Workplace implementation and will be supported at least as long as SAP R/3 4.6C and R/3 Enterprise is supported.
    This ESS stand-alone menu is intended solely to allow independent scheduling of the 4.6C or 470 upgrade and the Enterprise Portal / mySAP Workplace installation. To use this solution, you have to take the following steps:
    1. If you do not already have R/3 4.6C, HR support package 8,
    please import HR support packages to at least this level. From
    HR support package 8 and above, the correct services are
    implemented. For 470, the corresponding recommended HR SP is 16 (See note 621589)
    2. Verify that the ITS you want to use does not contain a service or service-related files (HTML templates, MIME files) for the services PZLE, PZM3 or PZM3_start. If you find these files,
    delete them.
    3. Publish the services PZLE, PZM3 and PZM3_start from your R/3 4.6C system (or R/3 470 system whichever is the case) to your ITS using the SAP@Web Studio or the IACOR service.
    4. Maintain the username-employeenumber assignment in your system by customizing Infotype 0105, Subtype 0001 of those employees, who should be able to use ESS.
    5. Verify that your users have proper authorizations for
    executing RFCs (that is, authorization object S_RFC) from the
    function group EH08. If you run into problems, this is most
    likely due to missing RFC authorizations to start the service
    PZM3.
    6. Your users should now be able to access ESS by starting the service PZM3. They can do this by entering a URL like
    http://<ITS server>:<http port>/scripts/wgate/pzm3/!
    (the ! at the end is essential).
    7. ESS 4.70 Unicode System ITS 6.10 patch level 29 and above (With IE and Netscape). ITS 6.20, patch level 6 and above (With IE only).
    The ESS development tested these ITS versions.
    8. For Release 4.6C, ESS has the same browser requirements as the HTML (see also note 178788) and the mySAP Workplace 2.11 (if ESS is accessed through the mySAP Workplace 2.11).
    Hope it helps.Do award points if found helpful.
    Regards,
    Gourav

  • Issue with ESS Leave request workflow - Deleting a leave request

    Hi friends,
      This is my scenario: An employee has created a leave request from ESS - Leave Request Workflow(Copy of  WS12300111) gets triggered and work item gets created in manager's UWL. After that the employee realizes he has created a wrong leave request so he deletes that leave request from ESS. In this case the workflow instance which got triggered when he created the leave request is under process and the work item stays in the Manager's UWL( there is no terminating event or wait for event step in the approval step of workflow WS12300111), when the Manger opens that work item it shows a blank column, ideally speaking when the leave request is deleted by the employee the work item in the manger's UWL should be logically deleted and the workflow should complete, but this part is not handled in the standard workflow WS12300111as well. How to handle this case. I can put a wait for event or a condition to complete a work item at the approval step but i would like to know how the standard ESS leave request framework works in this case. Please advice.

    Hi sapient
      This is not handled in std. You have clear the next processor in your in method then only the work item will get vanished from the UWL.  For clearting the next processor either you can create a method in your BOR and get the request id. For the request id get the max version and clear the next processor or in the BADI you have wirte your own logic when the change happens what you have to do. This logic has to be written in you BADI.  I thing BADI will start with PT_ check with that name in se18
       You cannot use wait for event or terminating event since its not R/3 workflow its ESS workflow you cannot use ternminating event or wait step.
    Regards
    vijay

  • Unable send request, you are not one of the possible agents

    Hi,
    I am trying to configure workflow  for leave request, for my requirement i have to do some modifications to stadard workflow(12300111), so i copied it and made configuration settings in spro also, but when i create a leave from PTARQ transaction
    workflow is not getting created.
    when i debugged it, i got amessage saying 1) unable send request 2) you are not one of the possible agents
    Is there any other stting i have to do??
    Thanks,
    Krish.

    Hi Kishore,
    Please check below things.
    1. In the SPRO, have you maintained your workflow Template against the required leave type.
    2.Use CTRL + F2, and check is there any error in your workflow. Also check whether it is active or not.
    3. Check the workflow agent assignment in Basic data. It should be General Task.
    Thanks.

  • ESS Leave Request  Workflow Issue

    Hi Every one,
    Our client is using ESS/Portal Leave Request workflow(ZWorkflow template which is configured to the portal) which is working fine up to the last month.Recently i developed  3 level  Escalation functionaly which is working fine and we tested and finally transported to production in the last month .And recently i got an issue when the leave request is aproved after escallation is not setting the workflow status completed and keep on escalating to the next levels.
    Note:When the 1st manager approves the leave request without escallation the workflow status is going to be completed which is fine and only there is an issue when escallated and approved the status of that specific leave request is approved but the workflow is not going to the status completed and keep on escalating to the next levels.
    i checked the log and found there is condition based wait event step which have a condition when
    Req.status = Approved&
    Req.status = Withdrawn&
    Req.status = Error.
    must raise the event and complete the workflow only working fine when the escalation does'nt takes place and the direct manager reacted without escalating to another manager.
    Please help e what might be the problem is.
    Thanks,
    Raja.

    Hi,
    Where is this event called? And more over is it an AND condition between those statements?
    regards
    Krishna

  • Problem with ESS Leave Request Workflow

    We had configured ESS Leave request, which is working fine with Leave request approval.
    1)     Cancellation of Leave Request using the workflow WS12400005.  
                                  Workflow is not getting triggered when we try to delete the leave request.
    2)     Quota Overview
    While displaying the Casual Leaves (CL) I need to deduct the Paternity leaves (PL) also.
         Remaining CLu2019s = quota CLu2019s u2013 ( used CLu2019s + used PLu2019s).

    hi kishore. how did you resolve the issue of workflow not being triggered?

  • ESS Leave Request workflow customization

    Hi Guys,
    We are trying to customize the standard Leave Request Workflow WS12300111 in the ESS application for ECC6. The standard workflow passes the data to the workflow via the object REQ of type CL_PT_REQ_WF_ATTRIBS. I need to extract the leave information from the object.
    I tried creating an enhancement implementation for the Class CL_PT_REQ_WF_ATTRIBS and added my own method. But I can't see this method when I create a workflow task.
    I also tried copying the whole class and adding my code, but am not sure how to instantiate the new class in workflow. Pls help .

    Hi,
    Can you tell me the requirement.
    Do you want to change the Agent using a BADI ??
    or you want to send the leave request for another approval ??
    If you want to send the leave for another approval then just reset the status of the leave to SENT again using same class and using following code
    CALL METHOD cl_pt_req_badi=>initiate_state_transition
        EXPORTING
          im_request    = request
          im_event      = 'SENT'
       IM_RET_VALUE  = 0
        IMPORTING
          ex_new_status = me->status.
    After this, u can send this workitem to another processor..
    Another scenario could be:
    U want to determine a new agent for your workitem.
    In this case, u will have to implement BADI "PT_GEN_REQ"
    Read the documentation of this BADI.. this might help.
    And please tell me the requirement once again.. what you want to achieve.
    Regards
    Ashutosh

  • In ESS-Leave Request -A critical error has occured.

    In ESS when tried to enter the Leave which is under Leave request the below error occured:
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator.
    CREATE OBJECT: The class  was not found., error key: RFC_ERROR_SYSTEM_FAILURE  
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: CREATE OBJECT: The class  was not found., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.lea.blockcale.FcBlockCale.getBcData(FcBlockCale.java:232)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCale.getBcData(InternalFcBlockCale.java:250)
         at com.sap.xss.hr.lea.blockcale.FcBlockCaleInterface.getBcData(FcBlockCaleInterface.java:135)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface.getBcData(InternalFcBlockCaleInterface.java:224)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface$External.getBcData(InternalFcBlockCaleInterface.java:276)
         at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:261)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCale.onInit(InternalVcBlockCale.java:275)
         at com.sap.xss.hr.lea.blockcale.VcBlockCaleInterface.onInit(VcBlockCaleInterface.java:163)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface.onInit(InternalVcBlockCaleInterface.java:144)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface$External.onInit(InternalVcBlockCaleInterface.java:220)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: CREATE OBJECT: The class  was not found., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.pt_Arq_Eecale_Get(LeaveRequestAdaptiveModel.java:434)
         at com.sap.xss.hr.lea.model.Pt_Arq_Eecale_Get_Input.doExecute(Pt_Arq_Eecale_Get_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 60 more

    I found out the solution and solved this issue.
    Deleted the leave request which was created with error i.e: from the custom table zxx_vacr noted down the id initiater ( which had error) and in the Test Environment for Leave request (PTARQ) gave the PERNR and deleted the documents ( gave the id iniater in the document status ).
    To check the error work flow go to SWIA and check for that Workflow (Leave) raised by the PERNR at that duration ( check in IT2001 for the duration) and give it here.
    After deleting it check in the portal for the leave request.

  • ESS leave request workflow : not able to approve request

    Hi experts,
    When i create leave request, work item for approving request is not coming in the approver's bussiness workplace. I am using std workflow WS12300111. Is there any customization needs to be done ??
    please help me
    Pointes will be rewarded
    Regards,
    Sameer

    Hi Samee,
    Did you select General Task in the steps of workflow you have an agent?
    Sónia
    You have a chief position on the Organization Unit where you have the employees?
    Sometimes it's possible to forget this one:
    Transaction SWDD, select the workflow  WS12300111 and press CTRL+F8 (Basic Data)
    there's another button "Agent assignment for task" (SHIFT+F9)
    set task to "General task" with the "Attributes..." Button. (EVERY user can start this task).
    And check this to:
    Using transaction SWFVISU, check the following entries and correct these where required:                                                         
    TS12300097 Java WebDynpro  APPLICATION LeaveRequestApprover                       
                     PACKAGE sap.com/ess~lea                                
    TS12300116 Java WebDynpro                                               
                     APPLICATION LeaveRequest                               
                     PACKAGE sap.com/ess~lea                                
    (check this, because usually you have an error, instead of sap.com you have com.sap)
    Register the work items again. Additional information about registering  work items is available in the UWL documentation.                       
    After re-register the System Alias again in the UWL - THIS IS VERY IMPORTANT
    Edited by: Sonia Santos on Jan 28, 2008 12:49 PM
    Edited by: Sonia Santos on Jan 28, 2008 12:51 PM

  • ESS Leave Request - Portal Runtime Error when the "Cancel" button is hit

    We have configured the Leave Request application, created a custom workflow, created security roles, and we are now testing in our quality environment. 
    We are encountering a very strange "Portal runtime error" which we cannot resolve - When you come into the Leave Request application, and then, without completing the request, just hit the "Cancel" button, the runtime error is generated.
    We have run a trace of authorizations and everything has come up clean.  Everything is configured, and there are no problems actually creating, approving and posting requests. 
    Any ideas?

    Hi,
    please check whether the user is authorized to cancel the request.
    and take a look at this WS12300111
    Regards
    Manohar

  • ESS Leave Request Workflow Configuration

    Hi Experts,
    I Have ESS & MSS setup with mySAP ERP 2005 ECC 6.0, i have made the required configuration for absences, i assumed that leave requests should automatically be forwarded to the person with cheif position in the department, Now hwen an employee applies for a leave request i check the MSS UWL and nothing is appearing.
    My question is do i have to maintain any configuration in terms of workflow or is it automatically configured if PA & Om integration is active ?
    Points will be rewarded for any help..
    Regards,
    Ahmed Salah

    Ok follow this path
    Tools --> Business Workflow --> Development --> Tasks/Task Groups --> Change
    Task type = Workflow template
    Task      = 12300111
    Click on Change
    Click on Workflow Builder.
    Click on Process request by Employee.
    Click on Task Properties (Agent assignment)
    In Maintain Agent assignment,
    See for Process Leave Request by Employee , add General Task.
    Then click on the Update Index.
    Hope this works for you.
    Cheers!!!
    Sanjay Sharma.

  • ESS - Leave Request - Workflow

    Our requirement was for the leave request process to be a simple approval process that only includes the option for the employee to u2018changeu2019 or u2018deleteu2019 a request if the manager hasnu2019t approved it yet.
    In line with this, we have configured to switched off the u2018changeu2019 and u2018deleteu2019 buttons.
    This still allows the u2018changeu2019 and u2018deleteu2019 buttons before a leave request has been approved. (which we wanted)
    And these buttons disappear once the leave request has been approved. (which we wanted)
    However, for leave requests that have been rejected, we still get these buttons. (which we donu2019t want)
    After a Leave Request has been Approved or Rejected by the manager, the "Approve another Absence" link on results page doesn't work. Can we do anything about this?
    Also, when a manager is rejecting a leave request he is not forced to enter a rejection reason.Is there a way we can force the manager to enter a rejection reason?
    Thanks
    WB

    Hi
    No your right, you shouldn't transport from IDES to DEV, What kind of development system do you have ?
    A quick way to check if it exist is to check the HR Tables e.g. HRS1205.
    And just to cover the security issue, verify that your not using structural authorization, ar at least that your having full access to the PD Object in question. You can check this in OOSB - If your not using structural authorization you will only have one entry in here - SAP* with full access. If this user is missing in this transaction, or if your user is in the table with less authorization, you wont have access to the workflow templates
    Regards
    Morten Nielsen

Maybe you are looking for

  • How to convert (YYYY-MM-DD) to (DD-MM-YYYY)

    Hi Guys, I have one doubt on WDJ, While exporting data into Excel Sheet having date format is showing like the format (YYYY-MM-DD). But I need to convert into this format (DD-MM-YYYY). Can any one suggest me? How to convert (YYYY-MM-DD) to (DD-MM-YYY

  • FCP X PLUG INS/TEMPLATES

    Created some templates/plug ins in motion and saved them as generators that appear in the FCP X themes window. Want to delete some of these.....can anyone give me the correct path on my drive where they are likely to be saved? Thx.

  • HELP UPDATE HAS DELETED ALL INFO

    Hi there thanks for looking my sister has a macbook air and she has done an update today 17/09/2011, to be fair she is not amazing with macs but she knows she needs to do updates every so often. so an update occured and so she downloaded it. it said

  • Adobe PDF Test Tool Kit

    I need to validate data in a PDF through QTP. I have downloaded following softwares - 1. QTP 11.0 2. Adobe Reader 10.1.1 3. Adobe PDF Test Tool Kit (10.1.2) I am able to see acroqtp plugin when i open my QTP but still QTP is not able to identify the

  • HT1695 my iPhone wont connect to any wifi connections

    I have an iPhone 4S and anywhere I go and try to connect to the internet, if I type in the password it says "incorrect password". I have typed in the password correctly and it doesn't work at my house, work, or basically anywhere else. My brother has