SAP RKE_TRACE_WRITE_INIT Function Module for









RKE_TRACE_WRITE_INIT is a standard rke trace write init 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 rke trace write init FM, simply by entering the name RKE_TRACE_WRITE_INIT into the relevant SAP transaction such as SE37 or SE38.

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



Function RKE_TRACE_WRITE_INIT 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 'RKE_TRACE_WRITE_INIT'"
EXPORTING
I_S_HEADER_INFO = "
I_T_SEL = "
I_T_SF = "
I_T_ORDER_BY = "

IMPORTING
E_S_KEY = "
.



IMPORTING Parameters details for RKE_TRACE_WRITE_INIT

I_S_HEADER_INFO -

Data type: KEDC_S_PROT_HEADER_INIT
Optional: No
Call by Reference: Yes

I_T_SEL -

Data type: KED1_T_SEL
Optional: No
Call by Reference: Yes

I_T_SF -

Data type: KED1_T_SF
Optional: No
Call by Reference: Yes

I_T_ORDER_BY -

Data type: KED1_T_ORDER_BY
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for RKE_TRACE_WRITE_INIT

E_S_KEY -

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

Copy and paste ABAP code example for RKE_TRACE_WRITE_INIT 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_e_s_key  TYPE KEDC_S_PROT_KEY, "   
lv_i_s_header_info  TYPE KEDC_S_PROT_HEADER_INIT, "   
lv_i_t_sel  TYPE KED1_T_SEL, "   
lv_i_t_sf  TYPE KED1_T_SF, "   
lv_i_t_order_by  TYPE KED1_T_ORDER_BY. "   

  CALL FUNCTION 'RKE_TRACE_WRITE_INIT'  "
    EXPORTING
         I_S_HEADER_INFO = lv_i_s_header_info
         I_T_SEL = lv_i_t_sel
         I_T_SF = lv_i_t_sf
         I_T_ORDER_BY = lv_i_t_order_by
    IMPORTING
         E_S_KEY = lv_e_s_key
. " RKE_TRACE_WRITE_INIT




ABAP code using 7.40 inline data declarations to call FM RKE_TRACE_WRITE_INIT

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!