SAP RSPO_DELETE_LOMS_EVENTS Function Module for Deleting device events for LOM devices
RSPO_DELETE_LOMS_EVENTS is a standard rspo delete loms events SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Deleting device events for LOM devices 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 rspo delete loms events FM, simply by entering the name RSPO_DELETE_LOMS_EVENTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEXT
Program Name: SAPLSEXT
Main Program: SAPLSEXT
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSPO_DELETE_LOMS_EVENTS 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 'RSPO_DELETE_LOMS_EVENTS'"Deleting device events for LOM devices.
EXPORTING
LOMS = "
* DAYS = "
EXCEPTIONS
UNKNOWN_LOMS = 1
IMPORTING Parameters details for RSPO_DELETE_LOMS_EVENTS
LOMS -
Data type: TSPLOMS-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
DAYS -
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UNKNOWN_LOMS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSPO_DELETE_LOMS_EVENTS 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_loms | TYPE TSPLOMS-NAME, " | |||
| lv_unknown_loms | TYPE TSPLOMS, " | |||
| lv_days | TYPE I. " |
|   CALL FUNCTION 'RSPO_DELETE_LOMS_EVENTS' "Deleting device events for LOM devices |
| EXPORTING | ||
| LOMS | = lv_loms | |
| DAYS | = lv_days | |
| EXCEPTIONS | ||
| UNKNOWN_LOMS = 1 | ||
| . " RSPO_DELETE_LOMS_EVENTS | ||
ABAP code using 7.40 inline data declarations to call FM RSPO_DELETE_LOMS_EVENTS
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 NAME FROM TSPLOMS INTO @DATA(ld_loms). | ||||
Search for further information about these or an SAP related objects