SAP BAPI_CONDITION_CONTRACT_CHANGE Function Module for Change Condition Contract
BAPI_CONDITION_CONTRACT_CHANGE is a standard bapi condition contract 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 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 change FM, simply by entering the name BAPI_CONDITION_CONTRACT_CHANGE 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: 31-May-2005
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_CONDITION_CONTRACT_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 'BAPI_CONDITION_CONTRACT_CHANGE'"Change Condition Contract.
EXPORTING
* HEADDATAIN = "BAPI: Condition Contract Header
* HEADDATAINX = "BAPI: Condition Contract Header Changes
CONDITIONCONTRACTNUMBER = "Condition Contract: Key
IMPORTING
HEADDATAOUT = "BAPI: Condition Contract Header
TABLES
* ITEMDATAIN = "BAPI: Condition Contract: Eligible Partners
* EXTENSIONIN = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
* EXTENSIONOUT = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
* HEADTEXTIN = "Condition Contract for Header Texts If Changes Are Made
* HEADTEXTOUT = "Condition Contract for Header Texts If Changes Are Made
* ITEMTEXTIN = "Condition Contract: Texts for Eligible Partners for Changes
* ITEMTEXTOUT = "Condition Contract: Texts for Eligible Partners for Changes
* RETURN = "Return Parameter(s)
* SCALEDATAIN = "BAPI: Condition Contract: Conditions Scale
* SCALEDATAOUT = "BAPI: Condition Contract: Conditions Scales
* BVBDATAIN = "BAPI: Condition Contract Business Volume Base
* ITEMDATAINX = "BAPI: Condition Contract: Eligible Partner Changes
* BVBDATAINX = "BAPI: Condition Contract Business Volume Base Changes
* BVBDATAOUT = "BAPI: Condition Contract Business Volume Base
* CALENDARDATAIN = "BAPI: Condition Contract Calendar
* CALENDARDATAINX = "BAPI: Condition Contract Calendar
* CALENDARDATAOUT = "BAPI: Condition Contract Calendar
* CONDITIONKEYDATAIN = "BAPI Condition Contract: Condition Structure Fields
* CONDITIONKEYDATAINX = "BAPI Condition Contract: Condition Structure Changes
* CONDITIONITEMDATAIN = "BAPI: Condition Contract: Item Conditions
* CONDITIONITEMDATAINX = "BAPI Condition Contract: Item Condition Changes
* ITEMDATAOUT = "BAPI: Condition Contract: Eligible Partners
* CONDITIONKEYDATAOUT = "BAPI Condition Contract: Condition Structure Fields
* CONDITIONITEMDATAOUT = "BAPI: Condition Contract: Item Conditions
IMPORTING Parameters details for BAPI_CONDITION_CONTRACT_CHANGE
HEADDATAIN - BAPI: Condition Contract Header
Data type: BAPICCHEADOptional: Yes
Call by Reference: No ( called with pass by value option)
HEADDATAINX - BAPI: Condition Contract Header Changes
Data type: BAPICCHEADXOptional: Yes
Call by Reference: No ( called with pass by value option)
CONDITIONCONTRACTNUMBER - Condition Contract: Key
Data type: BAPICCKEY-CONDITION_CONTRACT_NUMBEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_CONDITION_CONTRACT_CHANGE
HEADDATAOUT - BAPI: Condition Contract Header
Data type: BAPICCHEADOSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_CONDITION_CONTRACT_CHANGE
ITEMDATAIN - BAPI: Condition Contract: Eligible Partners
Data type: BAPICCITEMOptional: Yes
Call by Reference: Yes
EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
EXTENSIONOUT - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
HEADTEXTIN - Condition Contract for Header Texts If Changes Are Made
Data type: BAPICCHEADTEXTCHANGEOptional: Yes
Call by Reference: Yes
HEADTEXTOUT - Condition Contract for Header Texts If Changes Are Made
Data type: BAPICCHEADTEXTOptional: Yes
Call by Reference: Yes
ITEMTEXTIN - Condition Contract: Texts for Eligible Partners for Changes
Data type: BAPICCITEMTEXTCHANGEOptional: Yes
Call by Reference: Yes
ITEMTEXTOUT - Condition Contract: Texts for Eligible Partners for Changes
Data type: BAPICCITEMTEXTOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
SCALEDATAIN - BAPI: Condition Contract: Conditions Scale
Data type: BAPICCSCALEOptional: Yes
Call by Reference: Yes
SCALEDATAOUT - BAPI: Condition Contract: Conditions Scales
Data type: BAPICCSCALEOOptional: Yes
Call by Reference: Yes
BVBDATAIN - BAPI: Condition Contract Business Volume Base
Data type: BAPICCBVBOptional: Yes
Call by Reference: Yes
ITEMDATAINX - BAPI: Condition Contract: Eligible Partner Changes
Data type: BAPICCITEMXOptional: Yes
Call by Reference: Yes
BVBDATAINX - BAPI: Condition Contract Business Volume Base Changes
Data type: BAPICCBVBXOptional: Yes
Call by Reference: Yes
BVBDATAOUT - BAPI: Condition Contract Business Volume Base
Data type: BAPICCBVBOOptional: Yes
Call by Reference: Yes
CALENDARDATAIN - BAPI: Condition Contract Calendar
Data type: BAPICCCALOptional: Yes
Call by Reference: Yes
CALENDARDATAINX - BAPI: Condition Contract Calendar
Data type: BAPICCCALXOptional: Yes
Call by Reference: Yes
CALENDARDATAOUT - BAPI: Condition Contract Calendar
Data type: BAPICCCALOOptional: Yes
Call by Reference: Yes
CONDITIONKEYDATAIN - BAPI Condition Contract: Condition Structure Fields
Data type: BAPICCCONDITIONKEYOptional: Yes
Call by Reference: Yes
CONDITIONKEYDATAINX - BAPI Condition Contract: Condition Structure Changes
Data type: BAPICCCONDITIONKEYXOptional: Yes
Call by Reference: Yes
CONDITIONITEMDATAIN - BAPI: Condition Contract: Item Conditions
Data type: BAPICCCONDITIONITEMOptional: Yes
Call by Reference: Yes
CONDITIONITEMDATAINX - BAPI Condition Contract: Item Condition Changes
Data type: BAPICCCONDITIONITEMXOptional: Yes
Call by Reference: Yes
ITEMDATAOUT - BAPI: Condition Contract: Eligible Partners
Data type: BAPICCITEMOOptional: Yes
Call by Reference: Yes
CONDITIONKEYDATAOUT - BAPI Condition Contract: Condition Structure Fields
Data type: BAPICCCONDITIONKEYOOptional: Yes
Call by Reference: Yes
CONDITIONITEMDATAOUT - BAPI: Condition Contract: Item Conditions
Data type: BAPICCCONDITIONITEMOOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_CONDITION_CONTRACT_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: | ||||
| lv_headdatain | TYPE BAPICCHEAD, " | |||
| lt_itemdatain | TYPE STANDARD TABLE OF BAPICCITEM, " | |||
| lv_headdataout | TYPE BAPICCHEADOS, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_extensionout | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lt_headtextin | TYPE STANDARD TABLE OF BAPICCHEADTEXTCHANGE, " | |||
| lt_headtextout | TYPE STANDARD TABLE OF BAPICCHEADTEXT, " | |||
| lt_itemtextin | TYPE STANDARD TABLE OF BAPICCITEMTEXTCHANGE, " | |||
| lt_itemtextout | TYPE STANDARD TABLE OF BAPICCITEMTEXT, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_scaledatain | TYPE STANDARD TABLE OF BAPICCSCALE, " | |||
| lt_scaledataout | TYPE STANDARD TABLE OF BAPICCSCALEO, " | |||
| lt_bvbdatain | TYPE STANDARD TABLE OF BAPICCBVB, " | |||
| lv_headdatainx | TYPE BAPICCHEADX, " | |||
| lt_itemdatainx | TYPE STANDARD TABLE OF BAPICCITEMX, " | |||
| lt_bvbdatainx | TYPE STANDARD TABLE OF BAPICCBVBX, " | |||
| lt_bvbdataout | TYPE STANDARD TABLE OF BAPICCBVBO, " | |||
| lt_calendardatain | TYPE STANDARD TABLE OF BAPICCCAL, " | |||
| lt_calendardatainx | TYPE STANDARD TABLE OF BAPICCCALX, " | |||
| lt_calendardataout | TYPE STANDARD TABLE OF BAPICCCALO, " | |||
| lt_conditionkeydatain | TYPE STANDARD TABLE OF BAPICCCONDITIONKEY, " | |||
| lv_conditioncontractnumber | TYPE BAPICCKEY-CONDITION_CONTRACT_NUMBER, " | |||
| lt_conditionkeydatainx | TYPE STANDARD TABLE OF BAPICCCONDITIONKEYX, " | |||
| lt_conditionitemdatain | TYPE STANDARD TABLE OF BAPICCCONDITIONITEM, " | |||
| lt_conditionitemdatainx | TYPE STANDARD TABLE OF BAPICCCONDITIONITEMX, " | |||
| lt_itemdataout | TYPE STANDARD TABLE OF BAPICCITEMO, " | |||
| lt_conditionkeydataout | TYPE STANDARD TABLE OF BAPICCCONDITIONKEYO, " | |||
| lt_conditionitemdataout | TYPE STANDARD TABLE OF BAPICCCONDITIONITEMO. " |
|   CALL FUNCTION 'BAPI_CONDITION_CONTRACT_CHANGE' "Change Condition Contract |
| EXPORTING | ||
| HEADDATAIN | = lv_headdatain | |
| HEADDATAINX | = lv_headdatainx | |
| CONDITIONCONTRACTNUMBER | = lv_conditioncontractnumber | |
| IMPORTING | ||
| HEADDATAOUT | = lv_headdataout | |
| TABLES | ||
| ITEMDATAIN | = lt_itemdatain | |
| EXTENSIONIN | = lt_extensionin | |
| EXTENSIONOUT | = lt_extensionout | |
| HEADTEXTIN | = lt_headtextin | |
| HEADTEXTOUT | = lt_headtextout | |
| ITEMTEXTIN | = lt_itemtextin | |
| ITEMTEXTOUT | = lt_itemtextout | |
| RETURN | = lt_return | |
| SCALEDATAIN | = lt_scaledatain | |
| SCALEDATAOUT | = lt_scaledataout | |
| BVBDATAIN | = lt_bvbdatain | |
| ITEMDATAINX | = lt_itemdatainx | |
| BVBDATAINX | = lt_bvbdatainx | |
| BVBDATAOUT | = lt_bvbdataout | |
| CALENDARDATAIN | = lt_calendardatain | |
| CALENDARDATAINX | = lt_calendardatainx | |
| CALENDARDATAOUT | = lt_calendardataout | |
| CONDITIONKEYDATAIN | = lt_conditionkeydatain | |
| CONDITIONKEYDATAINX | = lt_conditionkeydatainx | |
| CONDITIONITEMDATAIN | = lt_conditionitemdatain | |
| CONDITIONITEMDATAINX | = lt_conditionitemdatainx | |
| ITEMDATAOUT | = lt_itemdataout | |
| CONDITIONKEYDATAOUT | = lt_conditionkeydataout | |
| CONDITIONITEMDATAOUT | = lt_conditionitemdataout | |
| . " BAPI_CONDITION_CONTRACT_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_CONDITION_CONTRACT_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.| "SELECT single CONDITION_CONTRACT_NUMBER FROM BAPICCKEY INTO @DATA(ld_conditioncontractnumber). | ||||
Search for further information about these or an SAP related objects