SAP FMFG_FACTS_DERIVE Function Module for Derive values for FACTS









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

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



Function FMFG_FACTS_DERIVE 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_FACTS_DERIVE'"Derive values for FACTS
EXPORTING
I_ENV = "Environment for strategy

IMPORTING
E_TRACE_HANDLE = "ABADR: Trace Handle

CHANGING
IUSFGFDERIVE = "Derivation of US Federal government fields

EXCEPTIONS
DERIVATION_FAILED = 1 CHECK_CHIER_FAILED = 2
.




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_SAPLFMFG_DERIVE_001 User Exit for USFG Derivation Tool

IMPORTING Parameters details for FMFG_FACTS_DERIVE

I_ENV - Environment for strategy

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

EXPORTING Parameters details for FMFG_FACTS_DERIVE

E_TRACE_HANDLE - ABADR: Trace Handle

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

CHANGING Parameters details for FMFG_FACTS_DERIVE

IUSFGFDERIVE - Derivation of US Federal government fields

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

EXCEPTIONS details

DERIVATION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

CHECK_CHIER_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMFG_FACTS_DERIVE 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_i_env  TYPE TABADRS-ABADRENV, "   
lv_iusfgfderive  TYPE IUSFGFDERIVE, "   
lv_e_trace_handle  TYPE ABADR_TRACE_HANDLE, "   
lv_derivation_failed  TYPE ABADR_TRACE_HANDLE, "   
lv_check_chier_failed  TYPE ABADR_TRACE_HANDLE. "   

  CALL FUNCTION 'FMFG_FACTS_DERIVE'  "Derive values for FACTS
    EXPORTING
         I_ENV = lv_i_env
    IMPORTING
         E_TRACE_HANDLE = lv_e_trace_handle
    CHANGING
         IUSFGFDERIVE = lv_iusfgfderive
    EXCEPTIONS
        DERIVATION_FAILED = 1
        CHECK_CHIER_FAILED = 2
. " FMFG_FACTS_DERIVE




ABAP code using 7.40 inline data declarations to call FM FMFG_FACTS_DERIVE

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.

"SELECT single ABADRENV FROM TABADRS INTO @DATA(ld_i_env).
 
 
 
 
 


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!