X12 214 Transportation Carrier Shipment Status Message
This Draft Standard for Trial Use contains the format and establishes the data contents of the Transportation Carrier Shipment Status Message Transaction Set (214) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a transportation carrier to provide shippers, consignees, and their agents with the status of shipments in terms of dates, times, locations, route, identifying numbers, and conveyance.
- ~ Segment
- * Element
- > Component
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code identifying the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code indicating whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- QM
- Transportation Carrier Shipment Status Message (214)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission; codes agreed to by trading partners
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 214
- Transportation Carrier Shipment Status Message
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Transportation Carrier Shipment Status Message
To transmit identifying numbers and other basic data relating to the transaction set
Example Data: B1123456789654321*SCAC~
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- B1001 is the carrier assigned reference number.
- B1001 is the carrier's PRO (invoice number) that identifies the shipment.
This element should contain the Carrier's PRO/Load/Tracking ID.
Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)
If Best Buy is paying the Freight, this element should contain the Best Buy TMS Load/Carrier Move ID (also known as CID (Unique Consignee ID) or SID (Unique Shipper ID) from VICS).
For these types of loads the value in the B204 Element in the 204 Load Tender document should be mapped here. Otherwise the Bill of Lading ID should be mapped here.
Standard Carrier Alpha Code
- B1003 is required when used in Transaction Set 214.
This should contain the NMFTA registered SCAC code of the carrier who is ultimately responsible for the load and will be billing the customer for the shipment.
For Loads that were tendered to the carrier directly from Best Buy, this element should have the SCAC code that was transmitted in the B202 element of the 204 Load Tender document.
Detail
The LX/1000 Loop should contain shipment status information about the shipment identified in the B1002. It can be repeated from one to all statuses in a single 214.
One LX/1000 Loop N1/1200 Loop containing name and address information for the location of the status event in the AT7/1100 Loop.
Assigned Number
To reference a line number in a transaction set
Example Data: LX*1~
Number assigned for differentiation within a transaction set
This is the sequential number assigned for differentiation of each iteration of the LX/1000 Loop. It should start with 1 and be incremented by 1 for each iteration.
Business Instructions and Reference Number
To specify instructions in this business relationship or a reference number
An L11 segment is required on all 214 shipment status messages where Best Buy is paying for the freight charges. For shipments where Best Buy has transmitted a 204 Load Tender there should be two iterations of the L11 segment.
The first iteration should contain the Best Buy TMS load ID (also known as CID (Unique Consignee ID) or SID (Unique Shipper ID) from VICS)) and the L1102 must contain the "BN" qualifier.found in the B204 element from the
Load Tender which should be mapped to the L1102 and the L1102 should have a "BN" qualifier.
The second iteration should contain the Stop Sequence Number, of the Stop in the Load Tender that this EDI 214 Shipment status event is being sent in for. The L1102 should contain the Stop Sequence value and the L1102 should contain the Qualifier "QN".
If Best Buy is not paying the freight charges then this segment should either not be present or only the Best Buy schedule ID should be transmitted in the L1101 element with a "72" qualifier in the L1102 element if known.
Example Data:
Here is an L11 segment with Best Buy TMS Load ID
L11654321BN~
Here is an L11 segment with Best Buy Stop Sequence
L111QN~
Here is an L11 segment with Best Buy Schedule ID
L1199999972~
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
For shipments where Best Buy has transmitted a 204 Load Tender, there should be two iterations of the L11 segment.
The first iteration should contain the Best Buy TMS load ID, found in the B204 element from the Load Tender, which should be mapped to this element.
The second iteration should contain the Stop Sequence Number, from the S501 element within the stop detail of the Load tender for the stop in the Load Tender that this EDI 214 Shipment status event, is being sent in for.
Code qualifying the Reference Identification
If the L1101 value is the Best Buy Load ID then the t L1102 should use the qualifier "BN".
If the L1101 values is the Best Buy Stop Sequence Number than the L1102 should use the qualifier "QN" .
- 72
- Schedule Reference Number
This qualifier should be used to identify that the information in the L1101 element is the Best Buy Schedule ID.
- BN
- Booking Number
This qualifier should be used to identify that the information in the L1101 element is the Best Buy TMS Load/CarrierMove ID (also known as CID (Unique Cosignee ID) or SID (Unique Shipper ID) from VICS).
- QN
- Stop Sequence Number
This qualifier should be used to identify that the information in the L1101 element is the Best Buy Stop Sequence Number.
Lading Exception Code
To specify the status of the shipment in terms of lading exception information
The Q7 segment should only be sent if a lading exception has occurred with the shipment while in the carriers possession, then it should be sent on the next available Shipment Status update.
Example Data: Q7DCTN*1~
Code indicating the condition of the shipment
Code for packaging form of the lading quantity
Number of units (pieces) of the lading commodity
This element should contain the quantity or number of Logistical Shipping units impacted by the Lading exception. This number must be positive number, negative quantities will not be accepted.
Bill of Lading Handling Requirements
To identify Bill of Lading handling and service requirements
This segment should be used to transmit any special handling instructions or services requirements outlined within the Bill of lading or special instruction about the load to Best Buy. If this segment is sent then at least one or both the AT501 or AT502 must be present.
Example Data: AT5HVS1~
Each AT7/1100 Loop should contain status information for one of the events at one of the stopoff/freight points for the carrier shipment identified in the B1002 and/or L1101 element.
Shipment Status Details
To specify the status of a shipment, the reason for that status, the date and time of the status and the date and time of any appointments scheduled.
The AT7 segment must be sent in all 214 Shipment Status messages. In the AT7 segment either a combination of AT701 and AT702 or AT703 and AT704 must be present in the segment but not both pairs.
If the Shipment status is related to a Delivery location, then the AT706 must contain the Local time of the Delivery location and the AT707 must be "LT".
If the Shipment status is related to a Shipping location, then the AT706 must contain the Local time of the Shipping location and the AT707 must be "LT".
If the Shipment status is regards to arrival at a carrier's terminal or railhead, then the AT706 must contain the time at the location of the event and the AT707 should contain the qualifier for the Local Time of that event, "LT".
Example Data:
AT7X2NS*201006221000*LT~
AT7*AANA201006151500LT~
AT7X4NS**201006200900*LT~
Code indicating the status of a shipment
- If AT701 is present, AT705 is the date the status occurred. If AT703 is present, AT705 is a date related to an appointment.
- If AT701 is present, AT706 is the time of the status. If AT703 is present, AT706 is the time of the appointment.
Code indicating the reason a shipment status or appointment reason was transmitted
This code is required if AT701 is sent. If no specific Status Reason Code is needed, send "NS".
Code indicating the status of an appointment to pick-up or deliver a shipment
Code indicating the reason a shipment status or appointment reason was transmitted
This code is required if AT703 is sent. If no specific Status Reason Code is needed, send "NA".
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
The date that the event, indicated in the AT701 & AT702 or AT703 & AT704, occurred should be sent here.
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
The time that the event, indicated in the AT701 & AT702 or AT703 & AT704, occurred should be sent here.
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
- If AT707 is not present then AT706 represents local time of the status.
The time zone code that the event, indicated in the AT701 & AT702 or AT703 & AT704, occurred should be sent here.
Equipment, Shipment, or Real Property Location
To specify the location of a piece of equipment, a shipment, or real property in terms of city and state or longitude and latitude or postal code
Example Data: MS1MinneapolisMN*USA*****55423~
Free-form text for city name
This must be the name of the actual City that the piece of equipment or shipment is in at the time the shipment status message is being sent.
Code (Standard State/Province) as defined by appropriate government agency
This must be the name of the actual State or Province code that the piece of equipment or shipment is in at the time the shipment status message is being sent.
Code identifying the country
This must be the code name of the actual Country that the piece of equipment or shipment is in at the time the shipment status message is being sent.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
This should be the Postal Code of the actual location that the piece of equipment or shipment is in at the time the shipment status message is being sent.
Equipment or Container Owner and Type
To specify the owner, the identification number assigned by that owner, and the type of equipment
The MS2 segment is required for Truckload and Intermodal carriers only. If the MS202 Equipment ID is not known at the time of the transmission of the status event/Appointment, then the default of "NA" should be transmitted instead. The actual Trailer ID must be transmitted in a shipment status message prior to the physical arrival of the
load at Best Buy's facility.
Best Buy only expects to receive one MS2 segment per 1100 loop.
Example Data: MS2SCAC9876544321*TL~
Standard Carrier Alpha Code
This field must contain the NMFTA registered SCAC of the carrier who is physically moving the shipment and owns the trailer or container.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
This field must contain the actual ID of the trailer or container that contains the shipment that is being moved.
Code identifying type of equipment used for shipment
- MS203 identifies the type for the equipment specified in MS202.
This field should contain the qualifier that best describes the physical trailer or container length and type attributes.
Seal Numbers
To record seal numbers used and the organization that applied the seals
The M7 segment is primarily for Truckload and Intermodal carriers. Any known seal number given to the carrier by the shipper should be listed here and the parties identified who applied the seal. If the seal is broken by another party such as Customs (DOT), the new seal ID should be sent on an update with "CM" qualifier (if it was Customs) sent in the M705.
Example Data: M7Seal1***CM~
Code identifying an organizational entity, a physical location, property or an individual
- M705 indicates the name of the organization which applied the seal(s).
- CM
- Customs
There must be one and only one occurrence of this N1/1200 Loop within the LX/1000 Loop. It should contain the name and address of the facility at the stopoff/freight point location where the status event(s) described in the AT7 segment in the AT7/1100 Loop occurred.
Multiple occurrences of the N1/1200 Loop in one LX/1000 Loop will be ignored.
Name
To identify a party by type of organization, name, and code
The N1 segment should contain the location information pertaining to the actual location that the Shipment Status message relates to.
Example Data:
Example of Pick up Location
N1SHVendor Warehouse94UniqueLoadID~
Example of Deliver Location
N1STBest Buy RDC #709470~
Code identifying an organizational entity, a physical location, property or an individual
For a pickup location you will need to send the qualifier of "SH" or "SF". For a delivery location you will need to to send the qualifier of "ST" or "CN".
- CN
- Consignee
- SF
- Ship From
- SH
- Shipper
- ST
- Ship To
Free-form name
If the N101 is "SH" or "SF" and the shipment is moving between Best Buy locations, then the N102 is mandatory and should start with "Best Buy". Otherwise the N102 should contain the shipping location name.
Code designating the system/method of code structure used for Identification Code (67)
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
If the shipping charges are being paid for by Best Buy and a 204 Load Tender was received by the carrier for the shipment indicated within the 214 Shipment Status message, the N104 element should be filled with the ID from the N104 Element of the corresponding EDI 204 Load Tender for the appropriate location type indicated in the N101.
Address Information
To specify the location of the named party
This segment should hold the street address of the location that the Shipment Status message relates to.
Example Data: N3*12345 Best Buy Way~
Geographic Location
To specify the geographic place of the named party
Example Data: N4MinneapolisMN55423USA~
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
This must be the name of the actual City that the location indicated in the N1 segment is located within/by.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
This must be the code of the State or Province that the location indicated in the N1 segment is located within/by.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
This must be the Postal Code for the location that is indicated in the N1 segment is located within.
Code identifying the country
This must be the Country Code for the location that is indicated in the N1 segment is located within.
The values in this OID/1300 Loop describe each individual order/shipment in the carrier shipment identified in the B1002 and/or L1101 elements.
Each occurrence of this Loop should include one individual order/shipment that has been or will be loaded or unloaded at the stopoff/freight point where the event described in the AT7 segment of Loop 1100 occurred.
Order Identification Detail
To specify order identification detail
Example Data: OIDBestBuyPOCTN245L*18000~
Identifying number for Purchase Order assigned by the orderer/purchaser
This element should contain the Best Buy Purchase Order or similar reference number (Transfer ID, RTV (Return to Vendor Authorization number) #, etc) that has been assigned to all or some of the Logistical shipping/handling units on the shipment.
If a 204 Load Tender was received for this shipment from Best Buy, the OID02 element from the 204 Load tender should be mapped here.
Code for packaging form of the lading quantity
This should be the qualifier that defines the type of Logistical shipping/handling units that are being moved on the shipment under the Reference ID indicated in the OID02. In almost all cases the qualifier should be "CTN".
If a 204 Load Tender was received for this shipment from Best Buy the OID04 element from the 204 Load Tender should be mapped here.
Numeric value of quantity
This is the actual numerical quantity of the Logistical shipping/handling units being moved on the shipment under the Reference ID indicated in the OID02.
If Best Buy has provided a 204 Load Tender for this shipment then the OID05 from the 204 Load Tender should be mapped here.
Code specifying the weight unit
This should be the qualifier that defines the type of weight units used for the Logistical shipping/handling units that are being moved on the shipment under the Reference ID indicated in the OID02. In almost all cases the qualifier should be "L" for Pounds or "K" for kilograms.
If Best Buy has provided a 204 Load Tender for this shipment then the OID06 from the 204 Load Tender should be mapped here.
Numeric value of weight
This is the actual numerical weight of the Logistical shipping/handling units being moved on the shipment under the Reference ID indicated in the OID02.
If Best Buy has provided a 204 Load Tender for this shipment then the OID07 from the 204 Load Tender should be mapped here.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
All statuses
B10*987650*1234560*SCAC~
LX*1~
L11*1234560*BN~
L11*1*QN~
AT7*X3*NS***20100702*0900*LT~
MS1*BELLEVUE*WA*USA*****98004~
MS2*SCAC*13579~
N1*SF*VENDORS FACILITY*94*FACILITY1~
N3*225 PIONEER STREET~
N4*BELLEVUE*WA*98004*USA~
OID**ABCDEF**CTN*67*L*4357.3081~
OID**BCDEFG**CTN*138*L*5020.6649~
OID**CDEFGH**CTN*188*L*11423.610~
OID**DEFGHI**CTN*48*L*3214.119~
LX*2~
L11*1234560*BN~
L11*1*QN~
AT7*AF*NS***20100702*0935*LT~
MS1*BELLEVUE*WA*USA*****98004~
MS2*SCAC*13579~
N1*SF*VENDORS FACILITY*94*FACILITY1~
N3*225 PIONEER STREET~
N4*BELLEVUE*WA*98004*USA~
OID**ABCDEF**CTN*67*L*4357.3081~
OID**BCDEFG**CTN*138*L*5020.6649~
OID**CDEFGH**CTN*188*L*11423.610~
OID**DEFGHI**CTN*48*L*3214.119~
LX*3~
L11*1234560*BN~
L11*2*QN~
AT7*X1*NS***20100705*1135*LT~
MS1*BLOOMINGTON*MN*USA*****55438~
MS2*SCAC*13579~
N1*ST*BEST BUY BLOOMINGTON DDC*94*78~
N3*6150 WEST 110TH STREET~
N4*BLOOMINGTON*MN*55438*USA~
OID**ABCDEF**CTN*67*L*4357.3081~
OID**BCDEFG**CTN*138*L*5020.6649~
LX*4~
L11*1234560*BN~
L11*2*QN~
AT7*D1*NS***20100705*1215*LT~
MS1*BLOOMINGTON*MN*USA*****55423~
MS2*SCAC*13579~
N1*ST*BEST BUY BLOOMINGTON DDC*94*78~
N3*6150 WEST 110TH STREET~
N4*BLOOMINGTON*MN*55438*USA~
OID**ABCDEF**CTN*67*L*4357.3081~
OID**BCDEFG**CTN*138*L*5020.6649~
LX*5~
L11*1234560*BN~
L11*3*QN~
AT7*X1*NS***20100705*1245*LT~
MS1*BLOOMINGTON*MN*USA*****55438~
MS2*SCAC*13579~
N1*ST*BEST BUY BLOOMINGTON RDC*94*70~
N3*6203 (B) WEST 111TH STREET~
N4*BLOOMINGTON*MN*55438*USA~
OID**CDEFGH**CTN*188*L*11423.610~
OID**DEFGHI**CTN*48*L*3214.119~
LX*6~
L11*1234560*BN~
L11*3*QN~
AT7*D1*NS***20100705*1315*LT~
MS1*BLOOMINGTON*MN*USA*****55438~
MS2*SCAC*13579~
N1*ST*BEST BUY BLOOMINGTON RDC*94*70~
N3*6203 (B) WEST 111TH STREET~
N4*BLOOMINGTON*MN*55438*USA~
OID**CDEFGH**CTN*188*L*11423.610~
OID**DEFGHI**CTN*48*L*3214.119~
SE*73*0001~
Arrive at Pickup
B10*987655*5492588*SCAC~
LX*1~
L11*768521*72~
AT7*X3*NS***20100705*0835*LT~
MS1*BELLEVUE*WA*USA*****98004~
MS2*SCAC*13579~
N1*SF*VENDORS FACILITY*94*FACILITY1~
N3*225 PIONEER STREET~
N4*BELLEVUE*WA*98004*USA~
OID**FGEEOC**CTN*925*L*12665.1781~
OID**USSKOP**CTN*144*L*8455.6649~
SE*13*0001~
ETA at Delivery
B10*987655*5492588*SCAC~
LX*1~
L11*768521*72~
AT7*X2*NS***20100706*1200*LT~
MS1*BLOOMINGTON*MN*USA*****55438~
MS2*SCAC*13579~
N1*ST*BEST BUY BLOOMINGTON DDC*94*78~
N3*6150 WEST 110TH STREET~
N4*BLOOMINGTON*MN*55438*USA~
OID**FGEEOC**CTN*925*L*12665.1781~
OID**USSKOP**CTN*144*L*8455.6649~
SE*13*0001~
Pickup appointment
B10*987654*1234567*SCAC~
LX*1~
L11*1234567*BN~
L11*1*QN~
AT7***AA*AM*20100702*0600*LT~
MS1*BELLEVUE*WA*USA*****98004~
MS2*SCAC*13579~
N1*SF*VENDORS FACILITY*94*FACILITY1~
N3*225 PIONEER STREET~
N4*BELLEVUE*WA*98004*USA~
OID**ABCDEF**CTN*67*L*4357.3081~
OID**BCDEFG**CTN*138*L*5020.6649~
SE*14*0001~
Pickup appointment 2
B10*987655*5492588*SCAC~
LX*1~
L11*768522*72~
AT7***AA*NA*20100705*0900*LT~
MS1*BELLEVUE*WA*USA*****98004~
MS2*SCAC*13579~
N1*SF*VENDORS FACILITY*94*FACILITY1~
N3*225 PIONEER STREET~
N4*BELLEVUE*WA*98004*USA~
OID**FGEEOC**CTN*925*L*12665.1781~
OID**USSKOP**CTN*144*L*8455.6649~
SE*13*0001~
Pickup appointment, arrive at Pickup, depart Pickup
B10*987654*1234567*SCAC~
LX*1~
L11*1234567*BN~
L11*1*QN~
AT7***AA*NA*20100705*0900*LT~
MS1*BELLEVUE*WA*USA*****98004~
MS2*SCAC*13579~
N1*SF*VENDORS FACILITY*94*FACILITY1~
N3*225 PIONEER STREET~
N4*BELLEVUE*WA*98004*USA~
OID**ABCDEF**CTN*67*L*4357.3081~
OID**BCDEFG**CTN*138*L*5020.6649~
LX*2~
L11*1234567*BN~
L11*1*QN~
AT7*X3*NS***20100705*0900*LT~
MS1*BELLEVUE*WA*USA*****98004~
MS2*SCAC*13579~
N1*SF*VENDORS FACILITY*94*FACILITY1~
N3*225 PIONEER STREET~
N4*BELLEVUE*WA*98004*USA~
OID**ABCDEF**CTN*67*L*4357.3081~
OID**BCDEFG**CTN*138*L*5020.6649~
LX*3~
L11*1234567*BN~
L11*1*QN~
AT7*AF*NS***20100705*0935*LT~
MS1*BELLEVUE*WA*USA*****98004~
MS2*SCAC*13579~
N1*SF*VENDORS FACILITY*94*FACILITY1~
N3*225 PIONEER STREET~
N4*BELLEVUE*WA*98004*USA~
OID**ABCDEF**CTN*67*L*4357.3081~
OID**BCDEFG**CTN*138*L*5020.6649~
SE*36*0001~
Pickup Arrive & Depart in the same 214
B10*987654*1234567*SCAC~
LX*1~
L11*1234567*BN~
L11*1*QN~
AT7*X3*AH***20100702*0900*LT~
MS1*BELLEVUE*WA*USA*****98004~
MS2*SCAC*13579~
N1*SF*VENDORS FACILITY*94*FACILITY1~
N3*225 PIONEER STREET~
N4*BELLEVUE*WA*98004*USA~
OID**ABCDEF**CTN*67*L*4357.3081~
OID**BCDEFG**CTN*138*L*5020.6649~
LX*2~
L11*1234567*BN~
L11*1*QN~
AT7*AF*NS***20100702*0935*LT~
MS1*BELLEVUE*WA*USA*****98004~
MS2*SCAC*13579~
N1*SF*VENDORS FACILITY*94*FACILITY1~
N3*225 PIONEER STREET~
N4*BELLEVUE*WA*98004*USA~
OID**ABCDEF**CTN*67*L*4357.3081~
OID**BCDEFG**CTN*138*L*5020.6649~
SE*25*0001~
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.