SAP FMCU_GET_BUDTYPE Function Module for Get budget types









FMCU_GET_BUDTYPE is a standard fmcu get budtype SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get budget types 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 budtype FM, simply by entering the name FMCU_GET_BUDTYPE 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_BUDTYPE 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_BUDTYPE'"Get budget types
EXPORTING
I_FM_AREA = "FM area
I_VALTYPE = "Value Type
* I_FLG_BYPASS_BUFFER = ' ' "Flag for by-passing buffer

IMPORTING
E_T_BUDTYPE = "Budget types
E_T_VALBUDTYPE = "Value type - Budget type - Eligibility

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for FMCU_GET_BUDTYPE

I_FM_AREA - FM area

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

I_VALTYPE - Value Type

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

I_FLG_BYPASS_BUFFER - Flag for by-passing buffer

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

EXPORTING Parameters details for FMCU_GET_BUDTYPE

E_T_BUDTYPE - Budget types

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

E_T_VALBUDTYPE - Value type - Budget type - Eligibility

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

EXCEPTIONS details

NOT_FOUND - No record was found

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

Copy and paste ABAP code example for FMCU_GET_BUDTYPE 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_not_found  TYPE FIKRS, "   
lv_e_t_budtype  TYPE BUKU_T_BUDTYPE, "   
lv_i_valtype  TYPE BUKU_VALTYPE, "   
lv_e_t_valbudtype  TYPE BUKU_T_VALBUD_TYPE, "   
lv_i_flg_bypass_buffer  TYPE XFELD. "   ' '

  CALL FUNCTION 'FMCU_GET_BUDTYPE'  "Get budget types
    EXPORTING
         I_FM_AREA = lv_i_fm_area
         I_VALTYPE = lv_i_valtype
         I_FLG_BYPASS_BUFFER = lv_i_flg_bypass_buffer
    IMPORTING
         E_T_BUDTYPE = lv_e_t_budtype
         E_T_VALBUDTYPE = lv_e_t_valbudtype
    EXCEPTIONS
        NOT_FOUND = 1
. " FMCU_GET_BUDTYPE




ABAP code using 7.40 inline data declarations to call FM FMCU_GET_BUDTYPE

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.

 
 
 
 
 
DATA(ld_i_flg_bypass_buffer) = ' '.
 


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!