SAP FM_MEASURE_CHECK_DELETION Function Module for Check deletion allowed
FM_MEASURE_CHECK_DELETION is a standard fm measure check deletion 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 deletion allowed 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 measure check deletion FM, simply by entering the name FM_MEASURE_CHECK_DELETION into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMME4
Program Name: SAPLFMME4
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FM_MEASURE_CHECK_DELETION 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_MEASURE_CHECK_DELETION'"Check deletion allowed.
EXPORTING
I_FMAREA = "Financial Management Area
I_MEASURE = "Measure in Funds Management
EXCEPTIONS
DELETION_NOT_ALLOWED = 1 INPUT_ERROR = 2
IMPORTING Parameters details for FM_MEASURE_CHECK_DELETION
I_FMAREA - Financial Management Area
Data type: FIKRSOptional: No
Call by Reference: Yes
I_MEASURE - Measure in Funds Management
Data type: FM_MEASUREOptional: No
Call by Reference: Yes
EXCEPTIONS details
DELETION_NOT_ALLOWED - Deletion is not allowed
Data type:Optional: No
Call by Reference: Yes
INPUT_ERROR - FM area or measure empty
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FM_MEASURE_CHECK_DELETION 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_deletion_not_allowed | TYPE FIKRS, " | |||
| lv_i_measure | TYPE FM_MEASURE, " | |||
| lv_input_error | TYPE FM_MEASURE. " |
|   CALL FUNCTION 'FM_MEASURE_CHECK_DELETION' "Check deletion allowed |
| EXPORTING | ||
| I_FMAREA | = lv_i_fmarea | |
| I_MEASURE | = lv_i_measure | |
| EXCEPTIONS | ||
| DELETION_NOT_ALLOWED = 1 | ||
| INPUT_ERROR = 2 | ||
| . " FM_MEASURE_CHECK_DELETION | ||
ABAP code using 7.40 inline data declarations to call FM FM_MEASURE_CHECK_DELETION
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