SAP Function Modules

FMCU_GET_BS_BO_CHECK SAP Function module - Budget structure: Check of budget objects active?







FMCU_GET_BS_BO_CHECK is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FMCU_GET_BS_BO_CHECK into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FMCU_BUSERVICE
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM FMCU_GET_BS_BO_CHECK - FMCU GET BS BO CHECK





CALL FUNCTION 'FMCU_GET_BS_BO_CHECK' "Budget structure: Check of budget objects active?
  EXPORTING
    im_fm_area =                " fikrs         Financial Management Area
    im_fiscyear =               " gjahr         Fiscal Year
    im_version =                " buku_version  Budget version
  IMPORTING
    e_flg_bo_check =            " fmbs_flg_bo_check  Environment for strategy
  EXCEPTIONS
    NO_CUSTOMIZING = 1          "               no entry in fmbs_control
    .  "  FMCU_GET_BS_BO_CHECK

ABAP code example for Function Module FMCU_GET_BS_BO_CHECK





The ABAP code below is a full code listing to execute function module FMCU_GET_BS_BO_CHECK including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_flg_bo_check  TYPE FMBS_FLG_BO_CHECK .

DATA(ld_im_fm_area) = 'Check type of data required'.
DATA(ld_im_fiscyear) = 'Check type of data required'.
DATA(ld_im_version) = 'Check type of data required'. . CALL FUNCTION 'FMCU_GET_BS_BO_CHECK' EXPORTING im_fm_area = ld_im_fm_area im_fiscyear = ld_im_fiscyear im_version = ld_im_version IMPORTING e_flg_bo_check = ld_e_flg_bo_check EXCEPTIONS NO_CUSTOMIZING = 1 . " FMCU_GET_BS_BO_CHECK
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_e_flg_bo_check  TYPE FMBS_FLG_BO_CHECK ,
ld_im_fm_area  TYPE FIKRS ,
ld_im_fiscyear  TYPE GJAHR ,
ld_im_version  TYPE BUKU_VERSION .

ld_im_fm_area = 'Check type of data required'.
ld_im_fiscyear = 'Check type of data required'.
ld_im_version = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FMCU_GET_BS_BO_CHECK or its description.