Scribd
Upload
11 views6 pages

Dynamic Actions

The document explains the concept of dynamic actions in SAP, specifically how certain infotypes can automatically trigger the creation of related infotypes when maintained. An example is provided where updating an employee's marital status to 'Married' prompts the creation of the Family member/dependents infotype. It details the configuration process for dynamic actions, including the necessary infotype, field, and function character settings required for triggering these actions.

Uploaded by

srinivas.jodu564
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
11 views6 pages

Dynamic Actions

The document explains the concept of dynamic actions in SAP, specifically how certain infotypes can automatically trigger the creation of related infotypes when maintained. An example is provided where updating an employee's marital status to 'Married' prompts the creation of the Family member/dependents infotype. It details the configuration process for dynamic actions, including the necessary infotype, field, and function character settings required for triggering these actions.

Uploaded by

srinivas.jodu564
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Dynamic Actions - Automatic Triggering/Populating of Infotypes When Certain

Infotypes are Dynamically Maintained, Table = T588Z


If you have maintained the Personal data infotype (infotype 0002) for an employee in
SAP, you may have observed that whenever the marital status is saved as “Married”,
the system automatically proposes the creation of the Family member/dependents
infotype (infotype 0021), subtype “Spouse”.

This has been depicted in the following screenshots.

Here, Figure 1 shows the Marital status being updated as “Married” using transaction
code PA30 (Maintain HR master data).

On saving the record, the Create Family Member/Dependents screen is automatically displayed,
as you can see in Figure 2. The subtype proposed is ‘Spouse’.
Personnel Management – Personnel Administration – Customizing Procedures – Dynamic
Actions

When you click on the Activity “Dynamic Actions”

To see the configuration of the dynamic action explained in the previous section, click on the
‘Position

Now, one question that may arise here is, which infotype should one enter in the above
screenshot? The answer is this – we need to search for the infotype that triggers the action, not
the infotype being triggered by the action. So, in our example, we should search for Infotype
0002 (Personal data).

These columns respectively contain the Infotype, subtype and field that trigger the
Dynamic action.
The column ‘Infotype’ is mandatory, as a dynamic action is triggered only on saving an
infotype.
The column ‘Subtype’ is optional and must be filled only if the Dynamic action should be
triggered on saving a particular subtype of the infotype.
The column ‘Field’ is also optional, and should be filled only if the Dynamic action
should be triggered on saving a particular field of the infotype.
Now, in our example, the Dynamic action is triggered on saving the ‘Marital status’ field
in the infotype. Hence let us further refine our search based on this field. Before doing
this, we should find out the technical name of the field. To do this, execute transaction
code SE11 and enter PA0002 as the Database table. PA0002 is the table that
corresponds to infotype 0002 (Personal data).
Search the Short description column for the Marital status field, we have highlighted it in the
screenshot. You can see the field name is FAMST.

that is, Infotype 0002 (Personal data) and Field name FAMST (Marital status),

Function Character – This column is highlighted in Figure 13. This indicates the infotype
processing type for which the dynamic action should be triggered.

It can have the following values:

00 – Independent of processing type


02 – Change
04 – Create
06 – Change and Create
08 – Delete
10 – Change and Delete
12 – Create and Delete
For example, if you enter the Function character 02, the dynamic action will be triggered
when the specified infotype is changed.
If you enter the Function character 06, the dynamic action will be triggered when the
specified infotype is created as well as when it is changed.
The next three columns indicate the Sequence number, Step and Variable function part.
While Sequence number is self-explanatory, the Step and Variable function part
columns need a detailed explanation and hence we have dedicated a sub-section to
these two columns.

Step and Variable Function Part


Step can be assigned any of the below possible values:
P – Check conditions
I – Maintain Infotype record
W – Set default values when creating a new record
V – Reference to another step
F – Call routine
M – Send mail

Of all the above values, just the values ‘P’, ‘I’ and ‘W’ are relevant to our example and these will
be explained in detail.

You might also like