SAP RM_GAP_GET_SAVEIDS_PER_VIEW Function Module for RM ALM: Determines all save IDs for a view
RM_GAP_GET_SAVEIDS_PER_VIEW is a standard rm gap get saveids per view SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RM ALM: Determines all save IDs for a view 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 rm gap get saveids per view FM, simply by entering the name RM_GAP_GET_SAVEIDS_PER_VIEW into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMG6
Program Name: SAPLRMG6
Main Program: SAPLRMG6
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_GAP_GET_SAVEIDS_PER_VIEW 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 'RM_GAP_GET_SAVEIDS_PER_VIEW'"RM ALM: Determines all save IDs for a view.
EXPORTING
SICHTID = "View of an RM Area
TABLES
* ET_GAP_SAVEIDS = "RM ALM: IDs of Saved Gap Results
EXCEPTIONS
NO_SAVE_IDS = 1 NO_SICHTID = 2
IMPORTING Parameters details for RM_GAP_GET_SAVEIDS_PER_VIEW
SICHTID - View of an RM Area
Data type: JBRSI-SICHTIDOptional: No
Call by Reference: Yes
TABLES Parameters details for RM_GAP_GET_SAVEIDS_PER_VIEW
ET_GAP_SAVEIDS - RM ALM: IDs of Saved Gap Results
Data type: JBRSAVE_IDSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_SAVE_IDS - There are no gap results saved for this view
Data type:Optional: No
Call by Reference: Yes
NO_SICHTID - No view ID was transferred
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RM_GAP_GET_SAVEIDS_PER_VIEW 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_sichtid | TYPE JBRSI-SICHTID, " | |||
| lv_no_save_ids | TYPE JBRSI, " | |||
| lt_et_gap_saveids | TYPE STANDARD TABLE OF JBRSAVE_IDS, " | |||
| lv_no_sichtid | TYPE JBRSAVE_IDS. " |
|   CALL FUNCTION 'RM_GAP_GET_SAVEIDS_PER_VIEW' "RM ALM: Determines all save IDs for a view |
| EXPORTING | ||
| SICHTID | = lv_sichtid | |
| TABLES | ||
| ET_GAP_SAVEIDS | = lt_et_gap_saveids | |
| EXCEPTIONS | ||
| NO_SAVE_IDS = 1 | ||
| NO_SICHTID = 2 | ||
| . " RM_GAP_GET_SAVEIDS_PER_VIEW | ||
ABAP code using 7.40 inline data declarations to call FM RM_GAP_GET_SAVEIDS_PER_VIEW
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.| "SELECT single SICHTID FROM JBRSI INTO @DATA(ld_sichtid). | ||||
Search for further information about these or an SAP related objects