Event trace query

[Paul Batey]

Hi Irene,
 
You may have a spot of bother using the standard OMGQ workflow config
for release strategies as if I remember rightly your site does (or did)
not use the standard release strategy with classification.  How do they
want you to improve the workflow?  If you have a handle on workflow
development again why not try to get onto the BIT610 course in Sydney on
24-26 November, I hear the trainer is really good.
 
Cheers,
 
Paul
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Paulino, Irene
Sent: Thursday, 16 October 2003 10:54 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Event trace query
 
Ok. Thanks for that!
 
I haven't done any workflow development for 2 years now.
 
I just did the training and workflow admin and now they want me to
improve
current one which I didn't develop thus I am re-learning everything
again.
 
Assistance much appreciated!
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Thursday, 16 October 2003 10:28 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Event trace query
 
 
Irene,
Event linkage for Purchase Requisitions is NOT based on change document
objects.
You need to set up the events by setting up the Release Strategy with
Classification configuration and
related workflow settings in the IMG.  Please read the help in the SAP
Library on the workflow scenario for
purchase requisitions for more information.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Paulino, Irene [mailto:Irene.Paulino at kcc.com]
Sent: Thursday,16 October 2003 5:26 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Event trace query
 
 
Follow-on question:
 
Why is it that workflow gets triggered when I start it using trx SWUS
and
workflow doesn't get triggered when I just initiate the event using the
SAP
standard application of ME52N?
 
WS90000030 generates a work item when I start it using trx SWUS but no
work
item gets generated when I trigger the same event using ME52N where I
change
the GL account or cost centre?
 
Can anybody help me?
 
-----Original Message-----
From: Paulino, Irene
Sent: Tuesday, 14 October 2003 3:51 AM
To: 'SAP Workflow Users' Group'
Subject: Event trace query
Importance: High
 
 
 
 
BUS2105 SIGNIFICANTLYCHANGED    13.10.2003      16:55:04
EVENTITEM
SWW_EI_EVENT_RECEIVE
 
BUS2105 SIGNIFICANTLYCHANGED    13.10.2003      16:55:04
WS90000030
SWW_WI_CREATE_VIA_EVENT
 
BUS2105 SIGNIFICANTLYCHANGED    13.10.2003      17:16:42
No receiver entered
 
Hi all!
 
Listed above is Event trace list. First line indicates that I have not
linked my workflow to the object type BUS2105 and event
SIGNIFICANTLYCHANGED
thus when I changed a requisition, EVENTITEM was the receiver type.
 
Second line shows that I linked object type BUS2105 to WS90000030 and is
active in our TST client. I got the second line when I triggered the
workflow using trx SWUS.
 
Third line shows that there was no receiver type when I changed the GL
account of a requisition using ME52N, the link with WS90000030 becomes
deactivated. Why did this happen?
 
I activated the event linkage for change document object BANF business
object type BUS2105 event SIGNIFICANTLYCHANGED and put field
restrictions
when there are changes to the GL account, cost center, valuation price
and
order no. Then I linked this object type to WS90000030.
 
Why is it that my event linkage to the workflow template gets
deactivated
when I do requisition changes? Thus when you look at event trace, there
is
no receiver type for the event triggered.
 
Can anybody give me a clue as to what I should look for?
 
Assistance greatly appreciated.
 
Cheers,
Irene Paulino
 
------------------------------------------------------------------------
----
--
This e-mail is intended for the use of the addressee(s) only and may
contain
privileged, confidential, or proprietary information that is exempt from
disclosure under law.  If you have received this message in error,
please
inform us promptly by reply e-mail, then delete the e-mail and destroy
any
printed copy.   Thank you.
 =======================================================================
====
==
 
------------------------------------------------------------------------
------
This e-mail is intended for the use of the addressee(s) only and may
contain
privileged, confidential, or proprietary information that is exempt from
disclosure under law.  If you have received this message in error,
please
inform us promptly by reply e-mail, then delete the e-mail and destroy
any
printed copy.   Thank you.
 =======================================================================
======