B2B Integration 10.4 | Administering and Monitoring B2B Transactions | webMethods Module for EDI | Preparing to Process Inbound Non-TRADACOMS Documents Using Trading Networks | Coding Services to Process Transaction and Group Documents | Information in the Pipeline that Your Service Can Access
 
Information in the Pipeline that Your Service Can Access
When an Interchange, Group, or Transaction 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 variables are contained in the BizDocEnvelope:
Variable
Description
DocumentID
The EDI control number from the interchange, group, or transaction 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 document and generates this summary. 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 can also 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 Interchange document including the groups and transactions sets that it contains.
Key
Description
docID
String Internal ID that Trading Networks generated for the Interchange document.
docTypeID
String Internal ID of the TN document type used for the Interchange document.
docTypeName
String Name of the TN document type used for the Interchange document, for example, X12 Envelope.
group Documents
Document List (optional) Summary of all the Group documents in the interchange.
Key
Description
docID
String Internal ID that Trading Networks generated for the Group document.
docTypeID
String Internal ID of the TN document type.
docType Name
String Name of the TN document type used, for example, X12 Group.
transaction Documents
Document List (optional) Summary of all the Transaction documents in the group.
Key
Description
docID
String Internal ID that Trading Networks generated for the Transaction document.
docTypeID
String Internal ID of the TN document type used.
docType Name
String Name of the TN document type used, for example, X12 4010 850.
Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release