SAP FMCU_SET_SINGLE_BUDCAT Function Module for Set single budget category









FMCU_SET_SINGLE_BUDCAT is a standard fmcu set single 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 Set single 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 set single budcat FM, simply by entering the name FMCU_SET_SINGLE_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_SET_SINGLE_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_SET_SINGLE_BUDCAT'"Set single budget category
EXPORTING
I_FM_AREA = "Financial Management Area

IMPORTING
E_BUDCAT = "Budget Category
E_FLG_SINGLE_BUDCAT = "Flag set if only one budget category is defined
E_FLG_CEFFYEAR = "Flag set on if cash year defined

CHANGING
* C_R_BUDCAT = "Range for budget categories (BUKU_BUDCAT)
.



IMPORTING Parameters details for FMCU_SET_SINGLE_BUDCAT

I_FM_AREA - Financial Management Area

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

EXPORTING Parameters details for FMCU_SET_SINGLE_BUDCAT

E_BUDCAT - Budget Category

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

E_FLG_SINGLE_BUDCAT - Flag set if only one budget category is defined

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

E_FLG_CEFFYEAR - Flag set on if cash year defined

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

CHANGING Parameters details for FMCU_SET_SINGLE_BUDCAT

C_R_BUDCAT - Range for budget categories (BUKU_BUDCAT)

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

Copy and paste ABAP code example for FMCU_SET_SINGLE_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_e_budcat  TYPE BUKU_BUDCAT, "   
lv_i_fm_area  TYPE FIKRS, "   
lv_c_r_budcat  TYPE BUKU_T_RBUDCAT, "   
lv_e_flg_single_budcat  TYPE XFELD, "   
lv_e_flg_ceffyear  TYPE XFELD. "   

  CALL FUNCTION 'FMCU_SET_SINGLE_BUDCAT'  "Set single budget category
    EXPORTING
         I_FM_AREA = lv_i_fm_area
    IMPORTING
         E_BUDCAT = lv_e_budcat
         E_FLG_SINGLE_BUDCAT = lv_e_flg_single_budcat
         E_FLG_CEFFYEAR = lv_e_flg_ceffyear
    CHANGING
         C_R_BUDCAT = lv_c_r_budcat
. " FMCU_SET_SINGLE_BUDCAT




ABAP code using 7.40 inline data declarations to call FM FMCU_SET_SINGLE_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!