SAP OIU_BAPI_VENTURE_CHANGE Function Module for Change Joint Venture









OIU_BAPI_VENTURE_CHANGE is a standard oiu bapi venture change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Joint Venture 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 oiu bapi venture change FM, simply by entering the name OIU_BAPI_VENTURE_CHANGE into the relevant SAP transaction such as SE37 or SE38.

Function Group: OIU_VENTURE
Program Name: SAPLOIU_VENTURE
Main Program: SAPLOIU_VENTURE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function OIU_BAPI_VENTURE_CHANGE 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 'OIU_BAPI_VENTURE_CHANGE'"Change Joint Venture
  EXPORTING
   VENTUREHEADER =  "Venture Header
   VENTUREDETAIL =  "Venture Detail Information
   VENTURELOCATION =  "Venture Location Information
   VENTUREACQUISITIONS =  "Venture Acquisition Information

 IMPORTING
   VENTUREHEADER =  "Venture Header
   VENTUREDETAIL =  "Venture Detail Information
   VENTURELOCATION =  "Venture Location Information
   VENTUREACQUISITIONS =  "Venture Acquisition Information

TABLES
   RETURN =  "Error and Success Messages
.



IMPORTING Parameters details for OIU_BAPI_VENTURE_CHANGE

VENTUREHEADER - Venture Header

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

VENTUREDETAIL - Venture Detail Information

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

VENTURELOCATION - Venture Location Information

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

VENTUREACQUISITIONS - Venture Acquisition Information

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

EXPORTING Parameters details for OIU_BAPI_VENTURE_CHANGE

VENTUREHEADER - Venture Header

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

VENTUREDETAIL - Venture Detail Information

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

VENTURELOCATION - Venture Location Information

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

VENTUREACQUISITIONS - Venture Acquisition Information

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

TABLES Parameters details for OIU_BAPI_VENTURE_CHANGE

RETURN - Error and Success Messages

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

Copy and paste ABAP code example for OIU_BAPI_VENTURE_CHANGE 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_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_ventureheader  TYPE BAPI_OIU_VENTURE, "   
lv_ventureheader  TYPE BAPI_OIU_VENTURE, "   
lv_venturedetail  TYPE BAPI_OIU_VENTURE_1, "   
lv_venturedetail  TYPE BAPI_OIU_VENTURE_1, "   
lv_venturelocation  TYPE BAPI_OIU_VENTURE_2, "   
lv_venturelocation  TYPE BAPI_OIU_VENTURE_2, "   
lv_ventureacquisitions  TYPE BAPI_OIU_VENTURE_3, "   
lv_ventureacquisitions  TYPE BAPI_OIU_VENTURE_3. "   

  CALL FUNCTION 'OIU_BAPI_VENTURE_CHANGE'  "Change Joint Venture
    EXPORTING
         VENTUREHEADER = lv_ventureheader
         VENTUREDETAIL = lv_venturedetail
         VENTURELOCATION = lv_venturelocation
         VENTUREACQUISITIONS = lv_ventureacquisitions
    IMPORTING
         VENTUREHEADER = lv_ventureheader
         VENTUREDETAIL = lv_venturedetail
         VENTURELOCATION = lv_venturelocation
         VENTUREACQUISITIONS = lv_ventureacquisitions
    TABLES
         RETURN = lt_return
. " OIU_BAPI_VENTURE_CHANGE




ABAP code using 7.40 inline data declarations to call FM OIU_BAPI_VENTURE_CHANGE

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!