SenderID and ReceiverID System Attributes
When Trading Networks has a value for SenderID or ReceiverID, you can perform these tasks:
![*](bullet.gif)
Use the sender or receiver to determine whether a document is a duplicate (Check for Duplicate Document pre-processing action).
![*](bullet.gif)
Use the sender or receiver as criteria for determining the processing rule to use for the document.
![*](bullet.gif)
Deliver a document.
![*](bullet.gif)
Search for the document in
My webMethods based on sender or receiver.
![*](bullet.gif)
Have a business process perform steps based on sender or receiver.
If you extract the SenderID or ReceiverID system attributes from a document, you must specify how the sender or receiver is identified in the document. For example, if you want to extract ReceiverID from the XML document and the ReceiverID is identified in the document by a D-U-N-S number, define the XQL query to identify the location of the receiver information and select the external ID type DUNS. For example:
XQL Query for ReceiverID = /PurchaseOrder[0]/OrderHeader[0]/DUNS[0]
<PurchaseOrder>
<OrderHeader>
<CorpName>XYZ Steel Company</CorpName>
<DUNS>123456789</DUNS>
</OrderHeader>
.
.
.
</PurchaseOrder>
The XQL query points to the <DUNS> tag. Trading Networks stores the value 123456789 for the ReceiverID attribute and associates it with the external ID type DUNS.
Be sure to select an external ID type that your partners specify in their profiles. You can choose from a list of external ID types. If the external ID type you need is not in the list or if you have agreed on a non-standard format with a trading partner, select the external ID type Mutually Defined and add an appropriate ID value.