SAP OM_GUI_HAS_USER_COMMAND Function Module for NOTRANSL: OM: has user command
OM_GUI_HAS_USER_COMMAND is a standard om gui has user command SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: OM: has user command 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 om gui has user command FM, simply by entering the name OM_GUI_HAS_USER_COMMAND into the relevant SAP transaction such as SE37 or SE38.
Function Group: OMOD_GUI
Program Name: SAPLOMOD_GUI
Main Program: SAPLOMOD_GUI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OM_GUI_HAS_USER_COMMAND 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 'OM_GUI_HAS_USER_COMMAND'"NOTRANSL: OM: has user command.
IMPORTING
USER_COMMAND = "ABAP System Field: PAI-Triggering Function Code
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLOMOD_GUI_CUST_001
EXPORTING Parameters details for OM_GUI_HAS_USER_COMMAND
USER_COMMAND - ABAP System Field: PAI-Triggering Function Code
Data type: SY-UCOMMOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for OM_GUI_HAS_USER_COMMAND 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_user_command | TYPE SY-UCOMM. " |
|   CALL FUNCTION 'OM_GUI_HAS_USER_COMMAND' "NOTRANSL: OM: has user command |
| IMPORTING | ||
| USER_COMMAND | = lv_user_command | |
| . " OM_GUI_HAS_USER_COMMAND | ||
ABAP code using 7.40 inline data declarations to call FM OM_GUI_HAS_USER_COMMAND
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 UCOMM FROM SY INTO @DATA(ld_user_command). | ||||
Search for further information about these or an SAP related objects