EDI Transactions
EDI Transactions is a searchable log of every X12 interchange processed by Tediware β both inbound and outbound. Use it to look up specific transmissions, verify delivery, or troubleshoot processing issues.
What are EDI Transactions?
Each time Tediware processes an EDI interchange, a transaction record is created automatically. Records capture key details from the ISA, GS, and ST headers: the sender and receiver identifiers, control numbers, transaction set type (e.g., 810, 856, 204), and whether the document was inbound or outbound.
Transaction records are created for both directions:
- Inbound β EDI files received from a trading partner via SFTP, AS2, or sandbox
- Outbound β EDI files generated by Tediware and delivered to a trading partner
Searching Transactions
The search bar at the top of the page lets you filter transactions by:
- Sender ID β the interchange sender identifier from the ISA header
- Receiver ID β the interchange receiver identifier from the ISA header
- Direction β Inbound, Outbound, or All
Enter your filter values and click Search. Active filters appear as badges below the search bar. Click the X on a badge to remove that filter.
Results are paginated. Use the navigation controls at the bottom of the page to move between pages.
Transaction List
The transaction list displays the following columns:
- ID β a truncated identifier. Click it to open the transaction detail panel.
- Direction β Inbound or Outbound
- Transaction Set β the X12 transaction set identifier (e.g., 810, 204)
- Sender β the senderβs interchange ID, prefixed with its qualifier
- Receiver β the receiverβs interchange ID, prefixed with its qualifier
- ICN β the Interchange Control Number
- Created At β when the transaction was recorded
On smaller screens, some columns collapse into an expanded row below each entry.
Transaction Details
Click a transaction ID to open the detail panel. The panel shows:
- ID β the full transaction identifier
- Trace ID β the processing trace GUID, with a link to the trace view
- Created β timestamp
- Direction β Inbound or Outbound
- Interchange Control Number β from the ISA header
- Group Control Number β from the GS header
- Transaction Set Control Number β from the ST header
- Transaction Set Identifier β the document type code
- Sender β qualifier and identifier
- Receiver β qualifier and identifier
Artifacts
The Artifacts section shows the data that came in and what we sent out β the input payload from the trading partner (or the source flow) and the output payload that was actually delivered. Each card is format-aware: X12 envelopes render as raw text, JSON renders as pretty-printed JSON. Use the Trace Viewer link on a card to open the full trace at the producing node, where you can also see intermediate-stage payloads and node-by-node logs.
Associated Logs
Log entries generated during the processing of this transaction appear in the Associated Logs section. These are useful for diagnosing errors or understanding what happened during processing.
AS2 Delivery
If the transaction was sent or received via AS2, an AS2 Delivery section lists the underlying AS2 message(s). For each message you can see the direction, current status, filename and size, and (for inbound) the MDN disposition that Tediware sent back, or (for outbound) the MDN your partner returned.
When the signed MDN envelope is still on file, a Download MDN button is shown. The MDN is the cryptographic proof of delivery; download and archive it if your compliance process requires it. The download remains available for the AS2 messageβs full retention window (see Data Retention for details).
Tracing a Transaction
Every transaction is linked to a trace GUID that follows the document through the entire processing pipeline β from ingestion through transformation to delivery. Click View Trace in the transaction detail panel to see the full trace, including every node the document passed through and the result at each step.