SAP FMCU_CHECK_BUDCAT Function Module for Check existence of budget category









FMCU_CHECK_BUDCAT is a standard fmcu check budcat SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check existence of budget category 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 check budcat FM, simply by entering the name FMCU_CHECK_BUDCAT 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_CHECK_BUDCAT 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_CHECK_BUDCAT'"Check existence of budget category
EXPORTING
I_FM_AREA = "Financial management area
I_BUDCAT = "Budget category
* I_FLG_BYPASS_BUFFER = "Flag for by-passing buffer

IMPORTING
E_TIMEHORIZON = "Time horizon for budgeting
E_FLG_CEFFYEAR_USED = "Checkbox
E_NB_YEAR_NEXT = "Checkbox
E_CEFFYEAR_STATE = "State of Year of cash effectivity

EXCEPTIONS
NO_BUDCAT = 1
.



IMPORTING Parameters details for FMCU_CHECK_BUDCAT

I_FM_AREA - Financial management area

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

I_BUDCAT - Budget category

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

I_FLG_BYPASS_BUFFER - Flag for by-passing buffer

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

EXPORTING Parameters details for FMCU_CHECK_BUDCAT

E_TIMEHORIZON - Time horizon for budgeting

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

E_FLG_CEFFYEAR_USED - Checkbox

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

E_NB_YEAR_NEXT - Checkbox

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

E_CEFFYEAR_STATE - State of Year of cash effectivity

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

EXCEPTIONS details

NO_BUDCAT -

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

Copy and paste ABAP code example for FMCU_CHECK_BUDCAT 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_fm_area  TYPE FIKRS, "   
lv_no_budcat  TYPE FIKRS, "   
lv_e_timehorizon  TYPE BUCU_NBYEAR, "   
lv_i_budcat  TYPE BUKU_BUDCAT, "   
lv_e_flg_ceffyear_used  TYPE XFELD, "   
lv_e_nb_year_next  TYPE XFELD, "   
lv_i_flg_bypass_buffer  TYPE XFELD, "   
lv_e_ceffyear_state  TYPE FMCU_DIMSTATE. "   

  CALL FUNCTION 'FMCU_CHECK_BUDCAT'  "Check existence of budget category
    EXPORTING
         I_FM_AREA = lv_i_fm_area
         I_BUDCAT = lv_i_budcat
         I_FLG_BYPASS_BUFFER = lv_i_flg_bypass_buffer
    IMPORTING
         E_TIMEHORIZON = lv_e_timehorizon
         E_FLG_CEFFYEAR_USED = lv_e_flg_ceffyear_used
         E_NB_YEAR_NEXT = lv_e_nb_year_next
         E_CEFFYEAR_STATE = lv_e_ceffyear_state
    EXCEPTIONS
        NO_BUDCAT = 1
. " FMCU_CHECK_BUDCAT




ABAP code using 7.40 inline data declarations to call FM FMCU_CHECK_BUDCAT

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!