SAP MG_LIST_WIDTH Function Module for









MG_LIST_WIDTH is a standard mg list width 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 mg list width FM, simply by entering the name MG_LIST_WIDTH into the relevant SAP transaction such as SE37 or SE38.

Function Group: MSLT
Program Name: SAPLMSLT
Main Program: SAPLMSLT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MG_LIST_WIDTH 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 'MG_LIST_WIDTH'"
EXPORTING
* S_NAME = "
* CHECKBOX = "
* BOX_COLUMN = "

IMPORTING
WIDTH = "

TABLES
* T_SNAME = "
* TABLE = "
* FIELDS = "
* FIELDNAMES = "
.



IMPORTING Parameters details for MG_LIST_WIDTH

S_NAME -

Data type: RSRD1-OBJNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHECKBOX -

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

BOX_COLUMN -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MG_LIST_WIDTH

WIDTH -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MG_LIST_WIDTH

T_SNAME -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLE -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

FIELDS -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

FIELDNAMES -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MG_LIST_WIDTH 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_width  TYPE STRING, "   
lv_s_name  TYPE RSRD1-OBJNAME, "   
lt_t_sname  TYPE STANDARD TABLE OF RSRD1, "   
lt_table  TYPE STANDARD TABLE OF RSRD1, "   
lv_checkbox  TYPE C, "   
lt_fields  TYPE STANDARD TABLE OF C, "   
lv_box_column  TYPE C, "   
lt_fieldnames  TYPE STANDARD TABLE OF C. "   

  CALL FUNCTION 'MG_LIST_WIDTH'  "
    EXPORTING
         S_NAME = lv_s_name
         CHECKBOX = lv_checkbox
         BOX_COLUMN = lv_box_column
    IMPORTING
         WIDTH = lv_width
    TABLES
         T_SNAME = lt_t_sname
         TABLE = lt_table
         FIELDS = lt_fields
         FIELDNAMES = lt_fieldnames
. " MG_LIST_WIDTH




ABAP code using 7.40 inline data declarations to call FM MG_LIST_WIDTH

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 OBJNAME FROM RSRD1 INTO @DATA(ld_s_name).
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!