SAP BAPI_SYSTEM_MTE_GETTIDBYNAME Function Module for Read TID for a Uniquely-Named MTE

Search SAP Function Modules

BAPI_SYSTEM_MTE_GETTIDBYNAME is a standard bapi system mte gettidbyname SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read TID for a Uniquely-Named MTE 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 bapi system mte gettidbyname FM, simply by entering the name BAPI_SYSTEM_MTE_GETTIDBYNAME into the relevant SAP transaction such as SE37 or SE38.

Function Group: SALX
Program Name: SAPLSALX
Main Program: SAPLSALX
Appliation area: S
Release date: 13-Jan-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_SYSTEM_MTE_GETTIDBYNAME 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 'BAPI_SYSTEM_MTE_GETTIDBYNAME'"Read TID for a Uniquely-Named MTE
  EXPORTING
   SYSTEM_ID =  "System ID
   CONTEXT_NAME =  "The context name
*  OBJECT_NAME =  "Object Name
*  MTE_NAME =  "MTE Name
   EXTERNAL_USER_NAME =  "Name of the SAP-External User

 IMPORTING
   TID =  "The returned MTE ID (TID)
   RETURN =  "Return Messages

.

IMPORTING Parameters details for BAPI_SYSTEM_MTE_GETTIDBYNAME

SYSTEM_ID - System ID

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

CONTEXT_NAME - The context name

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

OBJECT_NAME - Object Name

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

MTE_NAME - MTE Name

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

EXTERNAL_USER_NAME - Name of the SAP-External User

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

EXPORTING Parameters details for BAPI_SYSTEM_MTE_GETTIDBYNAME

TID - The returned MTE ID (TID)

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

RETURN - Return Messages

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

Copy and paste ABAP code example for BAPI_SYSTEM_MTE_GETTIDBYNAME 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.

ABAP code using 7.40 inline data declarations to call FM BAPI_SYSTEM_MTE_GETTIDBYNAME

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