SAP VENTURE_EXISTENCE_CHECK Function Module for Does a specific venture exist?

Search SAP Function Modules

VENTURE_EXISTENCE_CHECK is a standard venture existence check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Does a specific venture exist? 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 venture existence check FM, simply by entering the name VENTURE_EXISTENCE_CHECK into the relevant SAP transaction such as SE37 or SE38.

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

Function VENTURE_EXISTENCE_CHECK 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 'VENTURE_EXISTENCE_CHECK'"Does a specific venture exist?
  EXPORTING
   I_BUKRS =  "Company Code
   I_VNAME =  "Joint venture

EXCEPTIONS
   NOT_FOUND = 1 

.

IMPORTING Parameters details for VENTURE_EXISTENCE_CHECK

I_BUKRS - Company Code

Data type: T8JV-BUKRS
Optional: No
Call by Reference: Yes

I_VNAME - Joint venture

Data type: T8JV-VNAME
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND - Venture does not exist in company code

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for VENTURE_EXISTENCE_CHECK 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.

ABAP code using 7.40 inline data declarations to call FM VENTURE_EXISTENCE_CHECK

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