on 03-16-2017 7:24 PM
We are recently facing this issue in existing workflows. When workflow is supposed to proceed to next step, it is creating orphaned and unknown node types. Sometimes causing short dump DBSQL_DUPLICATE_KEY_ERROR. This error is occurring in multiple workflows randomly/rarely without any pattern. Sometimes this occurs as soon as document is created and workflow triggered and sometimes in middle of in process workflow.
Workflow is processed afterwards as expected by reprocessing job SWWERRE. I have searched SAP community and OSS notes but not found any details on this. Any inputs on this error is much appreciated.
Thanks!
Hi,
Use transaction SWU7 and do a consistency check on these workflow templates. Also check OSS for similar issues, there might already be a solution for this behaviour.
Kind regards, Rob Dielemans
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This almost definitely looks like your WF template is corrupt. This could be due to a failed transport or a number of other reasons. If Rob's suggestion hasn't helped, reactivate from Dev and retransport the whole template.
If that doesn't help, rebuilding a new WF from scratch may be the quickest and most reliable route.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.