SAP ISU_DB_EDM_TRIGGER_CHECK Function Module for









ISU_DB_EDM_TRIGGER_CHECK is a standard isu db edm trigger check 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 isu db edm trigger check FM, simply by entering the name ISU_DB_EDM_TRIGGER_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_DB_EDM_TRIGGER_CHECK 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 'ISU_DB_EDM_TRIGGER_CHECK'"
EXPORTING
X_PROFILENR = "
X_FROM = "
X_TO = "
* X_ONLY_INPUT_TRIGGER = "
* X_ONLY_OUTPUT_TRIGGER = CO_FLAG_MARKED "

IMPORTING
Y_TRIGGER_EXIST = "
.



IMPORTING Parameters details for ISU_DB_EDM_TRIGGER_CHECK

X_PROFILENR -

Data type: E_PROFILE
Optional: No
Call by Reference: Yes

X_FROM -

Data type: EEDMDATEFROM
Optional: No
Call by Reference: Yes

X_TO -

Data type: EEDMDATETO
Optional: No
Call by Reference: Yes

X_ONLY_INPUT_TRIGGER -

Data type: KENNZX
Optional: Yes
Call by Reference: Yes

X_ONLY_OUTPUT_TRIGGER -

Data type: KENNZX
Default: CO_FLAG_MARKED
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISU_DB_EDM_TRIGGER_CHECK

Y_TRIGGER_EXIST -

Data type: KENNZX
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_DB_EDM_TRIGGER_CHECK 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_x_profilenr  TYPE E_PROFILE, "   
lv_y_trigger_exist  TYPE KENNZX, "   
lv_x_from  TYPE EEDMDATEFROM, "   
lv_x_to  TYPE EEDMDATETO, "   
lv_x_only_input_trigger  TYPE KENNZX, "   
lv_x_only_output_trigger  TYPE KENNZX. "   CO_FLAG_MARKED

  CALL FUNCTION 'ISU_DB_EDM_TRIGGER_CHECK'  "
    EXPORTING
         X_PROFILENR = lv_x_profilenr
         X_FROM = lv_x_from
         X_TO = lv_x_to
         X_ONLY_INPUT_TRIGGER = lv_x_only_input_trigger
         X_ONLY_OUTPUT_TRIGGER = lv_x_only_output_trigger
    IMPORTING
         Y_TRIGGER_EXIST = lv_y_trigger_exist
. " ISU_DB_EDM_TRIGGER_CHECK




ABAP code using 7.40 inline data declarations to call FM ISU_DB_EDM_TRIGGER_CHECK

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_x_only_output_trigger) = CO_FLAG_MARKED.
 


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!