Hi Daniel/Christian,
I am able to add the Technical trace to the CL_FDT_function_process=>process method. I am attaching my sample code below. I am using the method READ and READ_HIERARCHY of IF_FDT_TRACE to get back the Technical log/trace. However, these methods give the trace in the format which is not readable.
Do you have some sample code to read the trace. For e.g. the parameter ETS_TRACE in the method READ of IF_FDT_TRACE. Basically to interpret the xml trace in if_ixml_document. So that I can analyze the trace properly.
I will now debug the method CL_FDT_function_process=>process.
Thanks,
Nitin
****************************************************************************************************
* Trigger function processing
****************************************************************************************************
DATA: lcl_fdt_trace TYPE REF TO if_fdt_trace.
ASSIGN _vr_data->* TO <_v_any>.
CALL METHOD cl_fdt_function_process=>process
EXPORTING
iv_function_id = '005056940AF61EE49BD923E4A9140C54'
iv_timestamp = _v_timestamp
iv_trace_mode = 'T'
IMPORTING
ea_result = <_v_any>
eo_trace = lcl_fdt_trace
CHANGING
ct_name_value = _vts_name_value_pair.
TRY.
TYPES:
BEGIN OF s_trace,
timestamp TYPE fdt_trace_0000-trace_timestamp,
user TYPE fdt_trace_0000-trace_user,
function_id TYPE fdt_trace_0000-trace_fct_id,
o_document TYPE REF TO if_ixml_document,
END OF s_trace .
TYPES:
ts_trace TYPE SORTED TABLE OF s_trace WITH UNIQUE KEY timestamp user .
DATA: lv_trace TYPE string,
lcl_trace_doc TYPE REF TO if_ixml_document.
DATA: e_xml_trace TYPE string,
e_trace TYPE ts_trace.
lcl_fdt_trace->read( IMPORTING ev_trace = e_xml_trace
ets_trace = e_trace ).
CALL METHOD lcl_fdt_trace->read_hierarchy
* EXPORTING
* itr_timestamp =
* itr_user =
* itr_function_id =
* iv_memory_only = ABAP_FALSE
IMPORTING
ev_trace = lv_trace
eo_trace_document = lcl_trace_doc.
CATCH cx_fdt_input .
CATCH cx_fdt_system .
ENDTRY.