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 · Master data

EDI 603 Transportation Equipment Registration

The X12 document equipment owners or controllers use to register transportation equipment, such as containers and chassis, with service providers.

Sent by
Equipment owner or controller
Received by
Transportation service provider or registry
Standard
ANSI ASC X12

What is an EDI 603?

The EDI 603 Transportation Equipment Registration is the ANSI X12 transaction set transportation equipment owners or controllers use with transportation service providers and other interested parties to register equipment and maintain its details. Registered details include the equipment identification, type, dimensions and characteristics.

Terminals, railroads and other providers rely on accurate equipment data to plan handling, check compatibility and bill correctly. Registration keeps that data in step with the owner's fleet as equipment is added, modified or retired. It is often used by leasing companies and railroads.

How the EDI 603 worksDiagram of the EDI 603 Transportation Equipment Registration. Equipment owner or controller sends it to transportation service provider or registry. It usually starts the exchange. 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 N21 loop with N21 (Equipment Registration Details). 1 optional loops are listed by their first segment.How the EDI 603 worksTransportation Equipment Registration: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 603SENDEREquipment owner orcontrollerRECEIVERTransportation serviceprovider or registry997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code EOGS … GETransaction set 603ST … SEHEADINGBGNBeginning SegmentRequired loop N21 · repeats up to 9,999N21Equipment Registration Details+ 1 optional loop, starting with:N1Blue 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 603. Your trading partner's implementation guide adds its own requirements.
How the EDI 603 worksDiagram of the EDI 603 Transportation Equipment Registration. Equipment owner or controller sends it to transportation service provider or registry. It usually starts the exchange. 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 N21 loop with N21 (Equipment Registration Details). 1 optional loops are listed by their first segment.How the EDI 603 worksTransportation Equipment Registration: whosends it, where it fits and what the standardmarks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 603SENDEREquipmentowner orcontrollerRECEIVERTransportationservice provideror registry997 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 EO (GS … GE)Transaction set 603 (ST … SE)HEADINGBGNBeginning SegmentRequired loop N21 · repeats up to9,999N21Equipment RegistrationDetails+ 1 optional loop, starting with:N1Blue 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 603. Your trading partner'simplementation guide adds its own requirements.

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

  • Registering new containers, trailers or chassis
  • Updating equipment characteristics
  • Retiring equipment from service

Where it fits in the document flow

This document 603 Transportation Equipment Registration
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 603 (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
  • N21
  • SE

Practical example

The 603 in practice

A leasing company adds 500 new refrigerated containers to its fleet. It sends the registry and the railroads it works with a 603 for each container, with the identification, size and type code, tare weight and refrigeration characteristics. When the containers enter service, the railroads already have the data needed to plan and bill moves.

Implementation

Implementation considerations for the 603

  • Register equipment before it enters service.
  • Use standard equipment identification and type codes.
  • Send updates when equipment is modified or retired.
  • Reconcile registry data with operational records periodically.

How ECOM helps

Automate the 603 with ECOM

Industry

Trucking and Transportation

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

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

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 master data documents

All 25 master data documents

Need help with the EDI 603?

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

Request a Demo Contact us