SAP HTTP_VERSION Function Module for Procure SAPHTTP version

Search SAP Function Modules

HTTP_VERSION is a standard http version SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Procure SAPHTTP version 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 http version FM, simply by entering the name HTTP_VERSION into the relevant SAP transaction such as SE37 or SE38.

Function Group: SFTP
Program Name: SAPLSFTP
Main Program: SAPLSFTP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HTTP_VERSION 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 'HTTP_VERSION'"Procure SAPHTTP version
  EXPORTING
   RFC_DESTINATION =  "
*  DELETE_TRACE =  "

 IMPORTING
   EXEPATH =  "
   VERSION =  "
   P4VERSION =  "
   WORKING_DIR =  "
   RFCPATH =  "
   RFCVERSION =  "

TABLES
   HTTP_TRACE =  "

EXCEPTIONS
   SYSTEM_FAILURE = 1    COMMUNICATION_FAILURE = 2    CONNECT_FAILED = 3 

.

IMPORTING Parameters details for HTTP_VERSION

RFC_DESTINATION -

Data type: RFCDES-RFCDEST
Optional: No
Call by Reference: No ( called with pass by value option)

DELETE_TRACE -

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for HTTP_VERSION

EXEPATH -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

VERSION -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

P4VERSION -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

WORKING_DIR -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

RFCPATH -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

RFCVERSION -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for HTTP_VERSION

HTTP_TRACE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

SYSTEM_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

COMMUNICATION_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

CONNECT_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HTTP_VERSION 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.

ABAP code using 7.40 inline data declarations to call FM HTTP_VERSION

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