SAP FM_TRACE_STEP_BEGIN Function Module for









FM_TRACE_STEP_BEGIN is a standard fm trace step begin SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for fm trace step begin FM, simply by entering the name FM_TRACE_STEP_BEGIN into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMTR
Program Name: SAPLFMTR
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FM_TRACE_STEP_BEGIN pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'FM_TRACE_STEP_BEGIN'"
EXPORTING
I_NAME = "
* I_TYPE = 'F' "
I_LEVEL = "
I_VALUE = "

IMPORTING
E_LEVEL = "

EXCEPTIONS
NOT_ACTIVE = 1
.



IMPORTING Parameters details for FM_TRACE_STEP_BEGIN

I_NAME -

Data type: T090W-OBJCT
Optional: No
Call by Reference: No ( called with pass by value option)

I_TYPE -

Data type: T090W-TXTYP
Default: 'F'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_LEVEL -

Data type: SNODETEXT-TLEVEL
Optional: No
Call by Reference: No ( called with pass by value option)

I_VALUE -

Data type: SY-MSGV1
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FM_TRACE_STEP_BEGIN

E_LEVEL -

Data type: SNODETEXT-TLEVEL
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_ACTIVE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FM_TRACE_STEP_BEGIN Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_i_name  TYPE T090W-OBJCT, "   
lv_e_level  TYPE SNODETEXT-TLEVEL, "   
lv_not_active  TYPE SNODETEXT, "   
lv_i_type  TYPE T090W-TXTYP, "   'F'
lv_i_level  TYPE SNODETEXT-TLEVEL, "   
lv_i_value  TYPE SY-MSGV1. "   

  CALL FUNCTION 'FM_TRACE_STEP_BEGIN'  "
    EXPORTING
         I_NAME = lv_i_name
         I_TYPE = lv_i_type
         I_LEVEL = lv_i_level
         I_VALUE = lv_i_value
    IMPORTING
         E_LEVEL = lv_e_level
    EXCEPTIONS
        NOT_ACTIVE = 1
. " FM_TRACE_STEP_BEGIN




ABAP code using 7.40 inline data declarations to call FM FM_TRACE_STEP_BEGIN

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single OBJCT FROM T090W INTO @DATA(ld_i_name).
 
"SELECT single TLEVEL FROM SNODETEXT INTO @DATA(ld_e_level).
 
 
"SELECT single TXTYP FROM T090W INTO @DATA(ld_i_type).
DATA(ld_i_type) = 'F'.
 
"SELECT single TLEVEL FROM SNODETEXT INTO @DATA(ld_i_level).
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_i_value).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!