SAP BAPI_PO_DELETE_HISTORY Function Module for Delete Purchase Order History
BAPI_PO_DELETE_HISTORY is a standard bapi po delete history 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 Purchase Order History 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 po delete history FM, simply by entering the name BAPI_PO_DELETE_HISTORY into the relevant SAP transaction such as SE37 or SE38.
Function Group: MELE
Program Name: SAPLMELE
Main Program: SAPLMELE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_PO_DELETE_HISTORY 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_PO_DELETE_HISTORY'"Delete Purchase Order History.
EXPORTING
PURCHASEORDER = "Purchasing Document Number
TABLES
* RETURN = "Return Parameter
* POITEMHISTORY = "Transfer Structure for PO History
* TOKENREFERENCE = "CSL: Data Element CSL_TR_EXT as Structure (BAPI Tab.Arg.)
IMPORTING Parameters details for BAPI_PO_DELETE_HISTORY
PURCHASEORDER - Purchasing Document Number
Data type: BAPIEKKO-PO_NUMBEROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_PO_DELETE_HISTORY
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
POITEMHISTORY - Transfer Structure for PO History
Data type: BAPIEKBEOptional: Yes
Call by Reference: No ( called with pass by value option)
TOKENREFERENCE - CSL: Data Element CSL_TR_EXT as Structure (BAPI Tab.Arg.)
Data type: CSL_TR_EXSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_PO_DELETE_HISTORY 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: | ||||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_purchaseorder | TYPE BAPIEKKO-PO_NUMBER, " | |||
| lt_poitemhistory | TYPE STANDARD TABLE OF BAPIEKBE, " | |||
| lt_tokenreference | TYPE STANDARD TABLE OF CSL_TR_EXS. " |
| CALL FUNCTION 'BAPI_PO_DELETE_HISTORY' "Delete Purchase Order History |
| EXPORTING | ||
| PURCHASEORDER | = lv_purchaseorder | |
| TABLES | ||
| RETURN | = lt_return | |
| POITEMHISTORY | = lt_poitemhistory | |
| TOKENREFERENCE | = lt_tokenreference | |
| . " BAPI_PO_DELETE_HISTORY | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_PO_DELETE_HISTORY
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 PO_NUMBER FROM BAPIEKKO INTO @DATA(ld_purchaseorder). | ||||
Search for further information about these or an SAP related objects