uh-oh: verification workflow fails

[Bakker, Paul]

Free,
 
   Thanks, but I've already tried that. SAP just gives me the
popup: "Client xxx has status 'not modifiable'" and does not
allow me to save.
 
[ Oddly, I've noticed that you can *deactivate* event linkages
in a TST system (using this method), but not activate them. ]
 
 So it seems the only way to solve this problem is to create
a transport with the event linkage. It seems a little odd that=0D
you have to go to this effort to make a little verification workflow=0D
succeed....and that there's no mention of this necessary step
in The Book...
 
thanks
Paul
 
 
> -----Original Message-----
>> From: Kouw, FA - SPLXE [mailto:fa.kouw at td.klm.com]=0D
> Sent: Tuesday, 16 March 2004 01:20
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: uh-oh: verification workflow fails
>=0D
>=0D
> Hi,
>=0D
> There is a way to activate the event linkage directly on your=0D
> test system (4.6C):
>=0D
> Enter the workflow builder of the workflow, then choose 'Goto=0D
> - Basic data' and activate the linkage by selecting the grey=0D
> diamond. Hope this helps.
>=0D
> Regards,
>=0D
> Free Kouw
>=0D
> Vinod Ramchandani wrote:
>=0D
> > Paul..
> >
> > In Fresh Client, All Workflow Templates are de-activated by default.
> >
> > We need to activate them as well as to assign agents to the=0D
> standard=0D
> > tasks to customize them.
> >
> > 1) To activate workflow template in test system, create the=0D
> request in=0D
> > Development system with re-acivation of event.
> > 2) Transport that request to Test system.
> > 3) Refresh the Synchronous Buffer.
> > 4) Check with SWU0 - Simulate Event.
> >
> > Vinod.
> >
> > -----Original Message-----
> > From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On=0D
> Behalf Of=0D
> > Bakker, Paul
> > Sent: Friday, March 12, 2004 12:01 PM
> > To: SAP-WUG at MITVMA.MIT.EDU
> > Subject: uh-oh: verification workflow fails
> >
> > Hi All,
> >
> >   I've got a very basic problem: the verification workflow in SWU3=0D
> > doesn't work! It worked fine in our DEVelopment box, but in=0D
> our TEST=0D
> > environment I get the message:
> >
> >              Activate event linkage for workflow?
> >
> > If I answer yes, it then tells me that:
> >
> >              Client xx has status 'not modifiable'
> >
> > and then:
> >
> >              An error occurred activating the event linkage
> >
> > I investigated, and found that the linkage between the event=0D
> > WFTS.TRIGGERED and workflow WS30100051 (Verify) is not=0D
> active. And I=0D
> > can't activate it without creating a transport.
> >
> > So my questions are:
> > - is there any way to activate the event linkage directly=0D
> in our TEST=0D
> > system?
> > - or do I need to add this linkage to a change request in DEV and=0D
> > transport it?
> >
> > I'm surprised that this event linkage is inactive by=0D
> default. Is this=0D
> > the standard SAP setting? Why has no one else reported this=0D
> problem..?
> >
> > thankee
> > Paul Bakker
> > Brisbane, Australia
> >
> >=0D
> **********************************************************************
> > This email and any files transmitted with it are confidential and=0D
> > intended solely for the use of the individual or entity to=0D
> whom they=0D
> > are addressed. If you have received this email in error=0D
> please notify=0D
> > the system manager of QR.
> >
> > This message has been scanned for the presence of computer=0D
> viruses. No=0D
> > warranty is given that this message upon its receipt is=0D
> virus free and=0D
> > no liability is accepted by the sender in this respect.
> >
> > This email is a message only; does not constitute advice and should=0D
> > not be relied upon as such.
> >=0D
> **********************************************************************
> >
> >=0D
> ______________________________________________________________________
> > ___________________
> > This inbound message from KPN has been checked for all=0D
> known viruses by KPN IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl
> >=0D
> ______________________________________________________________
> _______________________________
>=0D
>=0D
> **********************************************************************
> This e-mail and any attachment may contain confidential and=0D
> privileged material intended for the addressee only. If you=0D
> are not the addressee, you are notified that no part of the=0D
> e-mail or any attachment may be disclosed, copied or=0D
> distributed, and that any other action related to this e-mail=0D
> or attachment is strictly prohibited, and may be unlawful. If=0D
> you have received this e-mail by error, please notify the=0D
> sender immediately by return e-mail, and delete this message.=0D
> Koninklijke Luchtvaart Maatschappij NV (KLM), its=0D
> subsidiaries and/or its employees shall not be liable for the=0D
> incorrect or incomplete transmission of this e-mail or any=0D
> attachments, nor responsible for any delay in receipt.
> **********************************************************************
>=0D
> ______________________________________________________________
> _______________________________
> This outbound message from KPN has been checked for all known=0D
> viruses by KPN IV-Scan, powered by MessageLabs. For further=0D
> information visit: http://www.veiliginternet.nl=0D
> ______________________________________________________________
> _______________________________
> Please visit http://www.klm-em.com for information about KLM=0D
> Engineering & Maintenance products and services.
>=0D
 
**********************************************************************
This email and any files transmitted with it are confidential and intended=
 solely for the use of the individual or entity to whom they are addressed.=
 If you have received this email in error please notify the system manager=
 of QR.
 
This message has been scanned for the presence of computer viruses. No=
 warranty is given that this message upon its receipt is
virus free and no liability is accepted by the sender in this respect.
 
This email is a message only; does not constitute advice and should not be=
 relied upon as such.
**********************************************************************