LXE_EXTERNAL_EDITOR_CHECK SAP Function module

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

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

Pattern for FM LXE_EXTERNAL_EDITOR_CHECK - LXE EXTERNAL EDITOR CHECK

CALL FUNCTION 'LXE_EXTERNAL_EDITOR_CHECK' "
  EXPORTING
    t_lang =                    " lxeisolang
    s_lang =                    " lxeisolang
    trl_area =                  " lxecustmnr
    objtype =                   " lxeobjtype
    objname =                   " lxeobjname
  IMPORTING
    ini =                       " lxe_xstring
    ininame =                   " lxeininame
    work_dir =                  " string
    template_id =               " lxetextkey
    tm_dest =                   " rfcdest
    .  "  LXE_EXTERNAL_EDITOR_CHECK

ABAP code example for Function Module LXE_EXTERNAL_EDITOR_CHECK

The ABAP code below is a full code listing to execute function module LXE_EXTERNAL_EDITOR_CHECK 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_ini  
 
 TYPE LXE_XSTRING
,
ld_ininame  
 
 TYPE LXEININAME
,
ld_work_dir  
 
 TYPE STRING
,
ld_template_id  
 
 TYPE LXETEXTKEY
,
ld_tm_dest  
 
 TYPE RFCDEST
.


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

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

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

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

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

CALL FUNCTION 'LXE_EXTERNAL_EDITOR_CHECK'
  EXPORTING
    t_lang =                     ld_t_lang
    s_lang =                     ld_s_lang
    trl_area =                   ld_trl_area
    objtype =                    ld_objtype
    objname =                    ld_objname
  IMPORTING
    ini =                        ld_ini
    ininame =                    ld_ininame
    work_dir =                   ld_work_dir
    template_id =                ld_template_id
    tm_dest =                    ld_tm_dest
    .  "  LXE_EXTERNAL_EDITOR_CHECK

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_ini
 
 TYPE LXE_XSTRING ,
ld_t_lang
 
 TYPE LXEISOLANG ,
ld_ininame
 
 TYPE LXEININAME ,
ld_s_lang
 
 TYPE LXEISOLANG ,
ld_work_dir
 
 TYPE STRING ,
ld_trl_area
 
 TYPE LXECUSTMNR ,
ld_template_id
 
 TYPE LXETEXTKEY ,
ld_objtype
 
 TYPE LXEOBJTYPE ,
ld_tm_dest
 
 TYPE RFCDEST ,
ld_objname
 
 TYPE LXEOBJNAME .


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