Skip to Content

SAP Workflow Re-generation/Re-activation

We are implementing support packs, as part of the process we have identified by implementing this suport pack one of the workflow is going in multiple loop, so a correction has been attached tested and all good, the support pack and the code has been moved to the production, its working good but issue is there are existing workflow who are in process got impacted by this support pack, and the apporvals went into infinite loops, now what is the best can be done here? we have 1000 workflow tasks are in infinite loop is there away to fix it or do we need to kill all of them?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Dec 12, 2017 at 08:52 PM


    I would think that you'll need to kill them, anyway if there are in infinite loop you need to finish them or at one point (10.000 loop) they will die.

    So you'd better handle them yourself and start the new version, you could even prepare a report to do that by checking all the workflow which are still running with the old version getting the object stopping the old workflow and starting the the new one.



    Add comment
    10|10000 characters needed characters exceeded

    • You can use transaction SWWL to logically delete the workitems, but I'd be very careful doing this. Make sure you have identified only the ones that need to be killed. I also recommend planning with the business owners for if/how the objects in these workflows get handled after the workflow deletion.

      Good luck,


  • Dec 13, 2017 at 07:28 AM


    You can also check the any configuration or customizing TR need to move or not.


    Add comment
    10|10000 characters needed characters exceeded

    • So we can see the changes implemented properly the issue here is, the new workflows are running as expected, but the workflows that are trigerred before the support packs are having issue, when analyzed further, its been identified that the old workflows are running in version 10, and new workflows are running in version 11. So the change applied is only available in version 11, not in version 10. this causing the loop of approvals.