Simultaneous change documents only triggering one event

[Chatterjee, Partha (US - San Ramon)]

Hi Ramki,
 
The problem is not multiple events on a single change document object--I
already have that and that functions correctly.
 
The problem is I need multiple events triggered simultaneously from the
same change document number.  In my case, I have multiple entries for
the same change document number (different table keys for each entry) in
CDHDR table.  SAP is kicking off an event for the first record in a
single change document but ignoring the others since the other entries
do not have their own change document number but rather just their own
unique tabkey entry under the same change document number.
 
I suspect this functionality is as intended by SAP but I need some way
of working around it if there is not configuration to change the
functionality.
 
With regards,
Partha Chatterjee
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Workflow99 at aol.com
Sent: Wednesday, September 29, 2004 12:13 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Simultaneous change documents only triggering one event
 
Hi Partha,
 
I have multiple events defined on a single change document object and
all  my
events trigger correctly (R/3 6.20). One option is to write an event
function
 module for the triggered event and control the triggering of the second
event  from there.
 
 
Regards,
Ramki Maley
Workflow Developer,  USCBP.
248-613-1287 (C)
 
 
In a message dated 9/29/2004 2:58:23 PM Eastern Standard Time,
pchatterjee at deloitte.com writes:
 
Hi  All,
 
I have change documents to trigger workflows in the EHS  area.  They
work
fine, however, when I save 2 records at the same time  and they create 2
simultaneous change documents (same change document  number but
different
table keys) they only trigger one of the 2 necessary  events.
 
I would expect to see 2 events raised but I only see one.   I have
turned
on the Event Queue and it only sees one event as  well.
 
I can think of a workaround where I can use the event that does  trigger
to start the workflow and then have a background step that checks  if a
second (third, fourth etc.)workflow should be started but I would
prefer
to change the problem at the source.
 
Any  ideas?
 
Thanks,
Partha Chatterjee
 
 
 
 
This message  (including any attachments) contains confidential
information
intended for a  specific individual and purpose, and is protected by
law.  If
you are not  the intended recipient, you should delete this message.
Any
disclosure,  copying, or distribution of this message, or the taking of
any action
based on  it, is strictly prohibited.
 
 
 
 
This message (including any attachments) contains confidential =
information intended for a specific individual and purpose, and is =
protected by law.  If you are not the intended recipient, you should =
delete this message.  Any disclosure, copying, or distribution of this =
message, or the taking of any action based on it, is strictly =
prohibited.