SAP LXE_OBJ_TEXT_PAIR_READ_BSP1 Function Module for LXE_OBJ_TEXT_PAIR_READ_BSP1

Search SAP Function Modules

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

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

Function LXE_OBJ_TEXT_PAIR_READ_BSP1 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_PAIR_READ_BSP1'"LXE_OBJ_TEXT_PAIR_READ_BSP1
  EXPORTING
   T_R3_LANG =  "Language Key
   S_R3_LANG =  "Language Key
   OBJNAME =  "Name of Translation Object
*  READ_ONLY = 'X' "Single-Character Flag

 IMPORTING
   PSTATUS =  "Process Status

TABLES
   LT_PCX_S1 =  "Text Pairs

.

IMPORTING Parameters details for LXE_OBJ_TEXT_PAIR_READ_BSP1

T_R3_LANG - Language Key

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

S_R3_LANG - Language Key

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

OBJNAME - Name of Translation Object

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

READ_ONLY - Single-Character Flag

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

EXPORTING Parameters details for LXE_OBJ_TEXT_PAIR_READ_BSP1

PSTATUS - Process Status

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

TABLES Parameters details for LXE_OBJ_TEXT_PAIR_READ_BSP1

LT_PCX_S1 - Text Pairs

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

Copy and paste ABAP code example for LXE_OBJ_TEXT_PAIR_READ_BSP1 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_PAIR_READ_BSP1

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