SWEHR3 Function

[Paul Batey]

Thanks Jocelyn,
 
Somehow it didn't sit right with me either, but the risk of stuffing up
an HR operation (however small) will surely kick this idea into touch.
 
Cheers,
 
Paul
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Dart, Jocelyn
Sent: Thursday, 6 November 2003 6:28 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: SWEHR3 Function
 
Hi Paul,
Using a tool for a purpose for which it was clearly never intended is
always extremely risky.
Doubt the LUWs will work out for this - and there is a risk that if
something goes wrong you could damage
the original HR operation - e.g. end up with inconsistent records.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Paul Batey [mailto:Paul.Batey at intelligroup.com.au]
Sent: Thursday,6 November 2003 2:14 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: SWEHR3 Function
 
 
Howdo,
 
Almost a workflow question.  In SWEHR3 you can use a function module to
pick an event to raise after a particular infotype operation.  EG when a
P0105 subtype 0001 changes or is created, I could link this to object
EMPLCOMM and in my function module create or change a user ID based on
the infotype data without going through the palaver of raising an event
and kicking off a workflow.  Is it advisable to use the function module
in this way?
 
Cheers,
 
Paul