SAP MGV_MAINTAIN_VALIDITY Function Module for
MGV_MAINTAIN_VALIDITY is a standard mgv maintain validity 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 mgv maintain validity FM, simply by entering the name MGV_MAINTAIN_VALIDITY into the relevant SAP transaction such as SE37 or SE38.
Function Group: MGV_MAINTAIN_VERSIONS
Program Name: SAPLMGV_MAINTAIN_VERSIONS
Main Program: SAPLMGV_MAINTAIN_VERSIONS
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MGV_MAINTAIN_VALIDITY 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 'MGV_MAINTAIN_VALIDITY'".
EXPORTING
IV_NEUFLAG = "
IV_MATNR = "
* IV_AKTYP = 'V' "
IV_RMMG1 = "
IV_AKTVSTATUS = "
IMPORTING Parameters details for MGV_MAINTAIN_VALIDITY
IV_NEUFLAG -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
IV_MATNR -
Data type: MARA-MATNROptional: No
Call by Reference: No ( called with pass by value option)
IV_AKTYP -
Data type: T130M-AKTYPDefault: 'V'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_RMMG1 -
Data type: RMMG1Optional: No
Call by Reference: No ( called with pass by value option)
IV_AKTVSTATUS -
Data type: T130M-PSTATOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MGV_MAINTAIN_VALIDITY 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_iv_neuflag | TYPE C, " | |||
| lv_iv_matnr | TYPE MARA-MATNR, " | |||
| lv_iv_aktyp | TYPE T130M-AKTYP, " 'V' | |||
| lv_iv_rmmg1 | TYPE RMMG1, " | |||
| lv_iv_aktvstatus | TYPE T130M-PSTAT. " |
|   CALL FUNCTION 'MGV_MAINTAIN_VALIDITY' " |
| EXPORTING | ||
| IV_NEUFLAG | = lv_iv_neuflag | |
| IV_MATNR | = lv_iv_matnr | |
| IV_AKTYP | = lv_iv_aktyp | |
| IV_RMMG1 | = lv_iv_rmmg1 | |
| IV_AKTVSTATUS | = lv_iv_aktvstatus | |
| . " MGV_MAINTAIN_VALIDITY | ||
ABAP code using 7.40 inline data declarations to call FM MGV_MAINTAIN_VALIDITY
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.| "SELECT single MATNR FROM MARA INTO @DATA(ld_iv_matnr). | ||||
| "SELECT single AKTYP FROM T130M INTO @DATA(ld_iv_aktyp). | ||||
| DATA(ld_iv_aktyp) | = 'V'. | |||
| "SELECT single PSTAT FROM T130M INTO @DATA(ld_iv_aktvstatus). | ||||
Search for further information about these or an SAP related objects