SAP BAPI_PLATFORM_DELETE Function Module for Deletes Specific Platform IDs.
BAPI_PLATFORM_DELETE is a standard bapi platform 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 Deletes Specific Platform IDs. 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 platform delete FM, simply by entering the name BAPI_PLATFORM_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIU_PLATFORM
Program Name: SAPLOIU_PLATFORM
Main Program: SAPLOIU_PLATFORM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_PLATFORM_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 'BAPI_PLATFORM_DELETE'"Deletes Specific Platform IDs..
EXPORTING
PF_NO = "
TABLES
RETURN = "Return Message
* PF_READINGS = "Measurement send
IMPORTING Parameters details for BAPI_PLATFORM_DELETE
PF_NO -
Data type: BAPI_OIU_PLATFORM-PF_NOOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_PLATFORM_DELETE
RETURN - Return Message
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
PF_READINGS - Measurement send
Data type: BAPI_OIU_MEAS_SENDOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_PLATFORM_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_pf_no | TYPE BAPI_OIU_PLATFORM-PF_NO, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_pf_readings | TYPE STANDARD TABLE OF BAPI_OIU_MEAS_SEND. " |
|   CALL FUNCTION 'BAPI_PLATFORM_DELETE' "Deletes Specific Platform IDs. |
| EXPORTING | ||
| PF_NO | = lv_pf_no | |
| TABLES | ||
| RETURN | = lt_return | |
| PF_READINGS | = lt_pf_readings | |
| . " BAPI_PLATFORM_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_PLATFORM_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 PF_NO FROM BAPI_OIU_PLATFORM INTO @DATA(ld_pf_no). | ||||
Search for further information about these or an SAP related objects