SAP DD_DROP_INDEX Function Module for
DD_DROP_INDEX is a standard dd drop index 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 dd drop index FM, simply by entering the name DD_DROP_INDEX into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDB2
Program Name: SAPLSDB2
Main Program: SAPLSDB2
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function DD_DROP_INDEX 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 'DD_DROP_INDEX'".
EXPORTING
* DBSYS = SY-DBSYS "DBS for which program is generated
* NO_EXEC = ' ' "X: Do not execute generated program
* PRID = 0 "Log ID
* PROGNAME = ' ' "Name of generated program
TABNAME = "Name of table to be deleted
* DB_CHECK_FLAG = 'X' "Execute checks against DB
INDEXNAME = "Index ID of up to three positions
IMPORTING
GENPROG = "Real name of the generated program
SUBRC = "0: deleted; 4: index does not exist
EXCEPTIONS
INDEX_NOT_DROPPED = 1 PROGRAM_NOT_GENERATED = 2 PROGRAM_NOT_WRITTEN = 3
IMPORTING Parameters details for DD_DROP_INDEX
DBSYS - DBS for which program is generated
Data type: SY-DBSYSDefault: SY-DBSYS
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_EXEC - X: Do not execute generated program
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PRID - Log ID
Data type: SY-TABIXOptional: Yes
Call by Reference: No ( called with pass by value option)
PROGNAME - Name of generated program
Data type: TRDIR-NAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABNAME - Name of table to be deleted
Data type: DD12L-SQLTABOptional: No
Call by Reference: No ( called with pass by value option)
DB_CHECK_FLAG - Execute checks against DB
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
INDEXNAME - Index ID of up to three positions
Data type: DD12L-INDEXNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DD_DROP_INDEX
GENPROG - Real name of the generated program
Data type: TRDIR-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
SUBRC - 0: deleted; 4: index does not exist
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INDEX_NOT_DROPPED - Error deleting the index
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROGRAM_NOT_GENERATED - Program could not be generated
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROGRAM_NOT_WRITTEN - Program could not be written
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DD_DROP_INDEX 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_dbsys | TYPE SY-DBSYS, " SY-DBSYS | |||
| lv_genprog | TYPE TRDIR-NAME, " | |||
| lv_index_not_dropped | TYPE TRDIR, " | |||
| lv_subrc | TYPE SY-SUBRC, " | |||
| lv_no_exec | TYPE SY, " SPACE | |||
| lv_program_not_generated | TYPE SY, " | |||
| lv_prid | TYPE SY-TABIX, " 0 | |||
| lv_program_not_written | TYPE SY, " | |||
| lv_progname | TYPE TRDIR-NAME, " SPACE | |||
| lv_tabname | TYPE DD12L-SQLTAB, " | |||
| lv_db_check_flag | TYPE DD12L, " 'X' | |||
| lv_indexname | TYPE DD12L-INDEXNAME. " |
| CALL FUNCTION 'DD_DROP_INDEX' " |
| EXPORTING | ||
| DBSYS | = lv_dbsys | |
| NO_EXEC | = lv_no_exec | |
| PRID | = lv_prid | |
| PROGNAME | = lv_progname | |
| TABNAME | = lv_tabname | |
| DB_CHECK_FLAG | = lv_db_check_flag | |
| INDEXNAME | = lv_indexname | |
| IMPORTING | ||
| GENPROG | = lv_genprog | |
| SUBRC | = lv_subrc | |
| EXCEPTIONS | ||
| INDEX_NOT_DROPPED = 1 | ||
| PROGRAM_NOT_GENERATED = 2 | ||
| PROGRAM_NOT_WRITTEN = 3 | ||
| . " DD_DROP_INDEX | ||
ABAP code using 7.40 inline data declarations to call FM DD_DROP_INDEX
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 DBSYS FROM SY INTO @DATA(ld_dbsys). | ||||
| DATA(ld_dbsys) | = SY-DBSYS. | |||
| "SELECT single NAME FROM TRDIR INTO @DATA(ld_genprog). | ||||
| "SELECT single SUBRC FROM SY INTO @DATA(ld_subrc). | ||||
| DATA(ld_no_exec) | = ' '. | |||
| "SELECT single TABIX FROM SY INTO @DATA(ld_prid). | ||||
| "SELECT single NAME FROM TRDIR INTO @DATA(ld_progname). | ||||
| DATA(ld_progname) | = ' '. | |||
| "SELECT single SQLTAB FROM DD12L INTO @DATA(ld_tabname). | ||||
| DATA(ld_db_check_flag) | = 'X'. | |||
| "SELECT single INDEXNAME FROM DD12L INTO @DATA(ld_indexname). | ||||
Search for further information about these or an SAP related objects