SAP UPE_DOC_DESTROY Function Module for Planning Framework SD: DESTROY
UPE_DOC_DESTROY is a standard upe doc destroy SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Planning Framework SD: DESTROY 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 upe doc destroy FM, simply by entering the name UPE_DOC_DESTROY into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPE_DOC
Program Name: SAPLUPE_DOC
Main Program: SAPLUPE_DOC
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPE_DOC_DESTROY 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 'UPE_DOC_DESTROY'"Planning Framework SD: DESTROY.
EXPORTING
* I_NO_TRANSACTION_DATA = "Single-Character Flag
IMPORTING Parameters details for UPE_DOC_DESTROY
I_NO_TRANSACTION_DATA - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for UPE_DOC_DESTROY 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_i_no_transaction_data | TYPE CHAR1. " |
|   CALL FUNCTION 'UPE_DOC_DESTROY' "Planning Framework SD: DESTROY |
| EXPORTING | ||
| I_NO_TRANSACTION_DATA | = lv_i_no_transaction_data | |
| . " UPE_DOC_DESTROY | ||
ABAP code using 7.40 inline data declarations to call FM UPE_DOC_DESTROY
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