SAP Function Modules

ATRA_SEND_TRACE_AGG_7X SAP Function module







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

Associated Function Group: S_ABAP_TRACE_DATA
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM ATRA_SEND_TRACE_AGG_7X - ATRA SEND TRACE AGG 7X





CALL FUNCTION 'ATRA_SEND_TRACE_AGG_7X' "
  EXPORTING
    p_fname =                   " se30fname
    p_dest =                    " rfcdes-rfcdest
    p_return_xstring = ' '      " char01
  IMPORTING
    e_satr_tab_key =            " satr_tab_key
    e_trans =                   " satr_trans_stru
  EXCEPTIONS
    ERROR_DURING_XSTRING_CONVERSIO = 1  "
    ERROR_NUMERIC_OVERFLOW = 2  "
    DATA_CONVERSION_ERROR = 3   "
    ERROR_BUILDING_CONTAINER_DATA = 4  "
    EMPTY_KEY = 5               "
    OTHER_ERRORS = 6            "
    .  "  ATRA_SEND_TRACE_AGG_7X

ABAP code example for Function Module ATRA_SEND_TRACE_AGG_7X





The ABAP code below is a full code listing to execute function module ATRA_SEND_TRACE_AGG_7X 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_e_satr_tab_key  TYPE SATR_TAB_KEY ,
ld_e_trans  TYPE SATR_TRANS_STRU .

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

SELECT single RFCDEST
FROM RFCDES
INTO @DATA(ld_p_dest).

DATA(ld_p_return_xstring) = 'Check type of data required'. . CALL FUNCTION 'ATRA_SEND_TRACE_AGG_7X' EXPORTING p_fname = ld_p_fname p_dest = ld_p_dest p_return_xstring = ld_p_return_xstring IMPORTING e_satr_tab_key = ld_e_satr_tab_key e_trans = ld_e_trans EXCEPTIONS ERROR_DURING_XSTRING_CONVERSIO = 1 ERROR_NUMERIC_OVERFLOW = 2 DATA_CONVERSION_ERROR = 3 ERROR_BUILDING_CONTAINER_DATA = 4 EMPTY_KEY = 5 OTHER_ERRORS = 6 . " ATRA_SEND_TRACE_AGG_7X
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 ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 6. "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_e_satr_tab_key  TYPE SATR_TAB_KEY ,
ld_p_fname  TYPE SE30FNAME ,
ld_e_trans  TYPE SATR_TRANS_STRU ,
ld_p_dest  TYPE RFCDES-RFCDEST ,
ld_p_return_xstring  TYPE CHAR01 .

ld_p_fname = 'Check type of data required'.

SELECT single RFCDEST
FROM RFCDES
INTO ld_p_dest.

ld_p_return_xstring = '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 ATRA_SEND_TRACE_AGG_7X or its description.