SAP LTR2_UI_CM_EDITOR_DELETE Function Module for Delete Content Module UI
LTR2_UI_CM_EDITOR_DELETE is a standard ltr2 ui cm editor 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 Content Module UI 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 ltr2 ui cm editor delete FM, simply by entering the name LTR2_UI_CM_EDITOR_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: LTR2_UI_CM_EDITOR
Program Name: SAPLLTR2_UI_CM_EDITOR
Main Program: SAPLLTR2_UI_CM_EDITOR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LTR2_UI_CM_EDITOR_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 'LTR2_UI_CM_EDITOR_DELETE'"Delete Content Module UI.
EXPORTING
IV_GUID = "Content Module GUID
IMPORTING
EV_RES = "
IMPORTING Parameters details for LTR2_UI_CM_EDITOR_DELETE
IV_GUID - Content Module GUID
Data type: LTR2_GUID_CMOptional: No
Call by Reference: Yes
EXPORTING Parameters details for LTR2_UI_CM_EDITOR_DELETE
EV_RES -
Data type: ABAP_BOOLOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for LTR2_UI_CM_EDITOR_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_ev_res | TYPE ABAP_BOOL, " | |||
| lv_iv_guid | TYPE LTR2_GUID_CM. " |
|   CALL FUNCTION 'LTR2_UI_CM_EDITOR_DELETE' "Delete Content Module UI |
| EXPORTING | ||
| IV_GUID | = lv_iv_guid | |
| IMPORTING | ||
| EV_RES | = lv_ev_res | |
| . " LTR2_UI_CM_EDITOR_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM LTR2_UI_CM_EDITOR_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