LXE_KTP_WRITE_OBJECT_TITLE SAP Function module

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

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

Pattern for FM LXE_KTP_WRITE_OBJECT_TITLE - LXE KTP WRITE OBJECT TITLE

CALL FUNCTION 'LXE_KTP_WRITE_OBJECT_TITLE' "
  EXPORTING
    logical_port_name =         " prx_logical_port_name
    object_key =                " lxeobjname
    javalang =                  " lxejavalang
    title =                     " xstring
*   objtype =                   " lxeobjtype
  IMPORTING
    proc_status =               " lxestatprc
  EXCEPTIONS
    CX_AI_SYSTEM_FAULT = 1      "
    CX_LXE_WRITE_OBJECT_FAULT1 = 2  "
    CX_AI_APPLICATION_FAULT = 3  "
    .  "  LXE_KTP_WRITE_OBJECT_TITLE

ABAP code example for Function Module LXE_KTP_WRITE_OBJECT_TITLE

The ABAP code below is a full code listing to execute function module LXE_KTP_WRITE_OBJECT_TITLE 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_proc_status  
 
 TYPE LXESTATPRC
.


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

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

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

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

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

CALL FUNCTION 'LXE_KTP_WRITE_OBJECT_TITLE'
  EXPORTING
    logical_port_name =          ld_logical_port_name
    object_key =                 ld_object_key
    javalang =                   ld_javalang
    title =                      ld_title
*   objtype =                    ld_objtype
  IMPORTING
    proc_status =                ld_proc_status
  EXCEPTIONS
    CX_AI_SYSTEM_FAULT =         1
    CX_LXE_WRITE_OBJECT_FAULT1 =    2
    CX_AI_APPLICATION_FAULT =    3
    .  "  LXE_KTP_WRITE_OBJECT_TITLE

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
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_proc_status
 
 TYPE LXESTATPRC ,
ld_logical_port_name
 
 TYPE PRX_LOGICAL_PORT_NAME ,
ld_object_key
 
 TYPE LXEOBJNAME ,
ld_javalang
 
 TYPE LXEJAVALANG ,
ld_title
 
 TYPE XSTRING ,
ld_objtype
 
 TYPE LXEOBJTYPE .


ld_logical_port_name = 'Check type of data required'.
ld_object_key = 'Check type of data required'.
ld_javalang = 'Check type of data required'.
ld_title = 'Check type of data required'.
ld_objtype = 'Check type of data required'.