SAP FDT_READ_TRACE_HEADERS Function Module for BRFplus: Read Lean Trace Headers









FDT_READ_TRACE_HEADERS is a standard fdt read trace headers SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BRFplus: Read Lean Trace Headers processing and below is the pattern details for this FM, 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 fdt read trace headers FM, simply by entering the name FDT_READ_TRACE_HEADERS into the relevant SAP transaction such as SE37 or SE38.

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



Function FDT_READ_TRACE_HEADERS 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 'FDT_READ_TRACE_HEADERS'"BRFplus: Read Lean Trace Headers
  EXPORTING
   IV_TRACE_DB_CTAB =  "Table Name for Trace Table (Cluster)
   IV_TRACE_DB_JSTAB_H =  "Table Name for Trace Table (JSON) Head
   ITR_TRACE_UUID =  "Range of Trace UUIDs
   ITR_USER =  "Range of Users
   ITR_FUNCTION_ID =  "Range of Function IDs
   ITR_EXTERNAL_ID =  "Range of External ID for Trace
   ITR_TRACE_REF_UUID =  "Range of Parent Trace UUID. Used to read child traces
   ITR_TRACE_START =  "Range of Trace Starting Timestamp
   ITR_TRACE_END =  "Range of Trace Ending Timestamp

 IMPORTING
   ET_HEADER =  "Header data
.



IMPORTING Parameters details for FDT_READ_TRACE_HEADERS

IV_TRACE_DB_CTAB - Table Name for Trace Table (Cluster)

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

IV_TRACE_DB_JSTAB_H - Table Name for Trace Table (JSON) Head

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

ITR_TRACE_UUID - Range of Trace UUIDs

Data type: IF_FDT_LEAN_TRACE=>TR_TRACE_UUID
Optional: No
Call by Reference: Yes

ITR_USER - Range of Users

Data type: IF_FDT_TRACE=>TR_USER
Optional: No
Call by Reference: Yes

ITR_FUNCTION_ID - Range of Function IDs

Data type: IF_FDT_TRACE=>TR_FUNCTION_ID
Optional: No
Call by Reference: Yes

ITR_EXTERNAL_ID - Range of External ID for Trace

Data type: IF_FDT_LEAN_TRACE=>TR_EXTERNAL_ID
Optional: No
Call by Reference: Yes

ITR_TRACE_REF_UUID - Range of Parent Trace UUID. Used to read child traces

Data type: IF_FDT_LEAN_TRACE=>TR_TRACE_UUID
Optional: No
Call by Reference: Yes

ITR_TRACE_START - Range of Trace Starting Timestamp

Data type: IF_FDT_LEAN_TRACE=>TR_TRACE_START
Optional: No
Call by Reference: Yes

ITR_TRACE_END - Range of Trace Ending Timestamp

Data type: IF_FDT_LEAN_TRACE=>TR_TRACE_END
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FDT_READ_TRACE_HEADERS

ET_HEADER - Header data

Data type: IF_FDT_LEAN_TRACE=>T_HEADER
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FDT_READ_TRACE_HEADERS 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_et_header  TYPE IF_FDT_LEAN_TRACE=>T_HEADER, "   
lv_iv_trace_db_ctab  TYPE TABNAME, "   
lv_iv_trace_db_jstab_h  TYPE TABNAME, "   
lv_itr_trace_uuid  TYPE IF_FDT_LEAN_TRACE=>TR_TRACE_UUID, "   
lv_itr_user  TYPE IF_FDT_TRACE=>TR_USER, "   
lv_itr_function_id  TYPE IF_FDT_TRACE=>TR_FUNCTION_ID, "   
lv_itr_external_id  TYPE IF_FDT_LEAN_TRACE=>TR_EXTERNAL_ID, "   
lv_itr_trace_ref_uuid  TYPE IF_FDT_LEAN_TRACE=>TR_TRACE_UUID, "   
lv_itr_trace_start  TYPE IF_FDT_LEAN_TRACE=>TR_TRACE_START, "   
lv_itr_trace_end  TYPE IF_FDT_LEAN_TRACE=>TR_TRACE_END. "   

  CALL FUNCTION 'FDT_READ_TRACE_HEADERS'  "BRFplus: Read Lean Trace Headers
    EXPORTING
         IV_TRACE_DB_CTAB = lv_iv_trace_db_ctab
         IV_TRACE_DB_JSTAB_H = lv_iv_trace_db_jstab_h
         ITR_TRACE_UUID = lv_itr_trace_uuid
         ITR_USER = lv_itr_user
         ITR_FUNCTION_ID = lv_itr_function_id
         ITR_EXTERNAL_ID = lv_itr_external_id
         ITR_TRACE_REF_UUID = lv_itr_trace_ref_uuid
         ITR_TRACE_START = lv_itr_trace_start
         ITR_TRACE_END = lv_itr_trace_end
    IMPORTING
         ET_HEADER = lv_et_header
. " FDT_READ_TRACE_HEADERS




ABAP code using 7.40 inline data declarations to call FM FDT_READ_TRACE_HEADERS

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!