__SAUCV_RUN_AND_DISPLAY SAP Function module - INTERNAL: Implemenation of launch and display / IDE Adapter

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

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

Pattern for FM __SAUCV_RUN_AND_DISPLAY - SAUCV RUN AND DISPLAY

CALL FUNCTION '__SAUCV_RUN_AND_DISPLAY' "INTERNAL: Implemenation of launch and display / IDE Adapter
  EXPORTING
    tadir_keys =                " sabp_t_tadir_keys  Tadir keys (R3TR)
    with_coverage =             " abap_bool     Execute with coverage
    limit_on_duration_category =   " saunit_d_allowed_rt_duration  Upper limit of runtime category
    limit_on_risk_level =       " saunit_d_allowed_risk_level  Upper limit of risk level
    warn_skipped_tests = ABAP_TRUE  " abap_bool
    .  "  __SAUCV_RUN_AND_DISPLAY

ABAP code example for Function Module __SAUCV_RUN_AND_DISPLAY

The ABAP code below is a full code listing to execute function module __SAUCV_RUN_AND_DISPLAY 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_tadir_keys) = 'Check type of data required'.

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

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

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

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

CALL FUNCTION '__SAUCV_RUN_AND_DISPLAY'
  EXPORTING
    tadir_keys =                 ld_tadir_keys
    with_coverage =              ld_with_coverage
    limit_on_duration_category =    ld_limit_on_duration_category
    limit_on_risk_level =        ld_limit_on_risk_level
    warn_skipped_tests =         ld_warn_skipped_tests
    .  "  __SAUCV_RUN_AND_DISPLAY

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_tadir_keys
 
 TYPE SABP_T_TADIR_KEYS ,
ld_with_coverage
 
 TYPE ABAP_BOOL ,
ld_limit_on_duration_category
 
 TYPE SAUNIT_D_ALLOWED_RT_DURATION ,
ld_limit_on_risk_level
 
 TYPE SAUNIT_D_ALLOWED_RISK_LEVEL ,
ld_warn_skipped_tests
 
 TYPE ABAP_BOOL .


ld_tadir_keys = 'Check type of data required'.
ld_with_coverage = 'Check type of data required'.
ld_limit_on_duration_category = 'Check type of data required'.
ld_limit_on_risk_level = 'Check type of data required'.
ld_warn_skipped_tests = 'Check type of data required'.