SAP LXE_OBJ_REMO_EDIT Function Module for
LXE_OBJ_REMO_EDIT is a standard lxe obj remo edit 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 remo edit FM, simply by entering the name LXE_OBJ_REMO_EDIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: LXE_OBJ_REMO
Program Name: SAPLLXE_OBJ_REMO
Main Program: SAPLLXE_OBJ_REMO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LXE_OBJ_REMO_EDIT 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_REMO_EDIT'".
EXPORTING
CUSTMNR = "
OBJTYPE = "
OBJNAME = "
S_LANG = "
T_LANG = "
* SEQUENTIAL = '' "
* VWO = '' "
IMPORTING
PSTATUS = "
UCOMM = "
CHANGE_FLAG = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for LXE_OBJ_REMO_EDIT
CUSTMNR -
Data type: LXECUSTMNROptional: No
Call by Reference: Yes
OBJTYPE -
Data type: LXEOBJTYPEOptional: No
Call by Reference: Yes
OBJNAME -
Data type: LXEOBJNAMEOptional: No
Call by Reference: Yes
S_LANG -
Data type: LXEISOLANGOptional: No
Call by Reference: Yes
T_LANG -
Data type: LXEISOLANGOptional: No
Call by Reference: Yes
SEQUENTIAL -
Data type: CHAR1Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
VWO -
Data type: CHAR1Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for LXE_OBJ_REMO_EDIT
PSTATUS -
Data type: LXESTATPRCOptional: No
Call by Reference: Yes
UCOMM -
Data type: SYUCOMMOptional: No
Call by Reference: Yes
CHANGE_FLAG -
Data type: CHAR1Optional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LXE_OBJ_REMO_EDIT 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_error | TYPE STRING, " | |||
| lv_custmnr | TYPE LXECUSTMNR, " | |||
| lv_pstatus | TYPE LXESTATPRC, " | |||
| lv_ucomm | TYPE SYUCOMM, " | |||
| lv_objtype | TYPE LXEOBJTYPE, " | |||
| lv_objname | TYPE LXEOBJNAME, " | |||
| lv_change_flag | TYPE CHAR1, " | |||
| lv_s_lang | TYPE LXEISOLANG, " | |||
| lv_t_lang | TYPE LXEISOLANG, " | |||
| lv_sequential | TYPE CHAR1, " '' | |||
| lv_vwo | TYPE CHAR1. " '' |
|   CALL FUNCTION 'LXE_OBJ_REMO_EDIT' " |
| EXPORTING | ||
| CUSTMNR | = lv_custmnr | |
| OBJTYPE | = lv_objtype | |
| OBJNAME | = lv_objname | |
| S_LANG | = lv_s_lang | |
| T_LANG | = lv_t_lang | |
| SEQUENTIAL | = lv_sequential | |
| VWO | = lv_vwo | |
| IMPORTING | ||
| PSTATUS | = lv_pstatus | |
| UCOMM | = lv_ucomm | |
| CHANGE_FLAG | = lv_change_flag | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " LXE_OBJ_REMO_EDIT | ||
ABAP code using 7.40 inline data declarations to call FM LXE_OBJ_REMO_EDIT
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.| DATA(ld_sequential) | = ''. | |||
| DATA(ld_vwo) | = ''. | |||
Search for further information about these or an SAP related objects