SAP MEV_DB_BO_ITEM_MM_DEL Function Module for Period-End Valuation: Delete AD Item MM Data
MEV_DB_BO_ITEM_MM_DEL is a standard mev db bo item mm del SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Period-End Valuation: Delete AD Item MM Data 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 mev db bo item mm del FM, simply by entering the name MEV_DB_BO_ITEM_MM_DEL into the relevant SAP transaction such as SE37 or SE38.
Function Group: MEV_BO_DB_UPD
Program Name: SAPLMEV_BO_DB_UPD
Main Program: SAPLMEV_BO_DB_UPD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function MEV_DB_BO_ITEM_MM_DEL 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 'MEV_DB_BO_ITEM_MM_DEL'"Period-End Valuation: Delete AD Item MM Data.
EXPORTING
IT_DATA = "Period-End Valuation: Sorted Table of MEV_D_AD_ITEM_MM
EXCEPTIONS
DB_ERROR = 1
IMPORTING Parameters details for MEV_DB_BO_ITEM_MM_DEL
IT_DATA - Period-End Valuation: Sorted Table of MEV_D_AD_ITEM_MM
Data type: MEV_T_BO_AD_ITEM_MM_STOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DB_ERROR - Database Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for MEV_DB_BO_ITEM_MM_DEL 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_it_data | TYPE MEV_T_BO_AD_ITEM_MM_ST, " | |||
| lv_db_error | TYPE MEV_T_BO_AD_ITEM_MM_ST. " |
|   CALL FUNCTION 'MEV_DB_BO_ITEM_MM_DEL' "Period-End Valuation: Delete AD Item MM Data |
| EXPORTING | ||
| IT_DATA | = lv_it_data | |
| EXCEPTIONS | ||
| DB_ERROR = 1 | ||
| . " MEV_DB_BO_ITEM_MM_DEL | ||
ABAP code using 7.40 inline data declarations to call FM MEV_DB_BO_ITEM_MM_DEL
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