Multiple event triggers - solved

Thu Jan 10 04:18:08 EST 2002

Hi

Thanks to everyone who responded. It was sorted out in an OSS. For those
interested, for HR, table T779W holds the SAP event linkages which were
correctly maintained for IT0000 and IT0001, but some-one had also loaded =
the
same objects and events to the customer event linkage table T779X. Deleti=
ng
these entries solved the problem.

Regards

Jos=E9 Burgman

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Becker Stephan (extern)
Sent: 09 January 2002 11:59
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Multiple event triggers

Jose,

which standard program and table are you talking about?

Another way to solve this is with a check function module that uses
something like "SAP_WAPI_WORKITEMS_TO_OBJECT" to check if instances for t=
he
same object already exist.

Stephan

-----Original Message-----
From: Jose Burgman [mailto:jose.burgman at ast.co.za]
Sent: Thursday, December 27, 2001 7:02 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Multiple event triggers

Thanks for your speedy response, Diane!

I tried this and it did not work... I suspect that the SAP standard progr=
am
triggers the event every time it does a loop pass through the table. The
number of triggers I receive appears to be equal to the number of lines i=
n
the table. Back to the drawing board, so to speak....

Compliments of the season.

Regards
Jose Burgman

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Nobles, Diane
Sent: 21 December 2001 04:33
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Multiple event triggers

Hi Jose, I have had this problem in other areas of WF.  Try this.  Remove
your event trigger and perform the transaction again.  Check your event l=
og
and see if any events were created.  We had a WF that was using an object=
 to
create an event and trigger our workflow.  The event was also being creat=
ed
by another program hard coded in SAP so we were getting two triggers of
which both triggered my workflow.  When I removed my triggering event, th=
en
I only had one trigger.  Unfortunately we never could find the SAP progra=
m
that was creating the first event, but we were only getting one trigger. =
 I
understand this has happened in more than one case.  Hope this helps.

Merry Christmas and Happy New Year

Diane H. Nobles
SDE PM Team
(757)380-7250
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
God has not given us a spirit of fear but
of power, love and a sound mind. 2Tim 1:7

-----Original Message-----
From: Jose Burgman [mailto:jose.burgman at ast.co.za]
Sent: Friday, December 21, 2001 8:18 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Multiple event triggers

Hi there

I've come across a problem that I'm unsure how to resolve. I thought
initially that it was my workflow until I switched on the event trace. Th=
e
scenario is as follows: when an employee is transferred or terminated, an
email must be sent to recruitment. The actions are performed by using
transaction PA40. The business object that I am using is BUS1065. For som=
e
unknown reason, when a transfer/termination is done using this transactio=
n,
the event is generated multiple times and obviously the emails are genera=
ted
the same number of times -- the information in terms of change/terminatio=
n
dates are not always the same in these emails though - dates drawn from
other actions are sometimes pulled through. Has anyway encountered this
before and does any one have a solution? Oh, we're on 4.6B package level =
43
for HR and the rest is on package level 32.

Much appreciated.

Regards

Jose Burgman

______________________________________________

"This information is intended only for the person or entity to which it i=
s
addressed and
may contain private, confidential, proprietary and/or privileged material
and may be subject
to confidentiality agreements.

Any review, retransmission, dissemination, or any other use of or taking =
of
any action in
reliance upon this information, by persons or entities other than the
intended recipient,
is prohibited.

If you received this in error, please contact the sender and delete the
material from all
storage media.

The company is neither liable for proper, complete transmission of the
information contained
in this communication, any delay in its receipt or that the mail is
virus-free"

______________________________________________

"This information is intended only for the person or entity to which it i=
s
addressed and
may contain private, confidential, proprietary and/or privileged material
and may be subject
to confidentiality agreements.

Any review, retransmission, dissemination, or any other use of or taking =
of
any action in
reliance upon this information, by persons or entities other than the
intended recipient,
is prohibited.

If you received this in error, please contact the sender and delete the
material from all
storage media.

The company is neither liable for proper, complete transmission of the
information contained
in this communication, any delay in its receipt or that the mail is
virus-free"

______________________________________________

"This information is intended only for the person or entity to which it i=
s addressed and=20
may contain private, confidential, proprietary and/or privileged material=
 and may be subject
to confidentiality agreements.

Any review, retransmission, dissemination, or any other use of or taking =
of any action in
reliance upon this information, by persons or entities other than the int=
ended recipient,
is prohibited.=20

If you received this in error, please contact the sender and delete the m=
aterial from all=20
storage media.

The company is neither liable for proper, complete transmission of the in=
formation contained
in this communication, any delay in its receipt or that the mail is virus=
-free"