SAP CBRC_OR_BD_DATA_DELETE Function Module for Delete Representative Data

Search SAP Function Modules

CBRC_OR_BD_DATA_DELETE is a standard cbrc or bd data 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 Delete Representative Data 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 cbrc or bd data delete FM, simply by entering the name CBRC_OR_BD_DATA_DELETE into the relevant SAP transaction such as SE37 or SE38.

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

Function CBRC_OR_BD_DATA_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 'CBRC_OR_BD_DATA_DELETE'"Delete Representative Data
  EXPORTING
*  I_FLG_REC_LOCK = ESP1_FALSE "Indicator: Single Data Record Lock
*  I_FLG_COMMIT = ESP1_FALSE "Indicator: Execute Commit

 IMPORTING
   E_FLG_LOCKFAIL =  "Indicator: Lock Error
   E_FLG_ERROR =  "Indicator: Error
   E_ERROR_TAB =  "Table Type Application Log

CHANGING
   X_OR_BD_DATA_TAB =  "Table Type for CCRCS_OR_BD_DATA_IOT

EXCEPTIONS
   COMMIT_ERROR = 1    INTERNAL_ERROR = 2 

.

IMPORTING Parameters details for CBRC_OR_BD_DATA_DELETE

I_FLG_REC_LOCK - Indicator: Single Data Record Lock

Data type: ESP1_BOOLEAN
Default: ESP1_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_COMMIT - Indicator: Execute Commit

Data type: ESP1_BOOLEAN
Default: ESP1_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CBRC_OR_BD_DATA_DELETE

E_FLG_LOCKFAIL - Indicator: Lock Error

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

E_FLG_ERROR - Indicator: Error

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

E_ERROR_TAB - Table Type Application Log

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

CHANGING Parameters details for CBRC_OR_BD_DATA_DELETE

X_OR_BD_DATA_TAB - Table Type for CCRCS_OR_BD_DATA_IOT

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

EXCEPTIONS details

COMMIT_ERROR - Error During Commit

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Internal error

Data type:
Optional: No
Call by Reference: Yes

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

ABAP code using 7.40 inline data declarations to call FM CBRC_OR_BD_DATA_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.

Search for further information about these or an SAP related objects