SAP Function Modules

comments icon Comments

SUAUTH_READ_TRACE_VALUES SAP Function module







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

Associated Function Group: SUAUTHTRACE
Released Date: Not Released
Processing type: Remote-Enabled + BasXML supported
remote enabled with basXML set


Pattern for FM SUAUTH_READ_TRACE_VALUES - SUAUTH READ TRACE VALUES 





CALL FUNCTION 'SUAUTH_READ_TRACE_VALUES' "
* EXPORTING
*   iv_function =               " char04
*   iv_st01_max_rec =           " i
*   iv_st01_datefrom =          " dats
*   iv_st01_timefrom =          " tims
*   iv_st01_dateto =            " dats
*   iv_st01_timeto =            " tims
*   iv_st01_user =              " xubname
*   it_su2x_start_act =         " usob_authvaltrc_t
*   iv_st01_tst_from =          " timestamp
*   iv_st01_tst_to =            " timestamp
*   iv_st01_read_epp =          " char01
  IMPORTING
    et_st01_data =              " suauthtrace_data_t
    ev_st01_data_in_utc =       " char01
    et_su2x_authvaltrc =        " usob_authvaltrc_t
    ev_sysid =                  " sysysid
    ev_mandt =                  " symandt
    ev_host =                   " syhost
    et_error =                  " bapirettab
    ev_server =                 " msxxlist-name
* TABLES
*   ct_su2s_sel_range =         " bapiussrge
    .  "  SUAUTH_READ_TRACE_VALUES

ABAP code example for Function Module SUAUTH_READ_TRACE_VALUES





The ABAP code below is a full code listing to execute function module SUAUTH_READ_TRACE_VALUES 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_et_st01_data    TYPE SUAUTHTRACE_DATA_T
,
ld_ev_st01_data_in_utc    TYPE CHAR01
,
ld_et_su2x_authvaltrc    TYPE USOB_AUTHVALTRC_T
,
ld_ev_sysid    TYPE SYSYSID
,
ld_ev_mandt    TYPE SYMANDT
,
ld_ev_host    TYPE SYHOST
,
ld_et_error    TYPE BAPIRETTAB
,
ld_ev_server    TYPE MSXXLIST-NAME
,
it_ct_su2s_sel_range    TYPE STANDARD TABLE OF BAPIUSSRGE,"TABLES PARAM
wa_ct_su2s_sel_range  LIKE LINE OF it_ct_su2s_sel_range
.




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

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

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

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

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

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

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

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

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

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

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

"populate fields of struture and append to itab
append wa_ct_su2s_sel_range to it_ct_su2s_sel_range.
.

CALL FUNCTION 'SUAUTH_READ_TRACE_VALUES'
* EXPORTING
*   iv_function =                ld_iv_function
*   iv_st01_max_rec =            ld_iv_st01_max_rec
*   iv_st01_datefrom =           ld_iv_st01_datefrom
*   iv_st01_timefrom =           ld_iv_st01_timefrom
*   iv_st01_dateto =             ld_iv_st01_dateto
*   iv_st01_timeto =             ld_iv_st01_timeto
*   iv_st01_user =               ld_iv_st01_user
*   it_su2x_start_act =          ld_it_su2x_start_act
*   iv_st01_tst_from =           ld_iv_st01_tst_from
*   iv_st01_tst_to =             ld_iv_st01_tst_to
*   iv_st01_read_epp =           ld_iv_st01_read_epp
  IMPORTING
    et_st01_data =               ld_et_st01_data
    ev_st01_data_in_utc =        ld_ev_st01_data_in_utc
    et_su2x_authvaltrc =         ld_et_su2x_authvaltrc
    ev_sysid =                   ld_ev_sysid
    ev_mandt =                   ld_ev_mandt
    ev_host =                    ld_ev_host
    et_error =                   ld_et_error
    ev_server =                  ld_ev_server
* TABLES
*   ct_su2s_sel_range =          it_ct_su2s_sel_range
    .  "  SUAUTH_READ_TRACE_VALUES

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_et_st01_data  TYPE SUAUTHTRACE_DATA_T ,
ld_iv_function  TYPE CHAR04 ,
it_ct_su2s_sel_range  TYPE STANDARD TABLE OF BAPIUSSRGE ,
wa_ct_su2s_sel_range  LIKE LINE OF it_ct_su2s_sel_range,
ld_ev_st01_data_in_utc  TYPE CHAR01 ,
ld_iv_st01_max_rec  TYPE I ,
ld_et_su2x_authvaltrc  TYPE USOB_AUTHVALTRC_T ,
ld_iv_st01_datefrom  TYPE DATS ,
ld_ev_sysid  TYPE SYSYSID ,
ld_iv_st01_timefrom  TYPE TIMS ,
ld_ev_mandt  TYPE SYMANDT ,
ld_iv_st01_dateto  TYPE DATS ,
ld_ev_host  TYPE SYHOST ,
ld_iv_st01_timeto  TYPE TIMS ,
ld_et_error  TYPE BAPIRETTAB ,
ld_iv_st01_user  TYPE XUBNAME ,
ld_ev_server  TYPE MSXXLIST-NAME ,
ld_it_su2x_start_act  TYPE USOB_AUTHVALTRC_T ,
ld_iv_st01_tst_from  TYPE TIMESTAMP ,
ld_iv_st01_tst_to  TYPE TIMESTAMP ,
ld_iv_st01_read_epp  TYPE CHAR01 .




ld_iv_function = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_ct_su2s_sel_range to it_ct_su2s_sel_range.
ld_iv_st01_max_rec = 'Check type of data required'.
ld_iv_st01_datefrom = 'Check type of data required'.
ld_iv_st01_timefrom = 'Check type of data required'.
ld_iv_st01_dateto = 'Check type of data required'.
ld_iv_st01_timeto = 'Check type of data required'.
ld_iv_st01_user = 'Check type of data required'.
ld_it_su2x_start_act = 'Check type of data required'.
ld_iv_st01_tst_from = 'Check type of data required'.
ld_iv_st01_tst_to = 'Check type of data required'.
ld_iv_st01_read_epp = '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 SUAUTH_READ_TRACE_VALUES or its description.


   
 

SUAUTH_READ_TRACE_VALUES - 
SUAUTH_IMPORT_TRACE_VALUES - 
SUAUTH_IMPORT_TRACE_APPL - 
SUAUTH_GET_ST01_TRACE_OBJECTS - 
SUAUTH_GET_RCF_DESTINATION - 
SU2X_TRANSPORT_OBJECT -