SAP K_TRACE_STEP_END_INTERNAL Function Module for









K_TRACE_STEP_END_INTERNAL is a standard k trace step end internal 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 k trace step end internal FM, simply by entering the name K_TRACE_STEP_END_INTERNAL into the relevant SAP transaction such as SE37 or SE38.

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



Function K_TRACE_STEP_END_INTERNAL 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 'K_TRACE_STEP_END_INTERNAL'"
EXPORTING
I_NAME = "
I_VALUE = "
* I_INTERNAL_CALL = "
.



IMPORTING Parameters details for K_TRACE_STEP_END_INTERNAL

I_NAME -

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

I_VALUE -

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

I_INTERNAL_CALL -

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

Copy and paste ABAP code example for K_TRACE_STEP_END_INTERNAL 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 C, "   
lv_i_value  TYPE C, "   
lv_i_internal_call  TYPE C. "   

  CALL FUNCTION 'K_TRACE_STEP_END_INTERNAL'  "
    EXPORTING
         I_NAME = lv_i_name
         I_VALUE = lv_i_value
         I_INTERNAL_CALL = lv_i_internal_call
. " K_TRACE_STEP_END_INTERNAL




ABAP code using 7.40 inline data declarations to call FM K_TRACE_STEP_END_INTERNAL

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.

 
 
 


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!