SAP FMFG_CHECK_FMAREAR_FOR_BLEXT Function Module for Check, whether this fmarea can be used for the BL ext.
FMFG_CHECK_FMAREAR_FOR_BLEXT is a standard fmfg check fmarear for blext SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check, whether this fmarea can be used for the BL ext. 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 fmfg check fmarear for blext FM, simply by entering the name FMFG_CHECK_FMAREAR_FOR_BLEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMFG_BLEXTCHECK
Program Name: SAPLFMFG_BLEXTCHECK
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMFG_CHECK_FMAREAR_FOR_BLEXT 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 'FMFG_CHECK_FMAREAR_FOR_BLEXT'"Check, whether this fmarea can be used for the BL ext..
EXPORTING
I_FMAREA = "Financial Management Area
EXCEPTIONS
WRONG_PROFILE = 1 WRONG_GR_INV_UPDATING = 2 FMAREA_READ_ERROR = 3
IMPORTING Parameters details for FMFG_CHECK_FMAREAR_FOR_BLEXT
I_FMAREA - Financial Management Area
Data type: FIKRSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_PROFILE - Wrong update profile is being used
Data type:Optional: No
Call by Reference: Yes
WRONG_GR_INV_UPDATING - Wrong customizing for GR updating
Data type:Optional: No
Call by Reference: Yes
FMAREA_READ_ERROR - Error while reading the customizing of fm
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FMFG_CHECK_FMAREAR_FOR_BLEXT 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_fmarea | TYPE FIKRS, " | |||
| lv_wrong_profile | TYPE FIKRS, " | |||
| lv_wrong_gr_inv_updating | TYPE FIKRS, " | |||
| lv_fmarea_read_error | TYPE FIKRS. " |
|   CALL FUNCTION 'FMFG_CHECK_FMAREAR_FOR_BLEXT' "Check, whether this fmarea can be used for the BL ext. |
| EXPORTING | ||
| I_FMAREA | = lv_i_fmarea | |
| EXCEPTIONS | ||
| WRONG_PROFILE = 1 | ||
| WRONG_GR_INV_UPDATING = 2 | ||
| FMAREA_READ_ERROR = 3 | ||
| . " FMFG_CHECK_FMAREAR_FOR_BLEXT | ||
ABAP code using 7.40 inline data declarations to call FM FMFG_CHECK_FMAREAR_FOR_BLEXT
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