Workflow Deadline Monitoring Question

[Michael Pokraka]

No prob, another small bit of info I might add is that I'm on a 6.20
system at the moment and as-needed scheduling is no longer available.
Which makes sense and emphasizes that SAP see workflow as becoming
widespread and much more utilized.
 
Cheers
Mike
 
Josefek, Richard wrote:
> Mike,
> Thank you so much for your response.
> Shortly after receiving it, we implemented the change and our workflow
> processing has been working flawlessly since.
> I cannot tell you how many hours have been put into researching this
> problem over the past year. We even went so far as opening up an OSS no=
te
> with SAP. They were no help at all.
>
> Thank you again!
>
> Rick
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
> Michael Pokraka
> Sent: Wednesday, November 19, 2003 7:17 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Workflow Deadline Monitoring Question
>
>
> Hi,
> Check that your monitoring is configured for periodic deadline monitori=
ng
> (as opposed to as-needed). Non-periodic causes WI's to check and schedu=
le
> deadline jobs. In other words, if an item is created and it sees that n=
o
> job is scheduled before it's deadline, it will schedule it unless the
> 'periodic monitoring' is set.
> Cheers
> Mike
>
> Somewhere in the mists of time Josefek, Richardwrote:
>>> We've run into a problem that I'm hoping you can shed some light on f=
or
>>> us.  We've had a problem occurring in our Production environment sinc=
e
>>> last December, 2002.  Recently, these problems have been causing our
>>> clients a lot of work to monitor and resolve.  Here's a synopsis:
>>>
>>> We use Maestro to control Workflow deadline monitoring.  Maestro runs
>>> SWWDHEX on a schedule that our clients have requested.  We do not use
>>> SAP.  However, last December, configuration for the SAP controlling o=
f
>>> deadline monitoring was turned on in our Production environment by an
>>> SAP consultant.  We immediately corrected the situation and turned it
>>> off.  However, this has caused a series of problems that we have yet =
to
>>> recover from.
>>>
>>> Individuals approving within one of two workflows were causing the
>>> SWWDHEX to instantiate in SAP (without their knowledge).  Once, this
>>> happens, it continues every 10 minutes.   One of the things we did to
>>> prevent this from happening was remove security from each individual.
>>> However, we have found this is not a good solution because every once
>>> in
>>> a while (under conditions we cannot determine) a client will receive =
an
>>> error message "Background job SWWDHEX cannot be scheduled (error 6)".
>>> Some of these clients will notice the error message and try to approv=
e
>>> the document again and the second time they are successful.
>>>
>>> We are assuming that the configuration that was turned on has somehow
>>> caused this irrevocable process to begin, even though we have shut it
>>> off.  We think that somewhere in the SAP environment, there is some
>>> trigger that is causing this job to run.  (Perhaps an assumption in t=
he
>>> code that if we are not using permanent deadline monitoring, we must =
be
>>> using periodic instead of checking table values?)
>>>
>>> Any assistance you can provide on what triggers there might be in SAP
>>> that would cause this to happen would be much appreciated!
>>>
>>> Thanks!
>> Rick
>>
>> ---------------------------------------------------------
>> This e-mail transmission may contain information that is proprietary,
>> privileged and/or confidential and is intended exclusively for the
>> person(s) to whom it is addressed. Any use, copying, retention or
>> disclosure by any person other than the intended recipient or the
>> intended
>> recipient's designees is strictly prohibited. If you are not the
>> intended
>> recipient or their designee, please notify the sender immediately by
>> return e-mail and delete all copies.
>>
>> ---------------------------------------------------------
>>
>
>