SAP RSTS_CHECK_NAME Function Module for Check TemSe Object Name for Validity
RSTS_CHECK_NAME is a standard rsts check name SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check TemSe Object Name for Validity 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 check name FM, simply by entering the name RSTS_CHECK_NAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: STMS
Program Name: SAPLSTMS
Main Program: SAPLSTMS
Appliation area: S
Release date: 01-Feb-1999
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSTS_CHECK_NAME 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_CHECK_NAME'"Check TemSe Object Name for Validity.
EXPORTING
NAME = "TemSe Object Name to Check
EXCEPTIONS
FB_NAME_INVALID = 1
IMPORTING Parameters details for RSTS_CHECK_NAME
NAME - TemSe Object Name to Check
Data type: RSTSTYPE-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FB_NAME_INVALID - Invalid Object Name
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSTS_CHECK_NAME 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_name | TYPE RSTSTYPE-NAME, " | |||
| lv_fb_name_invalid | TYPE RSTSTYPE. " |
|   CALL FUNCTION 'RSTS_CHECK_NAME' "Check TemSe Object Name for Validity |
| EXPORTING | ||
| NAME | = lv_name | |
| EXCEPTIONS | ||
| FB_NAME_INVALID = 1 | ||
| . " RSTS_CHECK_NAME | ||
ABAP code using 7.40 inline data declarations to call FM RSTS_CHECK_NAME
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 RSTSTYPE INTO @DATA(ld_name). | ||||
Search for further information about these or an SAP related objects