Common ABAP Function Modules – 1
Application Area – BC
Overview
In daily ABAP programming, we often need to use plenty of function modules. SAP doesn’t provide the detail API cookbook for these function modules. ABAPer always need to use their experience to use them freely. I try to list some common and useful fuction modules to my best and attach a short piece of description. For detail usage of these function modules, you can refer to the documentation as well as web resources. I plan to group the function modules to different functionalities, This post deals with the function module related to dynpro programming.
Function Modules Detail – Dynpro Programming
a) VIEW_MAINTENANCE_CALL – Call Extended Table Maintenance (View Maint) Highest Level like SM30.
b) DYNP_VALUES_READ – Read screen field values before PAI field transport. This function module reads screen field contents that are to be processed by the help modules.
c) DYNP_VALUES_UPDATE – Reset selected screen field contents. You can use this function module to reset selected help processor field contents in the corresponding screen fields. The module DYNP_GET_STEPL must first be called in strp-loop or table control to set the correct step-loop.
d) DYNP_GET_STEPL – In a module at the time Process On Value-Request (POV) or Process On Help-Request (POH), the function module defines the current step loop line from which the F4 or F1 help was called.The function module should always be called if one of the modules DYNP_VALUES_READ or DYNP_VALUES_UPDATE is used afterward.The value of the field STEP_LINE must be stored in field STEPL of table DYNPFIELDS of these two modules.
e) F4IF_INT_TABLE_VALUE_REQUEST - This module implements the standard help at POV while passing the values to be displayed in a table. The entire dialogue behaves as for a standard F4 help. This module also supports input help control.
f) F4IF_FIELD_VALUE_REQUEST – This module permits the implementation of the standard help for a screen field whose reference to the ABAP Dictionary is only known at runtime.If the module is called at the time PROCESS ON VALUE REQUEST, it behaves just like the standard help.
g) POPUP_TO_CONFIRM – The new POPUP_TO_CONFIRM includes the functions of the previous POPUP_TO_CONFIRM_….. . The transfer of diagnosis and question texts has been improved. The text length was previously limited to 3 times 35 characters. Diagnosis texts can now be any length, amd around 400 characters can be transferred in the question text.
h) POPUP_TO_CONFIRM_LOSS_OF_DATA – Do not use! Please use POPUP_TO_CONFIRM. This function module is obsolete.
i) POPUP_TO_SELECT_MONTH – Popup to choose a month
j) F4_DATE – Display factory calendar or Gregor. calendar and choose a day
k) SAPGUI_PROGRESS_INDICATOR – Display progress indicator in current window
l) GUI_FILE_LOAD_DIALOG/GUI_FILE_SAVE_DIALOG – Choose frontend file path and file name.
m) REUSE_ALV_GRID_DISPLAY – This must be the most important function module for ABAPer. We need to build lots of ALV report in each SAP implementation project.
n) Except function module, SAP has provided a class named ‘cl_gui_frontend_services‘ for some common functions. Method ‘FILE_OPEN_DIALOG‘ and ‘FILE_SAVE_DIALOG‘ can be used to show file choose dialog to frontend user.
