SAP SALM_GET_TID_BY_NAME Function Module for Determines Corresponding TID for Long MT Names
SALM_GET_TID_BY_NAME is a standard salm get tid by name SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines Corresponding TID for Long MT Names 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 salm get tid by name FM, simply by entering the name SALM_GET_TID_BY_NAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALM
Program Name: SAPLSALM
Main Program: SAPLSALM
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SALM_GET_TID_BY_NAME 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 'SALM_GET_TID_BY_NAME'"Determines Corresponding TID for Long MT Names.
TABLES
IN_LNAMES = "
OUT_TIDS_LNAMES = "
EXCEPTIONS
IN_LNAMES_MISSING = 1
TABLES Parameters details for SALM_GET_TID_BY_NAME
IN_LNAMES -
Data type: CCMSM_MT_LNAME_TBLOptional: No
Call by Reference: No ( called with pass by value option)
OUT_TIDS_LNAMES -
Data type: CCMSM_TID_LNAME_INFO_TBLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
IN_LNAMES_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SALM_GET_TID_BY_NAME 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: | ||||
| lt_in_lnames | TYPE STANDARD TABLE OF CCMSM_MT_LNAME_TBL, " | |||
| lv_in_lnames_missing | TYPE CCMSM_MT_LNAME_TBL, " | |||
| lt_out_tids_lnames | TYPE STANDARD TABLE OF CCMSM_TID_LNAME_INFO_TBL. " |
|   CALL FUNCTION 'SALM_GET_TID_BY_NAME' "Determines Corresponding TID for Long MT Names |
| TABLES | ||
| IN_LNAMES | = lt_in_lnames | |
| OUT_TIDS_LNAMES | = lt_out_tids_lnames | |
| EXCEPTIONS | ||
| IN_LNAMES_MISSING = 1 | ||
| . " SALM_GET_TID_BY_NAME | ||
ABAP code using 7.40 inline data declarations to call FM SALM_GET_TID_BY_NAME
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