SAP LXE_TS_API_GET_TS_OBJTYPES Function Module for Get list of object types supported by translation system
LXE_TS_API_GET_TS_OBJTYPES is a standard lxe ts api get ts objtypes SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get list of object types supported by translation system 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 lxe ts api get ts objtypes FM, simply by entering the name LXE_TS_API_GET_TS_OBJTYPES into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_TS_API
Program Name: SAPLLXE_TS_API
Main Program: SAPLLXE_TS_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function LXE_TS_API_GET_TS_OBJTYPES 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 'LXE_TS_API_GET_TS_OBJTYPES'"Get list of object types supported by translation system.
TABLES
EX_OBJTYPES = "Object type
EXCEPTIONS
UNAUTHORIZED = 1 LOCKED = 2
TABLES Parameters details for LXE_TS_API_GET_TS_OBJTYPES
EX_OBJTYPES - Object type
Data type: LXE_OBJTYPE_SOptional: No
Call by Reference: Yes
EXCEPTIONS details
UNAUTHORIZED - Unauthorized
Data type:Optional: No
Call by Reference: Yes
LOCKED - Operation is currently locked
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for LXE_TS_API_GET_TS_OBJTYPES 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_ex_objtypes | TYPE STANDARD TABLE OF LXE_OBJTYPE_S, " | |||
| lv_unauthorized | TYPE LXE_OBJTYPE_S, " | |||
| lv_locked | TYPE LXE_OBJTYPE_S. " |
|   CALL FUNCTION 'LXE_TS_API_GET_TS_OBJTYPES' "Get list of object types supported by translation system |
| TABLES | ||
| EX_OBJTYPES | = lt_ex_objtypes | |
| EXCEPTIONS | ||
| UNAUTHORIZED = 1 | ||
| LOCKED = 2 | ||
| . " LXE_TS_API_GET_TS_OBJTYPES | ||
ABAP code using 7.40 inline data declarations to call FM LXE_TS_API_GET_TS_OBJTYPES
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