SAP RSAR_ODS_NAME_MULTI_GET Function Module for output ODS name and technical description
RSAR_ODS_NAME_MULTI_GET is a standard rsar ods name multi get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for output ODS name and technical description 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 rsar ods name multi get FM, simply by entering the name RSAR_ODS_NAME_MULTI_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSAODS
Program Name: SAPLRSAODS
Main Program: SAPLRSAODS
Appliation area: B
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSAR_ODS_NAME_MULTI_GET 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_ODS_NAME_MULTI_GET'"output ODS name and technical description.
EXPORTING
I_T_REQUEST = "Requesttabelle
* I_PSA_NAME = "Name of the Persistant Staging Area
IMPORTING
E_T_REQUEST_ODS = "Request in ODS-Tabelle
E_T_REQUEST_ODS_FULL = "Request in ODS-Tabelle komplett
E_T_ODS_MISSING = "Request deren ODS-Tabelle nicht mehr existiert
E_ODS_MISSING = "X = ODS-Tabellen existieren nicht mehr
EXCEPTIONS
PARAMETER_FAILURE = 1 NO_ODS_FOUND = 2 NO_FIELDS_TO_ODS = 3
IMPORTING Parameters details for RSAR_ODS_NAME_MULTI_GET
I_T_REQUEST - Requesttabelle
Data type: RSODS_R_REQUESTOptional: No
Call by Reference: No ( called with pass by value option)
I_PSA_NAME - Name of the Persistant Staging Area
Data type: RSODSNAMEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSAR_ODS_NAME_MULTI_GET
E_T_REQUEST_ODS - Request in ODS-Tabelle
Data type: RSODS_T_REQUEST_ODSOptional: No
Call by Reference: No ( called with pass by value option)
E_T_REQUEST_ODS_FULL - Request in ODS-Tabelle komplett
Data type: RSODS_T_REQUEST_ODS_FULLOptional: No
Call by Reference: No ( called with pass by value option)
E_T_ODS_MISSING - Request deren ODS-Tabelle nicht mehr existiert
Data type: RSODS_T_REQUEST_ODSOptional: No
Call by Reference: No ( called with pass by value option)
E_ODS_MISSING - X = ODS-Tabellen existieren nicht mehr
Data type: RS_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARAMETER_FAILURE - Missing or Incorrect Parameter
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ODS_FOUND - Kein ODS gefunden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_FIELDS_TO_ODS - Keine Felder zum ODS gefunden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSAR_ODS_NAME_MULTI_GET 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_t_request | TYPE RSODS_R_REQUEST, " | |||
| lv_e_t_request_ods | TYPE RSODS_T_REQUEST_ODS, " | |||
| lv_parameter_failure | TYPE RSODS_T_REQUEST_ODS, " | |||
| lv_i_psa_name | TYPE RSODSNAME, " | |||
| lv_no_ods_found | TYPE RSODSNAME, " | |||
| lv_e_t_request_ods_full | TYPE RSODS_T_REQUEST_ODS_FULL, " | |||
| lv_e_t_ods_missing | TYPE RSODS_T_REQUEST_ODS, " | |||
| lv_no_fields_to_ods | TYPE RSODS_T_REQUEST_ODS, " | |||
| lv_e_ods_missing | TYPE RS_BOOL. " |
|   CALL FUNCTION 'RSAR_ODS_NAME_MULTI_GET' "output ODS name and technical description |
| EXPORTING | ||
| I_T_REQUEST | = lv_i_t_request | |
| I_PSA_NAME | = lv_i_psa_name | |
| IMPORTING | ||
| E_T_REQUEST_ODS | = lv_e_t_request_ods | |
| E_T_REQUEST_ODS_FULL | = lv_e_t_request_ods_full | |
| E_T_ODS_MISSING | = lv_e_t_ods_missing | |
| E_ODS_MISSING | = lv_e_ods_missing | |
| EXCEPTIONS | ||
| PARAMETER_FAILURE = 1 | ||
| NO_ODS_FOUND = 2 | ||
| NO_FIELDS_TO_ODS = 3 | ||
| . " RSAR_ODS_NAME_MULTI_GET | ||
ABAP code using 7.40 inline data declarations to call FM RSAR_ODS_NAME_MULTI_GET
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