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 · Transportation

EDI 873 Commodity Movement Services

The X12 document used to convey requests, and responses, for commodity movement services; it is not used for product sales or purchases.

Sent by
Shipper or marketer of a commodity
Received by
Transporter, such as a pipeline
Standard
ANSI ASC X12

What is an EDI 873?

The EDI 873 Commodity Movement Services is the ANSI X12 transaction set used to convey request and response information for commodity movement services. It is not used for product sales or purchases.

In the natural gas industry, for example, shippers nominate the quantities they want a pipeline to transport each day between receipt and delivery points. The request describes the service, points, quantities and dates, and the transporter validates it and returns the result with the 874. It is used in regulated industry processes.

How the EDI 873 worksDiagram of the EDI 873 Commodity Movement Services. Shipper or marketer of a commodity sends it to transporter, such as a pipeline. It usually starts the exchange. It is usually followed by 874 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required N1 loop with N1 (Party Identification) and detail: the required DTM loop with DTM (Date/Time Reference). 2 optional loops are listed by their first segment.How the EDI 873 worksCommodity Movement Services: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 873SENDERShipper or marketer ofa commodityRECEIVERTransporter, such as apipeline997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY874Commodity MovementServices Response997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code CUGS … GETransaction set 873ST … SEHEADINGBGNBeginning SegmentRequired loop N1 · repeats many timesN1Party IdentificationDETAILRequired loop DTM · repeats many timesDTMDate/Time Reference+ 2 optional loops, starting with:CSSLNBlue 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 873. Your trading partner's implementation guide adds its own requirements.
How the EDI 873 worksDiagram of the EDI 873 Commodity Movement Services. Shipper or marketer of a commodity sends it to transporter, such as a pipeline. It usually starts the exchange. It is usually followed by 874 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required N1 loop with N1 (Party Identification) and detail: the required DTM loop with DTM (Date/Time Reference). 2 optional loops are listed by their first segment.How the EDI 873 worksCommodity Movement Services: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 873SENDERShipper ormarketer of acommodityRECEIVERTransporter,such as apipeline997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY874Commodity Movement ServicesResponse997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code CU (GS … GE)Transaction set 873 (ST … SE)HEADINGBGNBeginning SegmentRequired loop N1 · repeats manytimesN1Party IdentificationDETAILRequired loop DTM · repeatsmany timesDTMDate/Time Reference+ 2 optional loops, starting with:CSSLNBlue 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 873. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 873, 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 873 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

  • Nominating quantities for transportation service
  • Requesting changes to scheduled movements
  • Requesting commodity movement services by point

Where it fits in the document flow

This document 873 Commodity Movement Services
Usually followed by 874 Commodity Movement Services Response997 Functional Acknowledgment

Structure

Mandatory segments in the 873 (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
  • N1
  • DTM
  • CS
  • SLN
  • SE

Practical example

The 873 in practice

A gas marketer needs to move gas from a production area to a city distribution system tomorrow. It sends the pipeline an 873 nominating the daily quantity at the receipt and delivery points under its transportation contract. The pipeline validates the nomination and confirms the scheduled quantity with an 874.

Implementation

Implementation considerations for the 873

  • Follow the industry's nomination standards and timelines.
  • Reference contracts and points with their official codes.
  • Process validation responses before deadlines.
  • Keep movement services separate from sales transactions.

How ECOM helps

Automate the 873 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

Solution

EDI Integration

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

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

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 873?

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

Request a Demo Contact us