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 · Catalogs and pricing

EDI 490 Rate Group Definition

The X12 document used to define and name a group of elements, such as patrons, geography, commodities or conditions, for a tariff.

Sent by
Railroad or rate publisher
Received by
Rate users such as shippers and railroads
Standard
ANSI ASC X12

What is an EDI 490?

The EDI 490 Rate Group Definition is the ANSI X12 transaction set used to define and name a group of elements pertinent to a tariff, such as patrons, geography, commodities and shipment conditions.

Rather than repeating long lists of stations or commodities in every rate, publishers define groups once, such as all stations in a region, and refer to them by name. Rate users must load the group definitions to interpret rates correctly. Groups make tariffs shorter and easier to maintain.

How the EDI 490 worksDiagram of the EDI 490 Rate Group Definition. Railroad or rate publisher sends it to rate users such as shippers and railroads. It usually starts the exchange. It is usually followed by 460 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: REN (Rate Request Information), DK (Docket Header) and GH (Group Header). 1 optional loops are listed by their first segment.How the EDI 490 worksRate Group Definition: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 490SENDERRailroad or ratepublisherRECEIVERRate users such asshippers and railroads997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY460Railroad Price DistributionRequest or Response997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TPGS … GETransaction set 490ST … SEHEADINGRENRate Request InformationDKDocket HeaderGHGroup Header+ 1 optional loop, starting with:PTBlue 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 490. Your trading partner's implementation guide adds its own requirements.
How the EDI 490 worksDiagram of the EDI 490 Rate Group Definition. Railroad or rate publisher sends it to rate users such as shippers and railroads. It usually starts the exchange. It is usually followed by 460 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: REN (Rate Request Information), DK (Docket Header) and GH (Group Header). 1 optional loops are listed by their first segment.How the EDI 490 worksRate Group Definition: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 490SENDERRailroad or ratepublisherRECEIVERRate users suchas shippers andrailroads997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY460Railroad Price Distribution Request orResponse997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code TP (GS … GE)Transaction set 490 (ST … SE)HEADINGRENRate Request InformationDKDocket HeaderGHGroup Header+ 1 optional loop, starting with:PTBlue 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 490. Your trading partner'simplementation guide adds its own requirements.

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

  • Defining station or commodity groups for tariffs
  • Changing the members of a group
  • Distributing group definitions to rate users

Where it fits in the document flow

This document 490 Rate Group Definition
Usually followed by 460 Railroad Price Distribution Request or Response997 Functional Acknowledgment

Structure

Mandatory segments in the 490 (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
  • REN
  • DK
  • GH
  • PT
  • SE

Practical example

The 490 in practice

A railroad defines a group of 40 grain elevators that share the same rates to export terminals. It sends shippers a 490 naming the group and listing its stations. Later rate dockets refer to the group, and shippers' systems expand it to the individual stations.

Implementation

Implementation considerations for the 490

  • Load group definitions before rates that reference them.
  • Version group changes with effective dates.
  • Use industry station and commodity codes.
  • Check that every rated location falls in the intended group.

How ECOM helps

Automate the 490 with ECOM

Industry

Trucking and Transportation

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

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

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 catalogs and pricing documents

All 21 catalogs and pricing documents

Need help with the EDI 490?

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

Request a Demo Contact us