SAP LXE_OBJ_TWO_PART_FUNC Function Module for Get object name with type FUNC









LXE_OBJ_TWO_PART_FUNC is a standard lxe obj two part func SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get object name with type FUNC 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 two part func FM, simply by entering the name LXE_OBJ_TWO_PART_FUNC into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_OBJ_TWO_PART_FUNC 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_TWO_PART_FUNC'"Get object name with type FUNC
EXPORTING
* I_DEVCLASS = "Package
* I_POS = 1 "
I_INPUT1 = "Name of Translation Object
* I_INPUT2 = '*' "255 Characters

TABLES
ET_VALUES = "Table of CHAR255

EXCEPTIONS
OBJECT_NOT_FOUND = 1 FIRST_INPUT_INVALID = 2
.



IMPORTING Parameters details for LXE_OBJ_TWO_PART_FUNC

I_DEVCLASS - Package

Data type: DEVCLASS
Optional: Yes
Call by Reference: Yes

I_POS -

Data type: I
Default: 1
Optional: No
Call by Reference: Yes

I_INPUT1 - Name of Translation Object

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

I_INPUT2 - 255 Characters

Data type: LXEOBJNAME
Default: '*'
Optional: No
Call by Reference: Yes

TABLES Parameters details for LXE_OBJ_TWO_PART_FUNC

ET_VALUES - Table of CHAR255

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

EXCEPTIONS details

OBJECT_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

FIRST_INPUT_INVALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LXE_OBJ_TWO_PART_FUNC 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:
lt_et_values  TYPE STANDARD TABLE OF LXE_COLOB, "   
lv_i_devclass  TYPE DEVCLASS, "   
lv_object_not_found  TYPE DEVCLASS, "   
lv_i_pos  TYPE I, "   1
lv_first_input_invalid  TYPE I, "   
lv_i_input1  TYPE LXEOBJNAME, "   
lv_i_input2  TYPE LXEOBJNAME. "   '*'

  CALL FUNCTION 'LXE_OBJ_TWO_PART_FUNC'  "Get object name with type FUNC
    EXPORTING
         I_DEVCLASS = lv_i_devclass
         I_POS = lv_i_pos
         I_INPUT1 = lv_i_input1
         I_INPUT2 = lv_i_input2
    TABLES
         ET_VALUES = lt_et_values
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        FIRST_INPUT_INVALID = 2
. " LXE_OBJ_TWO_PART_FUNC




ABAP code using 7.40 inline data declarations to call FM LXE_OBJ_TWO_PART_FUNC

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.

 
 
 
DATA(ld_i_pos) = 1.
 
 
 
DATA(ld_i_input2) = '*'.
 


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!