Representation of SAP Transactions

When using tRFC or IDocs, you have to specify a unique SAP transaction ID for each call to ensure delivery. This transaction ID can be either resolved from an SAP system as described in this guide or built locally. It should always consist of 24 hexadecimal characters and be globally unique.

Because BizTalk does not support transaction IDs (TIDs), Adapter for SAP uses the <referenceID> element, which is a sub element of the <state> element.

Note:
The <state> element can also be a sub-element of the <to> or <from> element.

Transaction IDs must be put in the <referenceID> element that belongs to the receiver's address information.

For example:

<?xml version="1.0" encoding="iso-8859-1"?>
<biztalk_1 xmlns="urn:schemas-biztalk-org:BizTalk/biztalk-1.0.xml">
<header>
<delivery>
<message>
<messageID>0A125F1315B3A11B00000035</messageID>
<sent>2000-06-07T09:22:40</sent>
</message>
<to>
<address>urn:sap-com:logical-system:SAPCLNT001</address>
<state>
<referenceID>120A135FB315A11B00003500<referenceID>
</state>
</to>
<from>
<address>urn:sap-com:logical-system:SAPADA0001</address>
</from>
</delivery>
</header>

</biztalk_1>