SAP DB_DROP_TRIG Function Module for Deletion of triggers

Search SAP Function Modules

DB_DROP_TRIG is a standard db drop trig SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Deletion of triggers 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 db drop trig FM, simply by entering the name DB_DROP_TRIG into the relevant SAP transaction such as SE37 or SE38.

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

Function DB_DROP_TRIG 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 'DB_DROP_TRIG'"Deletion of triggers
  EXPORTING
*  DBSYS = SY-DBSYS "DBS for which program is generated
*  EXEC = ' ' "X: Do not execute generated program
*  PRID = 0 "Row Index of Internal Tables
*  TABNAME =  "
*  TRIG_NAME =  "Name of table to be deleted
*  TRIG_NAME2 =  "Name of update trigger
*  TRIG_NAME3 =  "Name of update trigger
*  DB_CHECK_FLAG = ' ' "

 IMPORTING
   SUBRC =  "0: deleted; 4: table does not exist

TABLES
*  STATEMENTS =  "

EXCEPTIONS
   OP_FAILURE = 1    ILLEGAL_VALUE = 2    PROGRAM_NOT_GENERATED = 3 

.

IMPORTING Parameters details for DB_DROP_TRIG

DBSYS - DBS for which program is generated

Data type: SY-DBSYS
Default: SY-DBSYS
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXEC - X: Do not execute generated program

Data type: DDREFSTRUC-BOOL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PRID - Row Index of Internal Tables

Data type: SY-TABIX
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABNAME -

Data type: DD02L-TABNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRIG_NAME - Name of table to be deleted

Data type: TICNV-TRG_UPD1
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRIG_NAME2 - Name of update trigger

Data type: TICNV-TRG_UPD2
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRIG_NAME3 - Name of update trigger

Data type: TICNV-TRG_UPD3
Optional: Yes
Call by Reference: No ( called with pass by value option)

DB_CHECK_FLAG -

Data type: DDREFSTRUC-BOOL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for DB_DROP_TRIG

SUBRC - 0: deleted; 4: table does not exist

Data type: SY-SUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for DB_DROP_TRIG

STATEMENTS -

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

EXCEPTIONS details

OP_FAILURE -

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

ILLEGAL_VALUE -

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

PROGRAM_NOT_GENERATED -

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

Copy and paste ABAP code example for DB_DROP_TRIG 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.

ABAP code using 7.40 inline data declarations to call FM DB_DROP_TRIG

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