SAP BAPI_CONDITION_CONTRACT_EXIST Function Module for Does Condition Contract Exist?









BAPI_CONDITION_CONTRACT_EXIST is a standard bapi condition contract exist 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 Condition Contract 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 bapi condition contract exist FM, simply by entering the name BAPI_CONDITION_CONTRACT_EXIST into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_CONDITION_CONTRACT_EXIST 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 'BAPI_CONDITION_CONTRACT_EXIST'"Does Condition Contract Exist?
EXPORTING
CONDITIONCONTRACTNUMBER = "Condition Contract: Key

EXCEPTIONS
DOES_NOT_EXIST = 1
.



IMPORTING Parameters details for BAPI_CONDITION_CONTRACT_EXIST

CONDITIONCONTRACTNUMBER - Condition Contract: Key

Data type: BAPICCKEY-CONDITION_CONTRACT_NUMBER
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

DOES_NOT_EXIST - Does Not Exist

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_CONDITION_CONTRACT_EXIST 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_does_not_exist  TYPE STRING, "   
lv_conditioncontractnumber  TYPE BAPICCKEY-CONDITION_CONTRACT_NUMBER. "   

  CALL FUNCTION 'BAPI_CONDITION_CONTRACT_EXIST'  "Does Condition Contract Exist?
    EXPORTING
         CONDITIONCONTRACTNUMBER = lv_conditioncontractnumber
    EXCEPTIONS
        DOES_NOT_EXIST = 1
. " BAPI_CONDITION_CONTRACT_EXIST




ABAP code using 7.40 inline data declarations to call FM BAPI_CONDITION_CONTRACT_EXIST

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 CONDITION_CONTRACT_NUMBER FROM BAPICCKEY INTO @DATA(ld_conditioncontractnumber).
 


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!