SAP Function Modules

MESSAGES_TRACE SAP Function module







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

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


Pattern for FM MESSAGES_TRACE - MESSAGES TRACE





CALL FUNCTION 'MESSAGES_TRACE' "
* EXPORTING
*   id_key =                    " sydbcnt       DB operations, number of table lines processed
*   ib_activate =               " boole_d
*   ib_destroy =                " boole_d
*   ib_reset =                  " boole_d
  IMPORTING
    ed_key =                    " sydbcnt
    ed_msgty_max =              " symsgty
    ed_msg_count =              " sydbcnt
  EXCEPTIONS
    KEY_EMPTY = 1               "
    KEY_NOT_FOUND = 2           "
    KEY_FILLED_DURING_ACTIVATION = 3  "
    .  "  MESSAGES_TRACE

ABAP code example for Function Module MESSAGES_TRACE





The ABAP code below is a full code listing to execute function module MESSAGES_TRACE 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_ed_key  TYPE SYDBCNT ,
ld_ed_msgty_max  TYPE SYMSGTY ,
ld_ed_msg_count  TYPE SYDBCNT .

DATA(ld_id_key) = '123 '.
DATA(ld_ib_activate) = '123 '.
DATA(ld_ib_destroy) = '123 '.
DATA(ld_ib_reset) = '123 '. . CALL FUNCTION 'MESSAGES_TRACE' * EXPORTING * id_key = ld_id_key * ib_activate = ld_ib_activate * ib_destroy = ld_ib_destroy * ib_reset = ld_ib_reset IMPORTING ed_key = ld_ed_key ed_msgty_max = ld_ed_msgty_max ed_msg_count = ld_ed_msg_count EXCEPTIONS KEY_EMPTY = 1 KEY_NOT_FOUND = 2 KEY_FILLED_DURING_ACTIVATION = 3 . " MESSAGES_TRACE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "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_ed_key  TYPE SYDBCNT ,
ld_id_key  TYPE SYDBCNT ,
ld_ed_msgty_max  TYPE SYMSGTY ,
ld_ib_activate  TYPE BOOLE_D ,
ld_ed_msg_count  TYPE SYDBCNT ,
ld_ib_destroy  TYPE BOOLE_D ,
ld_ib_reset  TYPE BOOLE_D .

ld_id_key = '123 '.
ld_ib_activate = '123 '.
ld_ib_destroy = '123 '.
ld_ib_reset = '123 '.

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 MESSAGES_TRACE or its description.