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 127 Vehicle Baying Order

The X12 document used to request or report the assignment of a motor vehicle to a specific bay in a storage or shipping facility.

Sent by
Vehicle manufacturer, carrier or facility operator
Received by
Facility operator, carrier or manufacturer
Standard
ANSI ASC X12

What is an EDI 127?

The EDI 127 Vehicle Baying Order is the ANSI X12 transaction set used to request or report the assignment of a motor vehicle to a specific predetermined bay, or parking space, in a storage or shipping facility, and to report conditions of the facility.

At large vehicle ramps and ports, thousands of vehicles wait for loading. Assigning each to a known bay, often grouped by destination, lets drivers find vehicles quickly when loads are built, and lets all parties know where each vehicle is.

How the EDI 127 worksDiagram of the EDI 127 Vehicle Baying Order. Vehicle manufacturer, carrier or facility operator sends it to facility operator, carrier or manufacturer. It usually follows 120. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BVB (Beginning Segment for Vehicle Baying Order) and G62 (Date/Time). 0 optional loops are listed by their first segment.How the EDI 127 worksVehicle Baying Order: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS120Vehicle Shipping OrderEDI 127SENDERVehicle manufacturer,carrier or facilityoperatorRECEIVERFacility operator,carrier or manufacturer997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code VBGS … GETransaction set 127ST … SEHEADINGBVBBeginning Segment for Vehicle Baying OrderG62Date/TimeBlue 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 127. Your trading partner's implementation guide adds its own requirements.
How the EDI 127 worksDiagram of the EDI 127 Vehicle Baying Order. Vehicle manufacturer, carrier or facility operator sends it to facility operator, carrier or manufacturer. It usually follows 120. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BVB (Beginning Segment for Vehicle Baying Order) and G62 (Date/Time). 0 optional loops are listed by their first segment.How the EDI 127 worksVehicle Baying Order: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS120Vehicle Shipping OrderEDI 127SENDERVehiclemanufacturer,carrier orfacility operatorRECEIVERFacilityoperator, carrieror manufacturer997 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 VB (GS … GE)Transaction set 127 (ST … SE)HEADINGBVBBeginning Segment forVehicle Baying OrderG62Date/TimeBlue 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 127. Your trading partner'simplementation guide adds its own requirements.

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

  • Assigning vehicles to bays by destination
  • Reporting where vehicles have been parked
  • Reporting facility conditions such as capacity

Where it fits in the document flow

Usually follows 120 Vehicle Shipping Order
This document 127 Vehicle Baying Order
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 127 (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
  • BVB
  • G62
  • SE

Practical example

The 127 in practice

A port processing facility receives 2,000 vehicles for export. It assigns each to a bay grouped by vessel and destination and sends the manufacturer 127 transactions reporting each vehicle's bay. When the vessel arrives, the stevedores load vehicles bay by bay.

Implementation

Implementation considerations for the 127

  • Use bay identifiers that match the physical layout.
  • Update bay assignments when vehicles move.
  • Group bays in ways that speed up loading.
  • Report facility capacity constraints early.

How ECOM helps

Automate the 127 with ECOM

Industry

Automotive

Schedules, ship notices, labels, self-billing and multi-plant routing for automotive suppliers.

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.

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 127?

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

Request a Demo Contact us