SAP SIW_RFC_READ_PROXY_KEY_BY_RNG Function Module for Determine Proxies by Search Ranges
SIW_RFC_READ_PROXY_KEY_BY_RNG is a standard siw rfc read proxy key by rng SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Proxies by Search Ranges 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 siw rfc read proxy key by rng FM, simply by entering the name SIW_RFC_READ_PROXY_KEY_BY_RNG into the relevant SAP transaction such as SE37 or SE38.
Function Group: SIW_RFC_REPOSITORY
Program Name: SAPLSIW_RFC_REPOSITORY
Main Program: SAPLSIW_RFC_REPOSITORY
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SIW_RFC_READ_PROXY_KEY_BY_RNG 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 'SIW_RFC_READ_PROXY_KEY_BY_RNG'"Determine Proxies by Search Ranges.
EXPORTING
I_TAB_R3_TYPE = "Proxy Search Range: ABAP Type
I_TAB_R3_NAME = "Proxy Search Range: ABAP Name
I_TAB_TYPE = "Proxy Search Range: Category (ifmtypedef, ...)
I_TAB_NAME = "Proxy Search Range: Repository Name
I_TAB_NAME' ' = "Proxy Search Range: Namespaces
I_DIRECTION = "Proxy Generation: Interface Direction (Inbound/Outbound)
I_TAB_GEN_APPL_RANGE = "Range Table for PRXGENAPPL
I_MAX_COUNT = "Index of Internal Tables
IMPORTING
E_TAB_PROXY_KEYS = "Proxy Key Information
E_TAB_INTF_DATA = "Proxy: Interface Details
E_STR_EXCEPTION = "Message/Exception
IMPORTING Parameters details for SIW_RFC_READ_PROXY_KEY_BY_RNG
I_TAB_R3_TYPE - Proxy Search Range: ABAP Type
Data type: SIW_TAB_R3OBJ_RANGESOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_R3_NAME - Proxy Search Range: ABAP Name
Data type: SIW_TAB_R3NAME_RANGESOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_TYPE - Proxy Search Range: Category (ifmtypedef, ...)
Data type: SIW_TAB_TYPE_RANGESOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_NAME - Proxy Search Range: Repository Name
Data type: SIW_TAB_NAME_RANGESOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_NAMESPACE - Proxy Search Range: Namespaces
Data type: SIW_TAB_NSPCE_RANGESOptional: No
Call by Reference: No ( called with pass by value option)
I_DIRECTION - Proxy Generation: Interface Direction (Inbound/Outbound)
Data type: SIW_DTE_PRX_DIROptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_GEN_APPL_RANGE - Range Table for PRXGENAPPL
Data type: SIW_TAB_PROXY_GEN_APPLOptional: No
Call by Reference: No ( called with pass by value option)
I_MAX_COUNT - Index of Internal Tables
Data type: SY-TABIXOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SIW_RFC_READ_PROXY_KEY_BY_RNG
E_TAB_PROXY_KEYS - Proxy Key Information
Data type: SIW_TAB_PROXY_KEYSOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_INTF_DATA - Proxy: Interface Details
Data type: SIW_TAB_INTF_DETAILOptional: No
Call by Reference: No ( called with pass by value option)
E_STR_EXCEPTION - Message/Exception
Data type: SIW_STR_MSGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SIW_RFC_READ_PROXY_KEY_BY_RNG 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_tab_r3_type | TYPE SIW_TAB_R3OBJ_RANGES, " | |||
| lv_e_tab_proxy_keys | TYPE SIW_TAB_PROXY_KEYS, " | |||
| lv_i_tab_r3_name | TYPE SIW_TAB_R3NAME_RANGES, " | |||
| lv_e_tab_intf_data | TYPE SIW_TAB_INTF_DETAIL, " | |||
| lv_i_tab_type | TYPE SIW_TAB_TYPE_RANGES, " | |||
| lv_e_str_exception | TYPE SIW_STR_MSG, " | |||
| lv_i_tab_name | TYPE SIW_TAB_NAME_RANGES, " | |||
| lv_i_tab_namespace | TYPE SIW_TAB_NSPCE_RANGES, " | |||
| lv_i_direction | TYPE SIW_DTE_PRX_DIR, " | |||
| lv_i_tab_gen_appl_range | TYPE SIW_TAB_PROXY_GEN_APPL, " | |||
| lv_i_max_count | TYPE SY-TABIX. " |
|   CALL FUNCTION 'SIW_RFC_READ_PROXY_KEY_BY_RNG' "Determine Proxies by Search Ranges |
| EXPORTING | ||
| I_TAB_R3_TYPE | = lv_i_tab_r3_type | |
| I_TAB_R3_NAME | = lv_i_tab_r3_name | |
| I_TAB_TYPE | = lv_i_tab_type | |
| I_TAB_NAME | = lv_i_tab_name | |
| I_TAB_NAMESPACE | = lv_i_tab_namespace | |
| I_DIRECTION | = lv_i_direction | |
| I_TAB_GEN_APPL_RANGE | = lv_i_tab_gen_appl_range | |
| I_MAX_COUNT | = lv_i_max_count | |
| IMPORTING | ||
| E_TAB_PROXY_KEYS | = lv_e_tab_proxy_keys | |
| E_TAB_INTF_DATA | = lv_e_tab_intf_data | |
| E_STR_EXCEPTION | = lv_e_str_exception | |
| . " SIW_RFC_READ_PROXY_KEY_BY_RNG | ||
ABAP code using 7.40 inline data declarations to call FM SIW_RFC_READ_PROXY_KEY_BY_RNG
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 TABIX FROM SY INTO @DATA(ld_i_max_count). | ||||
Search for further information about these or an SAP related objects