SAP RSD_NAME_CHECK Function Module for Check Object Names (IOBJ, CUBE, CTRT) for New Objects
RSD_NAME_CHECK is a standard rsd 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 Check Object Names (IOBJ, CUBE, CTRT) for New Objects 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 rsd name check FM, simply by entering the name RSD_NAME_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSDN
Program Name: SAPLRSDN
Main Program: SAPLRSDN
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSD_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 'RSD_NAME_CHECK'"Check Object Names (IOBJ, CUBE, CTRT) for New Objects.
EXPORTING
I_OBJNM = "Name
I_TLOGO = "Object Type (IOBJ, CUBE, DIME, CTRT...)
* I_BWAPPL = RS_C_' '10 "BW Application, Proposal (Only for Customer Objects)
* I_OBJECT_CTO_ENABLED = RS_C_TRUE "Object is transportable
IMPORTING
E_NAME' ' = "Namespace
E_N' 'GEN = "Namespace (Gen. Objects)
E_NAME_W_O_PREFIX = "Name (Without Prefix) (30)
E_SOBJNM_W_O_PREFIX = "Name (Without Prefix) (40)
E_RELEVANT_NAME_W_O_PREFIX = "Relevant Name Without Prefix
E_BWAPPL = "BW application
E_SYSTP = "System Type
EXCEPTIONS
NAME_INVALID = 1 BWAPPL_NOT_SELECTED = 2
IMPORTING Parameters details for RSD_NAME_CHECK
I_OBJNM - Name
Data type:Optional: No
Call by Reference: Yes
I_TLOGO - Object Type (IOBJ, CUBE, DIME, CTRT...)
Data type: RS_TLOGOOptional: No
Call by Reference: Yes
I_BWAPPL - BW Application, Proposal (Only for Customer Objects)
Data type: RSBWAPPLDefault: RS_C_SPACE10
Optional: Yes
Call by Reference: Yes
I_OBJECT_CTO_ENABLED - Object is transportable
Data type: RS_BOOLDefault: RS_C_TRUE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSD_NAME_CHECK
E_NAMESPACE - Namespace
Data type: NAMESPACEOptional: No
Call by Reference: Yes
E_NSPACEGEN - Namespace (Gen. Objects)
Data type: NAMESPACEOptional: No
Call by Reference: Yes
E_NAME_W_O_PREFIX - Name (Without Prefix) (30)
Data type: RS_CHAR30Optional: No
Call by Reference: Yes
E_SOBJNM_W_O_PREFIX - Name (Without Prefix) (40)
Data type: SOBJ_NAMEOptional: No
Call by Reference: Yes
E_RELEVANT_NAME_W_O_PREFIX - Relevant Name Without Prefix
Data type: RS_CHAR30Optional: No
Call by Reference: Yes
E_BWAPPL - BW application
Data type: RSBWAPPLOptional: No
Call by Reference: Yes
E_SYSTP - System Type
Data type: RSSYSTPOptional: No
Call by Reference: Yes
EXCEPTIONS details
NAME_INVALID - Name Incorrect
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BWAPPL_NOT_SELECTED - Select a BW application
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSD_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_objnm | TYPE STRING, " | |||
| lv_e_namespace | TYPE NAMESPACE, " | |||
| lv_name_invalid | TYPE NAMESPACE, " | |||
| lv_i_tlogo | TYPE RS_TLOGO, " | |||
| lv_e_nspacegen | TYPE NAMESPACE, " | |||
| lv_bwappl_not_selected | TYPE NAMESPACE, " | |||
| lv_i_bwappl | TYPE RSBWAPPL, " RS_C_SPACE10 | |||
| lv_e_name_w_o_prefix | TYPE RS_CHAR30, " | |||
| lv_e_sobjnm_w_o_prefix | TYPE SOBJ_NAME, " | |||
| lv_i_object_cto_enabled | TYPE RS_BOOL, " RS_C_TRUE | |||
| lv_e_relevant_name_w_o_prefix | TYPE RS_CHAR30, " | |||
| lv_e_bwappl | TYPE RSBWAPPL, " | |||
| lv_e_systp | TYPE RSSYSTP. " |
|   CALL FUNCTION 'RSD_NAME_CHECK' "Check Object Names (IOBJ, CUBE, CTRT) for New Objects |
| EXPORTING | ||
| I_OBJNM | = lv_i_objnm | |
| I_TLOGO | = lv_i_tlogo | |
| I_BWAPPL | = lv_i_bwappl | |
| I_OBJECT_CTO_ENABLED | = lv_i_object_cto_enabled | |
| IMPORTING | ||
| E_NAMESPACE | = lv_e_namespace | |
| E_NSPACEGEN | = lv_e_nspacegen | |
| E_NAME_W_O_PREFIX | = lv_e_name_w_o_prefix | |
| E_SOBJNM_W_O_PREFIX | = lv_e_sobjnm_w_o_prefix | |
| E_RELEVANT_NAME_W_O_PREFIX | = lv_e_relevant_name_w_o_prefix | |
| E_BWAPPL | = lv_e_bwappl | |
| E_SYSTP | = lv_e_systp | |
| EXCEPTIONS | ||
| NAME_INVALID = 1 | ||
| BWAPPL_NOT_SELECTED = 2 | ||
| . " RSD_NAME_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM RSD_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_bwappl) | = RS_C_' '10. | |||
| DATA(ld_i_object_cto_enabled) | = RS_C_TRUE. | |||
Search for further information about these or an SAP related objects