LXE_OBJ_REMO_TRANSLATION_STAT SAP Function module

LXE_OBJ_REMO_TRANSLATION_STAT 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_OBJ_REMO_TRANSLATION_STAT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: LXE_OBJ_REMO
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM LXE_OBJ_REMO_TRANSLATION_STAT - LXE OBJ REMO TRANSLATION STAT

CALL FUNCTION 'LXE_OBJ_REMO_TRANSLATION_STAT' "
  EXPORTING
    t_lang =                    " lxeisolang
    s_lang =                    " lxeisolang
    custmnr =                   " lxecustmnr
    objtype =                   " lxeobjtype
    objname =                   " lxeobjname
*   min_pp_stat = '01'          " lxepp_stat
  IMPORTING
    stattrn =                   " lxestattrn
    cnttot =                    " lxecnttot
    cntnew =                    " lxecntnew
    cntmod =                    " lxecntmod
    cntavl =                    " lxecntavl
    .  "  LXE_OBJ_REMO_TRANSLATION_STAT

ABAP code example for Function Module LXE_OBJ_REMO_TRANSLATION_STAT

The ABAP code below is a full code listing to execute function module LXE_OBJ_REMO_TRANSLATION_STAT 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_stattrn  
 
 TYPE LXESTATTRN
,
ld_cnttot  
 
 TYPE LXECNTTOT
,
ld_cntnew  
 
 TYPE LXECNTNEW
,
ld_cntmod  
 
 TYPE LXECNTMOD
,
ld_cntavl  
 
 TYPE LXECNTAVL
.


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

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

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

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

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

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

CALL FUNCTION 'LXE_OBJ_REMO_TRANSLATION_STAT'
  EXPORTING
    t_lang =                     ld_t_lang
    s_lang =                     ld_s_lang
    custmnr =                    ld_custmnr
    objtype =                    ld_objtype
    objname =                    ld_objname
*   min_pp_stat =                ld_min_pp_stat
  IMPORTING
    stattrn =                    ld_stattrn
    cnttot =                     ld_cnttot
    cntnew =                     ld_cntnew
    cntmod =                     ld_cntmod
    cntavl =                     ld_cntavl
    .  "  LXE_OBJ_REMO_TRANSLATION_STAT

IF SY-SUBRC EQ 0.
  "All OK
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_stattrn
 
 TYPE LXESTATTRN ,
ld_t_lang
 
 TYPE LXEISOLANG ,
ld_cnttot
 
 TYPE LXECNTTOT ,
ld_s_lang
 
 TYPE LXEISOLANG ,
ld_cntnew
 
 TYPE LXECNTNEW ,
ld_custmnr
 
 TYPE LXECUSTMNR ,
ld_cntmod
 
 TYPE LXECNTMOD ,
ld_objtype
 
 TYPE LXEOBJTYPE ,
ld_cntavl
 
 TYPE LXECNTAVL ,
ld_objname
 
 TYPE LXEOBJNAME ,
ld_min_pp_stat
 
 TYPE LXEPP_STAT .


ld_t_lang = 'Check type of data required'.
ld_s_lang = 'Check type of data required'.
ld_custmnr = 'Check type of data required'.
ld_objtype = 'Check type of data required'.
ld_objname = 'Check type of data required'.
ld_min_pp_stat = 'Check type of data required'.