SAP ISP_MV_READ Function Module for









ISP_MV_READ is a standard isp mv read 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 isp mv read FM, simply by entering the name ISP_MV_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: JJG1
Program Name: SAPLJJG1
Main Program: SAPLJJG1
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISP_MV_READ 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 'ISP_MV_READ'"
EXPORTING
GPNR_IN = "
EKORG_IN = "
* BUKRS_IN = ' ' "

IMPORTING
MV_OUT = "
X_GESPERRT = "
X_LOESCHVM = "

EXCEPTIONS
DELETED = 1 NOT_EXISTS = 2 WRONG_PURCH_AREA = 3 WRONG_COMPANY_CODE = 4
.



IMPORTING Parameters details for ISP_MV_READ

GPNR_IN -

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

EKORG_IN -

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

BUKRS_IN -

Data type: T001-BUKRS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISP_MV_READ

MV_OUT -

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

X_GESPERRT -

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

X_LOESCHVM -

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

EXCEPTIONS details

DELETED -

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

NOT_EXISTS -

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

WRONG_PURCH_AREA -

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

WRONG_COMPANY_CODE -

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

Copy and paste ABAP code example for ISP_MV_READ 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_mv_out  TYPE JJVDB_MV, "   
lv_deleted  TYPE JJVDB_MV, "   
lv_gpnr_in  TYPE JGTGPNR-GPNR, "   
lv_ekorg_in  TYPE T024E-EKORG, "   
lv_not_exists  TYPE T024E, "   
lv_x_gesperrt  TYPE XFELD, "   
lv_bukrs_in  TYPE T001-BUKRS, "   SPACE
lv_x_loeschvm  TYPE XFELD, "   
lv_wrong_purch_area  TYPE XFELD, "   
lv_wrong_company_code  TYPE XFELD. "   

  CALL FUNCTION 'ISP_MV_READ'  "
    EXPORTING
         GPNR_IN = lv_gpnr_in
         EKORG_IN = lv_ekorg_in
         BUKRS_IN = lv_bukrs_in
    IMPORTING
         MV_OUT = lv_mv_out
         X_GESPERRT = lv_x_gesperrt
         X_LOESCHVM = lv_x_loeschvm
    EXCEPTIONS
        DELETED = 1
        NOT_EXISTS = 2
        WRONG_PURCH_AREA = 3
        WRONG_COMPANY_CODE = 4
. " ISP_MV_READ




ABAP code using 7.40 inline data declarations to call FM ISP_MV_READ

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 GPNR FROM JGTGPNR INTO @DATA(ld_gpnr_in).
 
"SELECT single EKORG FROM T024E INTO @DATA(ld_ekorg_in).
 
 
 
"SELECT single BUKRS FROM T001 INTO @DATA(ld_bukrs_in).
DATA(ld_bukrs_in) = ' '.
 
 
 
 


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!