SAP OIUT2_CHECKOUT_VENTURE Function Module for Check-out function for Venture
OIUT2_CHECKOUT_VENTURE is a standard oiut2 checkout venture SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check-out function for 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 oiut2 checkout venture FM, simply by entering the name OIUT2_CHECKOUT_VENTURE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIUT2_VEN_UTP_INTG
Program Name: SAPLOIUT2_VEN_UTP_INTG
Main Program: SAPLOIUT2_VEN_UTP_INTG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIUT2_CHECKOUT_VENTURE 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 'OIUT2_CHECKOUT_VENTURE'"Check-out function for Venture.
EXPORTING
P_BUKRS = "Company Code
P_UNIT_VNAME = "Joint venture
IMPORTING
P_CHKOUT_FLAG = "Checkout flag
IMPORTING Parameters details for OIUT2_CHECKOUT_VENTURE
P_BUKRS - Company Code
Data type: OIUOW_UNIT_JV-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
P_UNIT_VNAME - Joint venture
Data type: OIUOW_UNIT_JV-UNIT_VNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OIUT2_CHECKOUT_VENTURE
P_CHKOUT_FLAG - Checkout flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIUT2_CHECKOUT_VENTURE 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_p_bukrs | TYPE OIUOW_UNIT_JV-BUKRS, " | |||
| lv_p_chkout_flag | TYPE CHAR1, " | |||
| lv_p_unit_vname | TYPE OIUOW_UNIT_JV-UNIT_VNAME. " |
|   CALL FUNCTION 'OIUT2_CHECKOUT_VENTURE' "Check-out function for Venture |
| EXPORTING | ||
| P_BUKRS | = lv_p_bukrs | |
| P_UNIT_VNAME | = lv_p_unit_vname | |
| IMPORTING | ||
| P_CHKOUT_FLAG | = lv_p_chkout_flag | |
| . " OIUT2_CHECKOUT_VENTURE | ||
ABAP code using 7.40 inline data declarations to call FM OIUT2_CHECKOUT_VENTURE
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 OIUOW_UNIT_JV INTO @DATA(ld_p_bukrs). | ||||
| "SELECT single UNIT_VNAME FROM OIUOW_UNIT_JV INTO @DATA(ld_p_unit_vname). | ||||
Search for further information about these or an SAP related objects