SAP ICF_READ_PROXY_CONFIGURATION Function Module for
ICF_READ_PROXY_CONFIGURATION is a standard icf read proxy configuration SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 icf read proxy configuration FM, simply by entering the name ICF_READ_PROXY_CONFIGURATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SHTTP
Program Name: SAPLSHTTP
Main Program: SAPLSHTTP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICF_READ_PROXY_CONFIGURATION 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 'ICF_READ_PROXY_CONFIGURATION'".
EXPORTING
* AUTHORITY_CHECK = 'X' "
* MANDANT = SY-MANDT "R/3 System, Client Number from Logon
* REQUEST = "HTTP Framework (iHTTP) HTTP Request
* PROTOCOL = 1 "
HOSTNAME = "
IMPORTING
PROXY_CONFIGURAION = "Plugin Proxy Configuration for HTTP/HTTPS Client (Host/Port)
EXCEPTIONS
AUTHORITY_NOT_AVAILABLE = 1 PROXY_INVALID_PROTOCOL = 2 PROXY_ENTRY_NOT_AVAILABLE = 3 PROXY_ENTRY_NOT_ACTIVE = 4 PROXY_PARAMETER_NOT_AVAILABLE = 5 PROXY_NOT_NECESSARY = 6 PROXY_NO_AUTHORITY = 7 PROXY_EXIT_ERRONEOUS = 8
IMPORTING Parameters details for ICF_READ_PROXY_CONFIGURATION
AUTHORITY_CHECK -
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: Yes
MANDANT - R/3 System, Client Number from Logon
Data type: SYMANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: Yes
REQUEST - HTTP Framework (iHTTP) HTTP Request
Data type: IF_HTTP_REQUESTOptional: Yes
Call by Reference: Yes
PROTOCOL -
Data type: PRX_PROTDefault: 1
Optional: Yes
Call by Reference: Yes
HOSTNAME -
Data type: STRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ICF_READ_PROXY_CONFIGURATION
PROXY_CONFIGURAION - Plugin Proxy Configuration for HTTP/HTTPS Client (Host/Port)
Data type: PPROXY_COptional: No
Call by Reference: Yes
EXCEPTIONS details
AUTHORITY_NOT_AVAILABLE -
Data type:Optional: No
Call by Reference: Yes
PROXY_INVALID_PROTOCOL -
Data type:Optional: No
Call by Reference: Yes
PROXY_ENTRY_NOT_AVAILABLE -
Data type:Optional: No
Call by Reference: Yes
PROXY_ENTRY_NOT_ACTIVE -
Data type:Optional: No
Call by Reference: Yes
PROXY_PARAMETER_NOT_AVAILABLE -
Data type:Optional: No
Call by Reference: Yes
PROXY_NOT_NECESSARY -
Data type:Optional: No
Call by Reference: Yes
PROXY_NO_AUTHORITY -
Data type:Optional: No
Call by Reference: Yes
PROXY_EXIT_ERRONEOUS -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICF_READ_PROXY_CONFIGURATION 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_authority_check | TYPE C, " 'X' | |||
| lv_proxy_configuraion | TYPE PPROXY_C, " | |||
| lv_authority_not_available | TYPE PPROXY_C, " | |||
| lv_mandant | TYPE SYMANDT, " SY-MANDT | |||
| lv_proxy_invalid_protocol | TYPE SYMANDT, " | |||
| lv_request | TYPE IF_HTTP_REQUEST, " | |||
| lv_proxy_entry_not_available | TYPE IF_HTTP_REQUEST, " | |||
| lv_protocol | TYPE PRX_PROT, " 1 | |||
| lv_proxy_entry_not_active | TYPE PRX_PROT, " | |||
| lv_hostname | TYPE STRING, " | |||
| lv_proxy_parameter_not_available | TYPE STRING, " | |||
| lv_proxy_not_necessary | TYPE STRING, " | |||
| lv_proxy_no_authority | TYPE STRING, " | |||
| lv_proxy_exit_erroneous | TYPE STRING. " |
|   CALL FUNCTION 'ICF_READ_PROXY_CONFIGURATION' " |
| EXPORTING | ||
| AUTHORITY_CHECK | = lv_authority_check | |
| MANDANT | = lv_mandant | |
| REQUEST | = lv_request | |
| PROTOCOL | = lv_protocol | |
| HOSTNAME | = lv_hostname | |
| IMPORTING | ||
| PROXY_CONFIGURAION | = lv_proxy_configuraion | |
| EXCEPTIONS | ||
| AUTHORITY_NOT_AVAILABLE = 1 | ||
| PROXY_INVALID_PROTOCOL = 2 | ||
| PROXY_ENTRY_NOT_AVAILABLE = 3 | ||
| PROXY_ENTRY_NOT_ACTIVE = 4 | ||
| PROXY_PARAMETER_NOT_AVAILABLE = 5 | ||
| PROXY_NOT_NECESSARY = 6 | ||
| PROXY_NO_AUTHORITY = 7 | ||
| PROXY_EXIT_ERRONEOUS = 8 | ||
| . " ICF_READ_PROXY_CONFIGURATION | ||
ABAP code using 7.40 inline data declarations to call FM ICF_READ_PROXY_CONFIGURATION
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.| DATA(ld_authority_check) | = 'X'. | |||
| DATA(ld_mandant) | = SY-MANDT. | |||
| DATA(ld_protocol) | = 1. | |||
Search for further information about these or an SAP related objects