SAP GRFN_API_MENU_RETRIEVE Function Module for Get single Menu
GRFN_API_MENU_RETRIEVE is a standard grfn api menu retrieve SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get single Menu processing and below is the pattern details for this FM, 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 grfn api menu retrieve FM, simply by entering the name GRFN_API_MENU_RETRIEVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRFN_API_MENU
Program Name: SAPLGRFN_API_MENU
Main Program: SAPLGRFN_API_MENU
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GRFN_API_MENU_RETRIEVE 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 'GRFN_API_MENU_RETRIEVE'"Get single Menu.
EXPORTING
IO_SESSION = "Session
I_GROUP_ID = "Menu Group ID
* I_APP_COMP = 'FN' "Application Component
* I_REGULATION = "Regulation ID
IMPORTING
E_RETURN_CODE = "Natural number
ES_GROUP = "Menu Group
TABLES
* ET_MESSAGE = "Table with BAPI Return Information
* ET_SUBGROUP = "Menu Subgroup
* ET_ITEM = "Menu Item
IMPORTING Parameters details for GRFN_API_MENU_RETRIEVE
IO_SESSION - Session
Data type: CL_GRFN_API_SESSIONOptional: No
Call by Reference: No ( called with pass by value option)
I_GROUP_ID - Menu Group ID
Data type: GRFN_GROUP_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_APP_COMP - Application Component
Data type: GRFN_APP_COMPONENTDefault: 'FN'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_REGULATION - Regulation ID
Data type: GRFN_REGULATIONOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRFN_API_MENU_RETRIEVE
E_RETURN_CODE - Natural number
Data type: INT4Optional: No
Call by Reference: No ( called with pass by value option)
ES_GROUP - Menu Group
Data type: GRFN_S_API_MENU_GROUPOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GRFN_API_MENU_RETRIEVE
ET_MESSAGE - Table with BAPI Return Information
Data type: BAPIRETTABOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_SUBGROUP - Menu Subgroup
Data type: GRFN_T_API_MENU_SUBGROUPOptional: Yes
Call by Reference: Yes
ET_ITEM - Menu Item
Data type: GRFN_T_API_MENU_ITEMOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for GRFN_API_MENU_RETRIEVE 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: | ||||
| lt_et_message | TYPE STANDARD TABLE OF BAPIRETTAB, " | |||
| lv_io_session | TYPE CL_GRFN_API_SESSION, " | |||
| lv_e_return_code | TYPE INT4, " | |||
| lv_es_group | TYPE GRFN_S_API_MENU_GROUP, " | |||
| lv_i_group_id | TYPE GRFN_GROUP_ID, " | |||
| lt_et_subgroup | TYPE STANDARD TABLE OF GRFN_T_API_MENU_SUBGROUP, " | |||
| lt_et_item | TYPE STANDARD TABLE OF GRFN_T_API_MENU_ITEM, " | |||
| lv_i_app_comp | TYPE GRFN_APP_COMPONENT, " 'FN' | |||
| lv_i_regulation | TYPE GRFN_REGULATION. " |
|   CALL FUNCTION 'GRFN_API_MENU_RETRIEVE' "Get single Menu |
| EXPORTING | ||
| IO_SESSION | = lv_io_session | |
| I_GROUP_ID | = lv_i_group_id | |
| I_APP_COMP | = lv_i_app_comp | |
| I_REGULATION | = lv_i_regulation | |
| IMPORTING | ||
| E_RETURN_CODE | = lv_e_return_code | |
| ES_GROUP | = lv_es_group | |
| TABLES | ||
| ET_MESSAGE | = lt_et_message | |
| ET_SUBGROUP | = lt_et_subgroup | |
| ET_ITEM | = lt_et_item | |
| . " GRFN_API_MENU_RETRIEVE | ||
ABAP code using 7.40 inline data declarations to call FM GRFN_API_MENU_RETRIEVE
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.| DATA(ld_i_app_comp) | = 'FN'. | |||
Search for further information about these or an SAP related objects