Skip to Content

Workflow: How do I deal with a corrupt definition?

Hello everyone,

we have a workflow sitting in our test system that crashes (causes the transaction to hang indefinitely) whenever you try to do anything with it (i.e. use any transaction on it or one of its instances). This does not only apply to already-existing instances of that workflow: Even if you try to open the workflow in transaction SWDD, it hangs. In addition, this workflow causes memory problems on the system as it appears to consume huge amounts of memory in the process.

Trying to transport a fixed version of that workflow from our development system has not helped. What can we do if we cannot even open the workflow in SWDD? Is there any sort of correction report for workflows or another approach to get rid of it the hard way?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Jan 10, 2017 at 01:17 PM

    Hi,

    If you try to open the workflow definition in PFTC and click workflow builder will you get the message Workflow definition '&' not in version '&' (WD 401)

    If yes, then you can use FM SWD_WFD_REPLICATE_FROM_9999 to fix your problem. There is also a probability that when you try to import your workflowdefinition that the import has either missing objects or the workflow is using local objects as a reference.

    Kind regards, Rob Dielemans

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 09, 2017 at 09:18 AM

    Hi,

    Can you please check any dump in st22. or log in sm21. Also can take help from basis.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 09, 2017 at 05:30 PM

    Hi ,

    Few things I would like to understand from workflow execution point of view are

    1. Is this behaviour of the workflow is occurring only in Test System or even in development?
    2. What is the count of work process defined in the Test system?
    3. There is also a need to understand which is the step that is actually consuming a huge amount of memory I would also check if there are any bottlenecks in the implementation part of the Business object methods or Business class methods.
    4. You have also mentioned that you were not able to access the transaction related to Workflow. I doubt this is not only with the workflow related transactions. The reason could be the system is not defined with an adequate amount of work processes so the other are busy in serving the previous request. Due to which you were not able to open any other transactions.

    Thanks,

    Pavan

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 09, 2017 at 06:53 PM

    I know the question was a while ago, but as this may be relevant in other cases....:

    Please also check what is happening when it 'hangs', SM50 is the first place to look. Often it's not the WF, but some code in the business objects defined in the container. SWDD and the likes will try to instantiate all objects, and some bad code/design can cause havoc. (e.g. a header object instantiates it's item objects, which in turn instantiate their header object, which ...).

    Add comment
    10|10000 characters needed characters exceeded