SAP CLB2_RFC_SEND Function Module for Send HTTP-Request

Search SAP Function Modules

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

Function Group: CLB2_RFC
Program Name: SAPLCLB2_RFC
Main Program: SAPLCLB2_RFC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CLB2_RFC_SEND 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 'CLB2_RFC_SEND'"Send HTTP-Request
  EXPORTING
   IS_SEND_DATA =  "Collaboration Platform: Connection Data
   IS_APPLI_CONFIG =  "Collaboration Platform: Key Elements

 IMPORTING
   EV_ID =  "

EXCEPTIONS
   ARGUMENT_NOT_FOUND = 1    HTTP_COMMUNICATION_FAILURE = 2    HTTP_INVALID_TIMEOUT = 3    BADI_NOT_IMPLEMENTED = 4    EXTERNAL_CALL_NOT_SUPPORTED = 5 

.

IMPORTING Parameters details for CLB2_RFC_SEND

IS_SEND_DATA - Collaboration Platform: Connection Data

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

IS_APPLI_CONFIG - Collaboration Platform: Key Elements

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

EXPORTING Parameters details for CLB2_RFC_SEND

EV_ID -

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

EXCEPTIONS details

ARGUMENT_NOT_FOUND - Communication Parameters (Host or Service) Not Available

Data type:
Optional: No
Call by Reference: Yes

HTTP_COMMUNICATION_FAILURE - Communication Error

Data type:
Optional: No
Call by Reference: Yes

HTTP_INVALID_TIMEOUT - Invalid Time Entry

Data type:
Optional: No
Call by Reference: Yes

BADI_NOT_IMPLEMENTED - OAuth2 BAdi is not implemented

Data type:
Optional: No
Call by Reference: Yes

EXTERNAL_CALL_NOT_SUPPORTED - External call of this module is not supported

Data type:
Optional: No
Call by Reference: Yes

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

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