FDM_COLL_GET_TRIGGER SAP Function module

FDM_COLL_GET_TRIGGER is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FDM_COLL_GET_TRIGGER into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FDM_AR_CUST_SERVICES
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FDM_COLL_GET_TRIGGER - FDM COLL GET TRIGGER

CALL FUNCTION 'FDM_COLL_GET_TRIGGER' "
  EXPORTING
    i_application =             " fdm_coll_appl
    i_origin =                  " fdm_coll_origin
    i_tablename =               " tabname16
*   i_log_if_not_found = ' '    " xfeld
  IMPORTING
    et_trigger =                " fdm_t_coll_strig
    e_xupdate_always =          " fdm_coll_xupdate_always
    e_xupdate_never =           " fdm_coll_xupdate_never
    e_xnew =                    " fdm_coll_xnew
  EXCEPTIONS
    NOT_FOUND = 1               "
    .  "  FDM_COLL_GET_TRIGGER

ABAP code example for Function Module FDM_COLL_GET_TRIGGER

The ABAP code below is a full code listing to execute function module FDM_COLL_GET_TRIGGER including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_et_trigger  
 
 TYPE FDM_T_COLL_STRIG
,
ld_e_xupdate_always  
 
 TYPE FDM_COLL_XUPDATE_ALWAYS
,
ld_e_xupdate_never  
 
 TYPE FDM_COLL_XUPDATE_NEVER
,
ld_e_xnew  
 
 TYPE FDM_COLL_XNEW
.


DATA(ld_i_application) = 'Check type of data required'.

DATA(ld_i_origin) = 'Check type of data required'.

DATA(ld_i_tablename) = 'Check type of data required'.

DATA(ld_i_log_if_not_found) = 'Check type of data required'.
.

CALL FUNCTION 'FDM_COLL_GET_TRIGGER'
  EXPORTING
    i_application =              ld_i_application
    i_origin =                   ld_i_origin
    i_tablename =                ld_i_tablename
*   i_log_if_not_found =         ld_i_log_if_not_found
  IMPORTING
    et_trigger =                 ld_et_trigger
    e_xupdate_always =           ld_e_xupdate_always
    e_xupdate_never =            ld_e_xupdate_never
    e_xnew =                     ld_e_xnew
  EXCEPTIONS
    NOT_FOUND =                  1
    .  "  FDM_COLL_GET_TRIGGER

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_et_trigger
 
 TYPE FDM_T_COLL_STRIG ,
ld_i_application
 
 TYPE FDM_COLL_APPL ,
ld_e_xupdate_always
 
 TYPE FDM_COLL_XUPDATE_ALWAYS ,
ld_i_origin
 
 TYPE FDM_COLL_ORIGIN ,
ld_e_xupdate_never
 
 TYPE FDM_COLL_XUPDATE_NEVER ,
ld_i_tablename
 
 TYPE TABNAME16 ,
ld_e_xnew
 
 TYPE FDM_COLL_XNEW ,
ld_i_log_if_not_found
 
 TYPE XFELD .


ld_i_application = 'Check type of data required'.
ld_i_origin = 'Check type of data required'.
ld_i_tablename = 'Check type of data required'.
ld_i_log_if_not_found = 'Check type of data required'.