SAP GLE_MCA_SAP_TOOLBAR_FUNCTION Function Module for Add function to toolbar
GLE_MCA_SAP_TOOLBAR_FUNCTION is a standard gle mca sap toolbar function SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Add function to toolbar 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 gle mca sap toolbar function FM, simply by entering the name GLE_MCA_SAP_TOOLBAR_FUNCTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: GLE_MCA_SRV
Program Name: SAPLGLE_MCA_SRV
Main Program: SAPLGLE_MCA_SRV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GLE_MCA_SAP_TOOLBAR_FUNCTION 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 'GLE_MCA_SAP_TOOLBAR_FUNCTION'"Add function to toolbar.
EXPORTING
* I_USER_COMMAND = 'REVIEW' "Function Code
CHANGING
C_TAB_BUTTON = "Toolbar Buttons
IMPORTING Parameters details for GLE_MCA_SAP_TOOLBAR_FUNCTION
I_USER_COMMAND - Function Code
Data type: SYUCOMMDefault: 'REVIEW'
Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for GLE_MCA_SAP_TOOLBAR_FUNCTION
C_TAB_BUTTON - Toolbar Buttons
Data type: TTB_BUTTONOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for GLE_MCA_SAP_TOOLBAR_FUNCTION 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_c_tab_button | TYPE TTB_BUTTON, " | |||
| lv_i_user_command | TYPE SYUCOMM. " 'REVIEW' |
|   CALL FUNCTION 'GLE_MCA_SAP_TOOLBAR_FUNCTION' "Add function to toolbar |
| EXPORTING | ||
| I_USER_COMMAND | = lv_i_user_command | |
| CHANGING | ||
| C_TAB_BUTTON | = lv_c_tab_button | |
| . " GLE_MCA_SAP_TOOLBAR_FUNCTION | ||
ABAP code using 7.40 inline data declarations to call FM GLE_MCA_SAP_TOOLBAR_FUNCTION
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_user_command) | = 'REVIEW'. | |||
Search for further information about these or an SAP related objects