SAP BDC_PROTOCOL_DELETE Function Module for









BDC_PROTOCOL_DELETE is a standard bdc protocol delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bdc protocol delete FM, simply by entering the name BDC_PROTOCOL_DELETE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SBDP
Program Name: SAPLSBDP
Main Program: SAPLSBDP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BDC_PROTOCOL_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 'BDC_PROTOCOL_DELETE'"
EXPORTING
TEMSE_ID = "
* TEMSE_CLIENT = SY-MANDT "Client

EXCEPTIONS
NOT_FOUND = 1 TEMSE_ERROR = 2
.



IMPORTING Parameters details for BDC_PROTOCOL_DELETE

TEMSE_ID -

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

TEMSE_CLIENT - Client

Data type: TBTCO-AUTHCKMAN
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_FOUND - No record found

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

TEMSE_ERROR -

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

Copy and paste ABAP code example for BDC_PROTOCOL_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_temse_id  TYPE TST01-DNAME, "   
lv_not_found  TYPE TST01, "   
lv_temse_error  TYPE TST01, "   
lv_temse_client  TYPE TBTCO-AUTHCKMAN. "   SY-MANDT

  CALL FUNCTION 'BDC_PROTOCOL_DELETE'  "
    EXPORTING
         TEMSE_ID = lv_temse_id
         TEMSE_CLIENT = lv_temse_client
    EXCEPTIONS
        NOT_FOUND = 1
        TEMSE_ERROR = 2
. " BDC_PROTOCOL_DELETE




ABAP code using 7.40 inline data declarations to call FM BDC_PROTOCOL_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 DNAME FROM TST01 INTO @DATA(ld_temse_id).
 
 
 
"SELECT single AUTHCKMAN FROM TBTCO INTO @DATA(ld_temse_client).
DATA(ld_temse_client) = SY-MANDT.
 


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!