SAP FMCF_BUD_GET_MAX_CF_USER Function Module for

Search SAP Function Modules

FMCF_BUD_GET_MAX_CF_USER is a standard fmcf bud get max cf user 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 fmcf bud get max cf user FM, simply by entering the name FMCF_BUD_GET_MAX_CF_USER into the relevant SAP transaction such as SE37 or SE38.

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

Function FMCF_BUD_GET_MAX_CF_USER 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 'FMCF_BUD_GET_MAX_CF_USER'"
  EXPORTING
   I_F_HEADER =  "
   I_F_OBJECTS =  "
*  I_BTR_DOC_CF =  "
*  I_BTR_BOB_POSS =  "
*  I_CHECK_ONLY_USER_CALC =  "

 IMPORTING
   E_BUDGET_REST_USER =  "
   E_FLG_USER_CALCULATION =  "

TABLES
*  T_BUDGET =  "

.

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_SAPLFMCF_BUD_001 ISPS: FYC Budget: Calculation Maximum Transferable Amount
EXIT_SAPLFMCF_BUD_002 ISPS: FYC Budget: Can Approved/Requested Amount Be Negative

IMPORTING Parameters details for FMCF_BUD_GET_MAX_CF_USER

I_F_HEADER -

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

I_F_OBJECTS -

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

I_BTR_DOC_CF -

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

I_BTR_BOB_POSS -

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

I_CHECK_ONLY_USER_CALC -

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

EXPORTING Parameters details for FMCF_BUD_GET_MAX_CF_USER

E_BUDGET_REST_USER -

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

E_FLG_USER_CALCULATION -

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

TABLES Parameters details for FMCF_BUD_GET_MAX_CF_USER

T_BUDGET -

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

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

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