SAP RRSV_OBJECT_NAME_CHECK Function Module for Checks Validity of Object Name
RRSV_OBJECT_NAME_CHECK is a standard rrsv object name check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Checks Validity of Object Name 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 rrsv object name check FM, simply by entering the name RRSV_OBJECT_NAME_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: RRSV
Program Name: SAPLRRSV
Main Program: SAPLRRSV
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RRSV_OBJECT_NAME_CHECK 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 'RRSV_OBJECT_NAME_CHECK'"Checks Validity of Object Name.
EXPORTING
* I_MODE = RRSV_C_MODE_DEFINE "
* I_TYPE = RRSV_C_TYPE_VARIABLE "
* I_VARIABLE = "Name (ID) of a Report Variable
* I_COMPID = "Name (ID) of a reporting component
* I_CHANNEL = "Channel in the InfoCatalog
IMPORTING
E_TRANSPORTABLE = "
EXCEPTIONS
RESERVED_NAME_CREATE_CUS = 1 RESERVED_NAME_MODIFY_CUS = 2 RESERVED_NAME_CREATE_SAP = 3 RESERVED_NAME_MODIFY_SAP = 4 INVALID_CHARACTER_CREATE = 5 INVALID_TYPE = 6 INVALID_MODE = 7
IMPORTING Parameters details for RRSV_OBJECT_NAME_CHECK
I_MODE -
Data type: RS_FLAGDefault: RRSV_C_MODE_DEFINE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TYPE -
Data type: RS_FLAGDefault: RRSV_C_TYPE_VARIABLE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VARIABLE - Name (ID) of a Report Variable
Data type: RSZGLOBV-VNAMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_COMPID - Name (ID) of a reporting component
Data type: RSZCOMPDIR-COMPIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CHANNEL - Channel in the InfoCatalog
Data type: RSRCHANNEL-NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RRSV_OBJECT_NAME_CHECK
E_TRANSPORTABLE -
Data type: RS_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
RESERVED_NAME_CREATE_CUS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RESERVED_NAME_MODIFY_CUS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RESERVED_NAME_CREATE_SAP -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RESERVED_NAME_MODIFY_SAP -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_CHARACTER_CREATE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_TYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_MODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RRSV_OBJECT_NAME_CHECK 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_mode | TYPE RS_FLAG, " RRSV_C_MODE_DEFINE | |||
| lv_e_transportable | TYPE RS_BOOL, " | |||
| lv_reserved_name_create_cus | TYPE RS_BOOL, " | |||
| lv_i_type | TYPE RS_FLAG, " RRSV_C_TYPE_VARIABLE | |||
| lv_reserved_name_modify_cus | TYPE RS_FLAG, " | |||
| lv_i_variable | TYPE RSZGLOBV-VNAM, " | |||
| lv_reserved_name_create_sap | TYPE RSZGLOBV, " | |||
| lv_i_compid | TYPE RSZCOMPDIR-COMPID, " | |||
| lv_reserved_name_modify_sap | TYPE RSZCOMPDIR, " | |||
| lv_i_channel | TYPE RSRCHANNEL-NAME, " | |||
| lv_invalid_character_create | TYPE RSRCHANNEL, " | |||
| lv_invalid_type | TYPE RSRCHANNEL, " | |||
| lv_invalid_mode | TYPE RSRCHANNEL. " |
|   CALL FUNCTION 'RRSV_OBJECT_NAME_CHECK' "Checks Validity of Object Name |
| EXPORTING | ||
| I_MODE | = lv_i_mode | |
| I_TYPE | = lv_i_type | |
| I_VARIABLE | = lv_i_variable | |
| I_COMPID | = lv_i_compid | |
| I_CHANNEL | = lv_i_channel | |
| IMPORTING | ||
| E_TRANSPORTABLE | = lv_e_transportable | |
| EXCEPTIONS | ||
| RESERVED_NAME_CREATE_CUS = 1 | ||
| RESERVED_NAME_MODIFY_CUS = 2 | ||
| RESERVED_NAME_CREATE_SAP = 3 | ||
| RESERVED_NAME_MODIFY_SAP = 4 | ||
| INVALID_CHARACTER_CREATE = 5 | ||
| INVALID_TYPE = 6 | ||
| INVALID_MODE = 7 | ||
| . " RRSV_OBJECT_NAME_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM RRSV_OBJECT_NAME_CHECK
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.| DATA(ld_i_mode) | = RRSV_C_MODE_DEFINE. | |||
| DATA(ld_i_type) | = RRSV_C_TYPE_VARIABLE. | |||
| "SELECT single VNAM FROM RSZGLOBV INTO @DATA(ld_i_variable). | ||||
| "SELECT single COMPID FROM RSZCOMPDIR INTO @DATA(ld_i_compid). | ||||
| "SELECT single NAME FROM RSRCHANNEL INTO @DATA(ld_i_channel). | ||||
Search for further information about these or an SAP related objects