SAP FMCFBAPP_USE Function Module for









FMCFBAPP_USE is a standard fmcfbapp use 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 fmcfbapp use FM, simply by entering the name FMCFBAPP_USE 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 FMCFBAPP_USE 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 'FMCFBAPP_USE'"
EXPORTING
I_FIKRS = "
I_GJAHR = "

IMPORTING
E_USE_BAPP_PAY = "
E_USE_BAPP_COM = "
.




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 FMCFBAPP_USE

I_FIKRS -

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

I_GJAHR -

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

EXPORTING Parameters details for FMCFBAPP_USE

E_USE_BAPP_PAY -

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

E_USE_BAPP_COM -

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

Copy and paste ABAP code example for FMCFBAPP_USE 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_fikrs  TYPE FMCFBAPPUSE-FIKRS, "   
lv_e_use_bapp_pay  TYPE FMCFBAPPUSE-USE_BAPP_PAY, "   
lv_i_gjahr  TYPE FMCFBAPPUSE-GJAHR, "   
lv_e_use_bapp_com  TYPE FMCFBAPPUSE-USE_BAPP_COM. "   

  CALL FUNCTION 'FMCFBAPP_USE'  "
    EXPORTING
         I_FIKRS = lv_i_fikrs
         I_GJAHR = lv_i_gjahr
    IMPORTING
         E_USE_BAPP_PAY = lv_e_use_bapp_pay
         E_USE_BAPP_COM = lv_e_use_bapp_com
. " FMCFBAPP_USE




ABAP code using 7.40 inline data declarations to call FM FMCFBAPP_USE

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 FIKRS FROM FMCFBAPPUSE INTO @DATA(ld_i_fikrs).
 
"SELECT single USE_BAPP_PAY FROM FMCFBAPPUSE INTO @DATA(ld_e_use_bapp_pay).
 
"SELECT single GJAHR FROM FMCFBAPPUSE INTO @DATA(ld_i_gjahr).
 
"SELECT single USE_BAPP_COM FROM FMCFBAPPUSE INTO @DATA(ld_e_use_bapp_com).
 


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!