SAP HTTP_READ_PROFILE Function Module for









HTTP_READ_PROFILE is a standard http read profile 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 http read profile FM, simply by entering the name HTTP_READ_PROFILE into the relevant SAP transaction such as SE37 or SE38.

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



Function HTTP_READ_PROFILE 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_READ_PROFILE'"
EXPORTING
PATH = "
* CLIENT_USER_DEPENDENT = ' ' "

IMPORTING
ENTRY_EXISTS = "
ATRA_VARIANT = "Runtime Analysis: Name of Variant for Restricting Measuremt
ATRA_MESS = "RT analysis: For setting measurement clock
ATRA_USER = "SAP System, User Logon Name
ATRA_SINGLEREC = "
.



IMPORTING Parameters details for HTTP_READ_PROFILE

PATH -

Data type: STRING
Optional: No
Call by Reference: Yes

CLIENT_USER_DEPENDENT -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for HTTP_READ_PROFILE

ENTRY_EXISTS -

Data type: C
Optional: No
Call by Reference: Yes

ATRA_VARIANT - Runtime Analysis: Name of Variant for Restricting Measuremt

Data type: SE30VAR
Optional: No
Call by Reference: Yes

ATRA_MESS - RT analysis: For setting measurement clock

Data type: RS38TCLOCK
Optional: No
Call by Reference: Yes

ATRA_USER - SAP System, User Logon Name

Data type: SYUNAME
Optional: No
Call by Reference: Yes

ATRA_SINGLEREC -

Data type: ATRA_SINGLEREC
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HTTP_READ_PROFILE 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_path  TYPE STRING, "   
lv_entry_exists  TYPE C, "   
lv_atra_variant  TYPE SE30VAR, "   
lv_client_user_dependent  TYPE C, "   ' '
lv_atra_mess  TYPE RS38TCLOCK, "   
lv_atra_user  TYPE SYUNAME, "   
lv_atra_singlerec  TYPE ATRA_SINGLEREC. "   

  CALL FUNCTION 'HTTP_READ_PROFILE'  "
    EXPORTING
         PATH = lv_path
         CLIENT_USER_DEPENDENT = lv_client_user_dependent
    IMPORTING
         ENTRY_EXISTS = lv_entry_exists
         ATRA_VARIANT = lv_atra_variant
         ATRA_MESS = lv_atra_mess
         ATRA_USER = lv_atra_user
         ATRA_SINGLEREC = lv_atra_singlerec
. " HTTP_READ_PROFILE




ABAP code using 7.40 inline data declarations to call FM HTTP_READ_PROFILE

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_client_user_dependent) = ' '.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!