LXE_XT_XTEXT_WRITE SAP Function module - Write XNAT Texts

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

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

Pattern for FM LXE_XT_XTEXT_WRITE - LXE XT XTEXT WRITE

CALL FUNCTION 'LXE_XT_XTEXT_WRITE' "Write XNAT Texts
  EXPORTING
    s_lang =                    " lxeisolang    ISO Language ID
    t_lang =                    " lxeisolang    ISO Language ID
    trl_area =                  " lxecustmnr    Customer Number
    objname =                   " lxeobjname    Name of Translation Object
  TABLES
    lt_pcx_s1 =                 " lxe_pcx_s1    Text Pairs
  EXCEPTIONS
    OBJECT_DOES_NOT_EXIST = 1   "
    ORIG_LANG_CONFLICT = 2      "
    NO_VALID_TEXT_FOUND = 3     "
    DB_ERROR = 4                "
    .  "  LXE_XT_XTEXT_WRITE

ABAP code example for Function Module LXE_XT_XTEXT_WRITE

The ABAP code below is a full code listing to execute function module LXE_XT_XTEXT_WRITE 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:
it_lt_pcx_s1  
 
 TYPE STANDARD TABLE OF LXE_PCX_S1,"TABLES PARAM
wa_lt_pcx_s1
 
 LIKE LINE OF it_lt_pcx_s1
.


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

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

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

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

"populate fields of struture and append to itab
append wa_lt_pcx_s1 to it_lt_pcx_s1.
.

CALL FUNCTION 'LXE_XT_XTEXT_WRITE'
  EXPORTING
    s_lang =                     ld_s_lang
    t_lang =                     ld_t_lang
    trl_area =                   ld_trl_area
    objname =                    ld_objname
  TABLES
    lt_pcx_s1 =                  it_lt_pcx_s1
  EXCEPTIONS
    OBJECT_DOES_NOT_EXIST =      1
    ORIG_LANG_CONFLICT =         2
    NO_VALID_TEXT_FOUND =        3
    DB_ERROR =                   4
    .  "  LXE_XT_XTEXT_WRITE

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
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_s_lang
 
 TYPE LXEISOLANG ,
it_lt_pcx_s1
 
 TYPE STANDARD TABLE OF LXE_PCX_S1 ,
wa_lt_pcx_s1
 
 LIKE LINE OF it_lt_pcx_s1,
ld_t_lang
 
 TYPE LXEISOLANG ,
ld_trl_area
 
 TYPE LXECUSTMNR ,
ld_objname
 
 TYPE LXEOBJNAME .


ld_s_lang = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_lt_pcx_s1 to it_lt_pcx_s1.
ld_t_lang = 'Check type of data required'.
ld_trl_area = 'Check type of data required'.
ld_objname = 'Check type of data required'.