SAP MTQ_TO_SCREEN Function Module for NOTRANSL: transport MTQ data to Screen

Search SAP Function Modules

MTQ_TO_SCREEN is a standard mtq to screen 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: transport MTQ data to Screen 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 mtq to screen FM, simply by entering the name MTQ_TO_SCREEN into the relevant SAP transaction such as SE37 or SE38.

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

Function MTQ_TO_SCREEN 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 'MTQ_TO_SCREEN'"NOTRANSL: transport MTQ data to Screen
  EXPORTING
   IT_EXTDATA =  "Table Type for External Data in MIGO

.

IMPORTING Parameters details for MTQ_TO_SCREEN

IT_EXTDATA - Table Type for External Data in MIGO

Data type: LIME_T_EXTDATA
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MTQ_TO_SCREEN 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.

ABAP code using 7.40 inline data declarations to call FM MTQ_TO_SCREEN

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