Workflow Job SWWDHEX

[Dart, Jocelyn]

Hi Casey,
Not sure what you mean by a sleep/wait status on the job - perhaps you
are running it too frequently and it is deadlocking (unlikely)
or you are out of batch processes?  Remember SWWDHEX checks ALL work items
that have deadlines against them when it runs, then assesses whether the
deadline is
exceeded.
 
In any case a better approach for development is:
* Set the deadline job to run at the expected production frequency
* Set the deadline step with the desired production deadline time
Ok so that means everything matches production and any transports will
definitely send production values not test values.
 
During testing:
* Use an administration report, e.g. SWI1, to find the work item and use
the work item display in SAPGUI to check that the deadline was
calculated as per production.  Then use the work item display options
to manually adjust the deadline to a closer date/time so that you can
test escalation.
* If your SWWDHEX job is too infrequent for testing, then you can manually
execute report RSWWDHEX e.g. via transaction SA38.
 
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: Smith, Cassaundra [mailto:Cassaundra.Smith at anheuser-busch.com]
Sent: Wednesday, 10 April 2002 4:53 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: 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