SAP LXE_OBJ_TWO_PART_MES_SELECT Function Module for Select MES object









LXE_OBJ_TWO_PART_MES_SELECT is a standard lxe obj two part mes select SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Select MES object 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 mes select FM, simply by entering the name LXE_OBJ_TWO_PART_MES_SELECT 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_MES_SELECT 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_MES_SELECT'"Select MES object
  EXPORTING
   I_POS =  "
   I_OBJNAME1 =  "Name of Translation Object
   I_OBJNAME2 =  "Name of Translation Object
*  I_COLLTYP = '*' "Collection Type
*  I_COLLNAM = '*' "Collection Name

 IMPORTING
   E_CUSTMNR =  "Translation Area
   E_OBJTYPE =  "Type of Translation Object
   E_OBJNAME1 =  "Name of Translation Object
   E_OBJNAME2 =  "Name of Translation Object
   E_OBJ_FULLNAME =  "Name of Translation Object
.



IMPORTING Parameters details for LXE_OBJ_TWO_PART_MES_SELECT

I_POS -

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

I_OBJNAME1 - Name of Translation Object

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

I_OBJNAME2 - Name of Translation Object

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

I_COLLTYP - Collection Type

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

I_COLLNAM - Collection Name

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

EXPORTING Parameters details for LXE_OBJ_TWO_PART_MES_SELECT

E_CUSTMNR - Translation Area

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

E_OBJTYPE - Type of Translation Object

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

E_OBJNAME1 - Name of Translation Object

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

E_OBJNAME2 - Name of Translation Object

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

E_OBJ_FULLNAME - Name of Translation Object

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

Copy and paste ABAP code example for LXE_OBJ_TWO_PART_MES_SELECT 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_i_pos  TYPE I, "   
lv_e_custmnr  TYPE LXECUSTMNR, "   
lv_e_objtype  TYPE LXEOBJTYPE, "   
lv_i_objname1  TYPE LXEOBJNAME, "   
lv_e_objname1  TYPE LXEOBJNAME, "   
lv_i_objname2  TYPE LXEOBJNAME, "   
lv_i_colltyp  TYPE LXECOLLTYP, "   '*'
lv_e_objname2  TYPE LXEOBJNAME, "   
lv_i_collnam  TYPE LXECOLLNAM, "   '*'
lv_e_obj_fullname  TYPE LXEOBJNAME. "   

  CALL FUNCTION 'LXE_OBJ_TWO_PART_MES_SELECT'  "Select MES object
    EXPORTING
         I_POS = lv_i_pos
         I_OBJNAME1 = lv_i_objname1
         I_OBJNAME2 = lv_i_objname2
         I_COLLTYP = lv_i_colltyp
         I_COLLNAM = lv_i_collnam
    IMPORTING
         E_CUSTMNR = lv_e_custmnr
         E_OBJTYPE = lv_e_objtype
         E_OBJNAME1 = lv_e_objname1
         E_OBJNAME2 = lv_e_objname2
         E_OBJ_FULLNAME = lv_e_obj_fullname
. " LXE_OBJ_TWO_PART_MES_SELECT




ABAP code using 7.40 inline data declarations to call FM LXE_OBJ_TWO_PART_MES_SELECT

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_colltyp) = '*'.
 
 
DATA(ld_i_collnam) = '*'.
 
 


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!