SAP LXE_XT_API_GET_OBJECT Function Module for Export Object









LXE_XT_API_GET_OBJECT is a standard lxe xt api get object SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Export 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 xt api get object FM, simply by entering the name LXE_XT_API_GET_OBJECT into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_XT_API_GET_OBJECT 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_XT_API_GET_OBJECT'"Export Object
  EXPORTING
   TRL_AREA =  "Translation Area
   OBJNAME_EXT =  "External Object Name

 IMPORTING
   ORIG_LANG =  "ISO Language ID
   YTEXT_TAB =  "Long Texts
   ZTEXT_TAB =  "Special Texts
   ZBIN_TAB =  "Special Texts (Binary)
   TEXT_ATTR_TAB =  "Text Attributes
   COLLTYPE =  "Collection Type
   COLLNAME =  "Collection Name
   DOMATYPE =  "Domain Type
   DOMANAME =  "Domain Name
   DEVELOPER =  "Translation Unit for Short Text (Line)
   DESCRIPTION =  "Translation Unit for Short Text (Line)
   OBJ_ATTR_TAB =  "Attributes
   XTEXT_TAB =  "Short Texts

EXCEPTIONS
   INVALID_OBJECT = 1    HASH_ERROR = 2    OBJECT_DOES_NOT_EXIST = 3
.



IMPORTING Parameters details for LXE_XT_API_GET_OBJECT

TRL_AREA - Translation Area

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

OBJNAME_EXT - External Object Name

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

EXPORTING Parameters details for LXE_XT_API_GET_OBJECT

ORIG_LANG - ISO Language ID

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

YTEXT_TAB - Long Texts

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

ZTEXT_TAB - Special Texts

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

ZBIN_TAB - Special Texts (Binary)

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

TEXT_ATTR_TAB - Text Attributes

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

COLLTYPE - Collection Type

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

COLLNAME - Collection Name

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

DOMATYPE - Domain Type

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

DOMANAME - Domain Name

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

DEVELOPER - Translation Unit for Short Text (Line)

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

DESCRIPTION - Translation Unit for Short Text (Line)

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

OBJ_ATTR_TAB - Attributes

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

XTEXT_TAB - Short Texts

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

EXCEPTIONS details

INVALID_OBJECT -

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

HASH_ERROR -

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

OBJECT_DOES_NOT_EXIST -

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

Copy and paste ABAP code example for LXE_XT_API_GET_OBJECT 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_trl_area  TYPE LXECUSTMNR, "   
lv_orig_lang  TYPE LXEISOLANG, "   
lv_invalid_object  TYPE LXEISOLANG, "   
lv_ytext_tab  TYPE LXE_TT_YTEXT, "   
lv_ztext_tab  TYPE LXE_TT_ZTEXT, "   
lv_zbin_tab  TYPE LXE_TT_ZBIN, "   
lv_text_attr_tab  TYPE LXE_TT_TEXT_KEY_VALUE, "   
lv_colltype  TYPE LXECOLLTYP, "   
lv_hash_error  TYPE LXECOLLTYP, "   
lv_objname_ext  TYPE STRING, "   
lv_collname  TYPE LXECOLLNAM, "   
lv_object_does_not_exist  TYPE LXECOLLNAM, "   
lv_domatype  TYPE LXEDOMATYP, "   
lv_domaname  TYPE LXEDOMANAM, "   
lv_developer  TYPE LXEUNITLIN, "   
lv_description  TYPE LXEUNITLIN, "   
lv_obj_attr_tab  TYPE LXE_TT_KEY_VALUE, "   
lv_xtext_tab  TYPE LXE_TT_XTEXT. "   

  CALL FUNCTION 'LXE_XT_API_GET_OBJECT'  "Export Object
    EXPORTING
         TRL_AREA = lv_trl_area
         OBJNAME_EXT = lv_objname_ext
    IMPORTING
         ORIG_LANG = lv_orig_lang
         YTEXT_TAB = lv_ytext_tab
         ZTEXT_TAB = lv_ztext_tab
         ZBIN_TAB = lv_zbin_tab
         TEXT_ATTR_TAB = lv_text_attr_tab
         COLLTYPE = lv_colltype
         COLLNAME = lv_collname
         DOMATYPE = lv_domatype
         DOMANAME = lv_domaname
         DEVELOPER = lv_developer
         DESCRIPTION = lv_description
         OBJ_ATTR_TAB = lv_obj_attr_tab
         XTEXT_TAB = lv_xtext_tab
    EXCEPTIONS
        INVALID_OBJECT = 1
        HASH_ERROR = 2
        OBJECT_DOES_NOT_EXIST = 3
. " LXE_XT_API_GET_OBJECT




ABAP code using 7.40 inline data declarations to call FM LXE_XT_API_GET_OBJECT

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!