SAP LXE_OBJ_GET_TECH_INFO Function Module for Get Object Attributes









LXE_OBJ_GET_TECH_INFO is a standard lxe obj get tech info 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 Attributes 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 get tech info FM, simply by entering the name LXE_OBJ_GET_TECH_INFO into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_OBJ_GET_TECH_INFO 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_GET_TECH_INFO'"Get Object Attributes
  EXPORTING
   CUSTMNR =  "Customer Number
   OBJTYPE =  "Type of Translation Object
   OBJNAME =  "Name of Translation Object
*  BYPASS_BUFFER = '' "Single-Character Flag
*  KEEP_BUFFER = '' "Boolean

 IMPORTING
   COLLTYP =  "Collection Type
   COLLNAM =  "Collection Name
   DOMATYP =  "Domain Type
   DOMANAM =  "Domain Name
   ORIG_LANG =  "ISO Language ID
   TYPEATT =  "Type Attribute
   TCNTTYP =  "Counter Unit for Translation Units
.



IMPORTING Parameters details for LXE_OBJ_GET_TECH_INFO

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

BYPASS_BUFFER - Single-Character Flag

Data type: CHAR1
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEEP_BUFFER - Boolean

Data type: LXEBOOL
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for LXE_OBJ_GET_TECH_INFO

COLLTYP - Collection Type

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

COLLNAM - Collection Name

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

DOMATYP - Domain Type

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

DOMANAM - Domain Name

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

ORIG_LANG - ISO Language ID

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

TYPEATT - Type Attribute

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

TCNTTYP - Counter Unit for Translation Units

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

Copy and paste ABAP code example for LXE_OBJ_GET_TECH_INFO 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_colltyp  TYPE LXECOLLTYP, "   
lv_custmnr  TYPE LXECUSTMNR, "   
lv_collnam  TYPE LXECOLLNAM, "   
lv_objtype  TYPE LXEOBJTYPE, "   
lv_domatyp  TYPE LXEDOMATYP, "   
lv_objname  TYPE LXEOBJNAME, "   
lv_domanam  TYPE LXEDOMANAM, "   
lv_bypass_buffer  TYPE CHAR1, "   ''
lv_orig_lang  TYPE LXEISOLANG, "   
lv_keep_buffer  TYPE LXEBOOL, "   ''
lv_typeatt  TYPE LXETYPEATT, "   
lv_tcnttyp  TYPE LXETCNTTYP. "   

  CALL FUNCTION 'LXE_OBJ_GET_TECH_INFO'  "Get Object Attributes
    EXPORTING
         CUSTMNR = lv_custmnr
         OBJTYPE = lv_objtype
         OBJNAME = lv_objname
         BYPASS_BUFFER = lv_bypass_buffer
         KEEP_BUFFER = lv_keep_buffer
    IMPORTING
         COLLTYP = lv_colltyp
         COLLNAM = lv_collnam
         DOMATYP = lv_domatyp
         DOMANAM = lv_domanam
         ORIG_LANG = lv_orig_lang
         TYPEATT = lv_typeatt
         TCNTTYP = lv_tcnttyp
. " LXE_OBJ_GET_TECH_INFO




ABAP code using 7.40 inline data declarations to call FM LXE_OBJ_GET_TECH_INFO

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_bypass_buffer) = ''.
 
 
DATA(ld_keep_buffer) = ''.
 
 
 


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!