SAP GET_TRANSLATION_STATUS_FORMS Function Module for









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

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



Function GET_TRANSLATION_STATUS_FORMS 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 'GET_TRANSLATION_STATUS_FORMS'"
EXPORTING
SOURCELANG = "
TARGETLANG = "

TABLES
OBJECTS = "
.



IMPORTING Parameters details for GET_TRANSLATION_STATUS_FORMS

SOURCELANG -

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

TARGETLANG -

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

TABLES Parameters details for GET_TRANSLATION_STATUS_FORMS

OBJECTS -

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

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

  CALL FUNCTION 'GET_TRANSLATION_STATUS_FORMS'  "
    EXPORTING
         SOURCELANG = lv_sourcelang
         TARGETLANG = lv_targetlang
    TABLES
         OBJECTS = lt_objects
. " GET_TRANSLATION_STATUS_FORMS




ABAP code using 7.40 inline data declarations to call FM GET_TRANSLATION_STATUS_FORMS

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!