SAP MV_ADJUST_USER_TABLE Function Module for









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

Function Group: FVMA07
Program Name: SAPLFVMA07
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MV_ADJUST_USER_TABLE 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_USER_TABLE'"
EXPORTING
I_BUKRS = "
I_DGUELAB = "
* I_XIDENT = '' "
* I_SADJRSN = '' "
* I_DNACHBUCH = SY-DATUM "
* I_FLAGS = "
* I_SAVE = ' ' "
* I_ACTIVATE = ' ' "

IMPORTING
E_NUM_SELECTED = "
E_NUM_ADJUSTED = "
E_NUM_ACTIVATED = "

CHANGING
* IE_PROTNAME = '' "

TABLES
I_TAB_ADJUST = "
* E_TAB_ADJUST = "
* E_PROTOCOL = "

EXCEPTIONS
HEADER_ALREADY_USED = 1 CANNOT_CREATE_HEADER = 2 MULTIPLE_ADJUST_TYPES = 3 SAVING_FAILED = 4 ACTIVATION_NEEDS_SAVING = 5
.



IMPORTING Parameters details for MV_ADJUST_USER_TABLE

I_BUKRS -

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

I_DGUELAB -

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

I_XIDENT -

Data type: VIMI17-XIDENT
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SADJRSN -

Data type: VIMI17-SADJRSN
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DNACHBUCH -

Data type: SY-DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLAGS -

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

I_SAVE -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ACTIVATE -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MV_ADJUST_USER_TABLE

E_NUM_SELECTED -

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

E_NUM_ADJUSTED -

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

E_NUM_ACTIVATED -

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

CHANGING Parameters details for MV_ADJUST_USER_TABLE

IE_PROTNAME -

Data type: VIMI17-PROTNAME
Default: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MV_ADJUST_USER_TABLE

I_TAB_ADJUST -

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

E_TAB_ADJUST -

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

E_PROTOCOL -

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

EXCEPTIONS details

HEADER_ALREADY_USED -

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

CANNOT_CREATE_HEADER -

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

MULTIPLE_ADJUST_TYPES -

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

SAVING_FAILED -

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

ACTIVATION_NEEDS_SAVING -

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

Copy and paste ABAP code example for MV_ADJUST_USER_TABLE 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_i_bukrs  TYPE VIMI16-BUKRS, "   
lv_ie_protname  TYPE VIMI17-PROTNAME, "   ''
lt_i_tab_adjust  TYPE STANDARD TABLE OF FVIMA_TAB_ADJUST, "   
lv_e_num_selected  TYPE I, "   
lv_header_already_used  TYPE I, "   
lv_i_dguelab  TYPE VIMI17-DGUELAB, "   
lt_e_tab_adjust  TYPE STANDARD TABLE OF FVIMA_TAB_ADJUST, "   
lv_e_num_adjusted  TYPE I, "   
lv_cannot_create_header  TYPE I, "   
lv_i_xident  TYPE VIMI17-XIDENT, "   ''
lt_e_protocol  TYPE STANDARD TABLE OF FVIMA_TAB_MESG, "   
lv_e_num_activated  TYPE I, "   
lv_multiple_adjust_types  TYPE I, "   
lv_i_sadjrsn  TYPE VIMI17-SADJRSN, "   ''
lv_saving_failed  TYPE VIMI17, "   
lv_i_dnachbuch  TYPE SY-DATUM, "   SY-DATUM
lv_activation_needs_saving  TYPE SY, "   
lv_i_flags  TYPE FVIMA_REC_FLAGS, "   
lv_i_save  TYPE C, "   ' '
lv_i_activate  TYPE C. "   ' '

  CALL FUNCTION 'MV_ADJUST_USER_TABLE'  "
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_DGUELAB = lv_i_dguelab
         I_XIDENT = lv_i_xident
         I_SADJRSN = lv_i_sadjrsn
         I_DNACHBUCH = lv_i_dnachbuch
         I_FLAGS = lv_i_flags
         I_SAVE = lv_i_save
         I_ACTIVATE = lv_i_activate
    IMPORTING
         E_NUM_SELECTED = lv_e_num_selected
         E_NUM_ADJUSTED = lv_e_num_adjusted
         E_NUM_ACTIVATED = lv_e_num_activated
    CHANGING
         IE_PROTNAME = lv_ie_protname
    TABLES
         I_TAB_ADJUST = lt_i_tab_adjust
         E_TAB_ADJUST = lt_e_tab_adjust
         E_PROTOCOL = lt_e_protocol
    EXCEPTIONS
        HEADER_ALREADY_USED = 1
        CANNOT_CREATE_HEADER = 2
        MULTIPLE_ADJUST_TYPES = 3
        SAVING_FAILED = 4
        ACTIVATION_NEEDS_SAVING = 5
. " MV_ADJUST_USER_TABLE




ABAP code using 7.40 inline data declarations to call FM MV_ADJUST_USER_TABLE

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 BUKRS FROM VIMI16 INTO @DATA(ld_i_bukrs).
 
"SELECT single PROTNAME FROM VIMI17 INTO @DATA(ld_ie_protname).
DATA(ld_ie_protname) = ''.
 
 
 
 
"SELECT single DGUELAB FROM VIMI17 INTO @DATA(ld_i_dguelab).
 
 
 
 
"SELECT single XIDENT FROM VIMI17 INTO @DATA(ld_i_xident).
DATA(ld_i_xident) = ''.
 
 
 
 
"SELECT single SADJRSN FROM VIMI17 INTO @DATA(ld_i_sadjrsn).
DATA(ld_i_sadjrsn) = ''.
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_dnachbuch).
DATA(ld_i_dnachbuch) = SY-DATUM.
 
 
 
DATA(ld_i_save) = ' '.
 
DATA(ld_i_activate) = ' '.
 


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!