SAP BP_CHECK_FUNDS_FM Function Module for









BP_CHECK_FUNDS_FM is a standard bp check funds fm 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 bp check funds fm FM, simply by entering the name BP_CHECK_FUNDS_FM into the relevant SAP transaction such as SE37 or SE38.

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



Function BP_CHECK_FUNDS_FM 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 'BP_CHECK_FUNDS_FM'"
EXPORTING
* I_ORGVG = 'FIFM' "Activity group for determining threshold values
* I_ORGVG_SUPPL = ' ' "
* I_CHECK_FUNDS = 'X' "Carry out check yes ('X')/no (' ')
* I_CHECK_FUNDS_FORCE = ' ' "Checks even when value = 0, that is no change
* I_LEVEL_VG = ' ' "
* I_ENQUEUE = 'X' "Set lock yes ('X')/no (' ')

TABLES
* T_AVC_PAY = "Payments
* T_AVC_COM = "Commitments
.




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_SAPLBPFC_001 User Exist: Define Mail Recipients
EXIT_SAPLBPFC_002 User-Exit: Specification of the Action for the Availability Control
EXIT_SAPLBPFC_003 User Exit: Substitution of Functional Area's Commitment/Actual to Be Chkd

IMPORTING Parameters details for BP_CHECK_FUNDS_FM

I_ORGVG - Activity group for determining threshold values

Data type: COBK-ORGVG
Default: 'FIFM'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ORGVG_SUPPL -

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

I_CHECK_FUNDS - Carry out check yes ('X')/no (' ')

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

I_CHECK_FUNDS_FORCE - Checks even when value = 0, that is no change

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

I_LEVEL_VG -

Data type: COBK-ORGVG
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ENQUEUE - Set lock yes ('X')/no (' ')

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

TABLES Parameters details for BP_CHECK_FUNDS_FM

T_AVC_PAY - Payments

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

T_AVC_COM - Commitments

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

Copy and paste ABAP code example for BP_CHECK_FUNDS_FM 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_orgvg  TYPE COBK-ORGVG, "   'FIFM'
lt_t_avc_pay  TYPE STANDARD TABLE OF FMFI_T_AVC, "   
lt_t_avc_com  TYPE STANDARD TABLE OF FMFI_T_AVC, "   
lv_i_orgvg_suppl  TYPE FMFI_T_AVC, "   ' '
lv_i_check_funds  TYPE FMDY-XFELD, "   'X'
lv_i_check_funds_force  TYPE FMDY-XFELD, "   ' '
lv_i_level_vg  TYPE COBK-ORGVG, "   ' '
lv_i_enqueue  TYPE FMDY-XFELD. "   'X'

  CALL FUNCTION 'BP_CHECK_FUNDS_FM'  "
    EXPORTING
         I_ORGVG = lv_i_orgvg
         I_ORGVG_SUPPL = lv_i_orgvg_suppl
         I_CHECK_FUNDS = lv_i_check_funds
         I_CHECK_FUNDS_FORCE = lv_i_check_funds_force
         I_LEVEL_VG = lv_i_level_vg
         I_ENQUEUE = lv_i_enqueue
    TABLES
         T_AVC_PAY = lt_t_avc_pay
         T_AVC_COM = lt_t_avc_com
. " BP_CHECK_FUNDS_FM




ABAP code using 7.40 inline data declarations to call FM BP_CHECK_FUNDS_FM

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 ORGVG FROM COBK INTO @DATA(ld_i_orgvg).
DATA(ld_i_orgvg) = 'FIFM'.
 
 
 
DATA(ld_i_orgvg_suppl) = ' '.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_check_funds).
DATA(ld_i_check_funds) = 'X'.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_check_funds_force).
DATA(ld_i_check_funds_force) = ' '.
 
"SELECT single ORGVG FROM COBK INTO @DATA(ld_i_level_vg).
DATA(ld_i_level_vg) = ' '.
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_enqueue).
DATA(ld_i_enqueue) = 'X'.
 


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!