SAP TEXT_TRANSLATION_CALL Function Module for









TEXT_TRANSLATION_CALL is a standard text translation call 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 text translation call FM, simply by entering the name TEXT_TRANSLATION_CALL into the relevant SAP transaction such as SE37 or SE38.

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



Function TEXT_TRANSLATION_CALL 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 'TEXT_TRANSLATION_CALL'"
EXPORTING
OBJECT_NAME = "
OBJEKT_TYPE = "
* SOURCELANG = "
* TARGETLANG = "
.



IMPORTING Parameters details for TEXT_TRANSLATION_CALL

OBJECT_NAME -

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

OBJEKT_TYPE -

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

SOURCELANG -

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

TARGETLANG -

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

Copy and paste ABAP code example for TEXT_TRANSLATION_CALL 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_object_name  TYPE STRING, "   
lv_objekt_type  TYPE CHAR4, "   
lv_sourcelang  TYPE LWRKOBJ-SOURCELANG, "   
lv_targetlang  TYPE LWRKOBJ-TARGETLANG. "   

  CALL FUNCTION 'TEXT_TRANSLATION_CALL'  "
    EXPORTING
         OBJECT_NAME = lv_object_name
         OBJEKT_TYPE = lv_objekt_type
         SOURCELANG = lv_sourcelang
         TARGETLANG = lv_targetlang
. " TEXT_TRANSLATION_CALL




ABAP code using 7.40 inline data declarations to call FM TEXT_TRANSLATION_CALL

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 SOURCELANG FROM LWRKOBJ INTO @DATA(ld_sourcelang).
 
"SELECT single TARGETLANG FROM LWRKOBJ INTO @DATA(ld_targetlang).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!