SWEHR3 - T779X - Custom or standard events

[Koenraad Janssens]

Hi
 
I think with SWE_EVENT_CREATE you should always use an explicit commit to trigger.
There are however other functions to trigger events which don't need an
explicit commit (and you should use these in transactions.. so the commit
of the transaction will trigger the events.)
These are
SWE_EVENT_CREATE_FOR_UPD_TASK
SWE_EVENT_CREATE_IN_UPD_TASK
 
For the exact use: check WF course book  ...  I think the FOR_UPD_TASK is
preferred.
 
Kind regards
 
Koenraad Janssens
Sidmar N.V.- ISM
Leverage Team - Programmer
Tel: +32 9 347 35 76
E-mail: koenraad.janssens at sidmar.arcelor.com
 
 
 
 
 
 
 
tom.olaf at spring.no
Sent by: Owner-SAP-WUG at MITVMA.MIT.EDU
04/03/2004 11:05
Please respond to SAP-WUG
 
 
        To:     SAP-WUG at MITVMA.MIT.EDU
        cc:
        Subject:        SWEHR3 - T779X - Custom or standard events
 
 
Hi.
 
I will be developing custom function modules for triggering various HR
events
in training and other HR scenarios in 4.7. I've checked wugarchive and
found
quite a few interesting threads concerning this issue. Seems to be quite a
few
people with insight on this matter (Joeren and others). I have two
specific
questions:
 
1. For training and event management, an event will be triggered if an
employee tries to book and does not have authorization for booking. If I
create an entry in T779X for the specific logical function (f.ex BOKP or
BOKF)
and trigger the standard event pdrela_025->requested, will two events be
triggered? Is it better to define a custom event by extending the standard
object type?
 
2. This question might be to general, but here goes. There has been a
discussion about missing commit for calls of function SWE_EVENT_CREATE in
some
HR scenarios. Is there any general "rule" to have an explicit commit or
not
when using custom defined functions in T779X? I'm just concerned that a
commit
might disturb the standard application update, but if this is really an
issue
depends on when the function is called.
 
Thanks
Tom
 
 
 
 
***********************************************************************************
This message should only be read by those persons to whom it is
addressed, and may contain confidential information, the disclosure
of which is prohibited. This message is not intended to create rights
or obligations without subsequent written confirmation of its contents.
If you have received this message in error, please notify us immediately
***********************************************************************************