SAP TMS_UNI_DECODE_TABLE Function Module for
TMS_UNI_DECODE_TABLE is a standard tms uni decode table 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 uni decode table FM, simply by entering the name TMS_UNI_DECODE_TABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: TMSR
Program Name: SAPLTMSR
Main Program: SAPLTMSR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TMS_UNI_DECODE_TABLE 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_UNI_DECODE_TABLE'".
EXPORTING
IV_TABNAM = "
* IV_OPTIONAL = 'X' "
TABLES
TT_TABLE = "
EXCEPTIONS
ALERT = 1
IMPORTING Parameters details for TMS_UNI_DECODE_TABLE
IV_TABNAM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IV_OPTIONAL -
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for TMS_UNI_DECODE_TABLE
TT_TABLE -
Data type:Optional: No
Call by Reference: Yes
EXCEPTIONS details
ALERT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TMS_UNI_DECODE_TABLE 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_alert | TYPE STRING, " | |||
| lt_tt_table | TYPE STANDARD TABLE OF STRING, " | |||
| lv_iv_tabnam | TYPE STRING, " | |||
| lv_iv_optional | TYPE FLAG. " 'X' |
|   CALL FUNCTION 'TMS_UNI_DECODE_TABLE' " |
| EXPORTING | ||
| IV_TABNAM | = lv_iv_tabnam | |
| IV_OPTIONAL | = lv_iv_optional | |
| TABLES | ||
| TT_TABLE | = lt_tt_table | |
| EXCEPTIONS | ||
| ALERT = 1 | ||
| . " TMS_UNI_DECODE_TABLE | ||
ABAP code using 7.40 inline data declarations to call FM TMS_UNI_DECODE_TABLE
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.| DATA(ld_iv_optional) | = 'X'. | |||
Search for further information about these or an SAP related objects