Features are one of the ways in which SAP turns structured logic into something configurable. Typically, features use enterprise personnel fields (such as those from IT0001) to determine a default value. There are times, however, when the standard feature is not enough to meet your business requirements. This can happen if your business logic requires fields which are not available in the feature, or if your business logic is complex enough or long enough that it does not fit in , or becomes too confusing to work with, the feature. Fortunately, SAP provides ways to get the default values you need. We’ll take a quick look at the second scenario, where SAP allows you to call an ABAP program to accommodate your logic. Read more.
Viewing entries in
Creating dynamic actions to update infotype 41 is a challenge due to the fact that any given date type can exist in any one of the twelve available positions on the infotype. For example, one personnel number might have date type ‘XY’ in position two while another personnel number has the same date type in position four. There is also the possibility of one personnel number already having the desired date type while another is missing it. Because of this very real possibility of variation, a dynamic action to update infotype 41 cannot be configured using commands regarding explicit positions for the date types.
So now the question becomes how can a dynamic action be written to update infotype 41. The solution requires using ABAP form routines to determine the existing positions of the date types already stored on the current infotype 41 records and additional routines to either update an existing value or create a new date type entirely. The below dynamic action (Fig 1) is configured to update infotype 41 with the help of the custom ABAP form routines. Read more.