SAP MGV_GET_ALL_VALID_VERSIONS Function Module for









MGV_GET_ALL_VALID_VERSIONS is a standard mgv get all valid versions 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 get all valid versions FM, simply by entering the name MGV_GET_ALL_VALID_VERSIONS into the relevant SAP transaction such as SE37 or SE38.

Function Group: MGV_VALIDITY_CHECK
Program Name: SAPLMGV_VALIDITY_CHECK
Main Program: SAPLMGV_VALIDITY_CHECK
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MGV_GET_ALL_VALID_VERSIONS 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_GET_ALL_VALID_VERSIONS'"
EXPORTING
MATNR = "

CHANGING
* VALID_DATE = "

TABLES
VALID_MATNR = "

EXCEPTIONS
MATNR_NOT_FOUND = 1 INTERNAL_ERROR = 2
.



IMPORTING Parameters details for MGV_GET_ALL_VALID_VERSIONS

MATNR -

Data type: MATNR_INT
Optional: No
Call by Reference: Yes

CHANGING Parameters details for MGV_GET_ALL_VALID_VERSIONS

VALID_DATE -

Data type: D
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for MGV_GET_ALL_VALID_VERSIONS

VALID_MATNR -

Data type: PRE03
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

MATNR_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MGV_GET_ALL_VALID_VERSIONS 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_matnr  TYPE MATNR_INT, "   
lv_valid_date  TYPE D, "   
lt_valid_matnr  TYPE STANDARD TABLE OF PRE03, "   
lv_matnr_not_found  TYPE PRE03, "   
lv_internal_error  TYPE PRE03. "   

  CALL FUNCTION 'MGV_GET_ALL_VALID_VERSIONS'  "
    EXPORTING
         MATNR = lv_matnr
    CHANGING
         VALID_DATE = lv_valid_date
    TABLES
         VALID_MATNR = lt_valid_matnr
    EXCEPTIONS
        MATNR_NOT_FOUND = 1
        INTERNAL_ERROR = 2
. " MGV_GET_ALL_VALID_VERSIONS




ABAP code using 7.40 inline data declarations to call FM MGV_GET_ALL_VALID_VERSIONS

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!