SAP KEDR_TRACE_WRITE Function Module for

Search SAP Function Modules

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

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

Function KEDR_TRACE_WRITE 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 'KEDR_TRACE_WRITE'"
  EXPORTING
*  I_TRACE_HANDLE =  "
*  I_TAB_TRACE_HANDLES =  "
*  I_WRITE_DETAILS =  "
*  I_WRITE_TO_SPOOL =  "
*  I_WRITE_TO_MEMORY =  "
*  I_WRITE_TO_TKEDRX =  "
*  I_IMPORT_FROM_MEMORY =  "
*  I_IMPORT_FROM_TKEDRX =  "

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLKEDRCOPA_001 From Release 4.0: Exit in Characteristic Derivation

IMPORTING Parameters details for KEDR_TRACE_WRITE

I_TRACE_HANDLE -

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

I_TAB_TRACE_HANDLES -

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

I_WRITE_DETAILS -

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

I_WRITE_TO_SPOOL -

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

I_WRITE_TO_MEMORY -

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

I_WRITE_TO_TKEDRX -

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

I_IMPORT_FROM_MEMORY -

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

I_IMPORT_FROM_TKEDRX -

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

Copy and paste ABAP code example for KEDR_TRACE_WRITE 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.

ABAP code using 7.40 inline data declarations to call FM KEDR_TRACE_WRITE

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