X12 858 Freight Activity Shipment Information
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.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify 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 to identify 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)
Qualifier to designate 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
Qualifier to designate 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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate 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
- SI
- Shipment Information (858)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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 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
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
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) 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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
General Shipment Information
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.
Code specifying the method or type of transportation for the shipment
- X
- Intermodal (Piggyback)
Code identifying payment terms for transportation charges
- PP
- Prepaid (by Seller)
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)
Burlington Stores sends the Planning Number (WMS Load number) from the Burlington Stores Warehouse Management.
System (Manhattan Associates WMS) in this BX04 field.
Carrier's Reference Number (PRO/Invoice)
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- CN
- Carrier's Reference Number (PRO/Invoice)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Route Number
To transmit identifying information as specified by the Reference Identification Qualifier
Shipment Destination Code
To transmit identifying information as specified by the Reference Identification Qualifier
Route Information - Motor
To specify carrier and routing sequences and details
Code describing the relationship of a carrier to a specific shipment movement
- B
- Origin/Delivery Carrier (Any Mode)
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
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
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.
Address Information
To specify the location of the named party
N3 & N4 Segments are required when the N101 field is "SF" and "ST".
Geographic Location
To specify the geographic place of the named party
N3 & N4 Segments are required when the N101 field is "SF" and "ST".
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
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.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Detail
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
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.
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
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.
Line Item - Quantity and Weight
To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data
Basis for rating (miles, value, volume, etc.); Note: Weight may be defined by either data element 220 or 81
Code identifying the type of quantity or value on which the rate or item pricing is based
- LB
- Pound
Number of units (pieces) of the lading commodity
- L008 is the number of handling units of the line item tendered to the carrier.
Summary
Total Weight and Charges
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
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
EDI 858 Shipment Information Sample File
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|149014
IEA|1|000149014
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.