SAP ISU_S_EDMIDE_GRID_DELETE Function Module for Delete Grid
ISU_S_EDMIDE_GRID_DELETE is a standard isu s edmide grid delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete Grid 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 isu s edmide grid delete FM, simply by entering the name ISU_S_EDMIDE_GRID_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EEDMIDE_GRID_MAINT
Program Name: SAPLEEDMIDE_GRID_MAINT
Main Program: SAPLEEDMIDE_GRID_MAINT
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_S_EDMIDE_GRID_DELETE 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 'ISU_S_EDMIDE_GRID_DELETE'"Delete Grid.
EXPORTING
X_GRID = "Grid
* X_UPD_ONLINE = "Update online
* X_OBJ = "
* X_NO_OTHER = "No other Object Permitted
* X_NO_CHANGE = "No Changes Allowed
* X_NO_DIALOG = "Suppress maintenance screens
IMPORTING
Y_DB_UPDATE = "Database Updated (X) or not (' ')
Y_EXIT_TYPE = "Function with which editing was exited
EXCEPTIONS
NOT_FOUND = 1 FOREIGN_LOCK = 2 SYSTEM_ERROR = 3 CANCELLED = 4 NOT_AUTHORIZED = 5 INPUT_ERROR = 6
IMPORTING Parameters details for ISU_S_EDMIDE_GRID_DELETE
X_GRID - Grid
Data type: GRID_IDOptional: No
Call by Reference: Yes
X_UPD_ONLINE - Update online
Data type: REGEN-UPD_ONLINEOptional: Yes
Call by Reference: Yes
X_OBJ -
Data type: EEDMIDEGRID_OBJOptional: Yes
Call by Reference: Yes
X_NO_OTHER - No other Object Permitted
Data type: REGEN-NO_OTHEROptional: Yes
Call by Reference: Yes
X_NO_CHANGE - No Changes Allowed
Data type: REGEN-NO_CHANGEOptional: Yes
Call by Reference: Yes
X_NO_DIALOG - Suppress maintenance screens
Data type: REGEN-NO_DIALOGOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISU_S_EDMIDE_GRID_DELETE
Y_DB_UPDATE - Database Updated (X) or not (SPACE)
Data type: REGEN-DB_UPDATEOptional: No
Call by Reference: Yes
Y_EXIT_TYPE - Function with which editing was exited
Data type: REGEN-EXIT_TYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FOREIGN_LOCK -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANCELLED -
Data type:Optional: No
Call by Reference: Yes
NOT_AUTHORIZED - No Authorization
Data type:Optional: No
Call by Reference: Yes
INPUT_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_S_EDMIDE_GRID_DELETE 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_x_grid | TYPE GRID_ID, " | |||
| lv_not_found | TYPE GRID_ID, " | |||
| lv_y_db_update | TYPE REGEN-DB_UPDATE, " | |||
| lv_y_exit_type | TYPE REGEN-EXIT_TYPE, " | |||
| lv_foreign_lock | TYPE REGEN, " | |||
| lv_x_upd_online | TYPE REGEN-UPD_ONLINE, " | |||
| lv_x_obj | TYPE EEDMIDEGRID_OBJ, " | |||
| lv_system_error | TYPE EEDMIDEGRID_OBJ, " | |||
| lv_cancelled | TYPE EEDMIDEGRID_OBJ, " | |||
| lv_x_no_other | TYPE REGEN-NO_OTHER, " | |||
| lv_x_no_change | TYPE REGEN-NO_CHANGE, " | |||
| lv_not_authorized | TYPE REGEN, " | |||
| lv_input_error | TYPE REGEN, " | |||
| lv_x_no_dialog | TYPE REGEN-NO_DIALOG. " |
|   CALL FUNCTION 'ISU_S_EDMIDE_GRID_DELETE' "Delete Grid |
| EXPORTING | ||
| X_GRID | = lv_x_grid | |
| X_UPD_ONLINE | = lv_x_upd_online | |
| X_OBJ | = lv_x_obj | |
| X_NO_OTHER | = lv_x_no_other | |
| X_NO_CHANGE | = lv_x_no_change | |
| X_NO_DIALOG | = lv_x_no_dialog | |
| IMPORTING | ||
| Y_DB_UPDATE | = lv_y_db_update | |
| Y_EXIT_TYPE | = lv_y_exit_type | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| FOREIGN_LOCK = 2 | ||
| SYSTEM_ERROR = 3 | ||
| CANCELLED = 4 | ||
| NOT_AUTHORIZED = 5 | ||
| INPUT_ERROR = 6 | ||
| . " ISU_S_EDMIDE_GRID_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM ISU_S_EDMIDE_GRID_DELETE
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 DB_UPDATE FROM REGEN INTO @DATA(ld_y_db_update). | ||||
| "SELECT single EXIT_TYPE FROM REGEN INTO @DATA(ld_y_exit_type). | ||||
| "SELECT single UPD_ONLINE FROM REGEN INTO @DATA(ld_x_upd_online). | ||||
| "SELECT single NO_OTHER FROM REGEN INTO @DATA(ld_x_no_other). | ||||
| "SELECT single NO_CHANGE FROM REGEN INTO @DATA(ld_x_no_change). | ||||
| "SELECT single NO_DIALOG FROM REGEN INTO @DATA(ld_x_no_dialog). | ||||
Search for further information about these or an SAP related objects