AW: Workflow Job SWWDHEX

[Becker Stephan (extern)]

Casey,
 
the first ever SWWDHEX job runs when you run the workflow customizing
activity or run transaction swwb, and at the end of the run it then
schedules another instance of itself, which sits there and waits until =
its
time is come to run (i.e. it sits scheduled for the interval specified =
in
workflow customizing). If your basis people have a problem with that, =
show
them the workflow documentation, and if they still have problems after
verifying that the stuff works as designed, then they will have to take
their issue up with SAP..
 
Hth,
Stephan
 
-----Urspr=FCngliche Nachricht-----
Von: Smith, Cassaundra [mailto:Cassaundra.Smith at anheuser-busch.com]
Gesendet: Dienstag, 9. April 2002 20:53
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Workflow Job SWWDHEX
 
 
Workflowers,
 
We are on SAP 4.6c.  This job, SWWDHEX, is setup via the workflow
configuration
to monitor deadlines on workitems.  Our BASIS team is claiming that =
when
this
job runs it goes into a SLEEP/WAIT status which they say is a NO NO in
production.  We are currently having this problem in our test system.  =
One
of
our workflow developers is testing a workflow whereas one of the task =
would,
normally in the AB1 environment, wait 24 hours before forcing the =
workitem
status into a  'Ready' status. But because of testing, we don't want to =
wait
24
hours, so we set the job to run every 6 minutes.   My understanding is =
that
while a workitem is waiting for its deadline to be reached, the =
workitem
itself
is in a 'Wait' status in the SWWWIDH table.  Could this workitem status
possibly
be the same status that our BASIS folks are seeing in the job log.  Can
anyone
spread any light on this.  Has anyone experienced this problem before.
 
Thanks,
 
Casey