LXE_TS_API_GET_STATS SAP Function module - Determine translation status of texts

LXE_TS_API_GET_STATS is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name LXE_TS_API_GET_STATS into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: LXE_TS_API_AREA_GEN1
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM LXE_TS_API_GET_STATS - LXE TS API GET STATS

CALL FUNCTION 'LXE_TS_API_GET_STATS' "Determine translation status of texts
  CHANGING
    x_texts =                   " lxe_tt_x_text_stat  Translation status of PC1 short texts
    y_texts =                   " lxe_tt_y_text_stat  Translation status of long texts
    z_texts =                   " lxe_tt_z_text_stat  Translation status of special texts
  EXCEPTIONS
    UNAUTHORIZED = 1            "               Unauthorized
    UNKNOWN_TRANS_AREA = 2      "               Unknown translation area
    UNSUPPORTED_TRANS_AREA_TYPE = 3  "          Unsupported translation area type
    UNKNOWN_LANGUAGE = 4        "               Unknown language
    FINGERPRINTING_FAILED = 5   "               Fingerprinting failed
    UNKNOWN_DOMAIN = 6          "               Unknown domain
    LOCKED = 7                  "               Operation is currently locked
    .  "  LXE_TS_API_GET_STATS

ABAP code example for Function Module LXE_TS_API_GET_STATS

The ABAP code below is a full code listing to execute function module LXE_TS_API_GET_STATS including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_x_texts) = 'Check type of data required'.

DATA(ld_y_texts) = 'Check type of data required'.

DATA(ld_z_texts) = 'Check type of data required'.
.

CALL FUNCTION 'LXE_TS_API_GET_STATS'
  CHANGING
    x_texts =                    ld_x_texts
    y_texts =                    ld_y_texts
    z_texts =                    ld_z_texts
  EXCEPTIONS
    UNAUTHORIZED =               1
    UNKNOWN_TRANS_AREA =         2
    UNSUPPORTED_TRANS_AREA_TYPE =    3
    UNKNOWN_LANGUAGE =           4
    FINGERPRINTING_FAILED =      5
    UNKNOWN_DOMAIN =             6
    LOCKED =                     7
    .  "  LXE_TS_API_GET_STATS

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 7. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_x_texts
 
 TYPE LXE_TT_X_TEXT_STAT ,
ld_y_texts
 
 TYPE LXE_TT_Y_TEXT_STAT ,
ld_z_texts
 
 TYPE LXE_TT_Z_TEXT_STAT .


ld_x_texts = 'Check type of data required'.
ld_y_texts = 'Check type of data required'.
ld_z_texts = 'Check type of data required'.