SAP BAPI_CTRACBILLCONTRACT_DELETE Function Module for CT: Delete Provider Contract
BAPI_CTRACBILLCONTRACT_DELETE is a standard bapi ctracbillcontract delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CT: Delete Provider 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 ctracbillcontract delete FM, simply by entering the name BAPI_CTRACBILLCONTRACT_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_VT_BAPI
Program Name: SAPLFKK_VT_BAPI
Main Program: SAPLFKK_VT_BAPI
Appliation area:
Release date: 20-Sep-2010
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_CTRACBILLCONTRACT_DELETE 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_CTRACBILLCONTRACT_DELETE'"CT: Delete Provider Contract.
EXPORTING
CONTRACT = "Contract Key
VALID_TIMESTAMP = "Contract: Time Stamp in Character Format
* WRITECHANGEDOCUMENTS = 'X' "Indicator for Change Document Creation
* TESTRUN = ' ' "Switch to Simulation Mode for Write BAPIs
* NODATA = '/' "NODATA Indicator
TABLES
* CONTRACTLOCK = "BAPI Structure for Lock Data for Contract
* EXTENSIONIN = "Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
* RETURN = "Return Parameter(s)
IMPORTING Parameters details for BAPI_CTRACBILLCONTRACT_DELETE
CONTRACT - Contract Key
Data type: BAPI_BILLCONTR_H_CREATE-CONTRACTOptional: No
Call by Reference: No ( called with pass by value option)
VALID_TIMESTAMP - Contract: Time Stamp in Character Format
Data type: BAPI_BILLCONTR_CONTROL-VALID_FROMOptional: No
Call by Reference: No ( called with pass by value option)
WRITECHANGEDOCUMENTS - Indicator for Change Document Creation
Data type: BAPI_BILLCONTR_CONTROL-WRITECHANGEDOCUMENTSDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TESTRUN - Switch to Simulation Mode for Write BAPIs
Data type: BAPI_BILLCONTR_CONTROL-TESTRUNDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
NODATA - NODATA Indicator
Data type: BAPI_BILLCONTR_CONTROL-NODATADefault: '/'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_CTRACBILLCONTRACT_DELETE
CONTRACTLOCK - BAPI Structure for Lock Data for Contract
Data type: BAPI_BILLCONTR_LOCKSOptional: Yes
Call by Reference: Yes
EXTENSIONIN - Reference Structure for BAPI Parameters ExtensionIn/ExtensionOut
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_CTRACBILLCONTRACT_DELETE 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_contract | TYPE BAPI_BILLCONTR_H_CREATE-CONTRACT, " | |||
| lt_contractlock | TYPE STANDARD TABLE OF BAPI_BILLCONTR_LOCKS, " | |||
| lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lv_valid_timestamp | TYPE BAPI_BILLCONTR_CONTROL-VALID_FROM, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_writechangedocuments | TYPE BAPI_BILLCONTR_CONTROL-WRITECHANGEDOCUMENTS, " 'X' | |||
| lv_testrun | TYPE BAPI_BILLCONTR_CONTROL-TESTRUN, " ' ' | |||
| lv_nodata | TYPE BAPI_BILLCONTR_CONTROL-NODATA. " '/' |
|   CALL FUNCTION 'BAPI_CTRACBILLCONTRACT_DELETE' "CT: Delete Provider Contract |
| EXPORTING | ||
| CONTRACT | = lv_contract | |
| VALID_TIMESTAMP | = lv_valid_timestamp | |
| WRITECHANGEDOCUMENTS | = lv_writechangedocuments | |
| TESTRUN | = lv_testrun | |
| NODATA | = lv_nodata | |
| TABLES | ||
| CONTRACTLOCK | = lt_contractlock | |
| EXTENSIONIN | = lt_extensionin | |
| RETURN | = lt_return | |
| . " BAPI_CTRACBILLCONTRACT_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_CTRACBILLCONTRACT_DELETE
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 CONTRACT FROM BAPI_BILLCONTR_H_CREATE INTO @DATA(ld_contract). | ||||
| "SELECT single VALID_FROM FROM BAPI_BILLCONTR_CONTROL INTO @DATA(ld_valid_timestamp). | ||||
| "SELECT single WRITECHANGEDOCUMENTS FROM BAPI_BILLCONTR_CONTROL INTO @DATA(ld_writechangedocuments). | ||||
| DATA(ld_writechangedocuments) | = 'X'. | |||
| "SELECT single TESTRUN FROM BAPI_BILLCONTR_CONTROL INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
| "SELECT single NODATA FROM BAPI_BILLCONTR_CONTROL INTO @DATA(ld_nodata). | ||||
| DATA(ld_nodata) | = '/'. | |||
Search for further information about these or an SAP related objects