SAP MILL_VS_SAVE_SHADOWED_DB Function Module for









MILL_VS_SAVE_SHADOWED_DB is a standard mill vs save shadowed db 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 mill vs save shadowed db FM, simply by entering the name MILL_VS_SAVE_SHADOWED_DB into the relevant SAP transaction such as SE37 or SE38.

Function Group: MILL_VS
Program Name: SAPLMILL_VS
Main Program: SAPLMILL_VS
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function MILL_VS_SAVE_SHADOWED_DB 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 'MILL_VS_SAVE_SHADOWED_DB'"
  EXPORTING
   IF_VSNMR =  "
   IS_VBAK =  "
   IS_YVBAK =  "
   IF_YVBAK_UPDKZ =  "

TABLES
   FXVBUP =  "
   FYVBEP =  "
   FYVBUP =  "
   FXVBUK =  "
   FYVBUK =  "
   FXVBAP =  "
   FYVBAP =  "
   FXVBKD =  "
   FYVBKD =  "
   FXVBEP =  "

EXCEPTIONS
   WRONG_CALL = 1
.



IMPORTING Parameters details for MILL_VS_SAVE_SHADOWED_DB

IF_VSNMR -

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

IS_VBAK -

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

IS_YVBAK -

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

IF_YVBAK_UPDKZ -

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

TABLES Parameters details for MILL_VS_SAVE_SHADOWED_DB

FXVBUP -

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

FYVBEP -

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

FYVBUP -

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

FXVBUK -

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

FYVBUK -

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

FXVBAP -

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

FYVBAP -

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

FXVBKD -

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

FYVBKD -

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

FXVBEP -

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

EXCEPTIONS details

WRONG_CALL -

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

Copy and paste ABAP code example for MILL_VS_SAVE_SHADOWED_DB 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:
lt_fxvbup  TYPE STANDARD TABLE OF VBUPVB, "   
lv_if_vsnmr  TYPE VSVBUK_CN-VSNMR, "   
lv_wrong_call  TYPE VSVBUK_CN, "   
lt_fyvbep  TYPE STANDARD TABLE OF VBEPVB, "   
lt_fyvbup  TYPE STANDARD TABLE OF VBUPVB, "   
lv_is_vbak  TYPE VBAK, "   
lt_fxvbuk  TYPE STANDARD TABLE OF VBUKVB, "   
lv_is_yvbak  TYPE VBAK, "   
lt_fyvbuk  TYPE STANDARD TABLE OF VBUKVB, "   
lv_if_yvbak_updkz  TYPE VBAK-VBTYP, "   
lt_fxvbap  TYPE STANDARD TABLE OF VBAPVB, "   
lt_fyvbap  TYPE STANDARD TABLE OF VBAPVB, "   
lt_fxvbkd  TYPE STANDARD TABLE OF VBKDVB, "   
lt_fyvbkd  TYPE STANDARD TABLE OF VBKDVB, "   
lt_fxvbep  TYPE STANDARD TABLE OF VBEPVB. "   

  CALL FUNCTION 'MILL_VS_SAVE_SHADOWED_DB'  "
    EXPORTING
         IF_VSNMR = lv_if_vsnmr
         IS_VBAK = lv_is_vbak
         IS_YVBAK = lv_is_yvbak
         IF_YVBAK_UPDKZ = lv_if_yvbak_updkz
    TABLES
         FXVBUP = lt_fxvbup
         FYVBEP = lt_fyvbep
         FYVBUP = lt_fyvbup
         FXVBUK = lt_fxvbuk
         FYVBUK = lt_fyvbuk
         FXVBAP = lt_fxvbap
         FYVBAP = lt_fyvbap
         FXVBKD = lt_fxvbkd
         FYVBKD = lt_fyvbkd
         FXVBEP = lt_fxvbep
    EXCEPTIONS
        WRONG_CALL = 1
. " MILL_VS_SAVE_SHADOWED_DB




ABAP code using 7.40 inline data declarations to call FM MILL_VS_SAVE_SHADOWED_DB

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 VSNMR FROM VSVBUK_CN INTO @DATA(ld_if_vsnmr).
 
 
 
 
 
 
 
 
"SELECT single VBTYP FROM VBAK INTO @DATA(ld_if_yvbak_updkz).
 
 
 
 
 
 


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!