FTR_ALERT_READ_CUSTOMIZING SAP Function module - ###Read Customizing for Alert

FTR_ALERT_READ_CUSTOMIZING 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 FTR_ALERT_READ_CUSTOMIZING into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM FTR_ALERT_READ_CUSTOMIZING - FTR ALERT READ CUSTOMIZING

CALL FUNCTION 'FTR_ALERT_READ_CUSTOMIZING' "###Read Customizing for Alert
  EXPORTING
    i_bukrs =                   " bukrs         Company Code
*   i_sgsart =                  " vvsart        Product Type
*   i_sfhaart =                 " tb_sfhaart    Financial Transaction Type
*   i_sfgzustt =                " tb_sfgzuty    Transaction Activity Category
*   i_secac =                   " rldepo        Depot
  IMPORTING
    e_alrt_cat =                " salrtdcat     Alert Category
  EXCEPTIONS
    NO_ALRT_ASSGN = 1           "               ###No alert assignment in customizing
    .  "  FTR_ALERT_READ_CUSTOMIZING

ABAP code example for Function Module FTR_ALERT_READ_CUSTOMIZING

The ABAP code below is a full code listing to execute function module FTR_ALERT_READ_CUSTOMIZING 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_e_alrt_cat  
 
 TYPE SALRTDCAT
.


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

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

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

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

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

CALL FUNCTION 'FTR_ALERT_READ_CUSTOMIZING'
  EXPORTING
    i_bukrs =                    ld_i_bukrs
*   i_sgsart =                   ld_i_sgsart
*   i_sfhaart =                  ld_i_sfhaart
*   i_sfgzustt =                 ld_i_sfgzustt
*   i_secac =                    ld_i_secac
  IMPORTING
    e_alrt_cat =                 ld_e_alrt_cat
  EXCEPTIONS
    NO_ALRT_ASSGN =              1
    .  "  FTR_ALERT_READ_CUSTOMIZING

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_e_alrt_cat
 
 TYPE SALRTDCAT ,
ld_i_bukrs
 
 TYPE BUKRS ,
ld_i_sgsart
 
 TYPE VVSART ,
ld_i_sfhaart
 
 TYPE TB_SFHAART ,
ld_i_sfgzustt
 
 TYPE TB_SFGZUTY ,
ld_i_secac
 
 TYPE RLDEPO .


ld_i_bukrs = 'Check type of data required'.
ld_i_sgsart = 'Check type of data required'.
ld_i_sfhaart = 'Check type of data required'.
ld_i_sfgzustt = 'Check type of data required'.
ld_i_secac = 'Check type of data required'.