SAP RSOBI_EXT_NAME_CHECK Function Module for Checks if the specified name can be used
RSOBI_EXT_NAME_CHECK is a standard rsobi ext 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 if the specified name can be used 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 rsobi ext name check FM, simply by entering the name RSOBI_EXT_NAME_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSOBI_MF_EXT
Program Name: SAPLRSOBI_MF_EXT
Main Program: SAPLRSOBI_MF_EXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RSOBI_EXT_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 'RSOBI_EXT_NAME_CHECK'"Checks if the specified name can be used.
EXPORTING
I_OBJNM = "Object Name of Enhanced Object
I_TLOGO = "Object Type (TLOGO) of Enhanced Object
I_FIELDNM = "Field Name
I_NAME = "Required Name
IMPORTING
E_VALID = "Boolean Object Name is Valid
TABLES
* E_T_RETURN = "Return Table
IMPORTING Parameters details for RSOBI_EXT_NAME_CHECK
I_OBJNM - Object Name of Enhanced Object
Data type: SOBJ_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_TLOGO - Object Type (TLOGO) of Enhanced Object
Data type: RSTLOGOOptional: No
Call by Reference: No ( called with pass by value option)
I_FIELDNM - Field Name
Data type: FIELDNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_NAME - Required Name
Data type: SOBJ_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSOBI_EXT_NAME_CHECK
E_VALID - Boolean Object Name is Valid
Data type: RS_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RSOBI_EXT_NAME_CHECK
E_T_RETURN - Return Table
Data type: BAPIRET2_TOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for RSOBI_EXT_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_e_valid | TYPE RS_BOOL, " | |||
| lv_i_objnm | TYPE SOBJ_NAME, " | |||
| lt_e_t_return | TYPE STANDARD TABLE OF BAPIRET2_T, " | |||
| lv_i_tlogo | TYPE RSTLOGO, " | |||
| lv_i_fieldnm | TYPE FIELDNAME, " | |||
| lv_i_name | TYPE SOBJ_NAME. " |
|   CALL FUNCTION 'RSOBI_EXT_NAME_CHECK' "Checks if the specified name can be used |
| EXPORTING | ||
| I_OBJNM | = lv_i_objnm | |
| I_TLOGO | = lv_i_tlogo | |
| I_FIELDNM | = lv_i_fieldnm | |
| I_NAME | = lv_i_name | |
| IMPORTING | ||
| E_VALID | = lv_e_valid | |
| TABLES | ||
| E_T_RETURN | = lt_e_t_return | |
| . " RSOBI_EXT_NAME_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM RSOBI_EXT_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.Search for further information about these or an SAP related objects