Event Type Linkages set to "Do not change linkage"

[Michael Pokraka]

Hi Helene,
The difference between them is what happens _after_ an error occurs:
 
In my experience 'Deactivate linkage' should never be set as a production
default. It means your linkage is deactivated and no more workflows will
run, subsequent events are lost until you reactivate it by a transport fr=
om
dev.
 
'Mark linkage' is a good idea, however I personally think badly implement=
ed
as you can't unmark the linkage without a transport. It means that no
workflows will be started after a linkage error, BUT the events are store=
d
in the queue.
 
'Do not change' simply stores the errored event in the queue and continue=
s
to process any following events as normal. Thus only the errored events a=
re
stored in the queue and successful ones will still start the WFs.
 
In my opinion, you need to have a definite reason to use 'Mark linkage',
e.g. if workflows are critical and you're paranoid and want to stop the b=
us
on any hint of a problem (outgoing invoice processing?); or if you have a
batch scenario where you're starting 100's of flows together and/or have
system load issues that may cause a problem if things go wrong. You can s=
et
these individually in any case.
 
Cheers
Mike
 
HELENE_PAQUIN at acdi-cida.gc.ca wrote:
>
> Thank you very much Michael, your info sent me in the right direction.
>
> I have since read good messages from Jocelyn Dart on this subject.  In =
the
> transaction SWEQADM, she recommends setting the "Basic Data" -  "Behavi=
our
> on error feedback" to be "Mark linkages as having errors".
>
> What I would like to know is what are the disadvantages or advantages o=
f
> using "Do not change Linkage" versus "Mark linkages as having errors"?
>
> Our actual set-up:
>
> In production, in the "Basic data" tab of SWEQADM we are still on
> "Deactivation of linkage" and we have on the "Overview" tab:  "Event qu=
eue
> switched off".  But we have just transported to Production two of our e=
vent
> linkages which we have changed from "Deactivation of linkage" in SWETYP=
V
> to:  "Do not change Linkage"; we transported these changes in order to
> prevent the event linkages to get de-activated in Production whenever a=
n
> error is encountered.
>
> All comments to get our Production Environment to its best are welcome.
>
> Thank you!
>
>
> H=E9l=E8ne Paquin
> 819-994-2249 | helene_paquin at acdi-cida.gc.ca | T=E9l=E9copieur/Facsimil=
e:
> 819-953-6359
>
> Administratrice des d=E9roulements SAP, Application et soutien (TID)
> Direction g=E9n=E9rale de la gestion de l'information et de la technolo=
gie
> Agence canadienne de d=E9veloppement international
> 200, promenade du Portage, Gatineau (Qu=E9bec)
> Canada K1A 0G4
>
> SAP Workflow Administrator, Information Technology (ITD)
> Information Management and Technology Branch
> Canadian International Development Agency
> 200 Promenade du Portage, Gatineau (Quebec)
> Canada K1A 0G4
>
>
>
>
>                       Michael Pokraka
>                       <workflow at quirky.me         To:
> SAP-WUG at MITVMA.MIT.EDU
>                       .uk>                        cc:
>                       Sent by: SAP                Subject: Re: Event Ty=
pe
> Linkages set to "Do not change linkage"
>                       Workflow
>                       <Owner-SAP-WUG at MITV
>                       MA.MIT.EDU>
>
>
>                       2004-04-15 12:54 PM
>                       Please respond to
>                       SAP Workflow Users'
>                       Group
>
>
>
>
>
> That would be the event queue, SWEQADM.
> Note, it is used for event-based error handling even if you do not actu=
ally
> use it for normal processing. In other words, you do not need to schedu=
le
> the job if you do not otherwise use the event queue.
> Cheers
> Mike
>
> HELENE_PAQUIN at acdi-cida.gc.ca wrote:
>> Hello workflowers:
>>
>> Recently, in Production (Version 4.6C) we have changed our linkage
> settings
>> to:  "Do not change linkage".
>>
>> In the documentation it is said that "If an error is discovered the
>> relevant events are stored temporarily."
>>
>> My question is:  Where exactly would the errors be stored should they
> occur
>> and via which transaction would the Workflow Administrator access thes=
e
>> errors?
>>
>> Thank you!
>>
>>
>>
>> H=E9l=E8ne Paquin
>> 819-994-2249 | helene_paquin at acdi-cida.gc.ca | T=E9l=E9copieur/Facsimi=
le:
>> 819-953-6359
>>
>> Administratrice des d=E9roulements SAP, Application et soutien (TID)
>> Direction g=E9n=E9rale de la gestion de l'information et de la technol=
ogie
>> Agence canadienne de d=E9veloppement international
>> 200, promenade du Portage, Gatineau (Qu=E9bec)
>> Canada K1A 0G4
>>
>> SAP Workflow Administrator, Information Technology (ITD)
>> Information Management and Technology Branch
>> Canadian International Development Agency
>> 200 Promenade du Portage, Gatineau (Quebec)
>> Canada K1A 0G4
>>
>>
>
>
>
>