Step 2: Define Attributes to be Extracted from Documents
You must specify the attribute values to extract from the document's TN_parms parameter. You can extract both system attributes and custom attributes (the document data). In addition, you can use built-in or custom transformations to transform extracted attribute values before Trading Networks stores them in the BizDocEnvelope.
For VDA documents, the extraction query specified in the document type should be able to extract any field value in the header of the message. You must specify the sender and receiver attributes that you want Trading Networks to extract from the documents.
For TRADACOMS documents, you cannot extract attributes for TRADACOMS headers, messages, and trailers separately.
Trading Networks does not separate these sections in the attribute extraction dialog box. You can extract attributes only from the message section of a TRADACOMS document. For more information about the attributes that
Module for EDI stores for TRADACOMS document types, see
Attributes Stored for TRADACOMS Document
Types.
For more information about document attributes, see
Trading Networks Attributes and EDI Documents and the
webMethods Trading Networks Administrator’s Guide for your release.
To define the attributes that you want
Trading Networks to extract from the document
2. On the EDI Document Type Details page, click the Extract tab. The document tree view displays the contents of the installed TN EDI document type.
3. For each attribute that you want Trading Networks to extract from documents identified by this TN EDI document type:
a. Expand the document tree view, and select a node that represents the attribute that you want Trading Networks to extract.
b. Do one of the following to display the Add Extracted Attribute dialog box:
Click
next to the
Query field, and then select
Add Attribute.
In the EDI document tree view panel, click
in the
Action column, and then select
Add Attribute.
c. In the Add Extracted Attribute dialog box, specify the following:
Field | Description |
Query | The XQL query that instructs Trading Networks how to extract the attribute for the particular TN EDI document type. Trading Networks fills the Query field with the XQL query for the node that you selected. |
Name | The name of the attribute (for example, SenderID, ReceiverID, or ConversationID). Select a name from the list. Trading Networks fills in the Type and Description fields based on the document attribute definition. |
Required | Whether you want Trading Networks to log an error message in the activity log when it cannot extract the attribute. |
Transformation | How Trading Networks handles attribute data before storing it in the Trading Networks database. The data type of the attribute (shown in the Type field) determines the built-in or custom transformation options available. For VDA documents, you must also select the type of the external IDs (for example, DUNS) from the Built-in list for both SenderID and ReceiverID attributes so that Trading Networks can match the external IDs in SenderID and ReceiverID with the external IDs in the profiles. This is how Trading Networks verifies the identities of the sender and receiver. |
d. Click OK.
For information about using an XQL query of a node in a document tree to extract a document attribute, see
Extracting a Document Attribute Using an
XQL Query.