SAP FMBUCOPI_DELETE Function Module for Delete Records
FMBUCOPI_DELETE is a standard fmbucopi 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 Records 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 fmbucopi delete FM, simply by entering the name FMBUCOPI_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMBUCO_DB_ACCESS
Program Name: SAPLFMBUCO_DB_ACCESS
Main Program: SAPLFMBUCO_DB_ACCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FMBUCOPI_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 'FMBUCOPI_DELETE'"Delete Records.
EXPORTING
* IT_FUNDSCENTER_RANGE = "FM-CO Request Transaction Sequence Number
* IT_COMMITMENTITEM_RANGE = "Ranges table for FIPEX
* IT_BUDGETENTRYDOCUMENTID = "FM entry document ID
IMPORTING Parameters details for FMBUCOPI_DELETE
IT_FUNDSCENTER_RANGE - FM-CO Request Transaction Sequence Number
Data type: FM_T_RANGE_FICTROptional: Yes
Call by Reference: Yes
IT_COMMITMENTITEM_RANGE - Ranges table for FIPEX
Data type: FM_T_RANGE_FIPEXOptional: Yes
Call by Reference: Yes
IT_BUDGETENTRYDOCUMENTID - FM entry document ID
Data type: FMED_T_DOCIDOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FMBUCOPI_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_it_fundscenter_range | TYPE FM_T_RANGE_FICTR, " | |||
| lv_it_commitmentitem_range | TYPE FM_T_RANGE_FIPEX, " | |||
| lv_it_budgetentrydocumentid | TYPE FMED_T_DOCID. " |
|   CALL FUNCTION 'FMBUCOPI_DELETE' "Delete Records |
| EXPORTING | ||
| IT_FUNDSCENTER_RANGE | = lv_it_fundscenter_range | |
| IT_COMMITMENTITEM_RANGE | = lv_it_commitmentitem_range | |
| IT_BUDGETENTRYDOCUMENTID | = lv_it_budgetentrydocumentid | |
| . " FMBUCOPI_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM FMBUCOPI_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