SAP FC_BCF Function Module for









FC_BCF is a standard fc bcf 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 fc bcf FM, simply by entering the name FC_BCF into the relevant SAP transaction such as SE37 or SE38.

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



Function FC_BCF 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 'FC_BCF'"
  EXPORTING
   E_RVERS =  "
*  E_DELETE_ZERO =  "
   ET_DATA =  "
   E_ITCLG =  "
*  E_DIMEN =  "
*  E_RYEAR =  "
*  ET_CU_CURR =  "
*  E_GCURR =  "
*  ET_FIELDS =  "
*  ET_KFIG =  "
*  E_PROT =  "

 IMPORTING
   IT_DATA =  "
   IT_BCF =  "
   IT_MESSAGE =  "

EXCEPTIONS
   FIELDNAME_WRONG = 1    FIELDNAME_MISSING = 2    VALUE_MISSING = 3
.



IMPORTING Parameters details for FC_BCF

E_RVERS -

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

E_DELETE_ZERO -

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

ET_DATA -

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

E_ITCLG -

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

E_DIMEN -

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

E_RYEAR -

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

ET_CU_CURR -

Data type: FC00_T_BCF_CU_CURR
Optional: Yes
Call by Reference: Yes

E_GCURR -

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

ET_FIELDS -

Data type: FC00_T_FIELDS
Optional: Yes
Call by Reference: Yes

ET_KFIG -

Data type: FC00_T_FIELDS
Optional: Yes
Call by Reference: Yes

E_PROT -

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

EXPORTING Parameters details for FC_BCF

IT_DATA -

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

IT_BCF -

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

IT_MESSAGE -

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

EXCEPTIONS details

FIELDNAME_WRONG -

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

FIELDNAME_MISSING -

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

VALUE_MISSING -

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

Copy and paste ABAP code example for FC_BCF 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_e_rvers  TYPE FC_RVERS, "   
lv_it_data  TYPE TABLE, "   
lv_fieldname_wrong  TYPE TABLE, "   
lv_e_delete_zero  TYPE FC_FLG, "   
lv_et_data  TYPE TABLE, "   
lv_it_bcf  TYPE FC00_T_BCF, "   
lv_e_itclg  TYPE FC_ITCLG, "   
lv_fieldname_missing  TYPE FC_ITCLG, "   
lv_e_dimen  TYPE FC_DIMEN, "   
lv_it_message  TYPE FC00_T_MESSAGE, "   
lv_value_missing  TYPE FC00_T_MESSAGE, "   
lv_e_ryear  TYPE FC_RYEAR, "   
lv_et_cu_curr  TYPE FC00_T_BCF_CU_CURR, "   
lv_e_gcurr  TYPE FC_CURRENCY, "   
lv_et_fields  TYPE FC00_T_FIELDS, "   
lv_et_kfig  TYPE FC00_T_FIELDS, "   
lv_e_prot  TYPE FC_FLG. "   

  CALL FUNCTION 'FC_BCF'  "
    EXPORTING
         E_RVERS = lv_e_rvers
         E_DELETE_ZERO = lv_e_delete_zero
         ET_DATA = lv_et_data
         E_ITCLG = lv_e_itclg
         E_DIMEN = lv_e_dimen
         E_RYEAR = lv_e_ryear
         ET_CU_CURR = lv_et_cu_curr
         E_GCURR = lv_e_gcurr
         ET_FIELDS = lv_et_fields
         ET_KFIG = lv_et_kfig
         E_PROT = lv_e_prot
    IMPORTING
         IT_DATA = lv_it_data
         IT_BCF = lv_it_bcf
         IT_MESSAGE = lv_it_message
    EXCEPTIONS
        FIELDNAME_WRONG = 1
        FIELDNAME_MISSING = 2
        VALUE_MISSING = 3
. " FC_BCF




ABAP code using 7.40 inline data declarations to call FM FC_BCF

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!