Burlington
/
Freight Activity Shipment Information
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Burlington. Contact Burlington for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Burlington logo

X12 858 Freight Activity Shipment Information

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Shipment Information Transaction Set (858) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the sender with the capability to transmit detailed bill-of-lading, rating, and/or scheduling information pertinent to a shipment.

This transaction set can also be used to exchange Government Bills of Lading (GBLs), Commercial Bills of Lading (CBLs), Transportation Control and Movement Documents (TCMDs), and Personal Property Government Bills of Lading (PPGBLs).
It may be used by the U.S. Civilian Government, U.S. Department of Defense, and any of their trading partners to exchange information about the shipment of freight, household goods, and passengers. This transaction set fulfills information requirements established by U.S. Government transportation movement rules and regulations.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • EDI 858 Shipment Information Sample File
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/burlington/freight-activity-shipment-information/01H8Q38GXEDF1FBZ5V0CPWV45G
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BX
030
General Shipment Information
Max use 1
Required
N9
060
Carrier's Reference Number (PRO/Invoice)
Max use 30
Required
N9
060
Route Number
Max use 30
Required
N9
060
Shipment Destination Code
Max use 30
Required
G62
110
Date/Time
Max use 10
Required
R3
175
Route Information - Motor
Max use 13
Required
N1 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

SI
Shipment Information (858)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
858
Shipment Information
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BX
030
Heading > BX

General Shipment Information

RequiredMax use 1

To transmit identification numbers and other basic shipment data

  • BX05 contains the Standard Carrier Alpha Code (SCAC) of the original roadhaul carrier receiving the shipment.
Example
BX-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
BX-02
91
Transportation Method/Type Code
Required
Identifier (ID)

Code specifying the method or type of transportation for the shipment

X
Intermodal (Piggyback)
BX-03
146
Shipment Method of Payment
Required
Identifier (ID)

Code identifying payment terms for transportation charges

PP
Prepaid (by Seller)
BX-04
145
Shipment Identification Number
Required
String (AN)
Min 1Max 30

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)

Usage notes

Burlington Stores sends the Planning Number (WMS Load number) from the Burlington Stores Warehouse Management.

System (Manhattan Associates WMS) in this BX04 field.

BX-05
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

BX-06
188
Weight Unit Code
Required
Identifier (ID)

Code specifying the weight unit

L
Pounds
N9
060
Heading > N9

Carrier's Reference Number (PRO/Invoice)

RequiredMax use 30

To transmit identifying information as specified by the Reference Identification Qualifier

Example
Variants (all may be used)
N9Route NumberN9Shipment Destination Code
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

CN
Carrier's Reference Number (PRO/Invoice)
N9-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N9
060
Heading > N9

Route Number

RequiredMax use 30

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

RU
Route Number
N9-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N9
060
Heading > N9

Shipment Destination Code

RequiredMax use 30

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

4C
Shipment Destination Code
N9-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

G62
110
Heading > G62

Date/Time

RequiredMax use 10

To specify pertinent dates and times

Example
G62-01
432
Date Qualifier
Required
Identifier (ID)

Code specifying type of date

10
Requested Ship Date/Pick-up Date
G62-02
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

R3
175
Heading > R3

Route Information - Motor

RequiredMax use 13

To specify carrier and routing sequences and details

Example
R3-01
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

R3-02
133
Routing Sequence Code
Required
Identifier (ID)

Code describing the relationship of a carrier to a specific shipment movement

B
Origin/Delivery Carrier (Any Mode)
R3-09
369
Free-form Description
Required
String (AN)
Min 1Max 45

Free-form descriptive text

N1 Loop
RequiredMax >1
N1
390
Heading > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BY
Buying Party (Purchaser)
SE
Selling Party
SF
Ship From
ST
Ship To
N1-02
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
FA
Facility Identification
SV
Service Provider Number
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

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.
N3
410
Heading > N1 Loop > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Usage notes

N3 & N4 Segments are required when the N101 field is "SF" and "ST".

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N4
420
Heading > N1 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Usage notes

N3 & N4 Segments are required when the N101 field is "SF" and "ST".

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

N1 Loop end
Heading end

Detail

HL Loop
RequiredMax >1
HL
010
Detail > HL Loop > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
9
Line Detail
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

Code indicating if there are hierarchical child data segments subordinate to the level being described

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
0
No Subordinate HL Segment in This Hierarchical Structure.
L0 Loop
RequiredMax >1
L0
145
Detail > HL Loop > L0 Loop > L0

Line Item - Quantity and Weight

RequiredMax use 1

To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data

Example
L0-01
213
Lading Line Item Number
Required
Numeric (N0)
Min 1Max 3

Sequential line number for a lading item

L0-02
220
Billed/Rated-as Quantity
Required
Decimal number (R)
Min 1Max 11

Basis for rating (miles, value, volume, etc.); Note: Weight may be defined by either data element 220 or 81

L0-03
221
Billed/Rated-as Qualifier
Required
Identifier (ID)

Code identifying the type of quantity or value on which the rate or item pricing is based

LB
Pound
L0-04
81
Weight
Required
Decimal number (R)
Min 1Max 10

Numeric value of weight

L0-05
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

FR
Freight Weight
L0-08
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

  • L008 is the number of handling units of the line item tendered to the carrier.
L0-09
211
Packaging Form Code
Required
Identifier (ID)

Code for packaging form of the lading quantity

CTN
Carton
L0 Loop end
HL Loop end
Detail end

Summary

L3
010
Summary > L3

Total Weight and Charges

RequiredMax use 1

To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items

Example
L3-01
81
Weight
Required
Decimal number (R)
Min 1Max 10

Numeric value of weight

L3-02
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

FR
Freight Weight
SE
020
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

EDI 858 Shipment Information Sample File

ISA|00| |00| |ZZ|SENDER |ZZ|RECEIVER |231106|1336|U|00401|000000001|0|T|>
GS|SI|SENDERGS|RECEIVERGS|20231106|133659|000000001|X|004010
ST|858|0001
BX|00|X|PP|100237289|SCDS|L
N9|CN|100237289
N9|4C|O
N9|RU|29
G62|10|20221206
R3|SCDS|B|||||||O
N1|SF|Burlington DC - PNR|FA|PNR 512-CA
N3|27582 Pioneer Avenue
N4|Redlands|CA|92374|USA
N1|ST|Forward Air|FA|CSNY
N3|8701 Warehouse Center Dr
N4|Humble|TX|77338|USA
N1|BY|Burlington Stores Distribution Center|92|BRLNGTNUSA
N1|SE|SCHNEIDER IMDL|SV|SCDS
HL|1||9
L0|1|23290.19|LB|23290.19|FR|||1389|CTN
L3|23290.19|FR
SE|19|0001
GE|1|000000001
IEA|1|000000001

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.