SAP MM_ARRANG_ALV_DIALOG_USER_COM Function Module for NOTRANSL: User Command im Dialog Modus
MM_ARRANG_ALV_DIALOG_USER_COM is a standard mm arrang alv dialog user com 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: User Command im Dialog Modus 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 mm arrang alv dialog user com FM, simply by entering the name MM_ARRANG_ALV_DIALOG_USER_COM into the relevant SAP transaction such as SE37 or SE38.
Function Group: WNB1
Program Name: SAPLWNB1
Main Program: SAPLWNB1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MM_ARRANG_ALV_DIALOG_USER_COM 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 'MM_ARRANG_ALV_DIALOG_USER_COM'"NOTRANSL: User Command im Dialog Modus.
EXPORTING
I_ONLY_USER_COMMAND = "Single-Character Flag
I_SALV_FUNCTION = "ALV Function
I_REPORT_TYPE = "Report ID: 2-char. ID for reports in 'subsequent settlement'
IMPORTING
ET_ALV_HEAD = "Display Table of Header Data in ALV Grid
ET_EXCLUDING = "Excluded Function Codes
E_TITLEBAR = "Structure for Dynamic Call-up of Title Bar
ET_ALV_ITEM = "Display Table of Item Data in ALV Grid
ET_ERROR = "Table via ARRANGERRA (Messages for Arrangements)
ES_CONDENSE_KEY = "Summarization Key per Arrangement
EV_LEAVE = "Single-Character Flag
EV_STAY = "Single-Character Flag
EV_DELEGATE = "Single-Character Flag
EV_ERROR = "Single-Character Flag
ES_SCREEN_STATUS = "Status To Be Set
IMPORTING Parameters details for MM_ARRANG_ALV_DIALOG_USER_COM
I_ONLY_USER_COMMAND - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
I_SALV_FUNCTION - ALV Function
Data type: SALV_DE_FUNCTIONOptional: No
Call by Reference: Yes
I_REPORT_TYPE - Report ID: 2-char. ID for reports in 'subsequent settlement'
Data type: REPOTOptional: No
Call by Reference: Yes
EXPORTING Parameters details for MM_ARRANG_ALV_DIALOG_USER_COM
ET_ALV_HEAD - Display Table of Header Data in ALV Grid
Data type: ARRANG_ALV_GRID_DISP_HEAD_TTYOptional: No
Call by Reference: Yes
ET_EXCLUDING - Excluded Function Codes
Data type: ARRANG_FCODE_EXCLUDE_TTYOptional: No
Call by Reference: Yes
E_TITLEBAR - Structure for Dynamic Call-up of Title Bar
Data type: ARRANG_SCREEN_TITLE_STYOptional: No
Call by Reference: Yes
ET_ALV_ITEM - Display Table of Item Data in ALV Grid
Data type: ARRANG_ALV_GRID_DISP_ITEM_TTYOptional: No
Call by Reference: Yes
ET_ERROR - Table via ARRANGERRA (Messages for Arrangements)
Data type: TYPE_ARRANGERRAOptional: No
Call by Reference: Yes
ES_CONDENSE_KEY - Summarization Key per Arrangement
Data type: ARRANG_CONDENSE_STYOptional: No
Call by Reference: Yes
EV_LEAVE - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
EV_STAY - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
EV_DELEGATE - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
EV_ERROR - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
ES_SCREEN_STATUS - Status To Be Set
Data type: ARRANG_SCREEN_STATUS_STYOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MM_ARRANG_ALV_DIALOG_USER_COM 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_et_alv_head | TYPE ARRANG_ALV_GRID_DISP_HEAD_TTY, " | |||
| lv_i_only_user_command | TYPE CHAR1, " | |||
| lv_et_excluding | TYPE ARRANG_FCODE_EXCLUDE_TTY, " | |||
| lv_e_titlebar | TYPE ARRANG_SCREEN_TITLE_STY, " | |||
| lv_et_alv_item | TYPE ARRANG_ALV_GRID_DISP_ITEM_TTY, " | |||
| lv_i_salv_function | TYPE SALV_DE_FUNCTION, " | |||
| lv_et_error | TYPE TYPE_ARRANGERRA, " | |||
| lv_i_report_type | TYPE REPOT, " | |||
| lv_es_condense_key | TYPE ARRANG_CONDENSE_STY, " | |||
| lv_ev_leave | TYPE CHAR1, " | |||
| lv_ev_stay | TYPE CHAR1, " | |||
| lv_ev_delegate | TYPE CHAR1, " | |||
| lv_ev_error | TYPE CHAR1, " | |||
| lv_es_screen_status | TYPE ARRANG_SCREEN_STATUS_STY. " |
|   CALL FUNCTION 'MM_ARRANG_ALV_DIALOG_USER_COM' "NOTRANSL: User Command im Dialog Modus |
| EXPORTING | ||
| I_ONLY_USER_COMMAND | = lv_i_only_user_command | |
| I_SALV_FUNCTION | = lv_i_salv_function | |
| I_REPORT_TYPE | = lv_i_report_type | |
| IMPORTING | ||
| ET_ALV_HEAD | = lv_et_alv_head | |
| ET_EXCLUDING | = lv_et_excluding | |
| E_TITLEBAR | = lv_e_titlebar | |
| ET_ALV_ITEM | = lv_et_alv_item | |
| ET_ERROR | = lv_et_error | |
| ES_CONDENSE_KEY | = lv_es_condense_key | |
| EV_LEAVE | = lv_ev_leave | |
| EV_STAY | = lv_ev_stay | |
| EV_DELEGATE | = lv_ev_delegate | |
| EV_ERROR | = lv_ev_error | |
| ES_SCREEN_STATUS | = lv_es_screen_status | |
| . " MM_ARRANG_ALV_DIALOG_USER_COM | ||
ABAP code using 7.40 inline data declarations to call FM MM_ARRANG_ALV_DIALOG_USER_COM
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.Search for further information about these or an SAP related objects