SAP BAPI_CONDITION_CONTRACT_CLONE Function Module for Clone Condition Contract

Search SAP Function Modules

BAPI_CONDITION_CONTRACT_CLONE is a standard bapi condition contract clone SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Clone Condition Contract 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 clone FM, simply by entering the name BAPI_CONDITION_CONTRACT_CLONE 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: 10-Jun-2011
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_CONDITION_CONTRACT_CLONE 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_CLONE'"Clone Condition Contract
  EXPORTING
   CONDITIONCONTRACTNUMBER =  "Condition Contract Number
*  TESTRUN =  "Switch to Simulation Session for Write BAPIs
*  CLONE_AS_SUCCESSOR =  "Clone as Successor

 IMPORTING
   CONDITIONCONTRACTNUMBERNEW =  "Condition Contract Number

TABLES
   RETURN =  "Return Parameter(s)

.

IMPORTING Parameters details for BAPI_CONDITION_CONTRACT_CLONE

CONDITIONCONTRACTNUMBER - Condition Contract Number

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

TESTRUN - Switch to Simulation Session for Write BAPIs

Data type: WCB_FOR_BAPI-TESTRUN
Optional: Yes
Call by Reference: No ( called with pass by value option)

CLONE_AS_SUCCESSOR - Clone as Successor

Data type: WCB_FOR_BAPI-CLONE_AS_SUCCESSOR
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_CONDITION_CONTRACT_CLONE

CONDITIONCONTRACTNUMBERNEW - Condition Contract Number

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

TABLES Parameters details for BAPI_CONDITION_CONTRACT_CLONE

RETURN - Return Parameter(s)

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

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

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