DBA_ALERT_GENERIC_RFC_WRAPPER SAP Function module - DBA: Generic EFWK Wrapper for Database Alert Metrics

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

Associated Function Group: SDBA_SOLMAN
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM DBA_ALERT_GENERIC_RFC_WRAPPER - DBA ALERT GENERIC RFC WRAPPER

CALL FUNCTION 'DBA_ALERT_GENERIC_RFC_WRAPPER' "DBA: Generic EFWK Wrapper for Database Alert Metrics
  EXPORTING
    dbcname =                   " dbcon_name    Logical name for a database connection
*   bypass_dispatching = ABAP_FALSE  " char1    Bypass dispatching to correct AS for DB type
    i_selopt_para =             " dba_alert_rdi_query_tab  DBA-RDI: Generic Alert Query for RDI
  IMPORTING
    metrics =                   " dba_alert_metrics  DBA: Database Alert Metrics
    return_status =             " dba_dbh_return_status  DBA-DBH: Return Status (RC and Message)
    .  "  DBA_ALERT_GENERIC_RFC_WRAPPER

ABAP code example for Function Module DBA_ALERT_GENERIC_RFC_WRAPPER

The ABAP code below is a full code listing to execute function module DBA_ALERT_GENERIC_RFC_WRAPPER 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_metrics  
 
 TYPE DBA_ALERT_METRICS
,
ld_return_status  
 
 TYPE DBA_DBH_RETURN_STATUS
.


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

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

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

CALL FUNCTION 'DBA_ALERT_GENERIC_RFC_WRAPPER'
  EXPORTING
    dbcname =                    ld_dbcname
*   bypass_dispatching =         ld_bypass_dispatching
    i_selopt_para =              ld_i_selopt_para
  IMPORTING
    metrics =                    ld_metrics
    return_status =              ld_return_status
    .  "  DBA_ALERT_GENERIC_RFC_WRAPPER

IF SY-SUBRC EQ 0.
  "All OK
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_metrics
 
 TYPE DBA_ALERT_METRICS ,
ld_dbcname
 
 TYPE DBCON_NAME ,
ld_return_status
 
 TYPE DBA_DBH_RETURN_STATUS ,
ld_bypass_dispatching
 
 TYPE CHAR1 ,
ld_i_selopt_para
 
 TYPE DBA_ALERT_RDI_QUERY_TAB .


ld_dbcname = 'Check type of data required'.
ld_bypass_dispatching = 'Check type of data required'.
ld_i_selopt_para = 'Check type of data required'.