SAP Function Modules
EFG_FORM_GET_STATUS SAP Function module
EFG_FORM_GET_STATUS is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name EFG_FORM_GET_STATUS into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
EFGF
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM EFG_FORM_GET_STATUS - EFG FORM GET STATUS
CALL FUNCTION 'EFG_FORM_GET_STATUS' "
* EXPORTING
* x_client = SY-MANDT " efg_dte_srcclient Source Client for Accessing Other Clients
* x_formkey = " formkey Application Form
* x_form = " efg00_form
* x_contr = " efg00_obj_contr Control object
* x_actual = " rfgen-actual
* x_flg_no_warnings = " c
* x_flg_formclass = " c
* x_flg_runtime = " c
* x_flg_bem_or_aim = " efg_dte_flag
* ref_log = CL_EFG_LOG=>NULL " if_efg_log
IMPORTING
y_strn_status = " efg_strn_status_form Status
y_flg_warnings = " c
y_formlog = " efg_formlog Logs for Generating Application Forms
y_efrm = " efrm Print Workbench: Application Forms
y_flg_messages = " c Notifications exist
y_flg_func_active = " c
y_genfunc = " efg_dte_genfunc Generated Module
y_errors = " efg00_error_object Error
y_flg_switchoff = " efg_dte_flag
EXCEPTIONS
NOT_QUALIFIED = 1 "
NOT_FOUND = 2 "
FAILED = 3 "
. " EFG_FORM_GET_STATUS
ABAP code example for Function Module EFG_FORM_GET_STATUS
The ABAP code below is a full code listing to execute function module EFG_FORM_GET_STATUS including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_y_strn_status | TYPE EFG_STRN_STATUS_FORM , |
| ld_y_flg_warnings | TYPE C , |
| ld_y_formlog | TYPE EFG_FORMLOG , |
| ld_y_efrm | TYPE EFRM , |
| ld_y_flg_messages | TYPE C , |
| ld_y_flg_func_active | TYPE C , |
| ld_y_genfunc | TYPE EFG_DTE_GENFUNC , |
| ld_y_errors | TYPE EFG00_ERROR_OBJECT , |
| ld_y_flg_switchoff | TYPE EFG_DTE_FLAG . |
DATA(ld_x_client) = 'Check type of data required'.
DATA(ld_x_formkey) = 'Check type of data required'.
DATA(ld_x_form) = 'Check type of data required'.
DATA(ld_x_contr) = 'Check type of data required'.
DATA(ld_x_actual) = some text here
DATA(ld_x_flg_no_warnings) = 'Check type of data required'.
DATA(ld_x_flg_formclass) = 'Check type of data required'.
DATA(ld_x_flg_runtime) = 'Check type of data required'.
DATA(ld_x_flg_bem_or_aim) = 'Check type of data required'.
DATA(ld_ref_log) = 'Check type of data required'. . CALL FUNCTION 'EFG_FORM_GET_STATUS' * EXPORTING * x_client = ld_x_client * x_formkey = ld_x_formkey * x_form = ld_x_form * x_contr = ld_x_contr * x_actual = ld_x_actual * x_flg_no_warnings = ld_x_flg_no_warnings * x_flg_formclass = ld_x_flg_formclass * x_flg_runtime = ld_x_flg_runtime * x_flg_bem_or_aim = ld_x_flg_bem_or_aim * ref_log = ld_ref_log IMPORTING y_strn_status = ld_y_strn_status y_flg_warnings = ld_y_flg_warnings y_formlog = ld_y_formlog y_efrm = ld_y_efrm y_flg_messages = ld_y_flg_messages y_flg_func_active = ld_y_flg_func_active y_genfunc = ld_y_genfunc y_errors = ld_y_errors y_flg_switchoff = ld_y_flg_switchoff EXCEPTIONS NOT_QUALIFIED = 1 NOT_FOUND = 2 FAILED = 3 . " EFG_FORM_GET_STATUS
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_y_strn_status | TYPE EFG_STRN_STATUS_FORM , |
| ld_x_client | TYPE EFG_DTE_SRCCLIENT , |
| ld_x_formkey | TYPE FORMKEY , |
| ld_y_flg_warnings | TYPE C , |
| ld_x_form | TYPE EFG00_FORM , |
| ld_y_formlog | TYPE EFG_FORMLOG , |
| ld_y_efrm | TYPE EFRM , |
| ld_x_contr | TYPE EFG00_OBJ_CONTR , |
| ld_y_flg_messages | TYPE C , |
| ld_x_actual | TYPE RFGEN-ACTUAL , |
| ld_y_flg_func_active | TYPE C , |
| ld_x_flg_no_warnings | TYPE C , |
| ld_y_genfunc | TYPE EFG_DTE_GENFUNC , |
| ld_x_flg_formclass | TYPE C , |
| ld_y_errors | TYPE EFG00_ERROR_OBJECT , |
| ld_x_flg_runtime | TYPE C , |
| ld_y_flg_switchoff | TYPE EFG_DTE_FLAG , |
| ld_x_flg_bem_or_aim | TYPE EFG_DTE_FLAG , |
| ld_ref_log | TYPE IF_EFG_LOG . |
ld_x_client = 'Check type of data required'.
ld_x_formkey = 'Check type of data required'.
ld_x_form = 'Check type of data required'.
ld_x_contr = 'Check type of data required'.
ld_x_actual = some text here
ld_x_flg_no_warnings = 'Check type of data required'.
ld_x_flg_formclass = 'Check type of data required'.
ld_x_flg_runtime = 'Check type of data required'.
ld_x_flg_bem_or_aim = 'Check type of data required'.
ld_ref_log = 'Check type of data required'.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name EFG_FORM_GET_STATUS or its description.