SAP LXE_SE63_LEDIT_OBJECT_FORMAT Function Module for NOTRANSL: edit texts









LXE_SE63_LEDIT_OBJECT_FORMAT is a standard lxe se63 ledit object format SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: edit texts 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 se63 ledit object format FM, simply by entering the name LXE_SE63_LEDIT_OBJECT_FORMAT into the relevant SAP transaction such as SE37 or SE38.

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



Function LXE_SE63_LEDIT_OBJECT_FORMAT 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_SE63_LEDIT_OBJECT_FORMAT'"NOTRANSL: edit texts
EXPORTING
LXE_XL_EDITOR_SETTING = "
LXE_XL_OBJECT = "
.



IMPORTING Parameters details for LXE_SE63_LEDIT_OBJECT_FORMAT

LXE_XL_EDITOR_SETTING -

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

LXE_XL_OBJECT -

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

Copy and paste ABAP code example for LXE_SE63_LEDIT_OBJECT_FORMAT 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_lxe_xl_editor_setting  TYPE LXELG_EDITOR_SETTING, "   
lv_lxe_xl_object  TYPE LXELG_TEXT_OBJECT. "   

  CALL FUNCTION 'LXE_SE63_LEDIT_OBJECT_FORMAT'  "NOTRANSL: edit texts
    EXPORTING
         LXE_XL_EDITOR_SETTING = lv_lxe_xl_editor_setting
         LXE_XL_OBJECT = lv_lxe_xl_object
. " LXE_SE63_LEDIT_OBJECT_FORMAT




ABAP code using 7.40 inline data declarations to call FM LXE_SE63_LEDIT_OBJECT_FORMAT

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!