SAP FMCU_CHECK_BUDTYPE Function Module for Check existence of budget type in a combination

Search SAP Function Modules

FMCU_CHECK_BUDTYPE is a standard fmcu check 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 Check existence of budget type in a combination 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 budtype FM, simply by entering the name FMCU_CHECK_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_CHECK_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_CHECK_BUDTYPE'"Check existence of budget type in a combination
  EXPORTING
   I_FM_AREA =  "Financial management area
   I_VALTYPE =  "Value Type
   I_BUDTYPE =  "User defined budget type
*  I_FLG_BYPASS_BUFFER = ' ' "Flag for by-passing buffer

 IMPORTING
   E_FLG_ELIGIBILITY =  "Flag for Eligibility in Budgeting (set on: non eligible)
   E_BUDTYPE_TXT5 =  "Budget type short text (5)
   E_BUDTYPE_TXT20 =  "Budget type medium text (20)
   E_BUDTYPE_TXT =  "Budget type long text(30)

EXCEPTIONS
   NO_BUDTYPE = 1 

.

IMPORTING Parameters details for FMCU_CHECK_BUDTYPE

I_FM_AREA - Financial management 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_BUDTYPE - User defined budget type

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

I_FLG_BYPASS_BUFFER - Flag for by-passing buffer

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

EXPORTING Parameters details for FMCU_CHECK_BUDTYPE

E_FLG_ELIGIBILITY - Flag for Eligibility in Budgeting (set on: non eligible)

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

E_BUDTYPE_TXT5 - Budget type short text (5)

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

E_BUDTYPE_TXT20 - Budget type medium text (20)

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

E_BUDTYPE_TXT - Budget type long text(30)

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

EXCEPTIONS details

NO_BUDTYPE -

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

Copy and paste ABAP code example for FMCU_CHECK_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.

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

Search for further information about these or an SAP related objects