BBP_OUTPUT_X_HTTP_GET SAP Function module

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

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

Pattern for FM BBP_OUTPUT_X_HTTP_GET - BBP OUTPUT X HTTP GET

CALL FUNCTION 'BBP_OUTPUT_X_HTTP_GET' "
* EXPORTING
*   is_http =                   " bbps_http
*   iv_url =                    " string
*   iv_method = 'GET'           " string
*   is_proxy =                  " bbps_http_proxy
  IMPORTING
    ev_mimetype =               " w3conttype
    ev_mimetypestring =         " string
    ev_size =                   " i
    ev_string =                 " string
    ev_xstring =                " xstring
    et_content =                " bbpt_att_cont
  EXCEPTIONS
    HTTP_ERROR = 1              "
    .  "  BBP_OUTPUT_X_HTTP_GET

ABAP code example for Function Module BBP_OUTPUT_X_HTTP_GET

The ABAP code below is a full code listing to execute function module BBP_OUTPUT_X_HTTP_GET 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_ev_mimetype  
 
 TYPE W3CONTTYPE
,
ld_ev_mimetypestring  
 
 TYPE STRING
,
ld_ev_size  
 
 TYPE I
,
ld_ev_string  
 
 TYPE STRING
,
ld_ev_xstring  
 
 TYPE XSTRING
,
ld_et_content  
 
 TYPE BBPT_ATT_CONT
.


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

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

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

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

CALL FUNCTION 'BBP_OUTPUT_X_HTTP_GET'
* EXPORTING
*   is_http =                    ld_is_http
*   iv_url =                     ld_iv_url
*   iv_method =                  ld_iv_method
*   is_proxy =                   ld_is_proxy
  IMPORTING
    ev_mimetype =                ld_ev_mimetype
    ev_mimetypestring =          ld_ev_mimetypestring
    ev_size =                    ld_ev_size
    ev_string =                  ld_ev_string
    ev_xstring =                 ld_ev_xstring
    et_content =                 ld_et_content
  EXCEPTIONS
    HTTP_ERROR =                 1
    .  "  BBP_OUTPUT_X_HTTP_GET

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_ev_mimetype
 
 TYPE W3CONTTYPE ,
ld_is_http
 
 TYPE BBPS_HTTP ,
ld_ev_mimetypestring
 
 TYPE STRING ,
ld_iv_url
 
 TYPE STRING ,
ld_ev_size
 
 TYPE I ,
ld_iv_method
 
 TYPE STRING ,
ld_ev_string
 
 TYPE STRING ,
ld_is_proxy
 
 TYPE BBPS_HTTP_PROXY ,
ld_ev_xstring
 
 TYPE XSTRING ,
ld_et_content
 
 TYPE BBPT_ATT_CONT .


ld_is_http = 'Check type of data required'.
ld_iv_url = 'Check type of data required'.
ld_iv_method = 'Check type of data required'.
ld_is_proxy = 'Check type of data required'.