SAP FM_CONTROL_DATA_GET Function Module for
FM_CONTROL_DATA_GET is a standard fm control data get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for fm control data get FM, simply by entering the name FM_CONTROL_DATA_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMSV
Program Name: SAPLFMSV
Main Program: SAPLFMSV
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_CONTROL_DATA_GET pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'FM_CONTROL_DATA_GET'".
EXPORTING
I_PROFIL = "
* I_WRTTP = "
* I_VRGNG = "
* I_SPRAS = "
* I_FLG_ORIG_VALTYPE_PROFIL = ' ' "
IMPORTING
E_F_FMUP01 = "
E_F_FMUP00 = "
E_F_FMUP00T = "
TABLES
* T_FMUP01 = "
EXCEPTIONS
NO_ENTRY_FOUND = 1 NO_ENTRY_FOUND_WRTTP = 2 WRTTP_PARAMETER_MISSING = 3
IMPORTING Parameters details for FM_CONTROL_DATA_GET
I_PROFIL -
Data type: FMUP00-PROFILOptional: No
Call by Reference: No ( called with pass by value option)
I_WRTTP -
Data type: FMUP01-WRTTPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_VRGNG -
Data type: FMUP01-VRGNGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SPRAS -
Data type: FMUP00T-SPRASOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_ORIG_VALTYPE_PROFIL -
Data type: FMDY-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FM_CONTROL_DATA_GET
E_F_FMUP01 -
Data type: FMUP01Optional: No
Call by Reference: No ( called with pass by value option)
E_F_FMUP00 -
Data type: FMUP00Optional: No
Call by Reference: No ( called with pass by value option)
E_F_FMUP00T -
Data type: FMUP00TOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FM_CONTROL_DATA_GET
T_FMUP01 -
Data type: FMUP01Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_ENTRY_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ENTRY_FOUND_WRTTP -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRTTP_PARAMETER_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FM_CONTROL_DATA_GET Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_i_profil | TYPE FMUP00-PROFIL, " | |||
| lt_t_fmup01 | TYPE STANDARD TABLE OF FMUP01, " | |||
| lv_e_f_fmup01 | TYPE FMUP01, " | |||
| lv_no_entry_found | TYPE FMUP01, " | |||
| lv_i_wrttp | TYPE FMUP01-WRTTP, " | |||
| lv_e_f_fmup00 | TYPE FMUP00, " | |||
| lv_no_entry_found_wrttp | TYPE FMUP00, " | |||
| lv_i_vrgng | TYPE FMUP01-VRGNG, " | |||
| lv_e_f_fmup00t | TYPE FMUP00T, " | |||
| lv_wrttp_parameter_missing | TYPE FMUP00T, " | |||
| lv_i_spras | TYPE FMUP00T-SPRAS, " | |||
| lv_i_flg_orig_valtype_profil | TYPE FMDY-XFELD. " SPACE |
|   CALL FUNCTION 'FM_CONTROL_DATA_GET' " |
| EXPORTING | ||
| I_PROFIL | = lv_i_profil | |
| I_WRTTP | = lv_i_wrttp | |
| I_VRGNG | = lv_i_vrgng | |
| I_SPRAS | = lv_i_spras | |
| I_FLG_ORIG_VALTYPE_PROFIL | = lv_i_flg_orig_valtype_profil | |
| IMPORTING | ||
| E_F_FMUP01 | = lv_e_f_fmup01 | |
| E_F_FMUP00 | = lv_e_f_fmup00 | |
| E_F_FMUP00T | = lv_e_f_fmup00t | |
| TABLES | ||
| T_FMUP01 | = lt_t_fmup01 | |
| EXCEPTIONS | ||
| NO_ENTRY_FOUND = 1 | ||
| NO_ENTRY_FOUND_WRTTP = 2 | ||
| WRTTP_PARAMETER_MISSING = 3 | ||
| . " FM_CONTROL_DATA_GET | ||
ABAP code using 7.40 inline data declarations to call FM FM_CONTROL_DATA_GET
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single PROFIL FROM FMUP00 INTO @DATA(ld_i_profil). | ||||
| "SELECT single WRTTP FROM FMUP01 INTO @DATA(ld_i_wrttp). | ||||
| "SELECT single VRGNG FROM FMUP01 INTO @DATA(ld_i_vrgng). | ||||
| "SELECT single SPRAS FROM FMUP00T INTO @DATA(ld_i_spras). | ||||
| "SELECT single XFELD FROM FMDY INTO @DATA(ld_i_flg_orig_valtype_profil). | ||||
| DATA(ld_i_flg_orig_valtype_profil) | = ' '. | |||
Search for further information about these or an SAP related objects