SAP FMBCFF_CF_ALLOWED Function Module for Gener. of bdgt entry docs for cmt. carrd over allowed for bdgt. catg/valtp









FMBCFF_CF_ALLOWED is a standard fmbcff cf allowed SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Gener. of bdgt entry docs for cmt. carrd over allowed for bdgt. catg/valtp 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 fmbcff cf allowed FM, simply by entering the name FMBCFF_CF_ALLOWED into the relevant SAP transaction such as SE37 or SE38.

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



Function FMBCFF_CF_ALLOWED 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 'FMBCFF_CF_ALLOWED'"Gener. of bdgt entry docs for cmt. carrd over allowed for bdgt. catg/valtp
  EXPORTING
   I_FM_AREA =  "Financial Management Area
   I_SENDER_YEAR =  "
   I_UPD_VALUE_TYPE =  "Value type
   I_BUDCAT =  "Budget category

EXCEPTIONS
   NOT_ALLOWED = 1
.



IMPORTING Parameters details for FMBCFF_CF_ALLOWED

I_FM_AREA - Financial Management Area

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

I_SENDER_YEAR -

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

I_UPD_VALUE_TYPE - Value type

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

I_BUDCAT - Budget category

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

EXCEPTIONS details

NOT_ALLOWED - Creation of bdgt entry docs for commitments carried over is not allowed

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMBCFF_CF_ALLOWED 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_not_allowed  TYPE FIKRS, "   
lv_i_sender_year  TYPE FM_CCF_SYEAR, "   
lv_i_upd_value_type  TYPE FM_WRTTP, "   
lv_i_budcat  TYPE BUKU_BUDCAT. "   

  CALL FUNCTION 'FMBCFF_CF_ALLOWED'  "Gener. of bdgt entry docs for cmt. carrd over allowed for bdgt. catg/valtp
    EXPORTING
         I_FM_AREA = lv_i_fm_area
         I_SENDER_YEAR = lv_i_sender_year
         I_UPD_VALUE_TYPE = lv_i_upd_value_type
         I_BUDCAT = lv_i_budcat
    EXCEPTIONS
        NOT_ALLOWED = 1
. " FMBCFF_CF_ALLOWED




ABAP code using 7.40 inline data declarations to call FM FMBCFF_CF_ALLOWED

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



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!