SX_PERFORM_HTTPSEND 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 SX_PERFORM_HTTPSEND into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
SX01
Released Date:
Not Released
Processing type: Remote-Enabled
CALL FUNCTION 'SX_PERFORM_HTTPSEND' "
EXPORTING
receive_info = " sxrecinfi1 Data for Send Process
document_data = " sxdocchgi1 Data for Sent Document
system_data = " sxsysdati1 Data for Sender System
TABLES
receivers = " sxextreci1 Recipient list
packing_list = " sxpcklsti1 Packet List
object_header = " solisti1 SAP Internal Header Data
contents_bin = " sxlisti1 Body Parts Data Binary
contents_txt = " solisti1 Body Parts Data Textual
object_para = " soparai1 SAP Internal Selection Parameter List
object_parb = " soparbi1 SAP Internal Parameter List Further Processing
EXCEPTIONS
ERR_NODE_UNKNOWN = 1 " If Node Specified but Unknown
ERR_INVALID_VERSION = 2 " Format of Version Number Is Invalid
ERR_REC_NOT_SPECIFIED = 3 " RECEIVER Table Not Filled
ERR_INCOMPATIBLE_VERSION = 4 " Different Version Numbers (First Two Digits)
ERR_PAC_NOT_SPECIFIED = 5 " PACKING_LIST Not Filled
ERR_INTERNAL = 6 " An Internal, Temporary Error
ERR_AUTHORITY = 7 " Authorization Check Failed (S_RFC Authorization Object)
. " SX_PERFORM_HTTPSEND
The ABAP code below is a full code listing to execute function module SX_PERFORM_HTTPSEND 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).
| it_receivers | TYPE STANDARD TABLE OF SXEXTRECI1,"TABLES PARAM |
| wa_receivers | LIKE LINE OF it_receivers , |
| it_packing_list | TYPE STANDARD TABLE OF SXPCKLSTI1,"TABLES PARAM |
| wa_packing_list | LIKE LINE OF it_packing_list , |
| it_object_header | TYPE STANDARD TABLE OF SOLISTI1,"TABLES PARAM |
| wa_object_header | LIKE LINE OF it_object_header , |
| it_contents_bin | TYPE STANDARD TABLE OF SXLISTI1,"TABLES PARAM |
| wa_contents_bin | LIKE LINE OF it_contents_bin , |
| it_contents_txt | TYPE STANDARD TABLE OF SOLISTI1,"TABLES PARAM |
| wa_contents_txt | LIKE LINE OF it_contents_txt , |
| it_object_para | TYPE STANDARD TABLE OF SOPARAI1,"TABLES PARAM |
| wa_object_para | LIKE LINE OF it_object_para , |
| it_object_parb | TYPE STANDARD TABLE OF SOPARBI1,"TABLES PARAM |
| wa_object_parb | LIKE LINE OF it_object_parb . |
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_receive_info | TYPE SXRECINFI1 , |
| it_receivers | TYPE STANDARD TABLE OF SXEXTRECI1 , |
| wa_receivers | LIKE LINE OF it_receivers, |
| ld_document_data | TYPE SXDOCCHGI1 , |
| it_packing_list | TYPE STANDARD TABLE OF SXPCKLSTI1 , |
| wa_packing_list | LIKE LINE OF it_packing_list, |
| ld_system_data | TYPE SXSYSDATI1 , |
| it_object_header | TYPE STANDARD TABLE OF SOLISTI1 , |
| wa_object_header | LIKE LINE OF it_object_header, |
| it_contents_bin | TYPE STANDARD TABLE OF SXLISTI1 , |
| wa_contents_bin | LIKE LINE OF it_contents_bin, |
| it_contents_txt | TYPE STANDARD TABLE OF SOLISTI1 , |
| wa_contents_txt | LIKE LINE OF it_contents_txt, |
| it_object_para | TYPE STANDARD TABLE OF SOPARAI1 , |
| wa_object_para | LIKE LINE OF it_object_para, |
| it_object_parb | TYPE STANDARD TABLE OF SOPARBI1 , |
| wa_object_parb | LIKE LINE OF it_object_parb. |
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name SX_PERFORM_HTTPSEND or its description.
SX_PERFORM_HTTPSEND - SX_OUTGOING_VERSION_BUILD - SAPconnect: Conversion - Setting up Document Version to be Sent SX_OBJECT_STATUS_SEND - SAPconnect: Transfer Status to External System SX_OBJECT_STATUS_RECEIVE - SAPconnect: RFC for Receiving Status Information SX_OBJECT_RECEIVE - SAPconnect: RFC for Receiving Objects SX_OBJECT_CONVERT___T_TXT -