SAP FMCU_GET_BS_CONTROL Function Module for Budget structure: Gets the assignment rule

Search SAP Function Modules

FMCU_GET_BS_CONTROL is a standard fmcu get bs control SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Budget structure: Gets the assignment rule 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 fmcu get bs control FM, simply by entering the name FMCU_GET_BS_CONTROL into the relevant SAP transaction such as SE37 or SE38.

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

Function FMCU_GET_BS_CONTROL 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 'FMCU_GET_BS_CONTROL'"Budget structure: Gets the assignment rule
  EXPORTING
   IM_FM_AREA =  "Financial Management Area
   IM_FISCYEAR =  "Fiscal Year
*  IM_VERSION = '' "Budget version
*  IM_PLDNR = '' "Posting Ledger Number

 IMPORTING
   E_ASS_RULE =  "Strategy for Deriving Budget Addresses
   E_FLG_PO_CHECK =  "Check the existence of posting object
   E_BS =  "Name of budget structure
   E_FLG_BS_HIERARCHICAL =  "Activate Hierarchical Functions
   E_FLG_NO_INDEX_UPDATE =  "No Budget Structure Index Update

EXCEPTIONS
   NO_CUSTOMIZING = 1    WRONG_INPUT = 2 

.

IMPORTING Parameters details for FMCU_GET_BS_CONTROL

IM_FM_AREA - Financial Management Area

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

IM_FISCYEAR - Fiscal Year

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

IM_VERSION - Budget version

Data type: BUKU_VERSION
Default: ''
Optional: No
Call by Reference: Yes

IM_PLDNR - Posting Ledger Number

Data type: BUBAS_PLDNR
Default: ''
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FMCU_GET_BS_CONTROL

E_ASS_RULE - Strategy for Deriving Budget Addresses

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

E_FLG_PO_CHECK - Check the existence of posting object

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

E_BS - Name of budget structure

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

E_FLG_BS_HIERARCHICAL - Activate Hierarchical Functions

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

E_FLG_NO_INDEX_UPDATE - No Budget Structure Index Update

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

EXCEPTIONS details

NO_CUSTOMIZING - no entry in fmbs_control

Data type:
Optional: No
Call by Reference: Yes

WRONG_INPUT - posting ledger must be supplied if e_po_check required

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMCU_GET_BS_CONTROL 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.

ABAP code using 7.40 inline data declarations to call FM FMCU_GET_BS_CONTROL

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