SAP Function Modules

comments icon Comments

MINIALV_TRACE_FLOW SAP Function module







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

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


Pattern for FM MINIALV_TRACE_FLOW - MINIALV TRACE FLOW 





CALL FUNCTION 'MINIALV_TRACE_FLOW' "
  EXPORTING
    i_report =                  " syrepid       ABAP Program: Current Main Program
*   i_variant =                 " rsvar-variant  Variant Name
*   i_test =                    " char1         Single-Character Flag
*   i_trace =                   " char3         3-Byte Field
  IMPORTING
    error_string =              " w3_qvalue     Value for WWW query string name/value pair
* TABLES
*   et_data =                   " lvc_s_data    ALV control: Data transfer structure
*   et_info =                   " lvc_s_info    ALV control: Data information structure
*   et_hyperlinks =             " lvc_s_hype    ALV Control: Hyperlinks
*   et_fields =                 " lvc_s_fiel
*   et_int_data =               " lvc_s_tabl
    .  "  MINIALV_TRACE_FLOW

ABAP code example for Function Module MINIALV_TRACE_FLOW





The ABAP code below is a full code listing to execute function module MINIALV_TRACE_FLOW 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_error_string    TYPE W3_QVALUE
,
it_et_data    TYPE STANDARD TABLE OF LVC_S_DATA,"TABLES PARAM
wa_et_data  LIKE LINE OF it_et_data
,
it_et_info    TYPE STANDARD TABLE OF LVC_S_INFO,"TABLES PARAM
wa_et_info  LIKE LINE OF it_et_info
,
it_et_hyperlinks    TYPE STANDARD TABLE OF LVC_S_HYPE,"TABLES PARAM
wa_et_hyperlinks  LIKE LINE OF it_et_hyperlinks
,
it_et_fields    TYPE STANDARD TABLE OF LVC_S_FIEL,"TABLES PARAM
wa_et_fields  LIKE LINE OF it_et_fields
,
it_et_int_data    TYPE STANDARD TABLE OF LVC_S_TABL,"TABLES PARAM
wa_et_int_data  LIKE LINE OF it_et_int_data
.




DATA(ld_i_report) = 'some text here'.


DATA(ld_i_variant) = some text here

DATA(ld_i_test) = 'some text here'.

DATA(ld_i_trace) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_et_data to it_et_data.
 

"populate fields of struture and append to itab
append wa_et_info to it_et_info.
 

"populate fields of struture and append to itab
append wa_et_hyperlinks to it_et_hyperlinks.
 

"populate fields of struture and append to itab
append wa_et_fields to it_et_fields.
 

"populate fields of struture and append to itab
append wa_et_int_data to it_et_int_data.
.

CALL FUNCTION 'MINIALV_TRACE_FLOW'
  EXPORTING
    i_report =                   ld_i_report
*   i_variant =                  ld_i_variant
*   i_test =                     ld_i_test
*   i_trace =                    ld_i_trace
  IMPORTING
    error_string =               ld_error_string
* TABLES
*   et_data =                    it_et_data
*   et_info =                    it_et_info
*   et_hyperlinks =              it_et_hyperlinks
*   et_fields =                  it_et_fields
*   et_int_data =                it_et_int_data
    .  "  MINIALV_TRACE_FLOW

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_error_string  TYPE W3_QVALUE ,
ld_i_report  TYPE SYREPID ,
it_et_data  TYPE STANDARD TABLE OF LVC_S_DATA ,
wa_et_data  LIKE LINE OF it_et_data,
ld_i_variant  TYPE RSVAR-VARIANT ,
it_et_info  TYPE STANDARD TABLE OF LVC_S_INFO ,
wa_et_info  LIKE LINE OF it_et_info,
ld_i_test  TYPE CHAR1 ,
it_et_hyperlinks  TYPE STANDARD TABLE OF LVC_S_HYPE ,
wa_et_hyperlinks  LIKE LINE OF it_et_hyperlinks,
ld_i_trace  TYPE CHAR3 ,
it_et_fields  TYPE STANDARD TABLE OF LVC_S_FIEL ,
wa_et_fields  LIKE LINE OF it_et_fields,
it_et_int_data  TYPE STANDARD TABLE OF LVC_S_TABL ,
wa_et_int_data  LIKE LINE OF it_et_int_data.




ld_i_report = 'some text here'. 

"populate fields of struture and append to itab
append wa_et_data to it_et_data.

ld_i_variant = some text here 

"populate fields of struture and append to itab
append wa_et_info to it_et_info.
ld_i_test = 'some text here'. 

"populate fields of struture and append to itab
append wa_et_hyperlinks to it_et_hyperlinks.
ld_i_trace = 'some text here'. 

"populate fields of struture and append to itab
append wa_et_fields to it_et_fields. 

"populate fields of struture and append to itab
append wa_et_int_data to it_et_int_data.

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


   
 

MINIALV_TRACE_FLOW - 
MINIALV_TRACE_DISPLAY_WAO - 
MINIALV_TRACE_DISPLAY - 
MINIALV_TRACE_DISPATCH - 
MINIALV_TRACE_DELETE_WAO - 
MINIALV_TRACE_DELETE_INT_WAO -