SAP RSTS_REMOVE_OBJECT Function Module for Delete TemSe object
RSTS_REMOVE_OBJECT is a standard rsts remove object 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 TemSe object 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 rsts remove object FM, simply by entering the name RSTS_REMOVE_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: STMS
Program Name: SAPLSTMS
Main Program: SAPLSTMS
Appliation area: S
Release date: 21-Sep-1993
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSTS_REMOVE_OBJECT 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 'RSTS_REMOVE_OBJECT'"Delete TemSe object.
EXPORTING
* AUTHORITY = ' ' "Who carried out the authorization check
* CLIENT = SY-MANDT "Client (or the own one)
* COMMIT = ' ' "may possibly be COMMITed
* FORCE = ' ' "delete in any case
NAME = "Name of Temse object
EXCEPTIONS
FB_ERROR = 1 FB_RSTS_OTHER = 2 NO_OBJECT = 3 NO_PERMISSION = 4
IMPORTING Parameters details for RSTS_REMOVE_OBJECT
AUTHORITY - Who carried out the authorization check
Data type: RSTSTYPE-AUTHCHECKDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT - Client (or the own one)
Data type: RSTSTYPE-CLIENTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMIT - may possibly be COMMITed
Data type: RSTSTYPE-MOD_COMMITDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
FORCE - delete in any case
Data type: RSTSTYPE-MOD_FORCEDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
NAME - Name of Temse object
Data type: RSTSTYPE-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FB_ERROR - Errors in function module
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FB_RSTS_OTHER - other errors of TemSe-C system reported
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_OBJECT - Required TemSe object does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PERMISSION - No authorization for this operation
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSTS_REMOVE_OBJECT 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_fb_error | TYPE STRING, " | |||
| lv_authority | TYPE RSTSTYPE-AUTHCHECKD, " ' ' | |||
| lv_client | TYPE RSTSTYPE-CLIENT, " SY-MANDT | |||
| lv_fb_rsts_other | TYPE RSTSTYPE, " | |||
| lv_commit | TYPE RSTSTYPE-MOD_COMMIT, " ' ' | |||
| lv_no_object | TYPE RSTSTYPE, " | |||
| lv_force | TYPE RSTSTYPE-MOD_FORCE, " ' ' | |||
| lv_no_permission | TYPE RSTSTYPE, " | |||
| lv_name | TYPE RSTSTYPE-NAME. " |
|   CALL FUNCTION 'RSTS_REMOVE_OBJECT' "Delete TemSe object |
| EXPORTING | ||
| AUTHORITY | = lv_authority | |
| CLIENT | = lv_client | |
| COMMIT | = lv_commit | |
| FORCE | = lv_force | |
| NAME | = lv_name | |
| EXCEPTIONS | ||
| FB_ERROR = 1 | ||
| FB_RSTS_OTHER = 2 | ||
| NO_OBJECT = 3 | ||
| NO_PERMISSION = 4 | ||
| . " RSTS_REMOVE_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM RSTS_REMOVE_OBJECT
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 AUTHCHECKD FROM RSTSTYPE INTO @DATA(ld_authority). | ||||
| DATA(ld_authority) | = ' '. | |||
| "SELECT single CLIENT FROM RSTSTYPE INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
| "SELECT single MOD_COMMIT FROM RSTSTYPE INTO @DATA(ld_commit). | ||||
| DATA(ld_commit) | = ' '. | |||
| "SELECT single MOD_FORCE FROM RSTSTYPE INTO @DATA(ld_force). | ||||
| DATA(ld_force) | = ' '. | |||
| "SELECT single NAME FROM RSTSTYPE INTO @DATA(ld_name). | ||||
Search for further information about these or an SAP related objects