SAP TMS_UIQ_IMPORT_QUEUE_DISPLAY Function Module for Display import queue









TMS_UIQ_IMPORT_QUEUE_DISPLAY is a standard tms uiq import queue display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display import queue 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 tms uiq import queue display FM, simply by entering the name TMS_UIQ_IMPORT_QUEUE_DISPLAY into the relevant SAP transaction such as SE37 or SE38.

Function Group: TMSU_IQ
Program Name: SAPLTMSU_IQ
Main Program: SAPLTMSU_IQ
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function TMS_UIQ_IMPORT_QUEUE_DISPLAY 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 'TMS_UIQ_IMPORT_QUEUE_DISPLAY'"Display import queue
EXPORTING
IV_SYSTEM = "
* IV_DOMAIN = "
* IV_CLIENT = "Filter: Source clt
* IV_PROJECT = "
* IV_CLEAR_MEMORY = "
* IV_MAX_EXP = "
* IV_COLLAPSE = "
* IV_MONITOR = 'X' "Progress indicator
* IV_VERBOSE = "Output error messages

IMPORTING
EV_OK_CODE = "OK Code

EXCEPTIONS
IMPORT_QUEUE_DISPLAY_FAILED = 1
.



IMPORTING Parameters details for TMS_UIQ_IMPORT_QUEUE_DISPLAY

IV_SYSTEM -

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

IV_DOMAIN -

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

IV_CLIENT - Filter: Source clt

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

IV_PROJECT -

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

IV_CLEAR_MEMORY -

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

IV_MAX_EXP -

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

IV_COLLAPSE -

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

IV_MONITOR - Progress indicator

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

IV_VERBOSE - Output error messages

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

EXPORTING Parameters details for TMS_UIQ_IMPORT_QUEUE_DISPLAY

EV_OK_CODE - OK Code

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

EXCEPTIONS details

IMPORT_QUEUE_DISPLAY_FAILED -

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

Copy and paste ABAP code example for TMS_UIQ_IMPORT_QUEUE_DISPLAY 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_iv_system  TYPE TMSCSYS-SYSNAM, "   
lv_ev_ok_code  TYPE CHAR10, "   
lv_import_queue_display_failed  TYPE CHAR10, "   
lv_iv_domain  TYPE TMSCSYS-DOMNAM, "   
lv_iv_client  TYPE TMSBUFFER-TARCLI, "   
lv_iv_project  TYPE TMSBUFFER-PROJECT, "   
lv_iv_clear_memory  TYPE CHAR01, "   
lv_iv_max_exp  TYPE NUMC_3, "   
lv_iv_collapse  TYPE CHAR01, "   
lv_iv_monitor  TYPE CHAR01, "   'X'
lv_iv_verbose  TYPE CHAR01. "   

  CALL FUNCTION 'TMS_UIQ_IMPORT_QUEUE_DISPLAY'  "Display import queue
    EXPORTING
         IV_SYSTEM = lv_iv_system
         IV_DOMAIN = lv_iv_domain
         IV_CLIENT = lv_iv_client
         IV_PROJECT = lv_iv_project
         IV_CLEAR_MEMORY = lv_iv_clear_memory
         IV_MAX_EXP = lv_iv_max_exp
         IV_COLLAPSE = lv_iv_collapse
         IV_MONITOR = lv_iv_monitor
         IV_VERBOSE = lv_iv_verbose
    IMPORTING
         EV_OK_CODE = lv_ev_ok_code
    EXCEPTIONS
        IMPORT_QUEUE_DISPLAY_FAILED = 1
. " TMS_UIQ_IMPORT_QUEUE_DISPLAY




ABAP code using 7.40 inline data declarations to call FM TMS_UIQ_IMPORT_QUEUE_DISPLAY

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 SYSNAM FROM TMSCSYS INTO @DATA(ld_iv_system).
 
 
 
"SELECT single DOMNAM FROM TMSCSYS INTO @DATA(ld_iv_domain).
 
"SELECT single TARCLI FROM TMSBUFFER INTO @DATA(ld_iv_client).
 
"SELECT single PROJECT FROM TMSBUFFER INTO @DATA(ld_iv_project).
 
 
 
 
DATA(ld_iv_monitor) = 'X'.
 
 


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!