SAP CHECK_FORM_TRANSLATION_STATUS Function Module for Read translation status and language vector of a form
CHECK_FORM_TRANSLATION_STATUS is a standard check form translation status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read translation status and language vector of a form 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 check form translation status FM, simply by entering the name CHECK_FORM_TRANSLATION_STATUS 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 CHECK_FORM_TRANSLATION_STATUS 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 'CHECK_FORM_TRANSLATION_STATUS'"Read translation status and language vector of a form.
EXPORTING
FORM = "Form Name
* CLIENT = SY-MANDT "Client
IMPORTING
MASTER_LANGUAGE = "Original language of the form
TRANSLATION_WANTED = "
TRANSLATION_LANGUAGES = "
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for CHECK_FORM_TRANSLATION_STATUS
FORM - Form Name
Data type: ITCTA-TDFORMOptional: No
Call by Reference: No ( called with pass by value option)
CLIENT - Client
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CHECK_FORM_TRANSLATION_STATUS
MASTER_LANGUAGE - Original language of the form
Data type: SY-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
TRANSLATION_WANTED -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TRANSLATION_LANGUAGES -
Data type: ITCTA-TDLANGVECOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CHECK_FORM_TRANSLATION_STATUS 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_form | TYPE ITCTA-TDFORM, " | |||
| lv_not_found | TYPE ITCTA, " | |||
| lv_master_language | TYPE SY-LANGU, " | |||
| lv_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_translation_wanted | TYPE C, " | |||
| lv_translation_languages | TYPE ITCTA-TDLANGVEC. " |
|   CALL FUNCTION 'CHECK_FORM_TRANSLATION_STATUS' "Read translation status and language vector of a form |
| EXPORTING | ||
| FORM | = lv_form | |
| CLIENT | = lv_client | |
| IMPORTING | ||
| MASTER_LANGUAGE | = lv_master_language | |
| TRANSLATION_WANTED | = lv_translation_wanted | |
| TRANSLATION_LANGUAGES | = lv_translation_languages | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " CHECK_FORM_TRANSLATION_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM CHECK_FORM_TRANSLATION_STATUS
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 TDFORM FROM ITCTA INTO @DATA(ld_form). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_master_language). | ||||
| "SELECT single MANDT FROM SY INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
| "SELECT single TDLANGVEC FROM ITCTA INTO @DATA(ld_translation_languages). | ||||
Search for further information about these or an SAP related objects