SAP RSAR_NAME_DETERMINE Function Module for
RSAR_NAME_DETERMINE is a standard rsar name determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rsar name determine FM, simply by entering the name RSAR_NAME_DETERMINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSAC
Program Name: SAPLRSAC
Main Program: SAPLRSAC
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSAR_NAME_DETERMINE 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 'RSAR_NAME_DETERMINE'".
EXPORTING
I_OBJECT = "Object as a template
I_OBJECT_ID = "Objekt-identifier
* I_PREFIX = "Prefix
* I_PREFIX2 = "2. Prefix, if necessary
* I_SEGMENT_ID = "Segment ID
IMPORTING
E_OBJECT_NAME = "generated object name
E_OBJECT_CUSTOMIZING = "Object name for customizing (without Slash)
EXCEPTIONS
INTERNAL_ERROR = 1 NAME_RANGE_EXHAUSTED = 2 UNKNOWN_OBJECT_ID = 3
IMPORTING Parameters details for RSAR_NAME_DETERMINE
I_OBJECT - Object as a template
Data type:Optional: No
Call by Reference: Yes
I_OBJECT_ID - Objekt-identifier
Data type:Optional: No
Call by Reference: Yes
I_PREFIX - Prefix
Data type:Optional: Yes
Call by Reference: Yes
I_PREFIX2 - 2. Prefix, if necessary
Data type:Optional: Yes
Call by Reference: Yes
I_SEGMENT_ID - Segment ID
Data type: RSSEGIDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSAR_NAME_DETERMINE
E_OBJECT_NAME - generated object name
Data type:Optional: No
Call by Reference: Yes
E_OBJECT_CUSTOMIZING - Object name for customizing (without Slash)
Data type:Optional: No
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR - Internal error, check log
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NAME_RANGE_EXHAUSTED - Namespace exhausted
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_OBJECT_ID - Unknown parameter object_id
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSAR_NAME_DETERMINE 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_object | TYPE STRING, " | |||
| lv_e_object_name | TYPE STRING, " | |||
| lv_internal_error | TYPE STRING, " | |||
| lv_i_object_id | TYPE STRING, " | |||
| lv_e_object_customizing | TYPE STRING, " | |||
| lv_name_range_exhausted | TYPE STRING, " | |||
| lv_i_prefix | TYPE STRING, " | |||
| lv_unknown_object_id | TYPE STRING, " | |||
| lv_i_prefix2 | TYPE STRING, " | |||
| lv_i_segment_id | TYPE RSSEGID. " |
|   CALL FUNCTION 'RSAR_NAME_DETERMINE' " |
| EXPORTING | ||
| I_OBJECT | = lv_i_object | |
| I_OBJECT_ID | = lv_i_object_id | |
| I_PREFIX | = lv_i_prefix | |
| I_PREFIX2 | = lv_i_prefix2 | |
| I_SEGMENT_ID | = lv_i_segment_id | |
| IMPORTING | ||
| E_OBJECT_NAME | = lv_e_object_name | |
| E_OBJECT_CUSTOMIZING | = lv_e_object_customizing | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| NAME_RANGE_EXHAUSTED = 2 | ||
| UNKNOWN_OBJECT_ID = 3 | ||
| . " RSAR_NAME_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM RSAR_NAME_DETERMINE
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