SAP EFG_FORM_ACTIVATE Function Module for
EFG_FORM_ACTIVATE is a standard efg form activate 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 efg form activate FM, simply by entering the name EFG_FORM_ACTIVATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EFGF
Program Name: SAPLEFGF
Main Program: SAPLEFGF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EFG_FORM_ACTIVATE 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 'EFG_FORM_ACTIVATE'".
EXPORTING
X_FORMKEY = "Application Form
X_CLIENT = "R/3 System, Client Number from Logon
* X_ONLY_IF_NECESSARY = "
* X_ACTUAL = "
* X_FLG_SUPPRESS_INDICATOR = "
* X_FLG_BEM_OR_AIM = "
* REF_LOG = CL_EFG_LOG=>NULL "
IMPORTING
Y_MSG = "System Message
Y_GENFUNC = "Generated Module
Y_FLG_FUNC_ACTIVE = "
Y_STRN_STATUS = "Status of an Application Form
Y_FLG_SWITCHOFF = "
EXCEPTIONS
NOT_QUALIFIED = 1 NOT_FOUND = 2 FAILED = 3
IMPORTING Parameters details for EFG_FORM_ACTIVATE
X_FORMKEY - Application Form
Data type: FORMKEYOptional: No
Call by Reference: No ( called with pass by value option)
X_CLIENT - R/3 System, Client Number from Logon
Data type: SY-MANDTOptional: No
Call by Reference: No ( called with pass by value option)
X_ONLY_IF_NECESSARY -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
X_ACTUAL -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
X_FLG_SUPPRESS_INDICATOR -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
X_FLG_BEM_OR_AIM -
Data type: EFG_DTE_FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
REF_LOG -
Data type: IF_EFG_LOGDefault: CL_EFG_LOG=>NULL
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EFG_FORM_ACTIVATE
Y_MSG - System Message
Data type: EFG_STR_MSGOptional: No
Call by Reference: Yes
Y_GENFUNC - Generated Module
Data type: EFG_DTE_GENFUNCOptional: No
Call by Reference: No ( called with pass by value option)
Y_FLG_FUNC_ACTIVE -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
Y_STRN_STATUS - Status of an Application Form
Data type: EFG_STRN_STATUS_FORMOptional: No
Call by Reference: Yes
Y_FLG_SWITCHOFF -
Data type: EFG_DTE_FLAGOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_QUALIFIED -
Data type:Optional: No
Call by Reference: Yes
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EFG_FORM_ACTIVATE 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_y_msg | TYPE EFG_STR_MSG, " | |||
| lv_x_formkey | TYPE FORMKEY, " | |||
| lv_not_qualified | TYPE FORMKEY, " | |||
| lv_x_client | TYPE SY-MANDT, " | |||
| lv_not_found | TYPE SY, " | |||
| lv_y_genfunc | TYPE EFG_DTE_GENFUNC, " | |||
| lv_failed | TYPE EFG_DTE_GENFUNC, " | |||
| lv_y_flg_func_active | TYPE C, " | |||
| lv_x_only_if_necessary | TYPE C, " | |||
| lv_x_actual | TYPE C, " | |||
| lv_y_strn_status | TYPE EFG_STRN_STATUS_FORM, " | |||
| lv_y_flg_switchoff | TYPE EFG_DTE_FLAG, " | |||
| lv_x_flg_suppress_indicator | TYPE C, " | |||
| lv_x_flg_bem_or_aim | TYPE EFG_DTE_FLAG, " | |||
| lv_ref_log | TYPE IF_EFG_LOG. " CL_EFG_LOG=>NULL |
|   CALL FUNCTION 'EFG_FORM_ACTIVATE' " |
| EXPORTING | ||
| X_FORMKEY | = lv_x_formkey | |
| X_CLIENT | = lv_x_client | |
| X_ONLY_IF_NECESSARY | = lv_x_only_if_necessary | |
| X_ACTUAL | = lv_x_actual | |
| X_FLG_SUPPRESS_INDICATOR | = lv_x_flg_suppress_indicator | |
| X_FLG_BEM_OR_AIM | = lv_x_flg_bem_or_aim | |
| REF_LOG | = lv_ref_log | |
| IMPORTING | ||
| Y_MSG | = lv_y_msg | |
| Y_GENFUNC | = lv_y_genfunc | |
| Y_FLG_FUNC_ACTIVE | = lv_y_flg_func_active | |
| Y_STRN_STATUS | = lv_y_strn_status | |
| Y_FLG_SWITCHOFF | = lv_y_flg_switchoff | |
| EXCEPTIONS | ||
| NOT_QUALIFIED = 1 | ||
| NOT_FOUND = 2 | ||
| FAILED = 3 | ||
| . " EFG_FORM_ACTIVATE | ||
ABAP code using 7.40 inline data declarations to call FM EFG_FORM_ACTIVATE
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 MANDT FROM SY INTO @DATA(ld_x_client). | ||||
| DATA(ld_ref_log) | = CL_EFG_LOG=>NULL. | |||
Search for further information about these or an SAP related objects