Workflow Intermittently Not Creating Workitems

[Michael Pokraka]

Shouldn't cause much of a problem, unless you're using the event queue -
I've experienced some quite strange things under system load, including
duplicate events.
Teh next step is to wait for it to happen again and check if the event
is being raised, depending on problem it may give you the answer in the
event log.
Cheers
Mike
 
On Fri, Jan 24, 2003 at 09:42:54AM -0500, Thomas H. Cole wrote:
> Thanks for the assist.  I did not find anything troubling in ST22, SM58 or
> SM13.  Further event logging was inactive at this time.  I activated event
> logging.  Is it reasonable to assume that the situation I described would be
> reported as an error in SWEL?  Another thing that we tried was using
> transaction SWUF.  We found our workflow container object table to be in a
> red light status.  We're in the process of purging this table down.  Might
> this be a cause of my issue?
>
> Regards,
> Thom Cole
>
>
> -----Original Message-----
>> From: Michael Pokraka [mailto:workflow at quirky.me.uk]
> Sent: Thursday, January 23, 2003 12:11 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Workflow Intermittently Not Creating Workitems
>
>
> Hi,
> Have you looked at the event log (SWELS to activate/deactivate, SWEL to
> view). See if the events are being raised correctly for the documents in
> question.
> If so, you can look in ST22, SM58, SM13 for any system-related problems
> preventing the workflow starting.
>
> This is just a starting point, let us know how you get on.
> Cheers
> Mike
>
>
> On Thu, Jan 23, 2003 at 11:52:37AM -0500, Thomas H. Cole wrote:
> > Hi WF Group,
> >
> > In 4.0b I am experiencing an intermittent workflow failure to create
> > workitems.  The workflow is the SAP standard workflow for purchase
> > requisition approval.  I have noticed that over a period of days a number
> of
> > non-consecutive requisitions do not generate workitems.  However, when
> using
> > SWUS the workitems generate properly.  Can anyone provide me with some
> ideas
> > of areas to look for the root cause of this issue?
> >
> > Thanks,
> > Thom