Passing HR infotype start date to an event

[Michael Pokraka]

Indeed that is how it works - we're using BUS1065 and EmployeeT is an eve=
nt
parameter. OK, I should have thought of looking at the event params. All
works as planned.
Thanks to both for your replies,
Cheers
Mike
 
Dart, Jocelyn wrote:
> Mike,
> Most infotype-based business objects provide the "Aggregate" attribute =
which
> contains an instance of the EMPLOYEET object for the employee and
> validitybegin date of the infotype.
> You should just be able to use this attribute directly to fill your wor=
kflow
> container element or in your event start condition if that's what you a=
re
> doing.
> See business object EMPLCOMM for an example
>
> So long as your event is based on the business object for that infotype=
 you
> shouldn't need to do anything special.
>
> Plus all HR events that I've dealt with always pass an EMPLOYEET instan=
ce as
> a event parameter.  As all HR events are handled by central routines if=
 you
> look at standard HR events you can see that they all include two event
> parametesr:
> * Employee - an instance of EMPLOYEE
> * EmployeeUser - an instance of EMPLOYEET
>
> So if you are using your own event, you might want to try defining the =
event
> parameter "EmployeeUser" as an instance of Employeet and that should be
> enough to pick up the correct employeet instance.
>
> Jocelyn
>
> -----Original Message-----
>> From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Michael Pokraka
> Sent: Friday,28 May 2004 5:03 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Passing HR infotype start date to an event
>
>
> Greetings all,
> The subject says it all: I want to know the start date of an infotype w=
hen
> an event is raised.
> We've specified a custom function in T779X to raise an event when a Per=
son
> is updated. However the update is usually future-dated and may even be
> delimited. afterimage-begda is available within the FM and what I'm loo=
king
> for, but I cannot pass anything other than an event name out of the FM.=
.. so
> near and yet so far! Would be nice to fill an event container at this p=
oint.
>
> The issue behind all this is that the WF needs to instantiate an EMPLOY=
EET
> object based on the start time specified in the update that raised the
> event, just in case someone has a completely different alternative....
>
> Any insight appreciated,
> Cheers
> Mike
>
>