SAP FM_CHECK_MULTIANNUAL Function Module for
FM_CHECK_MULTIANNUAL is a standard fm check multiannual SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 check multiannual FM, simply by entering the name FM_CHECK_MULTIANNUAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMMA
Program Name: SAPLFMMA
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_CHECK_MULTIANNUAL 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_CHECK_MULTIANNUAL'".
EXPORTING
I_FIKRS = "
IMPORTING
E_FLG_MULTIANNUAL = "
EXCEPTIONS
NO_FMAREA = 1
IMPORTING Parameters details for FM_CHECK_MULTIANNUAL
I_FIKRS -
Data type: FIKRSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FM_CHECK_MULTIANNUAL
E_FLG_MULTIANNUAL -
Data type: FM_MULTIANNUAL_FMUPDATEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_FMAREA -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FM_CHECK_MULTIANNUAL 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_fikrs | TYPE FIKRS, " | |||
| lv_no_fmarea | TYPE FIKRS, " | |||
| lv_e_flg_multiannual | TYPE FM_MULTIANNUAL_FMUPDATE. " |
|   CALL FUNCTION 'FM_CHECK_MULTIANNUAL' " |
| EXPORTING | ||
| I_FIKRS | = lv_i_fikrs | |
| IMPORTING | ||
| E_FLG_MULTIANNUAL | = lv_e_flg_multiannual | |
| EXCEPTIONS | ||
| NO_FMAREA = 1 | ||
| . " FM_CHECK_MULTIANNUAL | ||
ABAP code using 7.40 inline data declarations to call FM FM_CHECK_MULTIANNUAL
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