SWIFT Module 7.1 SP10.July 2020 | Configuring SWIFT Module for Message Exchange over SAA | Using SAA to Exchange XML v2 Wrapped MT and MX Messages | Exchanging MT Messages in XMLv2 Format | Step 2: Create Trading Networks Assets | Viewing Trading Networks Assets for an MT Message | Viewing Details for TN Document Types
Viewing Details for TN Document Types
TN document types are created when the createDocType parameter in the wm.xmlv2.dev:createSWIFTItems service is set to true. You can view the following parameters for TN document types for MT messages:
*Identification Information. The information that Trading Networks uses to determine whether a document matches a defined TN XML document type.
*Extraction Information. The attributes that you want Trading Networks to extract from the XML document. The SenderID and ReceiverID attributes should be selected from the Data PDU XML document for use in processing rules, transaction analysis, and process management.
*To view details for TN document types for MT messages
1. Follow the instructions for viewing TN document types as described in webMethods Trading Networks Administrator’s Guide.
2. From the Document Types list, click the MT message document type that you want to view (for example, fin.535).
3. In the Document Type Details screen, on the Identify tab, the following identification information is available for the MT message TN document type:
The name of the document type, for example, fin.535.
Indicates that the XML format of the document corresponds to the Data PDU XML format (for example, DataPDU for doc type = fin.535).
Root Tag
The root tag that identifies 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 MT message, indicating the location of the MT 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 fin.535, Trading Networks does the following for any fin.535 document submitted:
*Runs the above query against the XML structure of the document and extracts the value at the specified location.
*Identifies the document as a fin.535 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.
4. To extract information about the SenderID and ReceiverID attributes, do the following:
a. Follow the instructions for extracting information about attributes as described in webMethods Trading Networks Administrator’s Guide.
b. From the Attributes to Extract list, select SenderID or ReceiverID to edit.
c. On the Edit Attribute screen, you can edit or view the following details:
The name of the attribute, for example, SenderID or ReceiverID.
Indicates to Trading Networks how to extract the attribute for the Data PDU XML document type, for example:
*SenderID Query: /*:DataPDU[0]/*:Header[0]/*:*/*:Sender[0]/*:*/*:X1[0]
*ReceiverID Query: /*:DataPDU[0]/*:Header[0]/*:*/*:Receiver[0]/*:*/*:X1[0]
Built-in Transformation
Specifies the external ID type associated with the information in the document for the sender or receiver. For MT messages, the external ID type for the sender and the receiver is BIC.