SAP CHECK_VALID_OBJNAME Function Module for Checks if the Object Name is valid for a component
CHECK_VALID_OBJNAME is a standard check valid objname 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 if the Object Name is valid for a component 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 check valid objname FM, simply by entering the name CHECK_VALID_OBJNAME into the relevant SAP transaction such as SE37 or SE38.
Function Group: BSP_DYN_DESIGN
Program Name: SAPLBSP_DYN_DESIGN
Main Program: SAPLBSP_DYN_DESIGN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CHECK_VALID_OBJNAME 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 'CHECK_VALID_OBJNAME'"Checks if the Object Name is valid for a component.
EXPORTING
COMPONENT = "Component Name
OBJ = "External Name of Object
* ATTR_NAME = "Component name
* CHILD_OBJ = "External Name of Object
IMPORTING
IS_OBJ_VALID = "Boolean Variable (X=True, -=False, Space=Unknown)
IS_ATTR_VALID = "Boolean Variable (X=True, -=False, Space=Unknown)
IS_CHILD_VALID = "Boolean Variable (X=True, -=False, Space=Unknown)
IS_OBJ_ROOT = "Boolean Variable (X=True, -=False, Space=Unknown)
IMPORTING Parameters details for CHECK_VALID_OBJNAME
COMPONENT - Component Name
Data type: CRMT_COMPONENT_NAMEOptional: No
Call by Reference: Yes
OBJ - External Name of Object
Data type: CRMT_EXT_OBJ_NAMEOptional: No
Call by Reference: Yes
ATTR_NAME - Component name
Data type: NAME_KOMPOptional: Yes
Call by Reference: Yes
CHILD_OBJ - External Name of Object
Data type: CRMT_EXT_OBJ_NAMEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CHECK_VALID_OBJNAME
IS_OBJ_VALID - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
IS_ATTR_VALID - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
IS_CHILD_VALID - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
IS_OBJ_ROOT - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CHECK_VALID_OBJNAME 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_component | TYPE CRMT_COMPONENT_NAME, " | |||
| lv_is_obj_valid | TYPE BOOLEAN, " | |||
| lv_obj | TYPE CRMT_EXT_OBJ_NAME, " | |||
| lv_is_attr_valid | TYPE BOOLEAN, " | |||
| lv_attr_name | TYPE NAME_KOMP, " | |||
| lv_is_child_valid | TYPE BOOLEAN, " | |||
| lv_child_obj | TYPE CRMT_EXT_OBJ_NAME, " | |||
| lv_is_obj_root | TYPE BOOLEAN. " |
|   CALL FUNCTION 'CHECK_VALID_OBJNAME' "Checks if the Object Name is valid for a component |
| EXPORTING | ||
| COMPONENT | = lv_component | |
| OBJ | = lv_obj | |
| ATTR_NAME | = lv_attr_name | |
| CHILD_OBJ | = lv_child_obj | |
| IMPORTING | ||
| IS_OBJ_VALID | = lv_is_obj_valid | |
| IS_ATTR_VALID | = lv_is_attr_valid | |
| IS_CHILD_VALID | = lv_is_child_valid | |
| IS_OBJ_ROOT | = lv_is_obj_root | |
| . " CHECK_VALID_OBJNAME | ||
ABAP code using 7.40 inline data declarations to call FM CHECK_VALID_OBJNAME
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.Search for further information about these or an SAP related objects