SAP-WUG Digest, Vol 38, Issue 76

Thu Jan 31 04:48:52 EST 2008

>
> Hi All,

Thanks for your replies.

I triggered the workflow using the PERSDATA.CREATED event, as only one event
was published in the system. To ensure that an employee was hired, the first
step of the workflow was a wait step for BUS1065.HIRED.

Carmen

> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 29 Jan 2008 21:49:51 -0000
> From: "Carmen Cheung" <carmen.cheung at roc-group.com>
> Subject: BUS1065 HIRED Event
> To: <sap-wug at mit.edu>
> Message-ID: <002401c862c0$e23c3aa0$4001a8c0 at rocgroup.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi All,
>
>
>
> I'm creating a notification workflow for when a new employee is hired
> (PA40)
> in R/3 4.7, using triggering event HIRED for BUS1065.
>
>
>
> The actual workflow is going fine, but the triggering event is being
> published twice in the system. I have tried to use the function module
> SAP_WAPI_WORKITEMS_TO_OBJECT to check if a workflow is already active and
> ensure the workflow is only triggered once, but to no avail.
>
>
>
> I have also tried triggering my own event to a delegate object and entered
> the configuration in SWEHR3. This also published duplicate events.
>
>
>
> Is there anyway to stop the duplicate event being triggered?
>
>
>
> Really appreciate any ideas.
>
>
>
> Many thanks,
>
>
>
> Carmen
>
>
>
>
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20080129/70b3c6f5/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Tue, 29 Jan 2008 16:12:00 -0800 (PST)
> From: <kaukabr at yahoo.com>
> Subject: Re: BUS1065 HIRED Event
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID: <345966.37062.qm at web55703.mail.re3.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
>
> Dear Carmen:
> I got the same problem, but now I triggered the new
> hire workflow on the basis of PERSDATA object. So when
> ever the personal data get created and save; only one
> triggering event will trigger.
> Try this option I hope it will help you.
> Aziz.
>
> --- Carmen Cheung <carmen.cheung at roc-group.com> wrote:
>
> > Hi All,
> >
> >
> >
> > I'm creating a notification workflow for when a new
> > employee is hired (PA40)
> > in R/3 4.7, using triggering event HIRED for
> > BUS1065.
> >
> >
> >
> > The actual workflow is going fine, but the
> > triggering event is being
> > published twice in the system. I have tried to use
> > the function module
> > SAP_WAPI_WORKITEMS_TO_OBJECT to check if a workflow
> > is already active and
> > ensure the workflow is only triggered once, but to
> > no avail.
> >
> >
> >
> > I have also tried triggering my own event to a
> > delegate object and entered
> > the configuration in SWEHR3. This also published
> > duplicate events.
> >
> >
> >
> > Is there anyway to stop the duplicate event being
> > triggered?
> >
> >
> >
> > Really appreciate any ideas.
> >
> >
> >
> > Many thanks,
> >
> >
> >
> > Carmen
> >
> >
> >
> >
> >
> >
> >
> > > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 30 Jan 2008 11:40:54 +1100
> From: "Cristiana D'Agosto" <cristiana.dagosto at au1.ibm.com>
> Subject: Re: BUS1065 HIRED Event
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
>        <
> OF6B880E18.AA61A801-ONCA2573DF.00811DC4-CA2573E0.0003BFE5 at au1.ibm.com>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Carmen,
>
> the HIRED event is published from Infotype 0001 (Function Module
> HR_EVENT_RULES_PA0001).
>
> I have seen the event being published twice when the position that you are
> hiring your employee has more than one relationship with different Org
> Units e.g.
>
> position 50000000
>
> 01.01.2007 - 14.02.2008 belongs to Org Unit 50000001
> 15.02.2008 - 31.12.9999 belongs to Org Unit 50000999
>
> If you hire an employee to this position on the 10.02.2008, the event will
> be published twice because the system will create 2 infotypes 0001 for
> this employee.
>
> I think an OSS should be raised so SAP can fix the way HIRED is published.
>
> Alternatively, you can try to 'play' with function module
> HR_EVENT_RULES_PA0001 and code something to prevent the event being
> published twice?
>
> I hope this helps.
>
> Good luck!
>
> Cristiana
> _________________________________
> Cristiana d'Agosto
> IBM Global Business Services
> Mobile:  +61 417 927 224
> cristiana.dagosto at au1.ibm.com
>
>
>
> "Carmen Cheung" <carmen.cheung at roc-group.com>
> Sent by: sap-wug-bounces at mit.edu
> 30/01/2008 08:49 AM
> Please respond to
> "SAP Workflow Users' Group" <sap-wug at mit.edu>
>
>
> To
> <sap-wug at mit.edu>
> cc
>
> Subject
> BUS1065 HIRED Event
>
>
>
>
>
>
> Hi All,
>
> I?m creating a notification workflow for when a new employee is hired
> (PA40) in R/3 4.7, using triggering event HIRED for BUS1065.
>
> The actual workflow is going fine, but the triggering event is being
> published twice in the system. I have tried to use the function module
> SAP_WAPI_WORKITEMS_TO_OBJECT to check if a workflow is already active and
> ensure the workflow is only triggered once, but to no avail.
>
> I have also tried triggering my own event to a delegate object and entered
> the configuration in SWEHR3. This also published duplicate events.
>
> Is there anyway to stop the duplicate event being triggered?
>
> Really appreciate any ideas.
>
> Many thanks,
>
> Carmen
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20080130/fa11c991/attachment-0001.htm
>
> ------------------------------
>
> Message: 4
> Date: Wed, 30 Jan 2008 09:35:58 +0000
> From: Mike Gambier <madgambler at hotmail.com>
> Subject: RE: BUS1065 HIRED Event
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID: <BAY117-W346E47314FB7AE52F85DA1D5360 at phx.gbl>
> Content-Type: text/plain; charset="windows-1252"
>
>
> Hi,
>
> No doubt, of course, you've checked your event linkages and made sure you
> only have 1 Receiver active for the event (seen that happen a lot because of
> test linkages on delegated objects). An event trace might show up multiple
> linkages if you can risk turning SWELS on for a bit.
>
> Assuming you have, this sounds like a issue with the standard SAP HR code
> being triggered twice synchronously and processed faster than the WAPI can
> read the database.
>
> We sometimes see this on high volume systems where COMMIT WORK statements
> (executed implicitly inside the code) aren't quite enough and you really
> need COMMIT WORK AND WAIT statements in the code (which SAP don't do that
> often).
>
> As a test you could implement a simple check Function Module against your
> event linkage in SWETYPV and put a break-point inside it and see when and
> how the event is triggered by the transaction. You might just spot a loop or
> something, unless the event is being issued asynchronously.
>
> Perhaps by using the event queue you could introduce a small enough delay
> to give the database more time to update the tables so that the WAPI has
> more of a chance to find the record, but seeing as the events are likely to
> be published in the same LUW I doubt it would help that much.
>
> If it is a SAP problem you might want to abandon the SAP event altogether
> (unless they provide a fix) and publish your own single event in a suitable
> exit somewhere. Sometimes SAP insist on raising multiple events during a
> session because that's the way they want to model the outcome of that LUW,
> so the multiple events you are seeing may actually be what they intend to
> happen rather than be down to a bug. In which case the event might not be
> the most appropriate way to trigger your Workflow.
>
> MGT
>
>
> To: sap-wug at mit.eduSubject: Re: BUS1065 HIRED EventFrom:
> cristiana.dagosto at au1.ibm.comDate: Wed, 30 Jan 2008 11:40:54 +1100Hi
> Carmen, the HIRED event is published from Infotype 0001 (Function Module
> HR_EVENT_RULES_PA0001). I have seen the event being published twice when the
> position that you are hiring your employee has more than one relationship
> with different Org Units e.g. position 50000000 01.01.2007 - 14.02.2008belongs to Org Unit 50000001
> 15.02.2008 - 31.12.9999 belongs to Org Unit 50000999 If you hire an
> employee to this position on the 10.02.2008, the event will be published
> twice because the system will create 2 infotypes 0001 for this employee. I
> think an OSS should be raised so SAP can fix the way HIRED is published.
> Alternatively, you can try to 'play' with function module
> HR_EVENT_RULES_PA0001 and code something to prevent the event being
> published twice? I hope this helps. Good
> luck!Cristiana_________________________________Cristiana d'AgostoIBM Global
> Busine!
> ss ServicesMobile:  +61 417 927 224cristiana.dagosto at au1.ibm.com
>
>
>
> "Carmen Cheung" <carmen.cheung at roc-group.com> Sent by:
> sap-wug-bounces at mit.edu
> 30/01/2008 08:49 AM
>
>
>
>
> Please respond to"SAP Workflow Users' Group" <sap-wug at mit.edu>
>
>
>
>
>
> To
> <sap-wug at mit.edu>
>
>
> cc
>
>
>
> Subject
> BUS1065 HIRED Event
>
>
>
>
> Hi All,   I?m creating a notification workflow for when a new employee is
> hired (PA40) in R/3 4.7, using triggering event HIRED for BUS1065.   The
> actual workflow is going fine, but the triggering event is being published
> twice in the system. I have tried to use the function module
> SAP_WAPI_WORKITEMS_TO_OBJECT to check if a workflow is already active and
> ensure the workflow is only triggered once, but to no avail.   I have also
> tried triggering my own event to a delegate object and entered the
> configuration in SWEHR3. This also published duplicate events.   Is there
> anyway to stop the duplicate event being triggered?   Really appreciate any
> ideas.   Many thanks,
> Carmen      _______________________________________________SAP-WUG mailing
> listSAP-WUG at mit.eduhttp://mailman.mit.edu/mailman/listinfo/sap-wug
> _________________________________________________________________
> Share what Santa brought you
> https://www.mycooluncool.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20080130/fb5151b0/attachment.htm
>
> ------------------------------
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> End of SAP-WUG Digest, Vol 38, Issue 76
> ***************************************
>

-- 
Carmen Cheung
roc
abbey house
wellington way
weybridge
surrey
kt13 0tt

phone:  +44 (0) 8702 414349
mbl:      +44 (0) 7887 842 812
fax:       +44 (0) 8702 415824
e-mail: carmen.cheung at roc-group.com
web: www.roc-group.com

The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorised. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. When addressed to our clients any
opinions or advice contained in this email are subject to the ROC standard
terms and conditions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080131/81fcf49a/attachment.htm