SAP JV_DATA_SUBSCREEN_PAI Function Module for Maintenance of JV data on application objects
JV_DATA_SUBSCREEN_PAI is a standard jv data subscreen pai SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Maintenance of JV data on application objects processing and below is the pattern details for this FM, 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 subscreen pai FM, simply by entering the name JV_DATA_SUBSCREEN_PAI into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJVO
Program Name: SAPLGJVO
Main Program: SAPLGJVO
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function JV_DATA_SUBSCREEN_PAI 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_SUBSCREEN_PAI'"Maintenance of JV data on application objects.
IMPORTING
SUBDATA_CHANGED = "
I_JV_DATA = "
I_JV_FIELD_F2 = "
EXPORTING Parameters details for JV_DATA_SUBSCREEN_PAI
SUBDATA_CHANGED -
Data type: SY-INPUTOptional: No
Call by Reference: No ( called with pass by value option)
I_JV_DATA -
Data type: GJV_DATAOptional: No
Call by Reference: No ( called with pass by value option)
I_JV_FIELD_F2 -
Data type: DD03D-FIELDNAMEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for JV_DATA_SUBSCREEN_PAI 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_subdata_changed | TYPE SY-INPUT, " | |||
| lv_i_jv_data | TYPE GJV_DATA, " | |||
| lv_i_jv_field_f2 | TYPE DD03D-FIELDNAME. " |
|   CALL FUNCTION 'JV_DATA_SUBSCREEN_PAI' "Maintenance of JV data on application objects |
| IMPORTING | ||
| SUBDATA_CHANGED | = lv_subdata_changed | |
| I_JV_DATA | = lv_i_jv_data | |
| I_JV_FIELD_F2 | = lv_i_jv_field_f2 | |
| . " JV_DATA_SUBSCREEN_PAI | ||
ABAP code using 7.40 inline data declarations to call FM JV_DATA_SUBSCREEN_PAI
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_subdata_changed). | ||||
| "SELECT single FIELDNAME FROM DD03D INTO @DATA(ld_i_jv_field_f2). | ||||
Search for further information about these or an SAP related objects