SAP IUUC_GET_TRIGGER_COND_GEN_ACT Function Module for Get condition part of active trigger and/or generated trigger









IUUC_GET_TRIGGER_COND_GEN_ACT is a standard iuuc get trigger cond gen act SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get condition part of active trigger and/or generated trigger 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 get trigger cond gen act FM, simply by entering the name IUUC_GET_TRIGGER_COND_GEN_ACT into the relevant SAP transaction such as SE37 or SE38.

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



Function IUUC_GET_TRIGGER_COND_GEN_ACT 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_GET_TRIGGER_COND_GEN_ACT'"Get condition part of active trigger and/or generated trigger
EXPORTING
IV_TABNAME = "Generic data element for database table names
IV_LOGTAB_NAME = "Table Name
* IT_SPECIFIC_CONDITIONS = "Table Type for ABAP Programs
IV_DBCON_NAME = "Logical name for a database connection
* IV_SCHEMA = "Configuration Name
* IV_TABCLASS = "Table category
* IV_ADD_CLNT_CONDITION = ' ' "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
* IV_DB_OPERAT = ' ' "IUUC: Operation
* IV_ARCH_DELETE = ' ' "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

IMPORTING
EV_CODE_EXISTING = "
EV_CODE_GEN = "
ET_ERROR_MSG = "Table of strings
EV_SUBRC = "Return Value, Return Value After ABAP Statements
EV_IS_OLD_ORACLE_TRIGGERS = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
EV_CONDITIONS_ARE_EQUAL = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

EXCEPTIONS
NO_AUTHORIZATION = 1
.



IMPORTING Parameters details for IUUC_GET_TRIGGER_COND_GEN_ACT

IV_TABNAME - Generic data element for database table names

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

IV_LOGTAB_NAME - Table Name

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

IT_SPECIFIC_CONDITIONS - Table Type for ABAP Programs

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

IV_DBCON_NAME - Logical name for a database connection

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

IV_SCHEMA - Configuration Name

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

IV_TABCLASS - Table category

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

IV_ADD_CLNT_CONDITION - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

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

IV_DB_OPERAT - IUUC: Operation

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

IV_ARCH_DELETE - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

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

EXPORTING Parameters details for IUUC_GET_TRIGGER_COND_GEN_ACT

EV_CODE_EXISTING -

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

EV_CODE_GEN -

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

ET_ERROR_MSG - Table of strings

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

EV_SUBRC - Return Value, Return Value After ABAP Statements

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

EV_IS_OLD_ORACLE_TRIGGERS - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

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

EV_CONDITIONS_ARE_EQUAL - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

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

EXCEPTIONS details

NO_AUTHORIZATION - No authorization

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for IUUC_GET_TRIGGER_COND_GEN_ACT 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_iv_tabname  TYPE DMC_DB_TABNAME, "   
lv_ev_code_existing  TYPE STRING, "   
lv_no_authorization  TYPE STRING, "   
lv_ev_code_gen  TYPE STRING, "   
lv_iv_logtab_name  TYPE TABNAME, "   
lv_et_error_msg  TYPE IUUC_TT_STRING, "   
lv_it_specific_conditions  TYPE ABAPPROG, "   
lv_ev_subrc  TYPE SYSUBRC, "   
lv_iv_dbcon_name  TYPE DBCON_NAME, "   
lv_iv_schema  TYPE IUUC_IMDB_SCHEMA, "   
lv_ev_is_old_oracle_triggers  TYPE BOOLE_D, "   
lv_iv_tabclass  TYPE TABCLASS, "   
lv_ev_conditions_are_equal  TYPE BOOLE_D, "   
lv_iv_add_clnt_condition  TYPE BOOLE_D, "   ' '
lv_iv_db_operat  TYPE IUUC_OPERATION, "   ' '
lv_iv_arch_delete  TYPE BOOLE_D. "   ' '

  CALL FUNCTION 'IUUC_GET_TRIGGER_COND_GEN_ACT'  "Get condition part of active trigger and/or generated trigger
    EXPORTING
         IV_TABNAME = lv_iv_tabname
         IV_LOGTAB_NAME = lv_iv_logtab_name
         IT_SPECIFIC_CONDITIONS = lv_it_specific_conditions
         IV_DBCON_NAME = lv_iv_dbcon_name
         IV_SCHEMA = lv_iv_schema
         IV_TABCLASS = lv_iv_tabclass
         IV_ADD_CLNT_CONDITION = lv_iv_add_clnt_condition
         IV_DB_OPERAT = lv_iv_db_operat
         IV_ARCH_DELETE = lv_iv_arch_delete
    IMPORTING
         EV_CODE_EXISTING = lv_ev_code_existing
         EV_CODE_GEN = lv_ev_code_gen
         ET_ERROR_MSG = lv_et_error_msg
         EV_SUBRC = lv_ev_subrc
         EV_IS_OLD_ORACLE_TRIGGERS = lv_ev_is_old_oracle_triggers
         EV_CONDITIONS_ARE_EQUAL = lv_ev_conditions_are_equal
    EXCEPTIONS
        NO_AUTHORIZATION = 1
. " IUUC_GET_TRIGGER_COND_GEN_ACT




ABAP code using 7.40 inline data declarations to call FM IUUC_GET_TRIGGER_COND_GEN_ACT

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_iv_add_clnt_condition) = ' '.
 
DATA(ld_iv_db_operat) = ' '.
 
DATA(ld_iv_arch_delete) = ' '.
 


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!