Trigger Events/Messages based on Org Chart changes

Fri Dec 15 16:03:55 EST 2000

In IMG transaction SPRO follow the menu path for Dynamic Actions :

Personnel Management -->
   Personnel Administration  -->
       Customizing Procedures -->
          Dynamic Actions

Check the help (F1) on the 'S' column field and it'll explain some
more.

Here's the help from the online help:

Dynamic Actions
Here, you control the initiation of actions when maintaining an infotype
record.
This can be the maintenance of an additional infotype record or performin=
g a
routine.
For each action, you can determine whether it is always carried out when =
you
change an infotype or a subtype or whether it is only carried out if you
change certain fields.
You can state whether the action is to be carried out for "Change", "Crea=
te"
and/or "Delete" record.
You can store the conditions for executing the action, for example, the
comparison of the old and new value of a field.
Finaly, you can also specify default values for a record that is to be
created.

Example
When you create the infotype Contract Elements (0016), you predefine a
period for the probation period. The system creates a date/deadline recor=
d
so that you can invite the employee to an employee inteview.

The social insurance number does not exist. The system creates a
date/deadline record.

Standard Settings
The standard SAP system contains some sample dynamic actions.

Activities
1. Determine which infotype, subtype or field is to trigger a dynamic
action.
2. Determine the infotype operation (please refer to the field
documentation).
3. You can now set up different actions using a sequential number:
a) P - plausibility checks, that is conditions.
If you also use Recruitment, you must make sure that the dynamic action i=
s
started for the correct application. You do this, by first calling up the
transaction class:
PSPAR-TCLAS=3D"A" for Personnel Administration.
PSPAR-TCLAS=3D"B" for Recruitment.
b) I - infotype accesses
c) W - infotype values
d) F - access for internal or external routines
Calling up an internal routine: just specify the name of the routine, thi=
s
must be in the infotype's module pool "MPmmmm00". You cannot assign
using-parameters.
Calling up external routines: specify the name of the routine and, in
parentheses, the name of the program in which the routine can be found. Y=
ou
cannot assign using-parameters.
For additional information, refer to the documentation for the column
variable function part.
Further Notes
Creating a date/deadline record

Dynamic actions are normally used for creating date/deadline records.
However, the date of the deadline does not have to match the initializing
date, but can be varied by a certain time interval.
You can add or subtract a number of time units for an outgoing date. The
time units "days" (internal 010), "weeks" (011), "months" (012) and "year=
s"
(0=DF13) are supported.

Example

: A year after an examination (infotype Internal Medical Service (0028)),
the employee is to undergo a subsequent examination.
You must then call up infotype Monitoring of Date (0019) using the
date/deadline type "follow-up examination" (30).

  I INS,0019,30

Assignment of default values:
W P0019-TERMN=3DP0028-BEGDA
W P0019-VTRAN=3D'1' number
W P0019-VTRZH=3D'013' time unif from table T538T
W P0019-VTROP=3D'+' operation '+' or '-'
Calling up an external routine

In an external routine, you can check additional conditions, even for oth=
er
infotypes:
Data definition
Include a statement for the current infotype structure (for example: TABL=
ES:
P0006.)
In include MPPDAT00, the fields required for flow control of an infotype
dialog are defined in the common part. If you have this include in your
program, some fields are available immediately: The field string CSAVE
refers in each case to the old record whose values can be compared with t=
he
new values in the plausibility checks. To do this, define a second work a=
rea
for the infotype structure that is used to store the contents of CSAVE. T=
his
means that the individual names of the infotypes are given.
SAP recommends that you use the *-workarea for the infotype structure in
each case (for example: *P0006).
Internal table DYNMEAS: contains the infotype accesses (see indicator 'I'=
).
Internal table INITIAL_VALUES: contains the default values for an infotyp=
e
that is created or copied. (see indicator 'W').

You want to call up a report - for example, the writing of a letter.
Include a submit statement for this report in your routine.

Note on creating a batch input session:

Dynamic actions are not processed in a batch input session.
In batch input, you must specify the exact sequence of the screens. To
ensure this is the case, you must have already programmed the dynamic act=
ion
checks before you create the batch input session.

To avoid errors only the static actions are processed when you program an=
d
process a session. Infotypes that usually only appear in the system as a
result of a dynamic action should be updated by calling up the transactio=
n
separately.

Cheers
Dave

-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
tony hick
Sent: Friday, December 15, 2000 3:41 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Trigger Events/Messages based on Org Chart changes

Hi Dave and Rakesh:

I would be very interested in knowing more!
What is the menu path to Dynamic Actions?
What kind of position changes are you notifying?
Are you notifying changes of person assignments to positions?

Thanks!
Tony

>From: David Weston <weston at clockwork.ca>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Trigger Events/Messages based on Org Chart changes
>Date: Fri, 15 Dec 2000 13:10:30 -0500
>
>Hi Rakesh
>
>This is a coincidence but this requirement just came up on my
>current project where they want to be notified on position changes.
>
>Just looked at the Dynamic Actions config in HR via SPRO and was wonderi=
ng
>which options you used ie was it an M for mail entry ? Also would you be
>willing
>to share the function module info i.e. was it a standard SAP FM or was i=
t
>a customer developed function module ?
>
>Any help would be great.
>
>Cheers
>Dave
>
>
>-----Original Message-----
>From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
>Rakesh Dube
>Sent: Thursday, December 14, 2000 10:59 PM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Trigger Events/Messages based on Org Chart changes
>
>
>Hi Tony,
>We did same scenario in one of the project but here we used Dynmic actio=
n
>rather then
>Workflow.
>In Dynmic action customization we trigger the function module
>FUnction module will send  mail to the appropriate person.
>This is one of the way to trigger mail ,
>
>Org chart hierarchy is saved in table HRP1001.
>If u need more detail in this let me know
>Thanks
>Rakesh
>
>
>
>tony hick wrote:
>
> > Hi All,
> >
> > We maintain our employee resources in the Org Chart (PPOME). The
>resources
> > (employees) are assigned to different projects (which are represented=
 as
> > Positions in the Org Chart),  by moving them from one position to
>another,
> > using drag and drop.
> >
> > We would like to trigger an email to the responsible persons of the n=
ew
> > Position, the old Position, and to the Person who has been assigned,
> > informing this change as a text message, when the change is saved.
> >
> > Any ideas on how this can be triggered?  Are there any events associa=
ted
> > with saving the Org Chart (PPOME) that I can use? What tables are the
>Org
> > chart hierarchy saved in?
> >
> > Thanks,
> > Tony
> >
>________________________________________________________________________=
___
_
>_________
> > Get more from the Web.  FREE MSN Explorer download :
>http://explorer.msn.com

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com