SAP JV_DATA_MAINTENANCE_MM Function Module for









JV_DATA_MAINTENANCE_MM is a standard jv data maintenance mm 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 jv data maintenance mm FM, simply by entering the name JV_DATA_MAINTENANCE_MM into the relevant SAP transaction such as SE37 or SE38.

Function Group: GJCI
Program Name: SAPLGJCI
Main Program: SAPLGJCI
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function JV_DATA_MAINTENANCE_MM 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 'JV_DATA_MAINTENANCE_MM'"
EXPORTING
* SCREEN_STARTING_AT_X = "
* SCREEN_STARTING_AT_Y = "
* SCREEN_ENDING_AT_X = "
* SCREEN_ENDING_AT_Y = "
* ACTION_TYPE = 'D' "
* POPUP_TITLE = "
* I_VORGANG = "
I_CAUFVD = "

IMPORTING
DATA_CHANGED = "
JV_DATA = "
JV_FIELD_F2 = "
.



IMPORTING Parameters details for JV_DATA_MAINTENANCE_MM

SCREEN_STARTING_AT_X -

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

SCREEN_STARTING_AT_Y -

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

SCREEN_ENDING_AT_X -

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

SCREEN_ENDING_AT_Y -

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

ACTION_TYPE -

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

POPUP_TITLE -

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

I_VORGANG -

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

I_CAUFVD -

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

EXPORTING Parameters details for JV_DATA_MAINTENANCE_MM

DATA_CHANGED -

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

JV_DATA -

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

JV_FIELD_F2 -

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

Copy and paste ABAP code example for JV_DATA_MAINTENANCE_MM 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_data_changed  TYPE SY-INPUT, "   
lv_screen_starting_at_x  TYPE SY-WINX1, "   
lv_jv_data  TYPE GJV_DATA, "   
lv_screen_starting_at_y  TYPE SY-WINY1, "   
lv_jv_field_f2  TYPE DD03D-FIELDNAME, "   
lv_screen_ending_at_x  TYPE SY-WINX2, "   
lv_screen_ending_at_y  TYPE SY-WINY2, "   
lv_action_type  TYPE SY-INPUT, "   'D'
lv_popup_title  TYPE SY, "   
lv_i_vorgang  TYPE AFVGD, "   
lv_i_caufvd  TYPE CAUFVD. "   

  CALL FUNCTION 'JV_DATA_MAINTENANCE_MM'  "
    EXPORTING
         SCREEN_STARTING_AT_X = lv_screen_starting_at_x
         SCREEN_STARTING_AT_Y = lv_screen_starting_at_y
         SCREEN_ENDING_AT_X = lv_screen_ending_at_x
         SCREEN_ENDING_AT_Y = lv_screen_ending_at_y
         ACTION_TYPE = lv_action_type
         POPUP_TITLE = lv_popup_title
         I_VORGANG = lv_i_vorgang
         I_CAUFVD = lv_i_caufvd
    IMPORTING
         DATA_CHANGED = lv_data_changed
         JV_DATA = lv_jv_data
         JV_FIELD_F2 = lv_jv_field_f2
. " JV_DATA_MAINTENANCE_MM




ABAP code using 7.40 inline data declarations to call FM JV_DATA_MAINTENANCE_MM

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 INPUT FROM SY INTO @DATA(ld_data_changed).
 
"SELECT single WINX1 FROM SY INTO @DATA(ld_screen_starting_at_x).
 
 
"SELECT single WINY1 FROM SY INTO @DATA(ld_screen_starting_at_y).
 
"SELECT single FIELDNAME FROM DD03D INTO @DATA(ld_jv_field_f2).
 
"SELECT single WINX2 FROM SY INTO @DATA(ld_screen_ending_at_x).
 
"SELECT single WINY2 FROM SY INTO @DATA(ld_screen_ending_at_y).
 
"SELECT single INPUT FROM SY INTO @DATA(ld_action_type).
DATA(ld_action_type) = 'D'.
 
 
 
 


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!