SAP FDT_BRS_DELETE_TRACES Function Module for Delete traces









FDT_BRS_DELETE_TRACES is a standard fdt brs delete traces SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Delete traces 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 brs delete traces FM, simply by entering the name FDT_BRS_DELETE_TRACES into the relevant SAP transaction such as SE37 or SE38.

Function Group: FDT_BRS_REMOTE_GENERATION
Program Name: SAPLFDT_BRS_REMOTE_GENERATION
Main Program: SAPLFDT_BRS_REMOTE_GENERATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function FDT_BRS_DELETE_TRACES 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_BRS_DELETE_TRACES'"Delete traces
EXPORTING
IT_TRACE_DATA = "Trace data for deletion (Only ID relvant)
IV_SERVICE_ID = "Service ID

EXCEPTIONS
TRACE_AUTH_FAILED = 1
.



IMPORTING Parameters details for FDT_BRS_DELETE_TRACES

IT_TRACE_DATA - Trace data for deletion (Only ID relvant)

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

IV_SERVICE_ID - Service ID

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

EXCEPTIONS details

TRACE_AUTH_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FDT_BRS_DELETE_TRACES 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_it_trace_data  TYPE FDT_BRS_T_TRACE_0100, "   
lv_trace_auth_failed  TYPE FDT_BRS_T_TRACE_0100, "   
lv_iv_service_id  TYPE SYSUUID_C. "   

  CALL FUNCTION 'FDT_BRS_DELETE_TRACES'  "Delete traces
    EXPORTING
         IT_TRACE_DATA = lv_it_trace_data
         IV_SERVICE_ID = lv_iv_service_id
    EXCEPTIONS
        TRACE_AUTH_FAILED = 1
. " FDT_BRS_DELETE_TRACES




ABAP code using 7.40 inline data declarations to call FM FDT_BRS_DELETE_TRACES

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!