Dynamic Action:

Dynamically triggering of an Infotype (defaulting some data too) based upon satisfying certain conditions.
If condition is satisfied it will populate Infotype, if condition is not satisfied it will not populate IT.

Actions will trigger Infotypes in a sequential order as defined in Info group.

Dynamic action will trigger the Infotype dynamically.
Dynamic actions will work from both PA30 and PA40.

Dynamic action can be defined at 3 levels.

1) Infotype Level
2) Subtype Level
3) Field Level

System default dynamic Actions

1) When IT 0194 is saved system populates IT 0195 (Its example for Infotype Level Dynamic Action)
2) When IT 0006, sub type 0001, Zip code field is created/changed system populates IT 0207 in background
(Field Level Dynamic Action)
3) When you maintain or change IT 0002 “Marital status” or “No of children” fields system populates IT 0021 with
respective subtype. (Field Level Dynamic Action)

The below is Dynamic action which we have written for the below requirement
When IT 0002 is created for first time, system should populate IT 0041 (This IT is not part of the Hiring Info group)
dynamically with “Hire Date” date type and Hire date.

U1 is date type for Hire date

T001P is table you can see its structure from SE11 and contents/data from SE16.
You need to know technical names thoroughly to write dynamic actions.
Table name for Dynamic actions is T588Z.

First 3 columns indicates Infotype Level, Sub type Level, Field Level

FC (Function Character): It indicates whether dynamic should work when you create an Infotype (04) or change an
Infotype (02) or either of the one (06).

02 for Change
04 for Create
06 for Change and create
08 for Delete
10 for Change and delete
12 for Create and delete
Step Indicator: (Also called as Plausibility check)
* - Comment, to write purpose of dynamic action, system will not read this, it is for our purpose
P – Checking condition
I – Insert an Infotype
W – Default a Value in an Infotype field
F – To call a Routine
V – Reference to another Step
M – Send a Mail

If you want to perform some calculations, formulas you can ask your ABAP’r to write a routine and you can call that
routine in dynamic actions.

Variable Function Part

This is the place where we write the actual logic of dynamic action

Another Requirement
When Basic Pay (IT 0008) is changed; system should populate IT 0041 with date type “U9 – Basic Pay Change date”
and date from when salary got changed.

Please note we are not supposed to change IT 0008 salary wage type amount directly, we need to run an action to do
so.

Same goes with “Change in Org Assignment”, if there is a change in PA, PSA, EG or ESG, that cant be changed
directly, we should run an action and then change these with an effective date.

To meet the above said requirement configure an action with name “Change in Basic Pay”

Creating a Info group ‘BP’

Info group Definition – Include Infotypes 0001, 0007 and 0008 in Info group
Please note for any action IT 0001 should be mandatory.
“Basic Pay Change” Action (IT0000) Definition

Define Reasons for Actions

Change action Menu – Add Action “Basic Pay Change” to PA40 screen under user group 44

Below is the dynamic action definition in table T588Z

Now Execute PA40 and run action “Basic Pay Change”, system populates IT 0041 with date type U9 and the date
when IT 0008 is changed (new effective date).
If an Infotype filed input is coming from a table, you can create new entries in that table from PA30 also.

 Execute PA30, select an EE, Enter IT 0041, Create /change

 Place your cursor on a date type, click on F4 to see drop down list
 Click on Create option
 Select continue without specifying project
 Select the appropriate module or node (It will be shown when a table has multiple nodes in SPRO, if not table
will be opened directly)
 Create new entries in the table.

You can create entries in table directly from SM30 (T548Y for date types) if you know the table OR
You can create new entries in a table from SPRO.