Start worflow due to infotype fields changes

Serge Boulay Serge.Boulay at n-spro.com
Tue Jul 11 06:34:51 EDT 2006


Shai,

You can do it with what Jocelyn gave you. Like she said do some reading
around... But to help you, look at field, in transaction SWEHR3, where you
can put a function module... This is where you can control at the field
level.

Serge

-----Message d'origine-----
De : sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] De la part de
Shai Eyal
Envoyé : 11 juillet 2006 02:54
À : sap-wug at mit.edu
Objet : RE: Start worflow due to infotype fields changes

Dear Jocelyn,

I've used the transaction you mentioned, however it doesn't suite my
case. Whenever the workflow is triggered, the object (BUS1065) instance
values are fixed and I do not what have changed. In SWEHR3 I can trigger
event on change at infotype or subtype level but not on field change...

Thanks anyway,

Shai E.



Message: 2
Date: Tue, 11 Jul 2006 13:03:42 +0800
From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
Subject: RE: Start worflow due to infotype fields changes
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
	<F843AF000027394A9F3D3194109269F46445A3 at sgsine11.sin.sap.corp>
Content-Type: text/plain;	charset="us-ascii"

Use transactions SWEHR1, SWEHR2, SWEHR3 for HR infotype changes. 
There's plenty of doco on this so suggest you do some reading.  


Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug







More information about the SAP-WUG mailing list