Event Creation for HR Info type

[Van der Burg, Jeroen JA SITI-ITABEE]

Richard, probably due to the auto updates of the PA0001-ename field =
based on your changes to the individual name components on infotype 2. =
Include an exception for changes to the ename field in your triggering =
module.=20
 
Can be done by moving your infotype before image and infotype after =
image into infotype structures, so you can compare individual field =
changes. Also allows you to trigger workflows on every individual field =
change in HR infotypes :)
 
 
Regards,
 
 
Jeroen
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Richard Marut
Sent: 03 December 2004 03:58
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Event Creation for HR Info type
 
 
I setup the event creation for info types 0001, 0002, 0006 and 0041 for =
a
delete, insert and update and created my own function modules that end =
up
calling function module SWE_EVENT_CREATE to trigger my own events =
against my
own business object.
 
 
 
Everything works fine except when I process changes to info type 0002. =
What
happens is that the function module for info type 0002 executes in =
addition
to the function module for info type 0001. Somehow, SAP is starting the
function module for info type 0001 setup and passing all entries that =
exist
even though they are out of the valid validity date range and have not =
been
changed.
 
 
 
Has anyone ever encountered this before? I guess I could check for a =
valid
validity date but I would like to know why SAP is passing invalid =
entries in
addition to why it's even calling the function module for info type 0001
since I am processing info type 0002 and not 0001.
 
 
 
I'm on an Enterprise 4.7 system.
 
 
 
Richard.