Viewing or Modifying Trading Networks Assets for an MX Message

Field	Description
Name	The name of the document type, for example, camt.029.001.01.
Description	Indicates that the document is in an XML format that corresponds to the Data PDU XML, for example, camt.029.001.01.
Root Tag	The root tag that serves to identify the message as a Data PDU XML document when it is submitted to Trading Networks. The default value is DataPDU.
Identifying Query	Uniquely identifies the MX message, indicating the location of the MX message element in the Data PDU XML document. You can specify which value Trading Networks evaluates to determine if it matches the TN XML document type. For example, if the Identifying Query is :DataPDU/:Header/:Message/:MessageIdentifier, and you define the value as camt.029.001.01, Trading Networks does the following for any camt.029.001.01 document submitted to it: Runs the above query against the XML structure of the document and extracts the value at the specified location. Identifies the document as a camt.029.001.01 message. Continues with the next action defined for this message type. To view or edit Identifying Queries, follow the instructions described in webMethods Trading Networks Administrator’s Guide.

Field	Description
Name	The name of the attribute. You can extract the following attributes for an MX message: SenderID ReceiverID SenderReference Format ReconciliationInfo
Query	Instructs Trading Networks how to extract the attribute for the Data PDU XML document type. For example: SenderID:/:DataPDU[0]/:Header[0]/:/:Sender[0]/:/:X1[0] ReceiverID:/:DataPDU[0]/:Header[0]/:/:Receiver[0]/:/:X1[0] SenderReference:/:DataPDU[0]/:Header[0]/:/:SenderReference[0] Format:/:DataPDU[0]/:Header[0]/:/:Format[0] ReconciliationInfo:/:DataPDU[0]/:Header[0]/:/*:ReconciliationInfo[0]
Built-in Transformation	Specifies the external ID type associated with the information in the document for the sender or receiver. For MX messages, the external ID type for the sender and the receiver is BIC.

Field	Description
Name	The name of the processing rule, for example, camt.029.001.01.
Sender	The sender. The default value is Any.
Receiver	The receiver. The default value is Any.
Document Type	The default value is Selected, and a TN document type is specified for the document. For example, if the TN document type is camt.029.001.01, the processing rule is triggered only for the routed camt.029.001.01 message.
User Status	For Trading Networks to determine which processing rule to invoke, the processing rule must define this additional User Status value for outgoing documents. The default value is AwaitingDelivery. This value is very important to the processing rule. All MT/MX messages are submitted to Trading Networks before they are sent to SAA from SWIFT Module. Trading Networks uses the information in the TPA to determine whether to send a document to SAA, and invokes the corresponding processing rule accordingly. The processing rule must have this additional User Status value. Messages received from SAA are processed similarly.
Recognition Errors	Indicates whether to specify if the document has errors. The default value is May have errors.

5. To view the MX TPA, follow the procedure described in Viewing Details for Trading Partner Agreements. The details are the same as in the MT TPA message, except for the Agreement ID, which shows the type of message that the TPA represents (MX message). For example, the Agreement ID for an MX message may have the value camt.029.001.01.