SAP TMS_UI_DOCU_INTERFACE Function Module for









TMS_UI_DOCU_INTERFACE is a standard tms ui docu interface 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 tms ui docu interface FM, simply by entering the name TMS_UI_DOCU_INTERFACE into the relevant SAP transaction such as SE37 or SE38.

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



Function TMS_UI_DOCU_INTERFACE 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_UI_DOCU_INTERFACE'"
EXPORTING
IV_OBJECT = "
* IV_PROGRAM = 'SAPLTMSU' "
.



IMPORTING Parameters details for TMS_UI_DOCU_INTERFACE

IV_OBJECT -

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

IV_PROGRAM -

Data type: IWREFERENC-PROGRAMM
Default: 'SAPLTMSU'
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for TMS_UI_DOCU_INTERFACE 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_object  TYPE STMS_DOCU_OBJ, "   
lv_iv_program  TYPE IWREFERENC-PROGRAMM. "   'SAPLTMSU'

  CALL FUNCTION 'TMS_UI_DOCU_INTERFACE'  "
    EXPORTING
         IV_OBJECT = lv_iv_object
         IV_PROGRAM = lv_iv_program
. " TMS_UI_DOCU_INTERFACE




ABAP code using 7.40 inline data declarations to call FM TMS_UI_DOCU_INTERFACE

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 PROGRAMM FROM IWREFERENC INTO @DATA(ld_iv_program).
DATA(ld_iv_program) = 'SAPLTMSU'.
 


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!