Obsolete work item

Hi all,
    I am thinking about this situation, when a employee create an Purchase order, it trigger my workflow to send a work item to his manager to approve the PO. If the manager doesn't go in his workplace and not see the workitem, but call transaction 'ME29N' to approve the PO directly. What shall I do with the work item stay in his workplace? Is this a problem or just let it go?

Hi,
The best approach would be to complete the workitem which can be done by  terminating events.
Just get the event which gets triggered from ME29N for the approval of the PO.
Now, mention that event in the terminating event of the workflow, so whenever that event gets triggered the workflow will get terminated and the workitem will be removed from his inbox.
Regards,

Similar Messages

  • Obsolete and batch users can receive work items

    Dear Experts,
    Currently, we have found a problem that obsolete and batch users can receive work items by manual forwarding from someone. The roles and responsibilities of obsolete users were removed and users have been locked. For Batchuser, it's only created for some certain job with limited roles.
    Could you help advise if this's a behavior of workflow or it's from some authorization problem? We have concern for business impact since no one is really handling work items and important messages are out of sight.
    Thank you very much in advance.
    Regards, Kae

    Hello,
    This is standard behaviour. It is even possible to send work items to users who do not yet exist (e.g. someone who is due to join the company).
    The easiest way to workaround is to set up a substitution for any users that get locked and for background users. Personal substitutes can be maintained directly in table HRUS_D2, you could possibly write your own maintenance transaction for this if it is to be an ongoing issue.
    Hope that helps,
    Mike
    Message was edited by:
            Mike Pokraka

  • Workflow - marking work items as obsolete

    I'm working on a workflow that allows cost center managers to approve or reject purchase requisitions.  I'm trying to create some logic that will trigger the workflow when the purchase req is significantly changed, in addition to just being created.  When it gets changed, I want to be sure that it's not deleted.  If it was deleted rather than being changed some other way, I want to mark all active work items for that particular req as obsolete so they're no longer out there for approval.  I put in a "set obsolete" step for each piece of the workflow that creates a work item prior to terminating the workflow.  When I try to test this, however, the workflow DOES recognize that the req was deleted, but it doesn't even show the "set obsolete" steps in the log, it just terminates.  The "set obsolete" step doesn't seem to have much to it, but is it possible that I'm just doing something wrong?
    Thanks,
    Eric

    Hi Eric
    You shouldn't use "set obsolete" for this.
    Depending on your version, you can either use a fork and a wait for the event "Deleted" in one of the branches or simply, in the new version, define a terminating event on the header level.
    Check this thread, it explains how, the example is based on restart, but you can use the methodology to cancel you workflow instances as well.
    Re: Restart Workflow ?
    Regards
    Morten Nielsen

  • One of the user is unable to remove obsolete Tags from new work items and search query

    Hi I am new to TFS Administration, User has some obsolete Tags in TFS site which is removed on the Backlogs but user can see those tags when he is creating new work items and while querying the Work Items but he is not able to see any obsolete tags in Backlogs.
    TFS version: TFS 2013 SP2
    Steps followed:
    we queried each tags, we see 0 work items associated with the tags
    As per MSDN, we have to remove associated tags which automatically removes the Tags after 3 days
    The user is facing the same from past week
    Am i missing something? or will the list of Tags be available in new work items and  querying WITs? Please help
    Thanks in Advance

    Hi BE,  
    I tested this scenario in my TFS 2013 Update 4 Server, and found that Tags will disappear  from Tags dropdown list automatically after serverl days, if there’s no any work item associated that Tags. 
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Setting work item as obsolete

    Hi Experts,
    We are using modeled deadline monitoring. We are setting the " Workitem to obsolete" in the process control step.
    Does this imply that the approver will not be able to execute the work item once it crosses it deadline.
    In case of repeated deadline monitoring, what do we need to do.
    Could you kindly guide us on the same.
    Cheers,
    Belinda Clarke

    Hi Gautam,
    Thanks for your response.
    You have specified Loop using status change in the second branch.....what i wanted to know whether is it necessary to validate whether the work item was processed in the second branch.
    Correct me if i am wrong....the concept of using a FORK is to have 2 activities running in parallel. Let us say that we have the first branch having the approval process and the second branch is having the loop using status change.
    In the second branch, if we create a DUMMY method and set a deadline to it as 1 day. Let us set a container variable say lv_deadline as 'X' in the DUMMY method. Below that we put in a send mail step that sends the mail to the approver. This happens inside a loop in which we set the condition as Loop until lv_deadline = X.
    Now in the case of FORK, these two activities will be running in parallel. The second branch will run after 1 day. If the work item is processed in the first branch, the control will go to the step after the FORK.
    Is my understanding correct....do we need to validate in the second branch whether the work item was processed.
    Kindly advice.
    Regards,
    Belinda Clarke

  • Delete credit memo work item created in VA01 when the user change value

    Hi,
    In T.code VA01 Credit memo request is creating, this document will automatically create  work item.  Based on Net value in credit memo request, the work item should go for 5 levels of approval. After 1st person is approved, the workflow initiator realized that the net value in created Credit Memo request is wrong; he is going to VA02 and correcting the net value. Again we have to create new work item for this and delete the already created work item. Client has clearly mentioned when ever there is change in 5 critical fields in VA02 then only create fresh work item otherwise no need to create SECOND TIME work item. Net value is one of the critical field in the list.
    How to track already created credit memo request and how to delete the previously created work item. What is the feasibility of this requirement and how to handle this situation?
    Regards
    Vijay

    Hi,
    Just put a Fork and put 1 out of 2 outcomes and in the first alternative, you put your witem that goes to user B. In the 2nd alternative, put a Wait for event "CHANGED". And after this, put a process control step with "Set workitems to Obsolete" or "Cancel workflow" etc., depending on your requirement.
    Pl note that this will only take out old witems, but you need to send a new witem for which you need to trigger another instance of the workflow as well. pl put CHANGED event also as one of the triggering events and use condition editor to restrict the fields that triggers the workflow.
    Also, look into the IMG config of the following path. This might be a fitting solution.
    In SPRO, go to Financial Accounting (New)---> Financial Accounting Global settings(New) -
    >Tools --->Workflow ---> Workflow for Document Parking -->Reset Release Approvals(Customers).
    Here, you can list down the fields, the workflow should restart. But, then you need to give the workflow details etc., in the relevant config settings.
    We have used this in restarting workflows for General Ledger(GL) documents' workflow when some important fields are changed.
    For this config settings, look into the following help link.
    http://help.sap.com/erp2005_ehp_02/helpdata/en/01/a9cdd8455711d182b40000e829fbfe/frameset.htm
    Hope this helps.
    venu

  • Work Item to be disappeared from user1 inbox when escalated to user2

    Hi,
       I created a customising workflow for Credit Memo Request with 2 escalations  for approval. I have used Fork operation to get this functionality with Requested start option in 2nd and 3rd branch to escalate after 3 and 6 days respectively if not the document is approved by the agent in branch 1.
    Every thing works fine, but the client wants the work item to be removed from USER1's inbox when escalates to USER2 and from USER1 & USER2's inbox when escalated to USER3.
    Could you guide how can we do it in my case.
    Thanks in advance.
    Edited by: Jaya on Sep 30, 2010 10:26 AM

    HI Jaya,
    you can make use of 'Processing Obsolete' here as it would remove workitems from the approvers inbox whose deadline is missed.
    First of all , in the decision step make 'processing obsolete' active under 'outcome tab' of the task.
    Use latest end with time as 3 days and  action as modeled.Now in modeled deadline, make use of process control step and select 'set workitem as obsolete'  and put step number of your dialogue step in 'workflow step'.
    This will make the workitem diasppear from the approver inbox once the deadline is missed after 3 days.
    Now to repeat the process fro 2nd and 3rd approver , put all of this in a loop, and before loop ends, find the next approver id in the outcome 'Processing obsolete' of the desicion step.and pass this id to the expression used for approver.
    The loop condition can be a flag that is set to X when a deadline is reached. To do so, add a container operation in modeled deadline before process control step that will put the flag X.
    So loop will continue to second pass if deadline is missed and hence so on till 3rd approver.Formulate condition for highest level of approval too.
    Hope this helps.
    Regards,
    Sangvir Singh

  • To Delete the PO Work Item after 2 days

    Hi Experts,
    I am new to workflow.
    In R/3,
    I want to delete the PO workitem automatically from UWL after 2 days .
    I am using WS20000075, and tasks TS20000166, TS20000167, TS20000168 .
    How can I delete the work item from UWL .
    Please give me a brief solution .
    Regards
    Krishhna

    Hi,
    Activate processing obsolete option in the task step for which workitem has to be deleted.
    Also specify the latest end for 2 days.
    Cheers,
    Raja.D

  • Terminating the work item

    Hi,
    I have an requirement where in i need to terminate the workitem after a user decision step. The termination should happen when the user decision is a 'Reject'.
    The termination needs to happen immediately after the rejection happens without any deadline monitoring.
    Can anyone please let me know how to set the work item to obsolete when the user decision is a reject?
    Many thanks,
    Raghav.

    My bad....I was a bit hasty in answering that!!
    Did you try activating the 'Processing obsolete' in the outcomes tab of the decision step? You should do that, and leave the path empty if you don't have any logic to add.
    Let me know if this works.
    -Krisnan
    Edited by: Krisnan Kumar on Jul 29, 2008 9:24 PM

  • Work item not getting displayed in the portal

    Hi  experts,
    We are creating a protoype for one of the standard HCM form for change in working time. When we initiate the process, the workflow is supposed to identify the agent(which is the manager in this case) and push the work item in the inbox of the manager.
    In our issue, we are able to see the workitem in SAP inbox, but the same work item is not getting displayed in the portal.
    If we try to approve from the SAP inbox, the hard coded message u201CWork item can only be executed using the Portal and the UWLu201D comes. [this comes through the method of  one of the tasks 17900101 which we are using for approving the form]
    We commented the message by using a Z class. Now we donu2019t get the hardcoded message, but still the workflow does not complete from here.
    Can this be aan integration issue of the workflow tasks with the portal??Can someone elaborate on this??

    <ItemType name="uwl.task.webflow.TS17900101.SAP_ECC" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
          <ItemTypeCriteria systemId="SAP_ECC" externalType="TS17900101" connector="WebFlowConnector"/>
          <Actions>
            <Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
              <Properties>
                <Property name="WebDynproApplication" value="ApproveFormApp"/>
                <Property name="WebDynproDeployableObject" value="sap.com/pa~asr~formstep"/>
                <Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
                <Property name="openInNewWindow" value="yes"/>
                <Property name="display_order_priority" value="5"/>
              </Properties>
              <Descriptions default=""/>
            </Action>
          </Actions>
        </ItemType>
    You have to say to your portal team to modify their XML file as above. In simple you hvae to configure the task in the portal and in the SWFVISU txn as follows with the following vizualization parameters
    Task TS17900101 and visualization type is JavaWebDynpro
    APPLICATION     ApproveFormApp
    PACKAGE     sap.com/pa~asr~formstep

  • Error while opening work item in Inbox sbwp for verifcaion of right invoice

    Hi,
    I am working on SAP workflow with IXOS.
    I faced  a problem in opening the workitem when it came into the inbox.
    In nomal scenario when i click on the workitem under workflow folder in my inbox, it opens the attached document in document viewer, i can see the attached document ,and after verifying it ,i can furher process it.
    But now when i click on the work item in my inbox it directly takes me to the next processing window, without opening the attached document for my verification, so i am unable to check that i am processing the right invoice.
    Please help.

    Yes, it was working fine before.
    And also the problem generally rise in afternoon.

  • Error when starting work item

    Hi
    We are having SRM5.0.
    Trying to create Contract. Workflow Without approval of contract(WS1400086)is activated and start conditions also no workflow activated.
    Contract is created and getting message Contract created.
    But when tried to release the contract it shows "Awaiting approval".
    In Workflow log (SWI1)it shows error."Error when starting work item xxxx".
    What could be the reason. Please let me know the solution if anyone of you come across such error.
    Thanks in advance
    Jagadish

    Masa
    It is maintained as General task already.
    It seems the workflow task WS14000085 does not have definition.
    When checked in SWDD for the above teask there are no steps defined for that workflow.
    SAP says that we need to define and action for workflow WS14000085.
    But what is the procedure to define the workflow.
    I presume this is the standard workflow and it should be defined by default when it comes along with the SRM package.
    Anyone of you know how to define the workflow and activate the same?
    Regards
    Jagadish

  • Work item never shows up in the approver queue

    Hi All,
        This is a specific issue to a particular user - approver. requisitioners are creating carts and are able to see that it is in approval queue. But the approver  is not able to see the approval items in his queue.
    We are in SRM 5.0 ECS SP15. This issue started all of recently. There has no changes in Org structure specifically to his attributes or workflow changes. Interestingly when workitem is forwarded to another approver, then that approver is able to view it. So, this tells me that this specific user has issues to view work items for approval.
    Any suggestions is greatly appreciated and rewared.
    Thanks
    Rao

    Hello Rao,
    Did you check in SWI1 transaction if your particular user is defined as approver for concerned workitem ?
    If you have user ID and password, can you see the workitem in SBWP transaction ?
    If you use offline approval, has approval mail for this approver been created ? You should see it in SOST transaction.
    Regards.
    Laurent.

  • Urgent help req : work item id not getting passed in the method

    Hi ,
    I have created a subtype zcats of business object CATS and delegated it .
    I have created a new method Approve1 ( with attributes  SYNCRONUS & DIALOG )  in zcats which is similar in coding  to Approve method of CATS ( DIALOG) .
    I have include the method Approve1 of business object zcats in a standard task .
    The problem is that when the eorkflow gets triggered ,  the workitem id is not getting passed in the method APProve1 of zcats.
    Can someone please help me with this .
    Points would surely be awarded .

    BEGIN_METHOD APPROVE1 CHANGING CONTAINER.                 
      DATA: WORKITEMID_IMP LIKE OBJECT-KEY-ITEMID.              
      DATA: WI_CHCKWI LIKE SWWWIHEAD-WI_ID.                     
      DATA: WORKITEM TYPE SWC_OBJECT.                           
       <u> WORKITEMID_IMP = OBJECT-KEY-ITEMID</u>.                     
        SWC_GET_ELEMENT CONTAINER '_WORKITEM' WORKITEM.         
        SWC_GET_PROPERTY WORKITEM 'WorkitemReference' WI_CHCKWI.
        IF SY-SUBRC EQ 0 AND NOT WI_CHCKWI IS INITIAL.          
          WORKITEMID_IMP = WI_CHCKWI.                           
        ENDIF.                                                  
        CALL FUNCTION 'CATS_WF_APPROVAL'                        
          EXPORTING                                             
            WORKITEMID_IMP = WORKITEMID_IMP                     
          TABLES                                                
            CONT_IMP = CONTAINER.                               
      END_METHOD.                                               
    hi ,
    the above is the code in the method .
    At the first step of execution underlined above , the work item id is appearing blank .
    I think that the value is not passed to the container , but i am not sure og how to pass data to this conatiner

  • Work Item not getting logically deleted

    Hi All,
    We have created a custom workflow for PR approval at Item Level. I have RELEASE STEP CREATED as triggering event.
    I have used a FORK with 5 branches with 4 wait events and min cond as 1. The inherited business object ZBUS2009 has been created with events CHANGE, DELETED. The business object has been delegated to Original Business object BUS2009.
    To trigger the events like DELETED and CHANGED, I have used POSTED METHOD of ME_REQ_POSTED BADI.
    When a PR Item is created the agents are determined successfully and work item is placed in his SAP Inbox. Later the PR Item has been deleted and saved the BADI Implementation is triggered and I can see the log in SWEL for DELETED event with success icon.
    However when i go back to PR Item which i have deleted and see the workflow log the work item is still in the approver's inbox. but the graphic log shows that the DELETED branch of the fork is completed. I tried all options like Buffer synch, background job, queue admin etc with no success.
    I did the same workflow at one of my previous clients and it is working perfectly for last 2yrs.
    Can any one guide me on what could have gone wrong or what i am missing?
    Thank you all in advance for help...
    Regards,
    Lakshmi Narayana

    Hi Arghadip,
    Thanks for your quick response.
    The fork is having 5 parallel branchs and 1 necessary branch and is INDEED HAS NO EXTRA CONDITIONS.
    Also as i mentioned the graphical log shows that the completion of BRANCH Beneth DELETED but the work item is still in approver's inbox. 
    Please let me know if I am missing something....
    Rgds,
    Lakshmi

Maybe you are looking for