SAP DB_GET_TRIGGERS Function Module for
DB_GET_TRIGGERS is a standard db get triggers 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 db get triggers FM, simply by entering the name DB_GET_TRIGGERS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDB1
Program Name: SAPLSDB1
Main Program: SAPLSDB1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DB_GET_TRIGGERS 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_GET_TRIGGERS'".
EXPORTING
* TABNAME = ' ' "
IMPORTING
SUBRC = "
TABLES
* TRIGGERS = "
IMPORTING Parameters details for DB_GET_TRIGGERS
TABNAME -
Data type: DD02L-TABNAMEDefault: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DB_GET_TRIGGERS
SUBRC -
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DB_GET_TRIGGERS
TRIGGERS -
Data type: DBOBJECTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for DB_GET_TRIGGERS 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_subrc | TYPE SY-SUBRC, " | |||
| lv_tabname | TYPE DD02L-TABNAME, " SPACE | |||
| lt_triggers | TYPE STANDARD TABLE OF DBOBJECT. " |
|   CALL FUNCTION 'DB_GET_TRIGGERS' " |
| EXPORTING | ||
| TABNAME | = lv_tabname | |
| IMPORTING | ||
| SUBRC | = lv_subrc | |
| TABLES | ||
| TRIGGERS | = lt_triggers | |
| . " DB_GET_TRIGGERS | ||
ABAP code using 7.40 inline data declarations to call FM DB_GET_TRIGGERS
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 SUBRC FROM SY INTO @DATA(ld_subrc). | ||||
| "SELECT single TABNAME FROM DD02L INTO @DATA(ld_tabname). | ||||
| DATA(ld_tabname) | = ' '. | |||
Search for further information about these or an SAP related objects