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

Function B40B_REQUISITION_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 'B40B_REQUISITION_DELETE'"Delete requisition.
EXPORTING
NUMBER = "
TABLES
REQUISITION_ITEMS_TO_DELETE = "Übergabestruktur Löschen/Erledigen Banf
* RETURN = "
* CONTROL_RECORD = "
IMPORTING Parameters details for B40B_REQUISITION_DELETE
NUMBER -
Data type: BAPIEBAN-PREQ_NOOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for B40B_REQUISITION_DELETE
REQUISITION_ITEMS_TO_DELETE - Übergabestruktur Löschen/Erledigen Banf
Data type: BBPS_BAPIEBANDOptional: No
Call by Reference: Yes
RETURN -
Data type: BAPIRETURNOptional: Yes
Call by Reference: No ( called with pass by value option)
CONTROL_RECORD -
Data type: BBP_CONTROL_RECORDOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for B40B_REQUISITION_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_number | TYPE BAPIEBAN-PREQ_NO, " | |||
| lt_requisition_items_to_delete | TYPE STANDARD TABLE OF BBPS_BAPIEBAND, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRETURN, " | |||
| lt_control_record | TYPE STANDARD TABLE OF BBP_CONTROL_RECORD. " |
|   CALL FUNCTION 'B40B_REQUISITION_DELETE' "Delete requisition |
| EXPORTING | ||
| NUMBER | = lv_number | |
| TABLES | ||
| REQUISITION_ITEMS_TO_DELETE | = lt_requisition_items_to_delete | |
| RETURN | = lt_return | |
| CONTROL_RECORD | = lt_control_record | |
| . " B40B_REQUISITION_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM B40B_REQUISITION_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 PREQ_NO FROM BAPIEBAN INTO @DATA(ld_number). | ||||
Search for further information about these or an SAP related objects