SAP IUUC_DELETE_ADBC_TRIGGER Function Module for delete trigger by means of ADBC









IUUC_DELETE_ADBC_TRIGGER is a standard iuuc delete adbc trigger 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 trigger by means of ADBC 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 iuuc delete adbc trigger FM, simply by entering the name IUUC_DELETE_ADBC_TRIGGER into the relevant SAP transaction such as SE37 or SE38.

Function Group: IUUC_ADBC
Program Name: SAPLIUUC_ADBC
Main Program: SAPLIUUC_ADBC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function IUUC_DELETE_ADBC_TRIGGER 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 'IUUC_DELETE_ADBC_TRIGGER'"delete trigger by means of ADBC
  EXPORTING
   I_TABNAME =  "Table Name
   I_SHADOWTAB =  "logging table name
*  I_CONNECTION_NAME = 'R/3*' "Logical name for a database connection
   I_PROCESS_OPTION =  "Numeric 1-character
*  I_POOL_HANDLING =  "boolean variable (X=true, -=false, space=unknown)
*  I_LOCK_TIMEOUT =  "lock timeout value for trigger creation (IBM DB)
*  I_DELETE_TEMP_TRIG =  "boolean variable (X=true, -=false, space=unknown)

 IMPORTING
   E_ERROR_MESSAGE =  "SQL Error Message
.



IMPORTING Parameters details for IUUC_DELETE_ADBC_TRIGGER

I_TABNAME - Table Name

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

I_SHADOWTAB - logging table name

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

I_CONNECTION_NAME - Logical name for a database connection

Data type: DBCON_NAME
Default: 'R/3*'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PROCESS_OPTION - Numeric 1-character

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

I_POOL_HANDLING - boolean variable (X=true, -=false, space=unknown)

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

I_LOCK_TIMEOUT - lock timeout value for trigger creation (IBM DB)

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

I_DELETE_TEMP_TRIG - boolean variable (X=true, -=false, space=unknown)

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

EXPORTING Parameters details for IUUC_DELETE_ADBC_TRIGGER

E_ERROR_MESSAGE - SQL Error Message

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

Copy and paste ABAP code example for IUUC_DELETE_ADBC_TRIGGER 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_i_tabname  TYPE TABNAME, "   
lv_e_error_message  TYPE DBSQLMSG, "   
lv_i_shadowtab  TYPE TABNAME, "   
lv_i_connection_name  TYPE DBCON_NAME, "   'R/3*'
lv_i_process_option  TYPE NUM1, "   
lv_i_pool_handling  TYPE BOOLEAN, "   
lv_i_lock_timeout  TYPE IUUC_LOCK_TIMEOUT_VALUE, "   
lv_i_delete_temp_trig  TYPE BOOLEAN. "   

  CALL FUNCTION 'IUUC_DELETE_ADBC_TRIGGER'  "delete trigger by means of ADBC
    EXPORTING
         I_TABNAME = lv_i_tabname
         I_SHADOWTAB = lv_i_shadowtab
         I_CONNECTION_NAME = lv_i_connection_name
         I_PROCESS_OPTION = lv_i_process_option
         I_POOL_HANDLING = lv_i_pool_handling
         I_LOCK_TIMEOUT = lv_i_lock_timeout
         I_DELETE_TEMP_TRIG = lv_i_delete_temp_trig
    IMPORTING
         E_ERROR_MESSAGE = lv_e_error_message
. " IUUC_DELETE_ADBC_TRIGGER




ABAP code using 7.40 inline data declarations to call FM IUUC_DELETE_ADBC_TRIGGER

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.

 
 
 
DATA(ld_i_connection_name) = 'R/3*'.
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!