972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Acknowledgments

EDI 242 Data Status Tracking

The X12 management document a service provider uses to report the transmission status of interchanges to the sender, the receiver or both.

Sent by
Network or service provider (service request handler)
Received by
Interchange sender, receiver or both
Standard
ANSI ASC X12

What is an EDI 242?

The EDI 242 Data Status Tracking is the ANSI X12 management transaction set by which a service request handler conveys transmission status information to the interchange sender, the interchange receiver or both. It can provide status on interchanges handled by the service.

Value-added networks and other service providers handle EDI traffic between partners. Status tracking tells the sender whether an interchange was delivered, is waiting in a mailbox or failed, so problems are found before the business notices a missing order or invoice.

How the EDI 242 worksDiagram of the EDI 242 Data Status Tracking. Network or service provider (service request handler) sends it to interchange sender, receiver or both. It usually starts the exchange. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment). 1 optional loops are listed by their first segment.How the EDI 242 worksData Status Tracking: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 242SENDERNetwork or serviceprovider (servicerequest handler)RECEIVERInterchange sender,receiver or both997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BYNo business reply expected2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code DSGS … GETransaction set 242ST … SEHEADINGBGNBeginning Segment+ 1 optional loop, starting with:HLBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 242. Your trading partner's implementation guide adds its own requirements.
How the EDI 242 worksDiagram of the EDI 242 Data Status Tracking. Network or service provider (service request handler) sends it to interchange sender, receiver or both. It usually starts the exchange. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment). 1 optional loops are listed by their first segment.How the EDI 242 worksData Status Tracking: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 242SENDERNetwork orservice provider(service requesthandler)RECEIVERInterchangesender, receiveror both997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BYNo business reply expected2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code DS (GS … GE)Transaction set 242 (ST … SE)HEADINGBGNBeginning Segment+ 1 optional loop, starting with:HLBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 242. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 242, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 242 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Reporting delivery status of interchanges
  • Reporting interchanges waiting for pickup
  • Reporting failed deliveries

Where it fits in the document flow

This document 242 Data Status Tracking

No other transaction set routinely comes directly before or after the 242; it is sent when the business event occurs. If the partners agree, the receiver confirms each functional group with a 997 Functional Acknowledgment or a 999 Implementation Acknowledgment.

Structure

Mandatory segments in the 242 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BGN
  • HL
  • STS
  • SE

Practical example

The 242 in practice

A supplier sends invoices to a customer through a network provider. The provider returns 242 status reports showing that most interchanges were delivered and one is still waiting in the customer's mailbox after a day. The supplier contacts the customer before the invoice becomes overdue.

Implementation

Implementation considerations for the 242

  • Monitor status reports for undelivered interchanges.
  • Match status to interchange control numbers.
  • Combine network status with partner acknowledgments.
  • Check whether the provider supports the 242.

How ECOM helps

Automate the 242 with ECOM

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Service

24×7 Support

Round-the-clock monitoring and incident support for EDI, B2B and MFT operations.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related acknowledgments documents

All 9 acknowledgments documents

Need help with the EDI 242?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us