background step getting hung up

Dart, Jocelyn jocelyn.dart at sap.com
Wed Apr 3 03:15:40 EST 2002


Hi Brian,
Looks like something is blocking the start of the last step.
Try looking at the workflow log.  If that doesn't show anything
try turning on the workflow trace for one run of the workflow to
see what's happening.
 
Likely causes are locking problems causing a temporary error (standard
system response is to wait for RSWWERRE job to retry the step). Could be
your previous step is not releasing the lock in time for the next step.
If your previous step is using the update task to make changes this could
be the source of the problem - you might need to make that step asynchronous
and use a terminating event to confirm when the updates is complete, and
therefore when the lock has been released.
 
Hope that helps.
Regards,
        Jocelyn Dart
Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
-----Original Message-----
From: Brian Bennings [mailto:bennings.bj at pg.com]
Sent: Wednesday, 3 April 2002 7:21 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: background step getting hung up
 
 
Hello Everyone,
 
What would cause a background step in a workflow (4.5b) to get hung up
consistently at the same place?  In our workflow, we have a sub-workflow for
capturing FI invoice approvals.  This sub-workflow exists as a step in
another
workflow definition.
 
The last step of the sub-workflow is a background step that completes just
fine.
The subsequent step in the parent workflow definition is also a background
step.
For some reason, that step consistently does not start.  The log just shows
the
previous step as complete.
 
When the RSWWERRE job runs, the background step in the parent workflow kicks
and
continues with the subsequent steps.
 
Thanks in advance,
Brian Bennings
 


More information about the SAP-WUG mailing list