SAP SALR_UTIL_TID_GET_DETAILS Function Module for
SALR_UTIL_TID_GET_DETAILS is a standard salr util tid get details 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 salr util tid get details FM, simply by entering the name SALR_UTIL_TID_GET_DETAILS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALR
Program Name: SAPLSALR
Main Program: SAPLSALR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SALR_UTIL_TID_GET_DETAILS 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 'SALR_UTIL_TID_GET_DETAILS'".
EXPORTING
TID = "
IMPORTING
SYSID = "System ID
APPLSERVER = "Server Name
CTXCLIENT = "R/3 System, Client Number from Logon
CSMSYSID = "Name of SAP R/3 System
DESTINATION_FOR_DIALOG = "Logical Destination (Specified in Function Call)
TID_IS_LOCAL = "
MCNAME = "
MCOWNER = "
NUMRANGE = "
UNIQUENUM = "
TYPECLASS = "
SEGMENT = "Monitoring Segment Name
SEGMENTTYPE = "
DESTINATION = "
EXCEPTIONS
INVALID_TID = 1 OTHER_PROBLEM = 2 TID_NOT_IN_LOCAL_SYSTEM = 3
IMPORTING Parameters details for SALR_UTIL_TID_GET_DETAILS
TID -
Data type: ALGLOBTIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SALR_UTIL_TID_GET_DETAILS
SYSID - System ID
Data type: ALGLOBTID-MTSYSIDOptional: No
Call by Reference: No ( called with pass by value option)
APPLSERVER - Server Name
Data type: MSXXLIST-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
CTXCLIENT - R/3 System, Client Number from Logon
Data type: SY-MANDTOptional: No
Call by Reference: No ( called with pass by value option)
CSMSYSID - Name of SAP R/3 System
Data type: SY-SYSIDOptional: No
Call by Reference: No ( called with pass by value option)
DESTINATION_FOR_DIALOG - Logical Destination (Specified in Function Call)
Data type: ALCONSEG-DESTINATOptional: No
Call by Reference: No ( called with pass by value option)
TID_IS_LOCAL -
Data type: ALFLAGOptional: No
Call by Reference: No ( called with pass by value option)
MCNAME -
Data type: ALGLOBTID-MTMCNAMEOptional: No
Call by Reference: No ( called with pass by value option)
MCOWNER -
Data type: ALCONSEG-CTXOWNEROptional: No
Call by Reference: No ( called with pass by value option)
NUMRANGE -
Data type: ALGLOBTID-MTNUMRANGEOptional: No
Call by Reference: No ( called with pass by value option)
UNIQUENUM -
Data type: ALGLOBTID-MTUIDOptional: No
Call by Reference: No ( called with pass by value option)
TYPECLASS -
Data type: ALGLOBTID-MTCLASSOptional: No
Call by Reference: No ( called with pass by value option)
SEGMENT - Monitoring Segment Name
Data type: ALGLOBAID-MSEGNAMEOptional: No
Call by Reference: No ( called with pass by value option)
SEGMENTTYPE -
Data type: ALCONSEG-SEGMENTTYPOptional: No
Call by Reference: No ( called with pass by value option)
DESTINATION -
Data type: ALCONSEG-DESTINATOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_TID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OTHER_PROBLEM -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TID_NOT_IN_LOCAL_SYSTEM -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SALR_UTIL_TID_GET_DETAILS 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_tid | TYPE ALGLOBTID, " | |||
| lv_sysid | TYPE ALGLOBTID-MTSYSID, " | |||
| lv_invalid_tid | TYPE ALGLOBTID, " | |||
| lv_applserver | TYPE MSXXLIST-NAME, " | |||
| lv_ctxclient | TYPE SY-MANDT, " | |||
| lv_csmsysid | TYPE SY-SYSID, " | |||
| lv_destination_for_dialog | TYPE ALCONSEG-DESTINAT, " | |||
| lv_tid_is_local | TYPE ALFLAG, " | |||
| lv_mcname | TYPE ALGLOBTID-MTMCNAME, " | |||
| lv_other_problem | TYPE ALGLOBTID, " | |||
| lv_mcowner | TYPE ALCONSEG-CTXOWNER, " | |||
| lv_tid_not_in_local_system | TYPE ALCONSEG, " | |||
| lv_numrange | TYPE ALGLOBTID-MTNUMRANGE, " | |||
| lv_uniquenum | TYPE ALGLOBTID-MTUID, " | |||
| lv_typeclass | TYPE ALGLOBTID-MTCLASS, " | |||
| lv_segment | TYPE ALGLOBAID-MSEGNAME, " | |||
| lv_segmenttype | TYPE ALCONSEG-SEGMENTTYP, " | |||
| lv_destination | TYPE ALCONSEG-DESTINAT. " |
|   CALL FUNCTION 'SALR_UTIL_TID_GET_DETAILS' " |
| EXPORTING | ||
| TID | = lv_tid | |
| IMPORTING | ||
| SYSID | = lv_sysid | |
| APPLSERVER | = lv_applserver | |
| CTXCLIENT | = lv_ctxclient | |
| CSMSYSID | = lv_csmsysid | |
| DESTINATION_FOR_DIALOG | = lv_destination_for_dialog | |
| TID_IS_LOCAL | = lv_tid_is_local | |
| MCNAME | = lv_mcname | |
| MCOWNER | = lv_mcowner | |
| NUMRANGE | = lv_numrange | |
| UNIQUENUM | = lv_uniquenum | |
| TYPECLASS | = lv_typeclass | |
| SEGMENT | = lv_segment | |
| SEGMENTTYPE | = lv_segmenttype | |
| DESTINATION | = lv_destination | |
| EXCEPTIONS | ||
| INVALID_TID = 1 | ||
| OTHER_PROBLEM = 2 | ||
| TID_NOT_IN_LOCAL_SYSTEM = 3 | ||
| . " SALR_UTIL_TID_GET_DETAILS | ||
ABAP code using 7.40 inline data declarations to call FM SALR_UTIL_TID_GET_DETAILS
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 MTSYSID FROM ALGLOBTID INTO @DATA(ld_sysid). | ||||
| "SELECT single NAME FROM MSXXLIST INTO @DATA(ld_applserver). | ||||
| "SELECT single MANDT FROM SY INTO @DATA(ld_ctxclient). | ||||
| "SELECT single SYSID FROM SY INTO @DATA(ld_csmsysid). | ||||
| "SELECT single DESTINAT FROM ALCONSEG INTO @DATA(ld_destination_for_dialog). | ||||
| "SELECT single MTMCNAME FROM ALGLOBTID INTO @DATA(ld_mcname). | ||||
| "SELECT single CTXOWNER FROM ALCONSEG INTO @DATA(ld_mcowner). | ||||
| "SELECT single MTNUMRANGE FROM ALGLOBTID INTO @DATA(ld_numrange). | ||||
| "SELECT single MTUID FROM ALGLOBTID INTO @DATA(ld_uniquenum). | ||||
| "SELECT single MTCLASS FROM ALGLOBTID INTO @DATA(ld_typeclass). | ||||
| "SELECT single MSEGNAME FROM ALGLOBAID INTO @DATA(ld_segment). | ||||
| "SELECT single SEGMENTTYP FROM ALCONSEG INTO @DATA(ld_segmenttype). | ||||
| "SELECT single DESTINAT FROM ALCONSEG INTO @DATA(ld_destination). | ||||
Search for further information about these or an SAP related objects