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 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.
When it is used
- Confirming accepted movement requests
- Reporting reduced or rejected quantities
- Explaining validation errors
Where it fits in the document flow
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.
How ECOM helps
Automate the 874 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
- 873Commodity Movement Services
- 104Air Shipment Information
- 106Motor Carrier Rate Proposal
- 107Request for Motor Carrier Rate Proposal
- 108Response to a Motor Carrier Rate Proposal
- 109Vessel Content Details
- 120Vehicle Shipping Order
- 121Vehicle Service
- 125Multilevel Railcar Load Details
- 127Vehicle Baying Order
- 160Transportation Automatic Equipment Identification
- 161Train Sheet
Need help with the EDI 874?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.