SAP FMCU_CHECK_BUDTYPECOMB Function Module for Check existence of budget type for a process (use this one!)









FMCU_CHECK_BUDTYPECOMB is a standard fmcu check budtypecomb 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 for a process (use this one!) 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 budtypecomb FM, simply by entering the name FMCU_CHECK_BUDTYPECOMB 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_BUDTYPECOMB 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_BUDTYPECOMB'"Check existence of budget type for a process (use this one!)
EXPORTING
I_FM_AREA = "Financial management area
I_PROCESS = "Process
I_VALTYPE = "Value Type
I_BUDTYPE = "User defined budget type
* I_NO_MAN = "No manual posting allowed
* I_FLG_BYPASS_BUFFER = ' ' "Flag for by-passing buffer

IMPORTING
E_BUDTYPE_TXT = "Budget type long text(30)

EXCEPTIONS
NO_BUDTYPE = 1
.



IMPORTING Parameters details for FMCU_CHECK_BUDTYPECOMB

I_FM_AREA - Financial management area

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

I_PROCESS - Process

Data type: BUKU_PROCESS
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_NO_MAN - No manual posting allowed

Data type: BUCU_NO_MAN
Optional: Yes
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_CHECK_BUDTYPECOMB

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_BUDTYPECOMB 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_budtype  TYPE FIKRS, "   
lv_e_budtype_txt  TYPE BUCU_BTYP30, "   
lv_i_process  TYPE BUKU_PROCESS, "   
lv_i_valtype  TYPE BUKU_VALTYPE, "   
lv_i_budtype  TYPE BUKU_BUDTYPE, "   
lv_i_no_man  TYPE BUCU_NO_MAN, "   
lv_i_flg_bypass_buffer  TYPE XFELD. "   ' '

  CALL FUNCTION 'FMCU_CHECK_BUDTYPECOMB'  "Check existence of budget type for a process (use this one!)
    EXPORTING
         I_FM_AREA = lv_i_fm_area
         I_PROCESS = lv_i_process
         I_VALTYPE = lv_i_valtype
         I_BUDTYPE = lv_i_budtype
         I_NO_MAN = lv_i_no_man
         I_FLG_BYPASS_BUFFER = lv_i_flg_bypass_buffer
    IMPORTING
         E_BUDTYPE_TXT = lv_e_budtype_txt
    EXCEPTIONS
        NO_BUDTYPE = 1
. " FMCU_CHECK_BUDTYPECOMB




ABAP code using 7.40 inline data declarations to call FM FMCU_CHECK_BUDTYPECOMB

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!