SAP LXE_OBJ_SLEX_IB Function Module for LXE_OBJ_SLEX_IB









LXE_OBJ_SLEX_IB is a standard lxe obj slex ib SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for LXE_OBJ_SLEX_IB processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for lxe obj slex ib FM, simply by entering the name LXE_OBJ_SLEX_IB into the relevant SAP transaction such as SE37 or SE38.

Function Group: LXE_OBJ_SLEX
Program Name: SAPLLXE_OBJ_SLEX
Main Program: SAPLLXE_OBJ_SLEX
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function LXE_OBJ_SLEX_IB pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'LXE_OBJ_SLEX_IB'"LXE_OBJ_SLEX_IB
  EXPORTING
   T_LANG =  "Language Key
   CUSTMNR =  "Customer Number
   OBJTYPE =  "Type of Translation Object
   OBJNAME =  "Name of Translation Object

EXCEPTIONS
   NOT_TO_BE_TRANSLATED = 1
.



IMPORTING Parameters details for LXE_OBJ_SLEX_IB

T_LANG - Language Key

Data type: LXEISOLANG
Optional: No
Call by Reference: Yes

CUSTMNR - Customer Number

Data type: LXECUSTMNR
Optional: No
Call by Reference: Yes

OBJTYPE - Type of Translation Object

Data type: LXEOBJTYPE
Optional: No
Call by Reference: Yes

OBJNAME - Name of Translation Object

Data type: LXEOBJNAME
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_TO_BE_TRANSLATED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for LXE_OBJ_SLEX_IB Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_t_lang  TYPE LXEISOLANG, "   
lv_not_to_be_translated  TYPE LXEISOLANG, "   
lv_custmnr  TYPE LXECUSTMNR, "   
lv_objtype  TYPE LXEOBJTYPE, "   
lv_objname  TYPE LXEOBJNAME. "   

  CALL FUNCTION 'LXE_OBJ_SLEX_IB'  "LXE_OBJ_SLEX_IB
    EXPORTING
         T_LANG = lv_t_lang
         CUSTMNR = lv_custmnr
         OBJTYPE = lv_objtype
         OBJNAME = lv_objname
    EXCEPTIONS
        NOT_TO_BE_TRANSLATED = 1
. " LXE_OBJ_SLEX_IB




ABAP code using 7.40 inline data declarations to call FM LXE_OBJ_SLEX_IB

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!