SAP BAPI_CONTACTCRM_DELETE Function Module for Proxy BAPI - Delete Contact Person in SFA Context
BAPI_CONTACTCRM_DELETE is a standard bapi contactcrm 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 Proxy BAPI - Delete Contact Person in SFA Context 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 contactcrm delete FM, simply by entering the name BAPI_CONTACTCRM_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM4
Program Name: SAPLCRM4
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_CONTACTCRM_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_CONTACTCRM_DELETE'"Proxy BAPI - Delete Contact Person in SFA Context.
EXPORTING
I_UPLOAD_ID = "Unique Reference Number
I_DESTIN = "RFC Destination Server System
I_SFA_REL = "SFA Release in Server System
I_KEYWORD_IN = "Keyword for Customer Enhancements
I_CONTACT = "BAPI Structure: Contact Person, General Data
I_TRANS_MODE = "Single-Character Indicator
IMPORTING
E_STATUS = "Upload Status at Table Level
TABLES
TI_SFA_KEYS = "Input Table Structure for SFA Key in Proxy Function Module
IMPORTING Parameters details for BAPI_CONTACTCRM_DELETE
I_UPLOAD_ID - Unique Reference Number
Data type: BAPICRMDH2-REF_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_DESTIN - RFC Destination Server System
Data type: CRM_PARA-RFCSERVEROptional: No
Call by Reference: No ( called with pass by value option)
I_SFA_REL - SFA Release in Server System
Data type: CRM_PARA-SERVER_RELOptional: No
Call by Reference: No ( called with pass by value option)
I_KEYWORD_IN - Keyword for Customer Enhancements
Data type: CRM_PARA-KEYWORD_INOptional: No
Call by Reference: No ( called with pass by value option)
I_CONTACT - BAPI Structure: Contact Person, General Data
Data type: BAPICUSCPGOptional: No
Call by Reference: No ( called with pass by value option)
I_TRANS_MODE - Single-Character Indicator
Data type: BAPIFLAG-BAPIFLAGOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_CONTACTCRM_DELETE
E_STATUS - Upload Status at Table Level
Data type: CRM_PARA-UPLOADSTATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_CONTACTCRM_DELETE
TI_SFA_KEYS - Input Table Structure for SFA Key in Proxy Function Module
Data type: BAPICRMSFKOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_CONTACTCRM_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_e_status | TYPE CRM_PARA-UPLOADSTAT, " | |||
| lv_i_upload_id | TYPE BAPICRMDH2-REF_ID, " | |||
| lt_ti_sfa_keys | TYPE STANDARD TABLE OF BAPICRMSFK, " | |||
| lv_i_destin | TYPE CRM_PARA-RFCSERVER, " | |||
| lv_i_sfa_rel | TYPE CRM_PARA-SERVER_REL, " | |||
| lv_i_keyword_in | TYPE CRM_PARA-KEYWORD_IN, " | |||
| lv_i_contact | TYPE BAPICUSCPG, " | |||
| lv_i_trans_mode | TYPE BAPIFLAG-BAPIFLAG. " |
|   CALL FUNCTION 'BAPI_CONTACTCRM_DELETE' "Proxy BAPI - Delete Contact Person in SFA Context |
| EXPORTING | ||
| I_UPLOAD_ID | = lv_i_upload_id | |
| I_DESTIN | = lv_i_destin | |
| I_SFA_REL | = lv_i_sfa_rel | |
| I_KEYWORD_IN | = lv_i_keyword_in | |
| I_CONTACT | = lv_i_contact | |
| I_TRANS_MODE | = lv_i_trans_mode | |
| IMPORTING | ||
| E_STATUS | = lv_e_status | |
| TABLES | ||
| TI_SFA_KEYS | = lt_ti_sfa_keys | |
| . " BAPI_CONTACTCRM_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_CONTACTCRM_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 UPLOADSTAT FROM CRM_PARA INTO @DATA(ld_e_status). | ||||
| "SELECT single REF_ID FROM BAPICRMDH2 INTO @DATA(ld_i_upload_id). | ||||
| "SELECT single RFCSERVER FROM CRM_PARA INTO @DATA(ld_i_destin). | ||||
| "SELECT single SERVER_REL FROM CRM_PARA INTO @DATA(ld_i_sfa_rel). | ||||
| "SELECT single KEYWORD_IN FROM CRM_PARA INTO @DATA(ld_i_keyword_in). | ||||
| "SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_i_trans_mode). | ||||
Search for further information about these or an SAP related objects