SAP Function Modules

comments icon Comments

RFC_READ_HTTP_DESTINATION SAP Function module







RFC_READ_HTTP_DESTINATION is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name RFC_READ_HTTP_DESTINATION into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CRFC
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM RFC_READ_HTTP_DESTINATION - RFC READ HTTP DESTINATION 





CALL FUNCTION 'RFC_READ_HTTP_DESTINATION' "
  EXPORTING
    destination =               " rfcdes-rfcdest
*   authority_check = 'X'       " rfcdisplay-rfctrace
*   bypass_buf =                " char1
  IMPORTING
    rfctype =                   " rfcdisplay-rfctype  Type of entry in RFCDES
    servicenr =                 " rfcdisplay-rfcsysid  System ID
    server =                    " rfcdisplay-rfchost
    trace =                     " rfcdisplay-rfctrace
    language =                  " rfcdisplay-rfclang
    client =                    " rfcdisplay-rfcclient
    user =                      " rfcdisplay-rfcalias  User Name
    password =                  " rfcdisplay-rfcexec  Program name (complete path)
    description =               " rfcdoc-rfcdoc1
    proxy_host =                " rfcdisplay-rfcgwhost
    proxy_service =             " rfcdisplay-rfcgwserv
    proxy_user =                " rfcdisplay-proxyuser  Display structure for RFCDES maintenance
    proxy_password =            " string
    sslapplic =                 " rfcdisplay-sslapplic  SSL Identity
    path_prefix =               " string        Program name (complete path)
    destlock =                  " rfcdisplay-rfclock
    authority =                 " destauth      Destination Authorization
    slogin =                    " rfcdisplay-rfcslogin  Trusted system (RFC single logon)
    sameusr =                   " rfcdisplay-rfcsameusr  Current User
    ssl =                       " rfcdisplay-rfcsnc
    http_timeout =              " i
    http_version =              " rfcdisplay-rfctype  HTTP Version
    http_compress =             " rfcdisplay-rfctype
    compressreply =             " rfcdisplay-rfctype
    cookie_accept =             " rfcdisplay-rfctype
    sso_ticket =                " rfcdisplay-rfctsysopt
    category =                  " rfcdisplay-rfccategory
    assertion_ticket =          " assertion_ticket
    assertion_ticket_sysid =    " assertion_ticket_sysid
    assertion_ticket_client =   " assertion_ticket_client
  EXCEPTIONS
    AUTHORITY_NOT_AVAILABLE = 1  "              You do not have this authorization.
    DESTINATION_NOT_EXIST = 2   "
    INFORMATION_FAILURE = 3     "
    INTERNAL_FAILURE = 4        "               Internal Error
    NO_HTTP_DESTINATION = 5     "
    .  "  RFC_READ_HTTP_DESTINATION

ABAP code example for Function Module RFC_READ_HTTP_DESTINATION





The ABAP code below is a full code listing to execute function module RFC_READ_HTTP_DESTINATION including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_rfctype    TYPE RFCDISPLAY-RFCTYPE
,
ld_servicenr    TYPE RFCDISPLAY-RFCSYSID
,
ld_server    TYPE RFCDISPLAY-RFCHOST
,
ld_trace    TYPE RFCDISPLAY-RFCTRACE
,
ld_language    TYPE RFCDISPLAY-RFCLANG
,
ld_client    TYPE RFCDISPLAY-RFCCLIENT
,
ld_user    TYPE RFCDISPLAY-RFCALIAS
,
ld_password    TYPE RFCDISPLAY-RFCEXEC
,
ld_description    TYPE RFCDOC-RFCDOC1
,
ld_proxy_host    TYPE RFCDISPLAY-RFCGWHOST
,
ld_proxy_service    TYPE RFCDISPLAY-RFCGWSERV
,
ld_proxy_user    TYPE RFCDISPLAY-PROXYUSER
,
ld_proxy_password    TYPE STRING
,
ld_sslapplic    TYPE RFCDISPLAY-SSLAPPLIC
,
ld_path_prefix    TYPE STRING
,
ld_destlock    TYPE RFCDISPLAY-RFCLOCK
,
ld_authority    TYPE DESTAUTH
,
ld_slogin    TYPE RFCDISPLAY-RFCSLOGIN
,
ld_sameusr    TYPE RFCDISPLAY-RFCSAMEUSR
,
ld_ssl    TYPE RFCDISPLAY-RFCSNC
,
ld_http_timeout    TYPE I
,
ld_http_version    TYPE RFCDISPLAY-RFCTYPE
,
ld_http_compress    TYPE RFCDISPLAY-RFCTYPE
,
ld_compressreply    TYPE RFCDISPLAY-RFCTYPE
,
ld_cookie_accept    TYPE RFCDISPLAY-RFCTYPE
,
ld_sso_ticket    TYPE RFCDISPLAY-RFCTSYSOPT
,
ld_category    TYPE RFCDISPLAY-RFCCATEGORY
,
ld_assertion_ticket    TYPE ASSERTION_TICKET
,
ld_assertion_ticket_sysid    TYPE ASSERTION_TICKET_SYSID
,
ld_assertion_ticket_client    TYPE ASSERTION_TICKET_CLIENT
.



 

