EDI Translation Detail Report

The EDI Translation Detail report enables you to access EDI data (transaction, group, or interchange) for a specified time period.

The EDI Translation Detail report further allows you to organize the report by selecting criteria such as direction of the transmission, sender and receiver identifier, envelope name, unique identifier for the envelope level, EDI standard used, and translation success or failure, among other parameters. This report allows you to quickly and easily access information about EDI translation in the Sterling B2B Integrator system.

EDI translation detail reports reflect the number of EDI groups and transactions that were actually processed by the system. If an interchange is non-compliant, its groups are not processed and therefore you cannot view a group count. If a group is non-compliant, its transactions are not processed and therefore you cannot view a transaction count for that group. For example, if you have an interchange that has two groups—each group containing one transaction set—and one of the groups is non-compliant, the EDI translation detail report indicates that the group count for the interchange is 2, and the transaction count is 1.

The EDI Translation Detail Report includes a parameter for document size (Doc Size). To improve performance, Sterling B2B Integrator avoids persisting intermediate documents to the database wherever possible. For example, when transactions are batched, a document is only persisted for the batch rather than for each individual transaction. Similarly, if transactions are being translated, only the translated version of the document is persisted to the database. This behavior greatly improves throughput.

Therefore, depending on the level of the report (interchange, group, or transaction) and the direction of the translation (inbound or outbound), the Doc Size parameter is defined differently:
  • When you filter by interchange, the Doc Size parameter contains the actual size of the EDI interchange, regardless of direction (inbound or outbound).
  • When you filter by outbound groups, the Doc Size parameter contains the actual size of the EDI interchange.
  • When you filter by inbound groups, the Doc Size parameter contains the actual size of the EDI group, including the group level envelope segments.
  • When you filter by inbound transactions, the Doc Size parameter contains the post-translation size. If the transaction sets are “batched,” there is one report entry to summarize and total post-translation size is reported. If the transaction sets are not batched, each transaction has its own report entry, and individual post-translation sizes are reported.
  • When you filter by outbound transactions, the Doc Size parameter contains the actual size of the entire EDI Interchange. Outbound transactions are always presented as “batched,” with one report entry to summarize multiple transaction sets.
  • If the EDI data is formatted as non-streamed, the doc size includes record separators.