SAP LXE_MT_TRANSLATION Function Module for NOTRANSL: Funktionsbaustein für MT Anbindung

Search SAP Function Modules

LXE_MT_TRANSLATION is a standard lxe mt translation SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Funktionsbaustein für MT Anbindung 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 mt translation FM, simply by entering the name LXE_MT_TRANSLATION into the relevant SAP transaction such as SE37 or SE38.

Function Group: LXE_MT
Program Name: SAPLLXE_MT
Main Program: SAPLLXE_MT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXE_MT_TRANSLATION 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_MT_TRANSLATION'"NOTRANSL: Funktionsbaustein für MT Anbindung
  EXPORTING
   I_SOURCE =  "Predefined Type
   I_REPO_URL =  "Predefined Type
   I_LICENSE_PATH =  "Predefined Type
*  I_SHOW_DIALOG = '' "Predefined Type
   I_DIRECTION =  "Predefined Type
*  I_SUBJECTAREA = 'CTV' "Predefined Type
*  I_MARK_UNKNOWNS = '0' "Predefined Type
*  I_MARK_COMPOUNDS = '0' "Predefined Type
*  I_MARK_ALTERNATIVES = '0' "Predefined Type
*  I_MARK_CONSTANTS = '0' "Predefined Type
*  I_DOCUMENTNAME =  "Predefined Type
   I_POOL_NAME =  "Predefined Type

 IMPORTING
   E_TRANSLATED_TEXT =  "Predefined Type
   E_OKCODE =  "ABAP System Field: PAI-Triggering Function Code

.

IMPORTING Parameters details for LXE_MT_TRANSLATION

I_SOURCE - Predefined Type

Data type: STRING
Optional: No
Call by Reference: Yes

I_REPO_URL - Predefined Type

Data type: STRING
Optional: No
Call by Reference: Yes

I_LICENSE_PATH - Predefined Type

Data type: STRING
Optional: No
Call by Reference: Yes

I_SHOW_DIALOG - Predefined Type

Data type: STRING
Default: ''
Optional: Yes
Call by Reference: Yes

I_DIRECTION - Predefined Type

Data type: STRING
Optional: No
Call by Reference: Yes

I_SUBJECTAREA - Predefined Type

Data type: STRING
Default: 'CTV'
Optional: Yes
Call by Reference: Yes

I_MARK_UNKNOWNS - Predefined Type

Data type: STRING
Default: '0'
Optional: Yes
Call by Reference: Yes

I_MARK_COMPOUNDS - Predefined Type

Data type: STRING
Default: '0'
Optional: Yes
Call by Reference: Yes

I_MARK_ALTERNATIVES - Predefined Type

Data type: STRING
Default: '0'
Optional: Yes
Call by Reference: Yes

I_MARK_CONSTANTS - Predefined Type

Data type: STRING
Default: '0'
Optional: Yes
Call by Reference: Yes

I_DOCUMENTNAME - Predefined Type

Data type: STRING
Optional: Yes
Call by Reference: Yes

I_POOL_NAME - Predefined Type

Data type: STRING
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for LXE_MT_TRANSLATION

E_TRANSLATED_TEXT - Predefined Type

Data type: STRING
Optional: No
Call by Reference: Yes

E_OKCODE - ABAP System Field: PAI-Triggering Function Code

Data type: SY-UCOMM
Optional: No
Call by Reference: Yes

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

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