SAP Function Modules

TBAV_PROTOCOL_DISPLAY SAP Function module - Display Result Log







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

Associated Function Group: TBAV
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM TBAV_PROTOCOL_DISPLAY - TBAV PROTOCOL DISPLAY





CALL FUNCTION 'TBAV_PROTOCOL_DISPLAY' "Display Result Log
  EXPORTING
*   im_testrun = 'X'            " tb_stest      Test Run Indicator
*   im_mode = 1                 " i             Mode: 1= Fill Rates, 2= Delete Rates
    im_tab_messages =           " ftr_tab_avg_prot  Table with Messages
*   im_flg_only_errors = SPACE  " xfeld         Flag: Log Errors Only
  EXCEPTIONS
    INVALID = 1                 "               Error Occurred
    .  "  TBAV_PROTOCOL_DISPLAY

ABAP code example for Function Module TBAV_PROTOCOL_DISPLAY





The ABAP code below is a full code listing to execute function module TBAV_PROTOCOL_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_im_testrun) = 'Check type of data required'.
DATA(ld_im_mode) = 'Check type of data required'.
DATA(ld_im_tab_messages) = 'Check type of data required'.
DATA(ld_im_flg_only_errors) = 'Check type of data required'. . CALL FUNCTION 'TBAV_PROTOCOL_DISPLAY' EXPORTING * im_testrun = ld_im_testrun * im_mode = ld_im_mode im_tab_messages = ld_im_tab_messages * im_flg_only_errors = ld_im_flg_only_errors EXCEPTIONS INVALID = 1 . " TBAV_PROTOCOL_DISPLAY
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_im_testrun  TYPE TB_STEST ,
ld_im_mode  TYPE I ,
ld_im_tab_messages  TYPE FTR_TAB_AVG_PROT ,
ld_im_flg_only_errors  TYPE XFELD .

ld_im_testrun = 'Check type of data required'.
ld_im_mode = 'Check type of data required'.
ld_im_tab_messages = 'Check type of data required'.
ld_im_flg_only_errors = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name TBAV_PROTOCOL_DISPLAY or its description.