Here, you control the initiation of actions
when maintaining an infotype record.
This can be the maintenance of an additional infotype record or performing 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", "Create"
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.
When you create the infotype Contract Elements (0016), you predefine a period for the probation period. The system creates a date/deadline record 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.
The standard SAP system contains some sample dynamic actions.
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 "years" (0ß13)
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,30Assignment of default values:
Calling up an external routine
In an external routine, you can check
additional conditions, even for other infotypes:
Data definition
Include a statement for the current infotype structure (for example: TABLES:
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 the new
values in the plausibility checks. To do this, define a second work area for
the infotype structure that is used to store the contents of CSAVE. This 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 infotype
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 action checks
before you create the batch input session.
To avoid errors only the static actions are processed when you program and 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 transaction separately.