SAP GJV_BW_GET_VENTURE_SPLIT Function Module for Get venture split data









GJV_BW_GET_VENTURE_SPLIT is a standard gjv bw get venture split SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get venture split data 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 gjv bw get venture split FM, simply by entering the name GJV_BW_GET_VENTURE_SPLIT into the relevant SAP transaction such as SE37 or SE38.

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



Function GJV_BW_GET_VENTURE_SPLIT 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 'GJV_BW_GET_VENTURE_SPLIT'"Get venture split data
EXPORTING
I_JVDATA = "Table entry for split of JV values in BW per parnter

IMPORTING
E_JVSPLIT = "Table for BW value split per partner

EXCEPTIONS
MISSING_PARAMETER = 1
.



IMPORTING Parameters details for GJV_BW_GET_VENTURE_SPLIT

I_JVDATA - Table entry for split of JV values in BW per parnter

Data type: GJV_BW_VALUE_TAB
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for GJV_BW_GET_VENTURE_SPLIT

E_JVSPLIT - Table for BW value split per partner

Data type: GJV_BW_VALUE_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

MISSING_PARAMETER - Mandatory parameter missing

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GJV_BW_GET_VENTURE_SPLIT 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_jvdata  TYPE GJV_BW_VALUE_TAB, "   
lv_e_jvsplit  TYPE GJV_BW_VALUE_TAB, "   
lv_missing_parameter  TYPE GJV_BW_VALUE_TAB. "   

  CALL FUNCTION 'GJV_BW_GET_VENTURE_SPLIT'  "Get venture split data
    EXPORTING
         I_JVDATA = lv_i_jvdata
    IMPORTING
         E_JVSPLIT = lv_e_jvsplit
    EXCEPTIONS
        MISSING_PARAMETER = 1
. " GJV_BW_GET_VENTURE_SPLIT




ABAP code using 7.40 inline data declarations to call FM GJV_BW_GET_VENTURE_SPLIT

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.

 
 
 


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!