ATRA_CHECK_ATRA_ANALYZER SAP Function module

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

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

Pattern for FM ATRA_CHECK_ATRA_ANALYZER - ATRA CHECK ATRA ANALYZER

CALL FUNCTION 'ATRA_CHECK_ATRA_ANALYZER' "
  EXPORTING
    i_filename =                " csequence
*   i_server =                  " csequence
*   i_flg_no_rfc =              " xflag
  IMPORTING
    e_exception =               " text200
* TABLES
*   e_tab_hitlist =             " atra_str_trace_hitlist
  EXCEPTIONS
    FAILURE = 1                 "
    .  "  ATRA_CHECK_ATRA_ANALYZER

ABAP code example for Function Module ATRA_CHECK_ATRA_ANALYZER

The ABAP code below is a full code listing to execute function module ATRA_CHECK_ATRA_ANALYZER 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_exception  
 
 TYPE TEXT200
,
it_e_tab_hitlist  
 
 TYPE STANDARD TABLE OF ATRA_STR_TRACE_HITLIST,"TABLES PARAM
wa_e_tab_hitlist
 
 LIKE LINE OF it_e_tab_hitlist
.


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

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

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

"populate fields of struture and append to itab
append wa_e_tab_hitlist to it_e_tab_hitlist.
.

CALL FUNCTION 'ATRA_CHECK_ATRA_ANALYZER'
  EXPORTING
    i_filename =                 ld_i_filename
*   i_server =                   ld_i_server
*   i_flg_no_rfc =               ld_i_flg_no_rfc
  IMPORTING
    e_exception =                ld_e_exception
* TABLES
*   e_tab_hitlist =              it_e_tab_hitlist
  EXCEPTIONS
    FAILURE =                    1
    .  "  ATRA_CHECK_ATRA_ANALYZER

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_e_exception
 
 TYPE TEXT200 ,
ld_i_filename
 
 TYPE CSEQUENCE ,
it_e_tab_hitlist
 
 TYPE STANDARD TABLE OF ATRA_STR_TRACE_HITLIST ,
wa_e_tab_hitlist
 
 LIKE LINE OF it_e_tab_hitlist,
ld_i_server
 
 TYPE CSEQUENCE ,
ld_i_flg_no_rfc
 
 TYPE XFLAG .


ld_i_filename = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_e_tab_hitlist to it_e_tab_hitlist.
ld_i_server = 'Check type of data required'.
ld_i_flg_no_rfc = 'Check type of data required'.