SAP FM_LEDGER_CHECK_ACTIVE Function Module for To check if the Budgetary Ledger is active









FM_LEDGER_CHECK_ACTIVE is a standard fm ledger check active SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for To check if the Budgetary Ledger is active 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 fm ledger check active FM, simply by entering the name FM_LEDGER_CHECK_ACTIVE into the relevant SAP transaction such as SE37 or SE38.

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



Function FM_LEDGER_CHECK_ACTIVE 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 'FM_LEDGER_CHECK_ACTIVE'"To check if the Budgetary Ledger is active
EXPORTING
I_FM_AREA = "
* I_FLG_EXCEPTIONS = ' ' "Flag for returning exceptions

IMPORTING
E_FLG_ACTIVE = "
E_F_FM01 = "Financial Management Areas
E_FLG_ERROR = "Return Value, Return Value After ABAP Statements

EXCEPTIONS
INPUT_ERROR = 1 NOT_FOUND = 2 OTHER_ERROR = 3 NO_ENTRY_FOUND = 4 NO_ENTRY_FOUND_WRTTP = 5 WRTTP_PARAMETER_MISSING = 6
.



IMPORTING Parameters details for FM_LEDGER_CHECK_ACTIVE

I_FM_AREA -

Data type: FM01-FIKRS
Optional: No
Call by Reference: No ( called with pass by value option)

I_FLG_EXCEPTIONS - Flag for returning exceptions

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

EXPORTING Parameters details for FM_LEDGER_CHECK_ACTIVE

E_FLG_ACTIVE -

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

E_F_FM01 - Financial Management Areas

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

E_FLG_ERROR - Return Value, Return Value After ABAP Statements

Data type: SY-SUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INPUT_ERROR - When reading FM area (FMFK_FIKRS_READ)

Data type:
Optional: No
Call by Reference: Yes

NOT_FOUND - When reading FM area (FMFK_FIKRS_READ)

Data type:
Optional: No
Call by Reference: Yes

OTHER_ERROR - When reading FM area (FMFK_FIKRS_READ)

Data type:
Optional: No
Call by Reference: Yes

NO_ENTRY_FOUND - From FM_CONTROL_DATA_GET

Data type:
Optional: No
Call by Reference: Yes

NO_ENTRY_FOUND_WRTTP - From FM_CONTROL_DATA_GET

Data type:
Optional: No
Call by Reference: Yes

WRTTP_PARAMETER_MISSING - From FM_CONTROL_DATA_GET

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FM_LEDGER_CHECK_ACTIVE 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 FM01-FIKRS, "   
lv_input_error  TYPE FM01, "   
lv_e_flg_active  TYPE FMDY-XFELD, "   
lv_e_f_fm01  TYPE FM01, "   
lv_not_found  TYPE FM01, "   
lv_i_flg_exceptions  TYPE C, "   SPACE
lv_e_flg_error  TYPE SY-SUBRC, "   
lv_other_error  TYPE SY, "   
lv_no_entry_found  TYPE SY, "   
lv_no_entry_found_wrttp  TYPE SY, "   
lv_wrttp_parameter_missing  TYPE SY. "   

  CALL FUNCTION 'FM_LEDGER_CHECK_ACTIVE'  "To check if the Budgetary Ledger is active
    EXPORTING
         I_FM_AREA = lv_i_fm_area
         I_FLG_EXCEPTIONS = lv_i_flg_exceptions
    IMPORTING
         E_FLG_ACTIVE = lv_e_flg_active
         E_F_FM01 = lv_e_f_fm01
         E_FLG_ERROR = lv_e_flg_error
    EXCEPTIONS
        INPUT_ERROR = 1
        NOT_FOUND = 2
        OTHER_ERROR = 3
        NO_ENTRY_FOUND = 4
        NO_ENTRY_FOUND_WRTTP = 5
        WRTTP_PARAMETER_MISSING = 6
. " FM_LEDGER_CHECK_ACTIVE




ABAP code using 7.40 inline data declarations to call FM FM_LEDGER_CHECK_ACTIVE

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 FIKRS FROM FM01 INTO @DATA(ld_i_fm_area).
 
 
"SELECT single XFELD FROM FMDY INTO @DATA(ld_e_flg_active).
 
 
 
DATA(ld_i_flg_exceptions) = ' '.
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_e_flg_error).
 
 
 
 
 


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!