Adapter for SAP 10.1 | webMethods Adapter for SAP Documentation | webMethods Adapter for SAP Installation and User’s Guide Documentation | Coding Client Applications and Services | Transaction Features for HTTP and SAP-XML | Example: HTTP POST of an IDoc
 
Example: HTTP POST of an IDoc
POST /invoke/pub.sap.transport.ALE/InboundProcess HTTP/1.0
X-tid: 9B38FA81133A38B518A10036
Content-type: application/x-sap.idoc
Content-Length: 4242
<?xml version="1.0" encoding="iso-8859-1"?>
<MATMAS02>
<IDOC BEGIN="1">
<EDI_DC SEGMENT="1">
<TABNAM>EDI_DC</TABNAM>
<MANDT>000</MANDT>
<DOCNUM>0000047112211178</DOCNUM>
<DOCREL/>
<STATUS/>
<DOCTYP>MATMAS02</DOCTYP>
<DIRECT>1</DIRECT>
...
For XRFC documents, you can also put the transaction ID in the header of the document:
<?xml version="1.0"?>
<sap:Envelope xmlns:sap="urn:sap-com:document:sap" version="1.0">
<sap:Header xmlns:rfcprop="urn:sap-com:document:sap:rfc:properties">
<rfcprop:Transaction>0A1104DC080C3C60F9E106A1</rfcprop:Transaction>
</sap:Header>
<sap:Body>
<rfc:SBC_TEST_SAVE xmlns:rfc="urn:sap-
com:document:sap:rfc:functions">
<INPUT>Have fun!</INPUT>
</rfc:SBC_TEST_SAVE>
</sap:Body>
</sap:Envelope>