SAP MD_MDVM_TABLE Function Module for Create planning file entries with transfer of item table
MD_MDVM_TABLE is a standard md mdvm table SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create planning file entries with transfer of item table 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 md mdvm table FM, simply by entering the name MD_MDVM_TABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: DISP
Program Name: SAPLDISP
Main Program: SAPLDISP
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MD_MDVM_TABLE 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 'MD_MDVM_TABLE'"Create planning file entries with transfer of item table.
EXPORTING
IMDCP = "
TABLES
ALTTAB = "
NEUTAB = "
IMPORTING Parameters details for MD_MDVM_TABLE
IMDCP -
Data type: MDCPOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MD_MDVM_TABLE
ALTTAB -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NEUTAB -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MD_MDVM_TABLE 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_imdcp | TYPE MDCP, " | |||
| lt_alttab | TYPE STANDARD TABLE OF MDCP, " | |||
| lt_neutab | TYPE STANDARD TABLE OF MDCP. " |
|   CALL FUNCTION 'MD_MDVM_TABLE' "Create planning file entries with transfer of item table |
| EXPORTING | ||
| IMDCP | = lv_imdcp | |
| TABLES | ||
| ALTTAB | = lt_alttab | |
| NEUTAB | = lt_neutab | |
| . " MD_MDVM_TABLE | ||
ABAP code using 7.40 inline data declarations to call FM MD_MDVM_TABLE
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