UWL - Leave Request item still in UWL after approval

Hello,
we are facing the problem that the leave request items have still state "new" after the approval and don't change the state.
But in the list the leave request is not visible any more... so the approval worked.
I found the discussion: Approved items in UWL remains in the status "new". and Leave request workitem in UWL status update issue but that didn't help.
Does someone know what to do?
thanks, Vanessa

Hello Lukas,
with the help of the wiki: http://wiki.sdn.sap.com/wiki/display/ERPHCM/UWLworkitemisnotrefreshedafteraLeaveRequesthasbeen+approved I was able to find the required note to get the status fixed. It is now completed and that's great. Unfortunately the items are still there. I am only able to see the new items in the transaction. The old ones are not visible but I need to delete them. Tomorrow I will ask some WF guru to help me fix it.
I also think that there is still a problem with the configuration of the UWL / backend WF. It could be that ne required jobs are not planned. I was happy that the UWL worked so fast but now....
Greetings,
  Vanessa

Similar Messages

  • Removing Task from UWL after approval

    HI Gurus
    I Need to Delete a task in the UWL after approval
    Scenario:
    I have developed the mss/pcr adobe forms inthe place of standard adobe forms i have configured the customized adobe forms which i have developed in Webdynpro for Java
    So in mss/pcr application we have two levels of approval
    First
    Intiator will enter the data and he will submit the form then it will goto the manager UWL
    Second
    Manager will click on the task(these task ids i have configured in SWFVISU) .And next one more form will be opened with the updated data and manager will approve it and he will click on the approve button then that form should not be in the UWL
    But I dont know what are the settings i need to do for that .
    Please help me in this .

    jvhncvbnc

  • Reminder workitems still showing up after approval

    Hi SRM Guru's,
    We are upgrading from EBP 3.0 to SRM 5.5. We have implemented dead line monitoring for invoice workflow in EBP3.0.  We are having some invoices created in EBP 3.0 system and reminders generated in SRM 5.5 sytem for those invoices. After approval of the invoices, the reminder work items are still showing up in Inbox of the approver. This happens only with the old carts that were created in EBP 3.0 system.
    Please help to fix this problem.
    Thanks.
    Srini

    Thanks Roger for the quick reply -- just to check, the URL they sent me in the Podcast Approved Notification is:
    https://itunes.apple.com/us/podcast/carl-mike-comedy-commentary/id926924295

  • Item in Transfer Process  after approval of shopping cart

    Dear Friends,
        Pls help in Providing a Solution for the Problem in Shopping Cart after approval the status is showing as   " Item in Transfer Process" and FOD is not going to generate.
    Thanks
    Mukesh

    Hello Mukesh,
    It will happen for any of the following reasons;
    1). If the vendor mentioned in the shopping cart is bolcked or marked for deletion (in R/3).
    2). Material in the shopping cart is blocked or marked for deletion in the backend (R/3).
    3). If the purchasing group is not existed in the backend.
    To see such errors you can login to GUI (SRM) and see the errors in t code RZ20.
    Navigate to the SAP EBP monitors>Shopping cart>click on "BAckend appln errors.
    there you can investigate for further reasons.
    Jagadheesh

  • Moving Change requests to new Maintenance cycle after approval

    Good Day
    I was wondering, is there an easy way to move any give change request from one maintenance cycle to another one. An example would be.
    I have a change request that currently has 1 ABAP, 1 Config and 1 Security transport assigned to our current maintenance cycle. I have been requested to move the change request (along with all the transports) to a future maintenance cycle.
    Is it just a case of re-assigning the change request to the future cycle, ?
    Regards
    Don Newton

    Hi Don,
    It's a very interesting question... I think that a lot of people here need this functionality and SAP finally hear that from us.
    This new functionality came with SP15. You should have a look to SAP notes 1071412, 1134993 and 1141086, it may help you to solve your problem.
    regards,
    Stéphane.

  • Problem in navigating Leave request.

    HI All,
    My leave request application is working fine after approving leave ,The page is shouing me a link that says "Approve another leave" when I click the link its not taking me anywhere.
    Please help me on this as quickly as possible.
    NOTE: My JCOs  both metadata JCOs and simple once are having connection type as SSO.
    I think meta data JCOs shld be of user/ID password type or the other way around.
    Please help me to figure out the problem.
    Point will be awarded accordingly.

    Hey sid,
    I dont have any development environment like NWDS and all where I can make the changes and upload it.....
    Is thare any other way......
    One more interesting observation when I click on the link " Approve another leave " though it doesnt take me back to approve another link, but when I right clivk on the portal page and take the link from properties(Normal windows right click and properties) I get a URL link ,when I post this link in explorer guess what its giving me that page to approve another leave so can we solve the problem without getting into touch the codes as I dont have development environment.
    Look fwd to ur reply.
    Thanks in adv.

  • UWL do not refresh correctly when leave request change status

    hi
    I implemented the standar workflow of "Leave Request"(succesfuly), and the leave request  appareced in UWL in MSS, I approved the leave request, but Leave Request is not change the status. But The employee of the leave request watch the new "status" with approved in the ESS option (Leave Request).
    I refresh the UWL but Leave request stills appears with status "new", I clicked in the Leave Request (it had already approved in the previous step) and the new window open with error "index 0,0".
    My questions are:
    1.  How I can refresh my UWL? and that I displayed the request approved
    2.  Why not change your status to approve the leave, if I do not get any error?
    thanks for your post and answers
    Ivan

    implement the note 1501377 which was created to clear the leave request workitems
    ensure it is done
    and then following settings, In SWU3 schedule background jobs
    in uwl administration you can set these
    Default Execution Mode: Optimistic
    Webflow User Format: Full Name
    Default Cache Validity Period, in Minutes: 2
    Maximum Number of Threads Created in the Thread Pool: 10
    Timeout Value for the Connected Systems, in Seconds: 60
    Please check how frequent you refresh your cache
    1.,,Open task in the same window in the portal - rather than opening in
    a new window when approving and rejecting tasks.  This is so that the
    actions will be controlled through the UWL UI rather than an external
    window.
    2.You can configure an additional column on the UWL UI called
    isLaunched to mark an item that were already executed and may have been
    completed already.  This is very similar to the marked as read
    functionality contained in an email client.  If a user opens a task the
    item will  be marked as launched.  If refresh happens either manually or
    automatically then the workitem may be completed (marked as launched)
    and disappears from the inbox.  If it has been opened but not completed
    the launched icon disappears.
    3. Is Delta Pull enabled in your system?
    Steps to clear the UWL cache
    please go to "System Administration" "System Configuration" ->
    -> Universal Work list & Workflow
    -> Universal Workflow Administration
    -> Click on cache administration page
    -> Click "Clear Cache" button.

  • ESS: UWL Leave request issue

    Hi folks,
    We are on EP 7.0 SP13 wit ESS/MSS 600 SP11 (for ERP2005) .
    We configured ESS Leave request and facing the below issue.
    When an employee takes leave with the leave request application and the manager rejects/approves this leave request,
    a work item is send in the UWL Inbox of the employee. Processing this work item leads to the following error:
    Application error occurred during request processing.
    Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'com.sap/ess~lea' and application 'LeaveRequest' are not deployed on the server. Please check the used URL for typos.
    Exception id: [0018FE28A06E006500000070000032B50004463FEC45E404]
    I've checked the SWFVISU transaction and changed the package name of workflow task 'TS12300116' to 'sap.com/esslea', initially, it was 'com.sap/esslea'. Though i make this change and re-register the UWL system, i still get the error when opening the task from UWL Inbox
    All ESS/MSS services/webdynpros are deployed without errors.
    Does any body have an Idea ??
    Thanks
    Karthik

    Hi Karthik,
    The error is because in SWFVISU transaction, where the Workflow task is linked with the Leave request approver application ,the package name is wrong.
    The task for approval process is TS12300097.
    In SWFVISU,
    Application name is : LeaveRequestApprover
    Package : com.sap/ess~lea
    If you notice,the package name mentioned here would be com.sap.xss.hr.lea.appl. Please correct it to com.sap/ess~lea.
    You can also check out note 779075
    Hope this solves it.
    Regards
    Reshma

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

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

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

  • Webdynpro leave request standard workflow

    Dear Expert,
    I am on EP 7 with ECC 6 backend. As for my leave request, i am able to trigger using the workflow (WS12300111) and the approver able to appprove it.
    The problem is when the approver reject the request, it will send back a notification the the requester UWL for resubmition and not matter how many times the requester resubmit the leave. The notification still in the UWL. Anyway to get rid of it.
    My second question is, is there any standard workflow for cancellation leave and change leave request?
    Thanks in advance....
    Regards,
    Bryan

    Dear Richard,
    Thanks for your reply. My situation is as below.
    1) The requester request for a leave and submit the application.
    2) The leave application reach the approver UWL.
    3) The approver REJECT the leave application.
    4) The workflow (WS12300111) went to the resubmission flow
        and trigger TS12300116.
    5) The requester receive an item "Process Leave Request by 
        Employee" in his UWL.
    6) The requester click on the item and it looks similar to the leave application screen. The requester then try to re-submit a new leave from there and send to request. However even after the requester send resubmit the leave, the item still remain in the requester UWL.
    My first question is why the item still remain in the requester UWL even after the requester execute it by re-submit a new leave application. Any way to remove it or it is the workflow error
    Second question is if the requester decide not to resubmit the leave application after being rejected. What is the procedure to remove the item from the requester UWL?
    Thanks,
    Regards,
    Bryan

  • Leave Request workflow in MSS - copying standard

    Dear All,
    can you please help me! Im new to this HCM and SAP.
    My Requirement is Manage or Team Lead creates the Leave request (on behalf of employee).
    If team lead creates the LR, then the approval mail has to reach manager's UWL. he has to approve or reject.
    If manager  created the LR, then no need to send the mail.
    What i did is, i copied the standard LR workflow - WS12300111 into a customized one.
    right now i didnt change anything.
    And dont even understand that how mail is going for approval in standard, since there is no mail step in standard.
    i have seen about two report also - RPTARQEMAIL & RPTARQPOST .
    whether i also need to use this..???????
    Please advice.
    Thanks,
    Rani.

    Hi,
    First of all, you should know the difference between workitem and mail.
    Work item - Action that needs to be taken on the request (i.e.)approve or reject
    Mail - notification saying that your leave request has been approved (or) employee A's leave request lying with you for approval.
    Work item - workflow generates it and it will go to UWL.
    Mail - External program or workflow will trigger and it will go to Outlook. (But standard workflow WS12300111 won't send mail)
    Now tell me your requirement.
    Do you need work item or mail not to be sent when manager raises leave request?
    I mean, Is no approval required for manager's leave request?
    Cheers,
    Raja.D

  • Leave Request SENT but does not show in Worklist (duplicate PTREQ_ACTOR)

    I have a wierd issue in our ESS Leave System.  We are on ECC 6.0 with EP 7.0.  We are using the iView for leave approval and not workflow/UWL.
    The leave system is working great for all users except for one.  The situation is there is one employee in the approvers team that has leave requests that are sent to the approver but they do not show in the approvers worklist.  The requests are visible from the team calendar and the approver can approve them that way.  The approver has other employees in the same team that can send leave requests to the approver and they will show on the worklist with no problems.  We have checked all of the relationships and employee data and all looks OK.
    I have identified that the approver with this issue has 2 records in the PTREQ_ACTOR table.  The requests that are not showing are linked to one ACTOR_ID and the ones that are showing correctly are linked to the other ACTOR_ID.
    1) What caused the employee to have 2 ACTOR_ID records in PTREQ_ACTOR?
    2) How do we cleanup/resolve this issue from happening in the future?

    duplicate can cause  a issue in the system!
    the leave requests should be approved in some timeline and then we can
    delete the table entries which are not used anymore, then The entries which are not used should be deleted, you can write
    a custom program to delete the entries in the system.
    ie
    What we could suggest in your case is to delete one of the
    Actor Ids (the old one or the one which is less used) of the
    manager in question.
    Please identify how many entries are there in the system
    first of all.
    read and apply  the note 1316777.
    You can approve and post via the trans code in PTARQ.

  • 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

  • ESS LEA: Leave request, RPTARQPOST

    Hi,
    I read on some forum posts that the program (SE38) - RPTARQPOST has to be scheduled in order to update the status of leave requests and post to PA2001 after they have been approved.
    I have not scheduled it, but in our system, when manager approves a leave request, it gets updated in PA2001 (PA30). I understand from our workflow consultant that table prarq_header is being updated with the status (sent, approved, rejected) through a step in the workflow.
    Wondering if it is still necessary to schedule RPTARQPOST
    Appreciate any advice.
    Thank you,
    Brgds,
    Zubair
    info:
    Using ESS BP ERP1.0 on Enterprise Portal 7.0, backend ECC6
    workflow template WS12300111

    Honestly speaking, I at my place have scheduled PTARQ for all the activities to be done. But you have done it through workflow. May be its a different way of doing. Really not able to say whether right or wrong.May be the Workflow consultant at your place is the right person to judge

  • 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

Maybe you are looking for