In the following example, you see the SOAP-compliant body of an HTTP post request for transferring data for the XML DataSource 6ATEST with the generated function module /BIC/QI6ATEST_RFC.
Correct structure of a SOAP message for transferring data to BW:
Components of the SOAP message |
Explanations |
<?xml version="1.0" ?> |
Marks the header |
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> |
Marks the beginning of the SOAP turnover |
<SOAP:Body> |
Marks the beginning of the body of data |
<rfc:_-BIO_-QI6ATEST_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions"> |
Calls the RFC-capable function module /BIO/QI<Techn. Name of XML DataSource>
The / character must be replaced in the XML document by the character string _- so that it can be properly reclassified. Therefore, there is the function module name in the XML document -BIO_-QI6ATEST_RFC |
<DATASOURCE>6ATEST</DATASOURCE> |
Contains the technical name for the XML DataSource |
<DATA> </DATA> |
Contains the data in an XML wrapper The data package is opened with <DATA> and ended with </DATA> .
The file only contains a data package in which different rows are included. The rows are opened with <item> and closed with </item>
The field names must correspond to the XML DataSource technical names. |
</rfc:_-BIO_-QI6ATEST_RFC> |
Ends the RFC-capable function module /BIO/QI<Techn. Name of XML DataSource>. |
</SOAP:Body> |
Marks the end of the body of data |
</SOAP:Envelope> |
Marks the end of the SOAP envelope |