SAP RSQ_ISET_SAVE_RUNTIME_OBJECT Function Module for save the run time object
RSQ_ISET_SAVE_RUNTIME_OBJECT is a standard rsq iset save runtime object SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for save the run time object 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 rsq iset save runtime object FM, simply by entering the name RSQ_ISET_SAVE_RUNTIME_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSQ_ISET_DB_RUNT
Program Name: SAPLRSQ_ISET_DB_RUNT
Main Program: SAPLRSQ_ISET_DB_RUNT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSQ_ISET_SAVE_RUNTIME_OBJECT 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 'RSQ_ISET_SAVE_RUNTIME_OBJECT'"save the run time object.
EXPORTING
INFOSET = "InfoSet
* RT_VI_MAP_FIELDS = "Assignment: VI-Fields
RT_INFOSET_DESC = "InfoSet: Include Structure for Technical Enhancements
RT_DB_QUERY = "Database view
RT_FQUERIES = "DB View per Field (SID)
RT_TABLES = "TType: InfoSet Table Objects (Runtime)
RT_FIELDS = "TType: InfoSet Field Objects (Runtime)
RT_DDIC_STRUC = "Table Name (OLAP)
RT_ISET_STRUC = "Table Name (InfoSet)
* RT_AMB_JOIN = "TTyp: InfoSet Ambiguous Joins
IMPORTING Parameters details for RSQ_ISET_SAVE_RUNTIME_OBJECT
INFOSET - InfoSet
Data type: RSQINFOSETOptional: No
Call by Reference: No ( called with pass by value option)
RT_VI_MAP_FIELDS - Assignment: VI-Fields
Data type: RSQ_T_VI_MAP_FIELDSOptional: Yes
Call by Reference: Yes
RT_INFOSET_DESC - InfoSet: Include Structure for Technical Enhancements
Data type: RSQSISETXOptional: No
Call by Reference: Yes
RT_DB_QUERY - Database view
Data type: RSDRS_SX_QUERYOptional: No
Call by Reference: Yes
RT_FQUERIES - DB View per Field (SID)
Data type: RSQIS_T_FQUERYOptional: No
Call by Reference: Yes
RT_TABLES - TType: InfoSet Table Objects (Runtime)
Data type: RSQ_T_TOBJ_RUNTOptional: No
Call by Reference: Yes
RT_FIELDS - TType: InfoSet Field Objects (Runtime)
Data type: RSQ_T_FOBJ_RUNTOptional: No
Call by Reference: Yes
RT_DDIC_STRUC - Table Name (OLAP)
Data type: TABNAMEOptional: No
Call by Reference: Yes
RT_ISET_STRUC - Table Name (InfoSet)
Data type: TABNAMEOptional: No
Call by Reference: Yes
RT_AMB_JOIN - TTyp: InfoSet Ambiguous Joins
Data type: RSQ_T_AMB_JOINOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for RSQ_ISET_SAVE_RUNTIME_OBJECT 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_infoset | TYPE RSQINFOSET, " | |||
| lv_rt_vi_map_fields | TYPE RSQ_T_VI_MAP_FIELDS, " | |||
| lv_rt_infoset_desc | TYPE RSQSISETX, " | |||
| lv_rt_db_query | TYPE RSDRS_SX_QUERY, " | |||
| lv_rt_fqueries | TYPE RSQIS_T_FQUERY, " | |||
| lv_rt_tables | TYPE RSQ_T_TOBJ_RUNT, " | |||
| lv_rt_fields | TYPE RSQ_T_FOBJ_RUNT, " | |||
| lv_rt_ddic_struc | TYPE TABNAME, " | |||
| lv_rt_iset_struc | TYPE TABNAME, " | |||
| lv_rt_amb_join | TYPE RSQ_T_AMB_JOIN. " |
|   CALL FUNCTION 'RSQ_ISET_SAVE_RUNTIME_OBJECT' "save the run time object |
| EXPORTING | ||
| INFOSET | = lv_infoset | |
| RT_VI_MAP_FIELDS | = lv_rt_vi_map_fields | |
| RT_INFOSET_DESC | = lv_rt_infoset_desc | |
| RT_DB_QUERY | = lv_rt_db_query | |
| RT_FQUERIES | = lv_rt_fqueries | |
| RT_TABLES | = lv_rt_tables | |
| RT_FIELDS | = lv_rt_fields | |
| RT_DDIC_STRUC | = lv_rt_ddic_struc | |
| RT_ISET_STRUC | = lv_rt_iset_struc | |
| RT_AMB_JOIN | = lv_rt_amb_join | |
| . " RSQ_ISET_SAVE_RUNTIME_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM RSQ_ISET_SAVE_RUNTIME_OBJECT
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