SAP RCP708_RESTRICT_KEYS_OPTIMIZE Function Module for NOTRANSL: RMS-RCP: Optimierung der Suchmenge
RCP708_RESTRICT_KEYS_OPTIMIZE is a standard rcp708 restrict keys optimize SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: RMS-RCP: Optimierung der Suchmenge 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 rcp708 restrict keys optimize FM, simply by entering the name RCP708_RESTRICT_KEYS_OPTIMIZE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RCP708
Program Name: SAPLRCP708
Main Program: SAPLRCP708
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RCP708_RESTRICT_KEYS_OPTIMIZE 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 'RCP708_RESTRICT_KEYS_OPTIMIZE'"NOTRANSL: RMS-RCP: Optimierung der Suchmenge.
EXPORTING
I_FLG_NO_RECIPE = "General Indicator
I_FLG_NO_STAGE = "General Indicator
IT_FRM_KEYS = "
IT_RCP_KEYS = "RMS-RCP: Table Type for RCGSTDRECN
IMPORTING
ET_RESTRICTION_KEYS = "RMS-RCP: API - Table Type for Specification Key
IMPORTING Parameters details for RCP708_RESTRICT_KEYS_OPTIMIZE
I_FLG_NO_RECIPE - General Indicator
Data type: FLAGOptional: No
Call by Reference: No ( called with pass by value option)
I_FLG_NO_STAGE - General Indicator
Data type: FLAGOptional: No
Call by Reference: No ( called with pass by value option)
IT_FRM_KEYS -
Data type: FRM31_KEY_TAB_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
IT_RCP_KEYS - RMS-RCP: Table Type for RCGSTDRECN
Data type: RCPTY_RCGSTDRECNOptional: No
Call by Reference: Yes
EXPORTING Parameters details for RCP708_RESTRICT_KEYS_OPTIMIZE
ET_RESTRICTION_KEYS - RMS-RCP: API - Table Type for Specification Key
Data type: RCPTY_API_SRCH_RECNOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RCP708_RESTRICT_KEYS_OPTIMIZE 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_flg_no_recipe | TYPE FLAG, " | |||
| lv_et_restriction_keys | TYPE RCPTY_API_SRCH_RECN, " | |||
| lv_i_flg_no_stage | TYPE FLAG, " | |||
| lv_it_frm_keys | TYPE FRM31_KEY_TAB_TYPE, " | |||
| lv_it_rcp_keys | TYPE RCPTY_RCGSTDRECN. " |
|   CALL FUNCTION 'RCP708_RESTRICT_KEYS_OPTIMIZE' "NOTRANSL: RMS-RCP: Optimierung der Suchmenge |
| EXPORTING | ||
| I_FLG_NO_RECIPE | = lv_i_flg_no_recipe | |
| I_FLG_NO_STAGE | = lv_i_flg_no_stage | |
| IT_FRM_KEYS | = lv_it_frm_keys | |
| IT_RCP_KEYS | = lv_it_rcp_keys | |
| IMPORTING | ||
| ET_RESTRICTION_KEYS | = lv_et_restriction_keys | |
| . " RCP708_RESTRICT_KEYS_OPTIMIZE | ||
ABAP code using 7.40 inline data declarations to call FM RCP708_RESTRICT_KEYS_OPTIMIZE
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