X12 transaction guide · Transportation

EDI 874 Commodity Movement Services Response

The X12 document used to return validation information in response to a commodity movement services request (873).

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

What is an EDI 874?

The EDI 874 Commodity Movement Services Response is the ANSI X12 transaction set used to return validation information in response to the Commodity Movement Services transaction set (873).

The response tells the shipper whether its request was accepted as submitted, accepted with changes, or rejected, and why. In gas transportation, for example, the scheduled quantity can be lower than nominated because of capacity constraints, and shippers must adjust their supply and delivery plans accordingly. Responses can cover several nominations. Shippers then adjust their plans.

How the EDI 874 worksDiagram of the EDI 874 Commodity Movement Services Response. Transporter, such as a pipeline sends it to shipper or marketer. It usually follows 873. It is usually followed by 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). 1 optional loops are listed by their first segment.How the EDI 874 worksCommodity Movement Services Response: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS873Commodity MovementServicesEDI 874SENDERTransporter, such as apipelineRECEIVERShipper or marketer997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code CQGS … GETransaction set 874ST … SEHEADINGBGNBeginning SegmentRequired loop N1 · repeats many timesN1Party IdentificationDETAIL+ 1 optional loop, starting with:N9Blue 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 874. Your trading partner's implementation guide adds its own requirements.
How the EDI 874 worksDiagram of the EDI 874 Commodity Movement Services Response. Transporter, such as a pipeline sends it to shipper or marketer. It usually follows 873. It is usually followed by 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). 1 optional loops are listed by their first segment.How the EDI 874 worksCommodity Movement Services Response: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWS873Commodity Movement ServicesEDI 874SENDERTransporter,such as apipelineRECEIVERShipper ormarketer997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code CQ (GS … GE)Transaction set 874 (ST … SE)HEADINGBGNBeginning SegmentRequired loop N1 · repeats manytimesN1Party IdentificationDETAIL+ 1 optional loop, starting with:N9Blue 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 874. Your trading partner'simplementation guide adds its own requirements.

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

  • Confirming accepted movement requests
  • Reporting reduced or rejected quantities
  • Explaining validation errors

Where it fits in the document flow

This document 874 Commodity Movement Services Response
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 874 (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
  • N9
  • SLN
  • SE

Practical example

The 874 in practice

A pipeline receives nominations for the next gas day. Because of a compressor outage, it can schedule only part of a marketer's nominated quantity. It sends an 874 with the scheduled quantity and the reason, and the marketer arranges alternative transport for the balance.

Implementation

Implementation considerations for the 874

  • Process responses quickly, since schedules are time-critical.
  • Compare scheduled with nominated quantities.
  • Map validation codes to corrective actions.
  • Follow industry timelines for confirmations.

Need help with the EDI 874?

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