Event Queuing inside workflows

[Yung. David]

Got it!! (I think) Just creating the entry manually.... dah!

Thanks

David

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Yung. David
Sent: 14 March 2005 11:18
To: 'SAP Workflow Users' Group'
Subject: RE: Event Queuing inside workflows

Using transaction SWEINST (also found SWE3 to be the same) I can see the
event which I want to "queue up" in our production system but I can not see
it in the Dev.  System.  Mind that in our Dev. Client this workflow has
never been run as it is a clean configuration client (no data).

I can only assume that the entry into tables SWETYPECOU and SWETYPEENA
(which transaction SWEINST looks at) are only created when a workflow that
is running receives the event in question.  Does this sound right?

In any case, is there a way for this event to show up in our dev client
without having to actually run the workflow?  I just need the event to show
up in transaction SWEINST so that I can set the event queue flag and
transport the change...   I tried transaction SWE5 (Consistency check for
event Linkages) but to no avail.

Regards,

David

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Michael Pokraka
Sent: 10 March 2005 13:19
To: SAP Workflow Users' Group
Subject: Re: Event Queuing inside workflows

SWEINST
Cheers
Mike

--- "Yung. David" <David.Yung at esb.ie> wrote:
> Hello gang, 
> 
> Here's a question for you, turning on event queuing for the start of
> workflows is straightforward enough by doing the proper steps for Event
> Queue Administration and specifying the events you want to go through the
> queue using transaction SWE2 or SWETYPV.  Now this all works well when the
> event is starting a workflow but when you have an event which triggers a
> step within an already running workflow, this event does not appear in the
> before mentioned transactions...
> 
> The problem it's causing us is that there are a large number of workflows
> waiting for an event which gets triggered by an upload program that runs
in
> batch.  This causes a huge number of workflows to start at once.
> 
> Does anybody know why this happens and if there's any other transaction
> which allows me to specify that an event that triggers a step within a
> workflow should be queued as well?
> 
> We are running R/3 release 4.6C, IS-U 4.64.
> 
> Regards,
> 
> David
> 
> 
> * ** *** ** * ** *** ** * ** *** ** * 
> 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. 
> Any views or opinions presented are solely those of the author, and do not
> necessarily 
> represent those of ESB. 
> If you have received this email in error please notify the sender. 
>  
> Although ESB scans e-mail and attachments for viruses, it does not
guarantee 
> that either are virus-free and accepts no liability for any damage
sustained 
> as a result of viruses. 
>  
> * ** *** ** * ** *** ** * ** *** ** *
> 
> > _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug