SAP LXE_OBJ_TEXT_READ_GENERIC_RFC Function Module for

Search SAP Function Modules

LXE_OBJ_TEXT_READ_GENERIC_RFC is a standard lxe obj text read generic rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 text read generic rfc FM, simply by entering the name LXE_OBJ_TEXT_READ_GENERIC_RFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: LXE_TD_REMO
Program Name: SAPLLXE_TD_REMO
Main Program: SAPLLXE_TD_REMO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function LXE_OBJ_TEXT_READ_GENERIC_RFC 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_TEXT_READ_GENERIC_RFC'"
  EXPORTING
   OBJTYPE =  "
   OBJNAME =  "
   CUSTMNR =  "
   LANG =  "
*  TEXTKEY = '' "

 IMPORTING
   CONTENT =  "

TABLES
*  LT_PCX_S1 =  "
*  LT_CONDITIONS =  "
*  LT_WHERECLAUS =  "

EXCEPTIONS
   LANGUAGE_ERROR = 1    NOTYPEATT_ERROR = 2    NOCUSTTYPE_ERROR = 3    GETTEXT_ERROR = 4    XSTRING2STRING_ERROR = 5    READ_ERROR = 6 

.

IMPORTING Parameters details for LXE_OBJ_TEXT_READ_GENERIC_RFC

OBJTYPE -

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

OBJNAME -

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

CUSTMNR -

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

LANG -

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

TEXTKEY -

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

EXPORTING Parameters details for LXE_OBJ_TEXT_READ_GENERIC_RFC

CONTENT -

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

TABLES Parameters details for LXE_OBJ_TEXT_READ_GENERIC_RFC

LT_PCX_S1 -

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

LT_CONDITIONS -

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

LT_WHERECLAUS -

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

EXCEPTIONS details

LANGUAGE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NOTYPEATT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NOCUSTTYPE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

GETTEXT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

XSTRING2STRING_ERROR -

Data type:
Optional: No
Call by Reference: Yes

READ_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for LXE_OBJ_TEXT_READ_GENERIC_RFC 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.

ABAP code using 7.40 inline data declarations to call FM LXE_OBJ_TEXT_READ_GENERIC_RFC

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