Validation and Conversion TIBCO BusinessConnect EDI Protocol powered by Instream offers different validation and conversion features. Logging • Logging and publication of user-defined keys for each transaction in the audit trail database. • Logging of raw inbound and outbound EDI documents to a file system organized by trading partners and the sending/receiving dates. • Logging of raw inbound EDI segments to a file extends to the interchange level. • Logging of raw inbound EDI segments to a file extends to the transaction level, with optional inclusion of the envelope (ISA) segments into the output raw EDI transaction file. • Audit, non-repudiation, and messaging queue logs. Validation • Validation only mode for inbound EDI documents without XML conversion. Control Numbers • Control number management for inbound and outbound EDI documents. • User-defined control numbers for interchange, group, and transaction envelopes. Modifiers • Empty Group and Name modifiers. You can create multiple transaction bindings for one transaction type to target transactions to specific departments at a trading partner. • Transaction modifiers. You can create multiple transaction definitions with different guidelines and XSDs for one transaction type to target different requirements for different trading partners. Utilities • Utility to test your processes before engaging in e-commerce. Detection • Duplicate detection of transactions for inbound EDI documents based on digest of the raw EDI segment for each transaction and the corresponding envelope information. Other • Pre-processor to strip out unwanted characters from inbound EDI files. • Automatic X12 997, 999 or EDIFACT CONTRL acknowledgment time-out alerts for transmitted outbound X12 transactions or EDIFACT messages. • Re-submission of inbound EDI documents for message validation and XML conversion using the resend facility available in the Audit Log viewer. • Pre-configuration and embedding of standard guidelines for interchanges, groups and acknowledgment (997, TA1, 999 and CONTRL) when customization is not required. • EDI Conversion Engine, a run-time EDI-to-XML, TEXT-to-EDI, and XML-to-EDI Conversion Engine that is part of TIBCO BusinessConnect EDI Protocol powered by Instream. • Publication of raw EDI segments of the transaction body along with the converted XML. • Automatic generation of acknowledgments for inbound EDI documents. • Automatic reconciliation of inbound EDI acknowledgments with the original outbound EDI document. • Generation of acknowledgments for inbound EDI message on inbound validation errors only. • Encoding support for X12, EDIFACT, TRADACOMS, and TEXT protocols: − For outbound XML to EDI conversion, all encoding types are supported. You can specify an encoding type for outbound XML to EDI conversion. − For inbound EDI data, TIBCO BusinessConnect EDI Protocol powered by Instream identifies encoding automatically. If inbound EDI data does not contain the BOM header, you can specify an encoding type to convert EDI data to XML. • Access control through trading partner identification and permissions. • Conditional denial of inbound EDI transactions from inbound documents that are not signed or encrypted by trading partners. • UNOA, UNOB, and UNOC character sets. • Wrap data feature is supported for the TEXT protocol so that when it is checked, no extra LF/CRLF breaks are added at the end of each segment. When this option is unchecked, each segment will start in a new line. EDI Data Formats Different EDI data formats are supported. • X12 North American ANSI Standard • X12N Health Care • UN/EDIFACT United Nations EDI Trade • TRADACOMS data format Article Numbering Association UK • User-defined Delimited and Positional files • VICS EDI Retail Industry • HIPAA Health Insurance Portability and Accountability Act