SAP MV_ADJUST_TYPE_MAINTAIN Function Module for
MV_ADJUST_TYPE_MAINTAIN is a standard mv adjust type maintain 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 mv adjust type maintain FM, simply by entering the name MV_ADJUST_TYPE_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVMD
Program Name: SAPLFVMD
Main Program: SAPLFVMD
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MV_ADJUST_TYPE_MAINTAIN 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 'MV_ADJUST_TYPE_MAINTAIN'".
EXPORTING
* I_KZ_SAVE_ON_COMMIT = ' ' "
* I_KZ_SHOW_ONLY = ' ' "
* I_KZ_RECN = ' ' "
I_VIMIMV = "
I_JTYPNUA = "
* I_SMIETR = ' ' "
IMPORTING
E_KZ_CHANGED = "
E_SMVANART = "
E_SMVANART_PRIMARY = "
E_JDIVANP = "
E_ADJT_BEG = "
E_ADJT_END = "
IMPORTING Parameters details for MV_ADJUST_TYPE_MAINTAIN
I_KZ_SAVE_ON_COMMIT -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_KZ_SHOW_ONLY -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_KZ_RECN -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VIMIMV -
Data type: VIMIMVOptional: No
Call by Reference: No ( called with pass by value option)
I_JTYPNUA -
Data type: RTIV01_13-JTYPNUAOptional: No
Call by Reference: No ( called with pass by value option)
I_SMIETR -
Data type: SMIETRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MV_ADJUST_TYPE_MAINTAIN
E_KZ_CHANGED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_SMVANART -
Data type: VIMIMV-SMVANARTOptional: No
Call by Reference: No ( called with pass by value option)
E_SMVANART_PRIMARY -
Data type: VIMIMV-SMVANARTOptional: No
Call by Reference: No ( called with pass by value option)
E_JDIVANP -
Data type: RF60V-JDIVANPOptional: No
Call by Reference: No ( called with pass by value option)
E_ADJT_BEG -
Data type: VIMI54-DGABANRTOptional: No
Call by Reference: No ( called with pass by value option)
E_ADJT_END -
Data type: VIMI54-DBISANRTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MV_ADJUST_TYPE_MAINTAIN 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_e_kz_changed | TYPE STRING, " | |||
| lv_i_kz_save_on_commit | TYPE STRING, " SPACE | |||
| lv_e_smvanart | TYPE VIMIMV-SMVANART, " | |||
| lv_i_kz_show_only | TYPE VIMIMV, " SPACE | |||
| lv_i_kz_recn | TYPE VIMIMV, " SPACE | |||
| lv_e_smvanart_primary | TYPE VIMIMV-SMVANART, " | |||
| lv_i_vimimv | TYPE VIMIMV, " | |||
| lv_e_jdivanp | TYPE RF60V-JDIVANP, " | |||
| lv_i_jtypnua | TYPE RTIV01_13-JTYPNUA, " | |||
| lv_e_adjt_beg | TYPE VIMI54-DGABANRT, " | |||
| lv_i_smietr | TYPE SMIETR, " SPACE | |||
| lv_e_adjt_end | TYPE VIMI54-DBISANRT. " |
|   CALL FUNCTION 'MV_ADJUST_TYPE_MAINTAIN' " |
| EXPORTING | ||
| I_KZ_SAVE_ON_COMMIT | = lv_i_kz_save_on_commit | |
| I_KZ_SHOW_ONLY | = lv_i_kz_show_only | |
| I_KZ_RECN | = lv_i_kz_recn | |
| I_VIMIMV | = lv_i_vimimv | |
| I_JTYPNUA | = lv_i_jtypnua | |
| I_SMIETR | = lv_i_smietr | |
| IMPORTING | ||
| E_KZ_CHANGED | = lv_e_kz_changed | |
| E_SMVANART | = lv_e_smvanart | |
| E_SMVANART_PRIMARY | = lv_e_smvanart_primary | |
| E_JDIVANP | = lv_e_jdivanp | |
| E_ADJT_BEG | = lv_e_adjt_beg | |
| E_ADJT_END | = lv_e_adjt_end | |
| . " MV_ADJUST_TYPE_MAINTAIN | ||
ABAP code using 7.40 inline data declarations to call FM MV_ADJUST_TYPE_MAINTAIN
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.| DATA(ld_i_kz_save_on_commit) | = ' '. | |||
| "SELECT single SMVANART FROM VIMIMV INTO @DATA(ld_e_smvanart). | ||||
| DATA(ld_i_kz_show_only) | = ' '. | |||
| DATA(ld_i_kz_recn) | = ' '. | |||
| "SELECT single SMVANART FROM VIMIMV INTO @DATA(ld_e_smvanart_primary). | ||||
| "SELECT single JDIVANP FROM RF60V INTO @DATA(ld_e_jdivanp). | ||||
| "SELECT single JTYPNUA FROM RTIV01_13 INTO @DATA(ld_i_jtypnua). | ||||
| "SELECT single DGABANRT FROM VIMI54 INTO @DATA(ld_e_adjt_beg). | ||||
| DATA(ld_i_smietr) | = ' '. | |||
| "SELECT single DBISANRT FROM VIMI54 INTO @DATA(ld_e_adjt_end). | ||||
Search for further information about these or an SAP related objects