The workflow system is set up as a very rigid solution, which takes care of the problems that could occur. The one exception to this rule is the workflows of which a dump is produced. Where a method (read> ABAP coding) dumps, the workflow logging on the respective flow "hangs". Therefore the first thing to do on a health check is: check for dumps from user WF-BATCH.

Note: Workflow related dumps could also be thrown by users other than WF-BATCH. In SRM these dumps do not have to be visible to the end user...

• Measurements: Dumps should not be found
• Tools: ST22 Dump analysis
• Impact: Instances for workflow or single step tasks are stopped, even though the workflow logs report e.g. "In process"... forever !

• Prev
• Next