SAP FMCU_GET_ACTIVE_DIMENSIONS Function Module for Retrieve FM Budgeting settings for dimensions (all FM areas)









FMCU_GET_ACTIVE_DIMENSIONS is a standard fmcu get active dimensions SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieve FM Budgeting settings for dimensions (all FM areas) 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 fmcu get active dimensions FM, simply by entering the name FMCU_GET_ACTIVE_DIMENSIONS into the relevant SAP transaction such as SE37 or SE38.

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



Function FMCU_GET_ACTIVE_DIMENSIONS 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 'FMCU_GET_ACTIVE_DIMENSIONS'"Retrieve FM Budgeting settings for dimensions (all FM areas)
 IMPORTING
   E_FUND_ACTIVE =  "Fund active  (Mandatory or not)
   E_FUNDSCTR_ACTIVE =  "Funds center active (Mandatory or not)
   E_CMMTITEM_ACTIVE =  "Commitment item active (Mandatory or not)
   E_FUNCAREA_ACTIVE =  "Functionnal area active (Mandatory or not)
   E_MEASURE_ACTIVE =  "Measure active (Mandatory or not)
   E_GRANT_NBR_ACTIVE =  "Grant active (Mandatory or not)
   E_USERDIM_ACTIVE =  "User dimension active (Mandatory or not)
   E_BUDGET_PD_ACTIVE =  "Budget period active (Mandatory or not)

EXCEPTIONS
   CUSTOMIZING_INCONSISTENT = 1
.



EXPORTING Parameters details for FMCU_GET_ACTIVE_DIMENSIONS

E_FUND_ACTIVE - Fund active (Mandatory or not)

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

E_FUNDSCTR_ACTIVE - Funds center active (Mandatory or not)

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

E_CMMTITEM_ACTIVE - Commitment item active (Mandatory or not)

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

E_FUNCAREA_ACTIVE - Functionnal area active (Mandatory or not)

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

E_MEASURE_ACTIVE - Measure active (Mandatory or not)

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

E_GRANT_NBR_ACTIVE - Grant active (Mandatory or not)

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

E_USERDIM_ACTIVE - User dimension active (Mandatory or not)

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

E_BUDGET_PD_ACTIVE - Budget period active (Mandatory or not)

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

EXCEPTIONS details

CUSTOMIZING_INCONSISTENT - FM and Budgeting customizing are not consistent

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

Copy and paste ABAP code example for FMCU_GET_ACTIVE_DIMENSIONS 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_e_fund_active  TYPE XFELD, "   
lv_customizing_inconsistent  TYPE XFELD, "   
lv_e_fundsctr_active  TYPE XFELD, "   
lv_e_cmmtitem_active  TYPE XFELD, "   
lv_e_funcarea_active  TYPE XFELD, "   
lv_e_measure_active  TYPE XFELD, "   
lv_e_grant_nbr_active  TYPE XFELD, "   
lv_e_userdim_active  TYPE XFELD, "   
lv_e_budget_pd_active  TYPE XFELD. "   

  CALL FUNCTION 'FMCU_GET_ACTIVE_DIMENSIONS'  "Retrieve FM Budgeting settings for dimensions (all FM areas)
    IMPORTING
         E_FUND_ACTIVE = lv_e_fund_active
         E_FUNDSCTR_ACTIVE = lv_e_fundsctr_active
         E_CMMTITEM_ACTIVE = lv_e_cmmtitem_active
         E_FUNCAREA_ACTIVE = lv_e_funcarea_active
         E_MEASURE_ACTIVE = lv_e_measure_active
         E_GRANT_NBR_ACTIVE = lv_e_grant_nbr_active
         E_USERDIM_ACTIVE = lv_e_userdim_active
         E_BUDGET_PD_ACTIVE = lv_e_budget_pd_active
    EXCEPTIONS
        CUSTOMIZING_INCONSISTENT = 1
. " FMCU_GET_ACTIVE_DIMENSIONS




ABAP code using 7.40 inline data declarations to call FM FMCU_GET_ACTIVE_DIMENSIONS

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!