SAP LXE_COMMON_ST_DATA_SET Function Module for Save Data









LXE_COMMON_ST_DATA_SET is a standard lxe common st data set SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save Data 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 common st data set FM, simply by entering the name LXE_COMMON_ST_DATA_SET into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_COMMON_ST_DATA_SET 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_COMMON_ST_DATA_SET'"Save Data
  EXPORTING
*  PV_T_LANG =  "Translation Language
*  PV_S_LANG =  "Translation Language
*  PV_CUSTMNR =  "Translation Area
*  PV_OBJTYPE =  "Type of Translation Object
*  PV_OBJNAME =  "Name of Translation Object
*  PV_TEXTKEY =  "Text Key
*  PV_TITLE_CH =  "Predefined Type
.



IMPORTING Parameters details for LXE_COMMON_ST_DATA_SET

PV_T_LANG - Translation Language

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

PV_S_LANG - Translation Language

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

PV_CUSTMNR - Translation Area

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

PV_OBJTYPE - Type of Translation Object

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

PV_OBJNAME - Name of Translation Object

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

PV_TEXTKEY - Text Key

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

PV_TITLE_CH - Predefined Type

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

Copy and paste ABAP code example for LXE_COMMON_ST_DATA_SET 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_pv_t_lang  TYPE LXEISOLANG, "   
lv_pv_s_lang  TYPE LXEISOLANG, "   
lv_pv_custmnr  TYPE LXECUSTMNR, "   
lv_pv_objtype  TYPE LXEOBJTYPE, "   
lv_pv_objname  TYPE LXEOBJNAME, "   
lv_pv_textkey  TYPE LXETEXTKEY, "   
lv_pv_title_ch  TYPE STRING. "   

  CALL FUNCTION 'LXE_COMMON_ST_DATA_SET'  "Save Data
    EXPORTING
         PV_T_LANG = lv_pv_t_lang
         PV_S_LANG = lv_pv_s_lang
         PV_CUSTMNR = lv_pv_custmnr
         PV_OBJTYPE = lv_pv_objtype
         PV_OBJNAME = lv_pv_objname
         PV_TEXTKEY = lv_pv_textkey
         PV_TITLE_CH = lv_pv_title_ch
. " LXE_COMMON_ST_DATA_SET




ABAP code using 7.40 inline data declarations to call FM LXE_COMMON_ST_DATA_SET

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!