Even linkage broken after update to 4.70

Dart, Jocelyn jocelyn.dart at sap.com
Wed Oct 8 22:52:02 EDT 2003


Please note everyone, this is NOT a bug but depends on your workflow =
configuration - specifically the configuration of the Event Queue.=20
 
This configuration is in transaction SWEQADM on the "Basic Data" tab.=20
To be consistent with prior releases the default behaviour on event =
error is set to "Deactivation of Linkage".
 
>From 4.6C onwards the most appropriate setting for "Behaviour on Error =
Feedback" is "Mark linkage as having errors".=20
This stops the event linkage being deactivated in the event of an =
error, instead the event linkage is sent to the "Linkages in Error" tab =
in transaction SWEQADM. From "Linkages in Error" you can reactivate the =
event linkage WITHOUT having to create a transport.=20
Regards,
        Jocelyn Dart=20
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"=20
SAP Australia
email: jocelyn.dart at sap.com=20
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Michael Pokraka [mailto:workflow at quirky.me.uk]=20
Sent: Wednesday,8 October 2003 10:51 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Even linkage broken after update to 4.70
 
 
Hi Ute,=20
You should be able to deactivate and reactivate the linkage in dev to =
create a new transport just for that particular linkage.=20
If not, remove the offending entry manually from whichever transport =
it's in and this should once again be possible.=20
HTH
Cheers
Mike
 
On Wed, Oct 08, 2003 at 12:01:54PM +0200, "Schr=F6der, Ute Marion" =
wrote:
> Hi everybody,
>=20
> we are right now upgrading our systems to 620.
>=20
> During the tests, following the update of our test-system, an error
> occurred.
> One of our workflows has not been started.
> Transaction SWUD showed that the event linkage is deactivated.
> Due to the system status being 'not modifiable', is there any other =
chance
> to activate this event?
>=20
> Transport from the development system is impossible due to
> workflow-development being in process.
>=20
> Any other idea?
>=20
> Thanx
>=20
> Ute
 


More information about the SAP-WUG mailing list