Why We Need Dynamic Actions?
Personnel administrators sometimes have the following problem when editing infotypes.
Depending on the conditions of the field values to be maintained, different follow-up actions often have to be carried out. Whether you set the marriage status to married or the number of children to 1 in infotype 0002, personal data can lead to different follow-up actions.
The solution to this requirement is a dynamic action that can automatically process further actions depending on certain conditions.
If you change the personnel data of an infotype, which then affects the data of a second infotype, the system automatically displays the infotype. The personnel administration component guarantees always-consistent data retention.
These dynamic actions are started automatically by the system, unlike the personal actions that you start by yourself. Dynamic actions assist you with many human resource processes that lead onto further activities.
In personnel administration customizing, you can set up user-defined processing chains that are suited to your company’s conditions.
Dynamic Actions
Dynamic actions are performed automatically by the system when specific conditions are met. For example, dynamic actions are set up on the Personal Data infotype (0002) to facilitate data entry. Based on entries in specific fields of this infotype, the system presents additional infotypes to ensure that complete information is stored.
Examples of infotypes dynamically called from the Personal Data infotype 0002 include the following:
| Field Completed on Personal Data Infotype 0002 | Infotype Dynamically Presented | Data Included |
|---|---|---|
Marital Status | Family Member/Dependents infotype 0021, subtype 1 Spouse | Information regarding the spouse |
No. of Children | Family Member/Dependents infotype 0021, subtype 2 Child | Information regarding the children |
Dynamic Actions – Principle
You can use dynamic actions to control actions that are initiated when maintaining an infotype record. In principle, it is an IF-THEN sequence.
IF condition:
The if condition can be defined in great detail for infotypes/subtypes/field values combined with individual processing steps, such as create or copy.
THEN sequence:
The consequence of the condition occurring can essentially be the following three actions:
- Maintaining an additional infotype record
- Sending mail using SAP Office
- Executing a routine