SAP Function Modules

MINIALV_TRACE_SAVE SAP Function module







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

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


Pattern for FM MINIALV_TRACE_SAVE - MINIALV TRACE SAVE





CALL FUNCTION 'MINIALV_TRACE_SAVE' "
* EXPORTING
*   i_report =                  " syrepid       ABAP Program: Current Main Program
*   i_variant =                 " rsvar-variant  Variant Name
*   i_trace_end =               " char01        Character Field Length 1
*   i_trace_obj =               " char01        Character Field Length 1
  EXCEPTIONS
    WRONG_RELID = 1             "
    NO_REPORT = 2               "
    NO_EXNAME = 3               "
    NO_EXTRACT_CREATED = 4      "
    .  "  MINIALV_TRACE_SAVE

ABAP code example for Function Module MINIALV_TRACE_SAVE





The ABAP code below is a full code listing to execute function module MINIALV_TRACE_SAVE 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_i_report) = 'some text here'.

DATA(ld_i_variant) = some text here
DATA(ld_i_trace_end) = 'some text here'.
DATA(ld_i_trace_obj) = 'some text here'. . CALL FUNCTION 'MINIALV_TRACE_SAVE' * EXPORTING * i_report = ld_i_report * i_variant = ld_i_variant * i_trace_end = ld_i_trace_end * i_trace_obj = ld_i_trace_obj EXCEPTIONS WRONG_RELID = 1 NO_REPORT = 2 NO_EXNAME = 3 NO_EXTRACT_CREATED = 4 . " MINIALV_TRACE_SAVE
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 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_i_report  TYPE SYREPID ,
ld_i_variant  TYPE RSVAR-VARIANT ,
ld_i_trace_end  TYPE CHAR01 ,
ld_i_trace_obj  TYPE CHAR01 .

ld_i_report = 'some text here'.

ld_i_variant = some text here
ld_i_trace_end = 'some text here'.
ld_i_trace_obj = 'some text here'.

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