HTTP_VERSION SAP Function module - Procure SAPHTTP version

HTTP_VERSION 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 HTTP_VERSION into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SFTP
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM HTTP_VERSION - HTTP VERSION

CALL FUNCTION 'HTTP_VERSION' "Procure SAPHTTP version
  EXPORTING
    rfc_destination =           " rfcdes-rfcdest
*   delete_trace =              " c
  IMPORTING
    exepath =                   " c
    version =                   " c
    p4version =                 " c
    working_dir =               " c
    rfcpath =                   " c
    rfcversion =                " c
  TABLES
    http_trace =                "
  EXCEPTIONS
    SYSTEM_FAILURE = 1          "
    COMMUNICATION_FAILURE = 2   "
    CONNECT_FAILED = 3          "
    .  "  HTTP_VERSION

ABAP code example for Function Module HTTP_VERSION

The ABAP code below is a full code listing to execute function module HTTP_VERSION 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_exepath  
 
 TYPE C
,
ld_version  
 
 TYPE C
,
ld_p4version  
 
 TYPE C
,
ld_working_dir  
 
 TYPE C
,
ld_rfcpath  
 
 TYPE C
,
ld_rfcversion  
 
 TYPE C
,
it_http_trace  
 
 TYPE STANDARD TABLE OF STRING,"TABLES PARAM
wa_http_trace
 
 LIKE LINE OF it_http_trace
.

 

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


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

"populate fields of struture and append to itab
append wa_http_trace to it_http_trace.
.

CALL FUNCTION 'HTTP_VERSION'
  EXPORTING
    rfc_destination =            ld_rfc_destination
*   delete_trace =               ld_delete_trace
  IMPORTING
    exepath =                    ld_exepath
    version =                    ld_version
    p4version =                  ld_p4version
    working_dir =                ld_working_dir
    rfcpath =                    ld_rfcpath
    rfcversion =                 ld_rfcversion
  TABLES
    http_trace =                 it_http_trace
  EXCEPTIONS
    SYSTEM_FAILURE =             1
    COMMUNICATION_FAILURE =      2
    CONNECT_FAILED =             3
    .  "  HTTP_VERSION

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
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_exepath
 
 TYPE C ,
ld_rfc_destination
 
 TYPE RFCDES-RFCDEST ,
it_http_trace
 
 TYPE STANDARD TABLE OF STRING ,
wa_http_trace
 
 LIKE LINE OF it_http_trace,
ld_version
 
 TYPE C ,
ld_delete_trace
 
 TYPE C ,
ld_p4version
 
 TYPE C ,
ld_working_dir
 
 TYPE C ,
ld_rfcpath
 
 TYPE C ,
ld_rfcversion
 
 TYPE C .



SELECT single RFCDEST 
  FROM RFCDES 
  INTO ld_rfc_destination.
 

"populate fields of struture and append to itab
append wa_http_trace to it_http_trace.
ld_delete_trace = 'Check type of data required'.