SAP IUUC_GET_TRIGGER_STATEMENT Function Module for retrieve the sql trigger statement from remote system









IUUC_GET_TRIGGER_STATEMENT is a standard iuuc get trigger statement SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for retrieve the sql trigger statement from remote system 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 statement FM, simply by entering the name IUUC_GET_TRIGGER_STATEMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function IUUC_GET_TRIGGER_STATEMENT 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_STATEMENT'"retrieve the sql trigger statement from remote system
EXPORTING
IV_TABLENAME = "Table Name

IMPORTING
ET_STATEMENTS = "Table Type for ABAP Programs
EV_ERROR_MESSAGE = "

EXCEPTIONS
NO_AUTHORIZATION = 1
.



IMPORTING Parameters details for IUUC_GET_TRIGGER_STATEMENT

IV_TABLENAME - Table Name

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

EXPORTING Parameters details for IUUC_GET_TRIGGER_STATEMENT

ET_STATEMENTS - Table Type for ABAP Programs

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

EV_ERROR_MESSAGE -

Data type: STRING
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_STATEMENT 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_tablename  TYPE DMC_DB_TABNAME, "   
lv_et_statements  TYPE ABAPPROG, "   
lv_no_authorization  TYPE ABAPPROG, "   
lv_ev_error_message  TYPE STRING. "   

  CALL FUNCTION 'IUUC_GET_TRIGGER_STATEMENT'  "retrieve the sql trigger statement from remote system
    EXPORTING
         IV_TABLENAME = lv_iv_tablename
    IMPORTING
         ET_STATEMENTS = lv_et_statements
         EV_ERROR_MESSAGE = lv_ev_error_message
    EXCEPTIONS
        NO_AUTHORIZATION = 1
. " IUUC_GET_TRIGGER_STATEMENT




ABAP code using 7.40 inline data declarations to call FM IUUC_GET_TRIGGER_STATEMENT

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



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!