SAP FMBAS_CHECK_FUNCAREA Function Module for Check Functional Area (including Validity Period)









FMBAS_CHECK_FUNCAREA is a standard fmbas check funcarea 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 Functional Area (including Validity Period) 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 fmbas check funcarea FM, simply by entering the name FMBAS_CHECK_FUNCAREA into the relevant SAP transaction such as SE37 or SE38.

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



Function FMBAS_CHECK_FUNCAREA 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 'FMBAS_CHECK_FUNCAREA'"Check Functional Area (including Validity Period)
EXPORTING
I_FM_AREA = "Financial Management Area
I_FUNCAREA = "Functional Area
* I_FISCYEAR = "Fiscal Year
* I_DATE = "Date

EXCEPTIONS
FUNCAREA_NOT_DEFINED = 1 FUNCAREA_NOT_VALID = 2
.



IMPORTING Parameters details for FMBAS_CHECK_FUNCAREA

I_FM_AREA - Financial Management Area

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

I_FUNCAREA - Functional Area

Data type: FMKU_S_DIMPART-FUNCAREA
Optional: No
Call by Reference: Yes

I_FISCYEAR - Fiscal Year

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

I_DATE - Date

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

EXCEPTIONS details

FUNCAREA_NOT_DEFINED - Functional area does not exist

Data type:
Optional: No
Call by Reference: Yes

FUNCAREA_NOT_VALID - Functional area not valid in fiscal year

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FMBAS_CHECK_FUNCAREA 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_fm_area  TYPE FIKRS, "   
lv_funcarea_not_defined  TYPE FIKRS, "   
lv_i_funcarea  TYPE FMKU_S_DIMPART-FUNCAREA, "   
lv_funcarea_not_valid  TYPE FMKU_S_DIMPART, "   
lv_i_fiscyear  TYPE GJAHR, "   
lv_i_date  TYPE DATUM. "   

  CALL FUNCTION 'FMBAS_CHECK_FUNCAREA'  "Check Functional Area (including Validity Period)
    EXPORTING
         I_FM_AREA = lv_i_fm_area
         I_FUNCAREA = lv_i_funcarea
         I_FISCYEAR = lv_i_fiscyear
         I_DATE = lv_i_date
    EXCEPTIONS
        FUNCAREA_NOT_DEFINED = 1
        FUNCAREA_NOT_VALID = 2
. " FMBAS_CHECK_FUNCAREA




ABAP code using 7.40 inline data declarations to call FM FMBAS_CHECK_FUNCAREA

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 FUNCAREA FROM FMKU_S_DIMPART INTO @DATA(ld_i_funcarea).
 
 
 
 


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!