Changing event linkages in PRD

[Dart, Jocelyn]

Have you tried using SAP_WAPI_SET_ERROR to stop the current workflows
and maybe have a look at how SWE_EVENT_RECEIVER_ERROR works to see how methods can be
called to set the event handler error. No guarantees on this but worth a look.
Sounds like a good dev request to me for a new admin function.
Jocelyn
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Michael Pokraka
Sent: Tuesday,25 May 2004 10:58 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Changing event linkages in PRD
 
 
Hi Jocelyn,
Thanks for the info, but that only solves half the problem. It still doesn't
let you SET something into error.
I know, I could create a linkage error, write a report, or trasnsport it.
This doesn't help when you're on a site and someone changes something which
results in a workflow loop. Or to troubleshoot/test something where you may
want to check the event before kicking off the WF....
 
Cheers
Mike
 
 
Dart, Jocelyn wrote:
> Mike,
> You should be using the event queue administration to control this.
> Transaction SWEQADM.
> If you reactivate the event linkage *** after resolving errors *** this
> should NOT require a transport
> - you just have to do it from the SWEQADM "linkages with errors" screen
> itself.
>
> Changing the event linkage any other way should require a transport.
> Jocelyn
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Michael Pokraka
> Sent: Tuesday,25 May 2004 3:04 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Changing event linkages in PRD
>
>
> Greetings all,
> I've noticed on our 4.7/620 system it is no longer possible to deactivate
> event linkage in production. Previously one could switch it off via PFTC but
> not on.
>
> Also, (I've asked this before), the alternative would be to mark linkage as
> having errors. This would for me be the ideal solution as it stores all the
> events which you can resubmit or delete afterwards. BUT event linkage status
> is also a transportable item. This makes it pretty useless.
>
> There were 'unofficial' ways around these in previous versions so it was
> never an issue, but I'd say it's an important safety feature to have in case
> things go wrong during a batch process or whatever. I've just seen another
> workflow bringing an entire system down because of this. Fortunately this
> one wasn't a productive one, but that has happened too...
>
> Any thoughts on this? Looking for ways to (temporarily) suspend a workflow
> linkage...
> Cheers
> Mike
>
>