AW: Output Determination - Event not Triggering

[Schmidinger, Heinz (Unaxis IT BZ)]

Hi David,
 
do you have had a look to Tx SWID too ? Maybe they are in Status ERROR =
?
You can try to use SWI1 also to see if the WF was started.
Or are the Ebvents set up queued ? Than look to the Event-Queue, maybe =
the
Queue is not started, in error, ...
 
Regards
 
Heinz
 
-----Urspr=FCngliche Nachricht-----
Von: Bibby, David [mailto:david.bibby at Linklaters.com]
Gesendet am: Donnerstag, 31. Juli 2003 15:09
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Output Determination - Event not Triggering
 
Jeroen,
I have checked the entries in SWE2 and the delegation is also set up.
I have re-transported the table entry into R3Q and it still doesn't =
trigger
the workflow.
The event log shows the event triggering and when I test the workflow =
via
SWUE it finds the event VBRK.CREATED as the event receiver.
 
Regards
David
 
-----Original Message-----
From: Van der Burg, Jeroen JA SITI-ITPSEE
[mailto:jeroen.vanderburg at shell.com]
Sent: 31 July 2003 11:24
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Output Determination - Event not Triggering
 
 
Hi David,
 
Did you check the (normally generated) entries in SWE2? I have found =
that
this table can become 'confused' when using delegated objects. If that =
is
the case a manual change or complete table transport can normally =
easily
resolve the situation.
 
 
Regards,
 
 
Jeroen
 
-----Original Message-----
From: Bibby, David [mailto:david.bibby at Linklaters.com]
Sent: 31 July 2003 12:10
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Output Determination - Event not Triggering
 
 
Hello All,
We have a workflow that uses output determination on object VBRK and a
custom event 'CREATED' for application V3 ' Billing'.
This workflow is triggering in our DEV and PRD environments, but not in =
our
QA environment.
 
The config. looks identical i.e. in NACE etc. however with the client =
in QA
is a copy of a production client.
Has anyone come across this sort of thing before ?
Could it be the client copy that has caused the problem and if so can =
anyone
suggest a solution ?
Any help appreciated.
 
Many Thanks
David
 
 
________________________________________________
This message is confidential. It may also be privileged or
otherwise protected by work product immunity or other legal
rules. If you have received it by mistake please let us know
by reply and then delete it from your system; you should not
copy the message or disclose its contents to anyone.
 
Please refer to < http://www.linklaters.com/regulation > for
important information on the regulatory position of the firm.