SAP BUDGET_INCREASED_CHECK Function Module for









BUDGET_INCREASED_CHECK is a standard budget increased check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 budget increased check FM, simply by entering the name BUDGET_INCREASED_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMUD
Program Name: SAPLFMUD
Main Program: SAPLFMUD
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BUDGET_INCREASED_CHECK 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 'BUDGET_INCREASED_CHECK'"
EXPORTING
IP_BUDAT = "
IP_BUKRS = "
IP_BZDAT = "
IP_DOCTYP = "
IP_FIKRS = "
* IP_FORECAST = "
IP_ITABKEY = "
* IP_RECOVERY_ORDER = "
* IP_SENDER = "

IMPORTING
OP_BUDGET_INCREASED = "
OP_RELEVANT_BUDGET_INCREASING = "
OP_FORECAST_NECESSARY = "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLFMUD_001 Check Compatibility of Output Addresses for Cmmt Bdgt and Payment Budget
EXIT_SAPLFMUD_002 Do not use! Check whether the commitment budget is to be increased
EXIT_SAPLFMUD_003 Check Whether a Forecast Is Required
EXIT_SAPLFMUD_004 User-Specific Check of Expend. FM Acct Assgt for Cmmt Bdgt and Payt Bdgt
EXIT_SAPLFMUD_005 Do not use! Check whether the commitment budget is to be increased
EXIT_SAPLFMUD_006 Determine Value Type for which a Revenues FM Account Assgnt Increases Bdgt

IMPORTING Parameters details for BUDGET_INCREASED_CHECK

IP_BUDAT -

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

IP_BUKRS -

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

IP_BZDAT -

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

IP_DOCTYP -

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

IP_FIKRS -

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

IP_FORECAST -

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

IP_ITABKEY -

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

IP_RECOVERY_ORDER -

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

IP_SENDER -

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

EXPORTING Parameters details for BUDGET_INCREASED_CHECK

OP_BUDGET_INCREASED -

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

OP_RELEVANT_BUDGET_INCREASING -

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

OP_FORECAST_NECESSARY -

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

Copy and paste ABAP code example for BUDGET_INCREASED_CHECK 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_ip_budat  TYPE COBL-BUDAT, "   
lv_op_budget_increased  TYPE FMDY-XFELD, "   
lv_ip_bukrs  TYPE COBL-BUKRS, "   
lv_op_relevant_budget_increasing  TYPE FMDY-XFELD, "   
lv_ip_bzdat  TYPE COBL-BZDAT, "   
lv_op_forecast_necessary  TYPE FMDY-XFELD, "   
lv_ip_doctyp  TYPE BKPF-BLART, "   
lv_ip_fikrs  TYPE FM01-FIKRS, "   
lv_ip_forecast  TYPE FMUD_FCDOC, "   
lv_ip_itabkey  TYPE IFMUDECK-ITABKEY, "   
lv_ip_recovery_order  TYPE FMUD_RODOC, "   
lv_ip_sender  TYPE FMUD_HOLDER. "   

  CALL FUNCTION 'BUDGET_INCREASED_CHECK'  "
    EXPORTING
         IP_BUDAT = lv_ip_budat
         IP_BUKRS = lv_ip_bukrs
         IP_BZDAT = lv_ip_bzdat
         IP_DOCTYP = lv_ip_doctyp
         IP_FIKRS = lv_ip_fikrs
         IP_FORECAST = lv_ip_forecast
         IP_ITABKEY = lv_ip_itabkey
         IP_RECOVERY_ORDER = lv_ip_recovery_order
         IP_SENDER = lv_ip_sender
    IMPORTING
         OP_BUDGET_INCREASED = lv_op_budget_increased
         OP_RELEVANT_BUDGET_INCREASING = lv_op_relevant_budget_increasing
         OP_FORECAST_NECESSARY = lv_op_forecast_necessary
. " BUDGET_INCREASED_CHECK




ABAP code using 7.40 inline data declarations to call FM BUDGET_INCREASED_CHECK

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.

"SELECT single BUDAT FROM COBL INTO @DATA(ld_ip_budat).
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_op_budget_increased).
 
"SELECT single BUKRS FROM COBL INTO @DATA(ld_ip_bukrs).
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_op_relevant_budget_increasing).
 
"SELECT single BZDAT FROM COBL INTO @DATA(ld_ip_bzdat).
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_op_forecast_necessary).
 
"SELECT single BLART FROM BKPF INTO @DATA(ld_ip_doctyp).
 
"SELECT single FIKRS FROM FM01 INTO @DATA(ld_ip_fikrs).
 
 
"SELECT single ITABKEY FROM IFMUDECK INTO @DATA(ld_ip_itabkey).
 
 
 


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!