SAP EDITOR_TABLE_WITH_STATUS Function Module for
EDITOR_TABLE_WITH_STATUS is a standard editor table with status 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 editor table with status FM, simply by entering the name EDITOR_TABLE_WITH_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: S38E
Program Name: SAPLS38E
Main Program: SAPLS38E
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EDITOR_TABLE_WITH_STATUS 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 'EDITOR_TABLE_WITH_STATUS'".
EXPORTING
* DISPLAY = ' ' "EDIC: Display only, no editing
* NAME = ' ' "
* PROGRAM = ' ' "ABAP Program Name
* CALLBACK_USERCOM = ' ' "Name of a module integrated into navigation
* CALLBACK_SET_PFKEY = ' ' "Name of a module integrated into navigation
* TITLE_TEXT = ' ' "Single-Character Flag
IMPORTING
CHANGED = "EDIC: Editor contents was changed
SUBRC = "Return Value, Return Value After ABAP Statements
TABLES
CONTENT = "Source Code
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLS38E_001 Exit for ABAP Editor
IMPORTING Parameters details for EDITOR_TABLE_WITH_STATUS
DISPLAY - EDIC: Display only, no editing
Data type: S38E-APP_DISPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NAME -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PROGRAM - ABAP Program Name
Data type: TRDIR-NAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CALLBACK_USERCOM - Name of a module integrated into navigation
Data type: RSTXP-TDOBJECTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CALLBACK_SET_PFKEY - Name of a module integrated into navigation
Data type: RSTXP-TDOBJECTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TITLE_TEXT - Single-Character Flag
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EDITOR_TABLE_WITH_STATUS
CHANGED - EDIC: Editor contents was changed
Data type: S38E-BUF_VARIEDOptional: No
Call by Reference: Yes
SUBRC - Return Value, Return Value After ABAP Statements
Data type: SY-SUBRCOptional: No
Call by Reference: Yes
TABLES Parameters details for EDITOR_TABLE_WITH_STATUS
CONTENT - Source Code
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EDITOR_TABLE_WITH_STATUS 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_changed | TYPE S38E-BUF_VARIED, " | |||
| lt_content | TYPE STANDARD TABLE OF S38E, " | |||
| lv_display | TYPE S38E-APP_DISP, " SPACE | |||
| lv_name | TYPE S38E, " SPACE | |||
| lv_subrc | TYPE SY-SUBRC, " | |||
| lv_program | TYPE TRDIR-NAME, " SPACE | |||
| lv_callback_usercom | TYPE RSTXP-TDOBJECT, " SPACE | |||
| lv_callback_set_pfkey | TYPE RSTXP-TDOBJECT, " SPACE | |||
| lv_title_text | TYPE RSTXP. " SPACE |
|   CALL FUNCTION 'EDITOR_TABLE_WITH_STATUS' " |
| EXPORTING | ||
| DISPLAY | = lv_display | |
| NAME | = lv_name | |
| PROGRAM | = lv_program | |
| CALLBACK_USERCOM | = lv_callback_usercom | |
| CALLBACK_SET_PFKEY | = lv_callback_set_pfkey | |
| TITLE_TEXT | = lv_title_text | |
| IMPORTING | ||
| CHANGED | = lv_changed | |
| SUBRC | = lv_subrc | |
| TABLES | ||
| CONTENT | = lt_content | |
| . " EDITOR_TABLE_WITH_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM EDITOR_TABLE_WITH_STATUS
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.| "SELECT single BUF_VARIED FROM S38E INTO @DATA(ld_changed). | ||||
| "SELECT single APP_DISP FROM S38E INTO @DATA(ld_display). | ||||
| DATA(ld_display) | = ' '. | |||
| DATA(ld_name) | = ' '. | |||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_subrc). | ||||
| "SELECT single NAME FROM TRDIR INTO @DATA(ld_program). | ||||
| DATA(ld_program) | = ' '. | |||
| "SELECT single TDOBJECT FROM RSTXP INTO @DATA(ld_callback_usercom). | ||||
| DATA(ld_callback_usercom) | = ' '. | |||
| "SELECT single TDOBJECT FROM RSTXP INTO @DATA(ld_callback_set_pfkey). | ||||
| DATA(ld_callback_set_pfkey) | = ' '. | |||
| DATA(ld_title_text) | = ' '. | |||
Search for further information about these or an SAP related objects