SAP FMFG_DERIVE_TRACE_ACTIVATE Function Module for Log the results of a trace

Search SAP Function Modules

FMFG_DERIVE_TRACE_ACTIVATE is a standard fmfg derive trace activate SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Log the results of a trace 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 fmfg derive trace activate FM, simply by entering the name FMFG_DERIVE_TRACE_ACTIVATE into the relevant SAP transaction such as SE37 or SE38.

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

Function FMFG_DERIVE_TRACE_ACTIVATE 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 'FMFG_DERIVE_TRACE_ACTIVATE'"Log the results of a trace
  EXPORTING
   I_FLG_TRACE =  "Derivation Trace setting
   I_APPL =  "Application class for DD objects (not used)
   I_SUBCLASS =  "Subgroup by Application Class
   I_STRATEGY_ID =  "Strategy ID
   I_ENV =  "Environment for strategy

 IMPORTING
   E_OVERALL_STATUS =  "Are any traces active after the call?

.

IMPORTING Parameters details for FMFG_DERIVE_TRACE_ACTIVATE

I_FLG_TRACE - Derivation Trace setting

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

I_APPL - Application class for DD objects (not used)

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

I_SUBCLASS - Subgroup by Application Class

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

I_STRATEGY_ID - Strategy ID

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

I_ENV - Environment for strategy

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

EXPORTING Parameters details for FMFG_DERIVE_TRACE_ACTIVATE

E_OVERALL_STATUS - Are any traces active after the call?

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

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

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