SAP TERM_TRALA_OBJECT_GET Function Module for NOTRANSL: Holen von Einträgen für die Übersetzung









TERM_TRALA_OBJECT_GET is a standard term trala object get 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: Holen von Einträgen für die Übersetzung 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 term trala object get FM, simply by entering the name TERM_TRALA_OBJECT_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function TERM_TRALA_OBJECT_GET 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 'TERM_TRALA_OBJECT_GET'"NOTRANSL: Holen von Einträgen für die Übersetzung
EXPORTING
SOURCELANG = "Source language
TARGETLANG = "Target language
* SUBTYPE = "Translation subtype

TABLES
OBJECTS = "Object lists for worklists
SOURCETEXTS = "Interface to Translation Tools
TARGETTEXTS = "Interface to Translation Tools
.



IMPORTING Parameters details for TERM_TRALA_OBJECT_GET

SOURCELANG - Source language

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

TARGETLANG - Target language

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

SUBTYPE - Translation subtype

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

TABLES Parameters details for TERM_TRALA_OBJECT_GET

OBJECTS - Object lists for worklists

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

SOURCETEXTS - Interface to Translation Tools

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

TARGETTEXTS - Interface to Translation Tools

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

Copy and paste ABAP code example for TERM_TRALA_OBJECT_GET 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_objects  TYPE STANDARD TABLE OF LWRKOBJ, "   
lv_sourcelang  TYPE LWRKOBJ-SOURCELANG, "   
lv_targetlang  TYPE LWRKOBJ-TARGETLANG, "   
lt_sourcetexts  TYPE STANDARD TABLE OF STERM_TRAL, "   
lv_subtype  TYPE LTYPESTECH-SUBTYPE, "   
lt_targettexts  TYPE STANDARD TABLE OF STERM_TRAL. "   

  CALL FUNCTION 'TERM_TRALA_OBJECT_GET'  "NOTRANSL: Holen von Einträgen für die Übersetzung
    EXPORTING
         SOURCELANG = lv_sourcelang
         TARGETLANG = lv_targetlang
         SUBTYPE = lv_subtype
    TABLES
         OBJECTS = lt_objects
         SOURCETEXTS = lt_sourcetexts
         TARGETTEXTS = lt_targettexts
. " TERM_TRALA_OBJECT_GET




ABAP code using 7.40 inline data declarations to call FM TERM_TRALA_OBJECT_GET

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).
 
 
"SELECT single SUBTYPE FROM LTYPESTECH INTO @DATA(ld_subtype).
 
 


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!