SELECT single RFCDEST 
  FROM RFCDES 
  INTO @DATA(ld_destination).



DATA(ld_authority_check) = some text here

DATA(ld_bypass_buf) = 'Check type of data required'.
.

CALL FUNCTION 'RFC_READ_HTTP_DESTINATION'
  EXPORTING
    destination =                ld_destination
*   authority_check =            ld_authority_check
*   bypass_buf =                 ld_bypass_buf
  IMPORTING
    rfctype =                    ld_rfctype
    servicenr =                  ld_servicenr
    server =                     ld_server
    trace =                      ld_trace
    language =                   ld_language
    client =                     ld_client
    user =                       ld_user
    password =                   ld_password
    description =                ld_description
    proxy_host =                 ld_proxy_host
    proxy_service =              ld_proxy_service
    proxy_user =                 ld_proxy_user
    proxy_password =             ld_proxy_password
    sslapplic =                  ld_sslapplic
    path_prefix =                ld_path_prefix
    destlock =                   ld_destlock
    authority =                  ld_authority
    slogin =                     ld_slogin
    sameusr =                    ld_sameusr
    ssl =                        ld_ssl
    http_timeout =               ld_http_timeout
    http_version =               ld_http_version
    http_compress =              ld_http_compress
    compressreply =              ld_compressreply
    cookie_accept =              ld_cookie_accept
    sso_ticket =                 ld_sso_ticket
    category =                   ld_category
    assertion_ticket =           ld_assertion_ticket
    assertion_ticket_sysid =     ld_assertion_ticket_sysid
    assertion_ticket_client =    ld_assertion_ticket_client
  EXCEPTIONS
    AUTHORITY_NOT_AVAILABLE =    1
    DESTINATION_NOT_EXIST =      2
    INFORMATION_FAILURE =        3
    INTERNAL_FAILURE =           4
    NO_HTTP_DESTINATION =        5
    .  "  RFC_READ_HTTP_DESTINATION

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_rfctype  TYPE RFCDISPLAY-RFCTYPE ,
ld_destination  TYPE RFCDES-RFCDEST ,
ld_servicenr  TYPE RFCDISPLAY-RFCSYSID ,
ld_authority_check  TYPE RFCDISPLAY-RFCTRACE ,
ld_server  TYPE RFCDISPLAY-RFCHOST ,
ld_bypass_buf  TYPE CHAR1 ,
ld_trace  TYPE RFCDISPLAY-RFCTRACE ,
ld_language  TYPE RFCDISPLAY-RFCLANG ,
ld_client  TYPE RFCDISPLAY-RFCCLIENT ,
ld_user  TYPE RFCDISPLAY-RFCALIAS ,
ld_password  TYPE RFCDISPLAY-RFCEXEC ,
ld_description  TYPE RFCDOC-RFCDOC1 ,
ld_proxy_host  TYPE RFCDISPLAY-RFCGWHOST ,
ld_proxy_service  TYPE RFCDISPLAY-RFCGWSERV ,
ld_proxy_user  TYPE RFCDISPLAY-PROXYUSER ,
ld_proxy_password  TYPE STRING ,
ld_sslapplic  TYPE RFCDISPLAY-SSLAPPLIC ,
ld_path_prefix  TYPE STRING ,
ld_destlock  TYPE RFCDISPLAY-RFCLOCK ,
ld_authority  TYPE DESTAUTH ,
ld_slogin  TYPE RFCDISPLAY-RFCSLOGIN ,
ld_sameusr  TYPE RFCDISPLAY-RFCSAMEUSR ,
ld_ssl  TYPE RFCDISPLAY-RFCSNC ,
ld_http_timeout  TYPE I ,
ld_http_version  TYPE RFCDISPLAY-RFCTYPE ,
ld_http_compress  TYPE RFCDISPLAY-RFCTYPE ,
ld_compressreply  TYPE RFCDISPLAY-RFCTYPE ,
ld_cookie_accept  TYPE RFCDISPLAY-RFCTYPE ,
ld_sso_ticket  TYPE RFCDISPLAY-RFCTSYSOPT ,
ld_category  TYPE RFCDISPLAY-RFCCATEGORY ,
ld_assertion_ticket  TYPE ASSERTION_TICKET ,
ld_assertion_ticket_sysid  TYPE ASSERTION_TICKET_SYSID ,
ld_assertion_ticket_client  TYPE ASSERTION_TICKET_CLIENT .





SELECT single RFCDEST 
  FROM RFCDES 
  INTO ld_destination.


ld_authority_check = some text here
ld_bypass_buf = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name RFC_READ_HTTP_DESTINATION or its description.


   
 

RFC_READ_HTTP_DESTINATION - 
RFC_READ_DYNPRO - 
RFC_READ_DEVELOPMENT_OBJECT - 
RFC_READ_DESTINATION_TYPE - 
RFC_READ_ALLOC_TABLE - 
RFC_RAISE_ERROR_VB -