Trading Networks 10.3 | Administering and Monitoring B2B Transactions | webMethods Module for EDI | Processing Inbound TRADACOMS Documents Using Trading Networks | Coding Services to Process File and Batch Documents When Using TRADACOMS | Information in the Pipeline that Your Service Can Access When Using TRADACOMS
 
Information in the Pipeline that Your Service Can Access When Using TRADACOMS
When a transmission, batch, or file document is passed to the processing rule, the following information is accessible to your service from the pipeline:
*BizDocEnvelope in the bizdoc variable. Use the BizDocEnvelope to retrieve information that Trading Networks maintains about the document. The BizDocEnvelope adheres to the wm.tn.rec:BizDocEnvelope IS document type. It is also an instance of com.wm.app.tn.doc.BizDocEnvelope. For more information about the BizDocEnvelope, see the webMethods Trading Networks Built-In Services Reference for your release.
The following table lists some of the variables within the BizDocEnvelope.
Variable
Description
DocumentID
The EDI transmission control number/file generation number from the transmission, batch, or file header as described in DocumentID.
Attributes
The custom attributes that were set for the document. For information about the custom attributes that Module for EDI sets, see Custom Attributes that Module for EDI Sets When Using TRADACOMS.
Errors
The errors that Trading Networks and Module for EDI encountered while processing the document.
* EDI document summary information in the envelopeDocuments variable. When Trading Networks originally receives the EDI document, it passes it to the EDI recognizer, which parses the EDI document. This EDI document summary is the result of the parse. It is the entire original EDI document as an IData object.
You can use the EDI document summary information to derive a total document count or to determine when all of the documents in the original EDI document have completed processing. To do so, your service can perform a simple count of the original documents and a count of the documents processed. When these counts match, processing of the entire original EDI document is complete. You also can perform a query within Trading Networks that checks the status of each document using the Trading Networks internal ID for each document.
The following table shows the structure of the EDI document summary information in the envelopeDocuments variable.
Variable
Description
envelopeDocuments
Document List Summary of the transmission document including the batch and file that it contains.
Key
Description
docID
A String that contains the Internal ID that Trading Networks generated for the Transmission document.
docTypeID
A String that contains the internal ID of the TN document type used for the Transmission document.
docTypeName
A String that contains the name of the TN document type used for the Transmission document, for example, TRADACOMS Transmission.
groupDocuments
(optional) A Document List that contains a summary of all the batch documents in the transmission.
Key
Description
docID
A String that contains the Internal ID that Trading Networks generated for the Batch document.
docTypeID
A String that contains the Internal ID of the TN document type used for the Batch document.
docTypeName
A String that contains the name of the TN document type used for the Batch document, for example, Tradacoms Batch.
transactionDocuments
(optional) A Document List that contains a summary of all the file documents in the batch.
Key
Description
docID
A String that contains the Internal ID that Trading Networks generated for the File document.
docTypeID
A String that contains the Internal ID of the TN document type used for the File document.
docTypeName
A String that contains the name of the TN document type used for the File document, for example, Tradacoms File.