X12 856 Non-Merchandise Ship Notice/Manifest
This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.
The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
- ~ Segment
- * Element
- > Component
- None included
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
- SH
- Ship Notice/Manifest (856)
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).
- 856
- Ship Notice/Manifest
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Code identifying purpose of transaction set
- 00
- Original
- 05
- Replace
The purpose of a replacement ASN is to update the original ASN with the required corrections; whenever retransmitting the ASN as a revised document ensure that the BSN01 = 05 and the BSN02 = the same Shipment Number indicated on the original ASN transmission, a Unique ISA Ctrl number is also applied. Applying these changes to each ASN retransmission ensures that the ASN avoids any Duplicate ASN error that would occur when a duplicate carton is received within 365 days of the first carton identity, which is often the case when retransmitting a replacement asn as an original.
A unique control number assigned by the original shipper to identify a specific shipment
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
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)
- BSN04 is the time the shipment transaction set is created.
Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set
Burlington Stores requires the SOPI format for the ASN; shipment, order,
pack (carton), and item (SKU). The ASN is therefore structured hierarchically with each of the 4 levels: shipment, order, pack (carton), and item (SKU).
Burlington Stores requires the HL segment at all levels, these must be named accordingly shipment, order, pack (carton), and item (SKU). At the shipment level, the HL segment marks the beginning of the shipment loop and may occur only once per transaction set; in other words, only one shipment is allowed per ASN, there can only be one HL03 = 'S'.
The shipment level specifies the details relative to the entire physical shipment and associated bill of lading. "Containment" is determined by the size of the trailer or container in other words, a maximum of one "containment" at the shipment level (one trailer or one container) is allowed per ASN.
However, One or more orders can be included per shipment number. One or more packs may be reported for each order. One or more items may be reported for each pack. Lastly, pack level data must be included in the ASN in order to report the contents of each shipping 'container' to the receiver so the contents of the carton/container are known throughout the receiving system and can be confirmed.
- 0001
- Shipment, Order, Packaging, Item
Burlington Stores requires that all ASN'S must be in a pick pack / SOPI structure, vendor should use the '0001' qualifier in the BSN05 if available to them in their system. Sending the ASN in a 'pick and pack' structure as demonstrated in the SOPI structure (Shipment, Order, Package Item) will ensure prompt delivery of the ASN to internal system and greatly reduce the possibility of chargebacks.
Burlington Stores recognizes that a limited number of our vendors cannot use a pick pack / SOPI structure, under these limited circumstances, Burlington Stores does allows the '0001' or the '0002' qualifier if the shipment is direct to consumers, as would be the case for internet or web based orders that are initiated by the consumer. Vendor should plan to use the '0001' qualifier in the BSN05 if available to them in their system. Sending the ASN in a 'pick and pack' (0001) structure will ensure prompt delivery of the ASN to internal systems and greatly reduce the possibility of chargebacks.
- 0002
- Shipment, Order, Item, Packaging
Burlington Stores allows the '0001' or the '0002' qualifier if the shipment is direct to consumers, as would be the case for internet or web based orders that are initiated by the consumer.
- 0004
- Shipment, Order, Item
Burlington Stores uses the '0004' qualifier if the shipment is a warehouse or store shipments and is GOH (Goods on Hanger). GOH shipments destined for warehouse or store shipments do not always have a pack segment.
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 011
- Shipped
Burlington Stores requires the '011' qualifier in the Shipment Level detail.
- 017
- Estimated Delivery
The '017' qualifier in the Shipment Level detail is Optional.
- 067
- Current Schedule Delivery
The '067' qualifier in the Shipment Level detail is Optional.
- 068
- Current Schedule Ship
The '068' qualifier in the Shipment Level detail is Optional.
- AA1
- Estimated Point of Arrival
Burlington Stores uses the 'AA1' qualifier on Import orders to indicate estimated dates and times associated with import orders that impact customs paperwork (i.e.customs filings).
- AA2
- Estimated Point of Discharge
Burlington Stores uses the 'AA2' qualifier on Import orders to indicate estimated dates and times associated with import orders that impact customs paperwork (i.e.customs filings).
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)
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
- AS
- Alaska Standard Time
- CS
- Central Standard Time
- ES
- Eastern Standard Time
- HS
- Hawaii-Aleutian Standard Time
- LT
- Local Time
- MS
- Mountain Standard Time
- NS
- Newfoundland Standard Time
- PS
- Pacific Standard Time
- TS
- Atlantic Standard Time
Detail
Burlington Stores requires the HL segment at the shipment level, the HL segment marks the beginning of the shipment loop and may occur only once per transaction set; in other words, only one shipment is allowed per ASN.
The shipment level specifies the details relative to the entire physical shipment and associated bill of lading. "Containment" is determined by the size of the trailer or container in other words, a maximum of one "containment unit" at the shipment level (one trailer or one container) is allowed per ASN.
Notes: A 40’ high cube container has an average weight limit of 62,942 lb (28,550 kg) and a volume of or 2,700 cubic feet (76.400 cubic meters).
ASN Notes: Any shipment that exceeds the average weight limit of 62,942 lb (28,550 kg) and a volume of or 2,700 cubic feet (76.400 cubic meters) is indicative of a second shipment. The second shipment is going to be necessary or already has taken place therefore a second ASN becomes necessary to define the second shipment. If an ASN has already been sent and the shipment exceeds the average weight limit of 62,942 lb (28,550 kg) and a volume of or 2,700 cubic feet (76.400 cubic meters; A modification to adjust the first ASN will also be required as there are now 2 shipments with each shipment uniquely identified by an ASN.
If you have any questions about containment contact EDI.Support@BurlingtonStores.com for clarification.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
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.
- S
- Shipment
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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Burlington Stores uses the TD1 segment in the Hierarchical Level (HL Loop) where HL03 = 'S'.
Burlington Stores uses the TD1 segment in the Hierarchical Level (HL Loop) where HL03 = 'O'.
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
Burlington Stores uses the TD103 segment in the Hierarchical Level (HL Loop) where HL03 = 'S'.
First 3 characters:
BAG Bag
CTN Carton
SLP Slip Sheet
SRW Shrink Wrap
Last 2 characters:
01 Aluminum
25 Corrugated or Solid
31 Fibre
58 Metal
76 Paper
79 Plastic
91 Stainless Steel
94 Wood
Number of units (pieces) of the lading commodity
Burlington Stores requires the 'TD102' segment at the shipment level to describe the lading quantity; the lading quantity reflects the total number of cartons, containers or GOH pieces in the shipment as consigned to the carrier.
Code identifying the commodity coding system used for Commodity Code
Code defining the type of weight
Burlington Stores requires the 'TD106' and 'TD107' segments at the shipment level to describe the gross weight; the gross weight reflects the total weight in pounds of the shipment as stated on the bill of lading and as consigned to the carrier.
- G
- Gross Weight
Burlington Stores requires the ''G' qualifier in the TD106' segment at the shipment level to describe the gross weight; the gross weight reflects the total weight in pounds of the shipment as stated on the bill of lading and as consigned to the carrier.
Numeric value of weight
Burlington Stores requires the 'TD106' and 'TD107' segments at the shipment level to describe the gross weight; the gross weight reflects the total weight in pounds of the shipment as stated on the bill of lading and as consigned to the carrier.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Burlington Stores requires this segment in the shipment level; Hierarchical
Level (HL Loop) where HL03 = 'S'.
- KG
- Kilogram
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Burlington Stores requires the TD5 segment when the Hierarchical Level (HL Loop) where HL03 = 'S'.
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
Burlington Stores requires the 'TD502' and 'TD503' segments at the shipment level, when 'TD502' = 2 it identifies the 'TD503' as the Standard Carrier Alpha Code (SCAC) of the carrier; 'TD503' segment identifies the actual SCAC of the carrier.
Burlington Stores does not require the 'TD502' and 'TD503' segments at the Order level.
- 2
- Standard Carrier Alpha Code (SCAC)
Burlington Stores requires the 'TD502' and 'TD503' segments at the shipment level, the 'TD502' = 2 and identifies the 'TD503' as the Standard Carrier Alpha Code (SCAC) of the carrier; 'TD503' segment identifies the actual SCAC of the carrier.
Code identifying a party or other code
When and if the carrier is unknown, as might be the case when transportation is arranged by Burlington Stores; the use of ‘UNKW’ identifying the carrier as unknown in the 'TD503' is considered acceptable.
If you are using FedEx exclusively, as might be the case when shipping 'direct to consumer (DTC), you may find one of these SCAC codes best describes the method of shipping via FedEx.
- FDE
- Express Only M ID 2/4
- FDEG
- Ground Only
- FDEN
- Express, Ground & SmartPost
- FXSP
- SmartPost Only
Code specifying the method or type of transportation for the shipment
Burlington Stores requires the 'TD504' segment at the shipment level.
- A
- Air
- AE
- Air Express
- BU
- Bus
- C
- Consolidation
- CE
- Customer Pickup / Customer's Expense
- D
- Parcel Post
- E
- Expedited Truck
- H
- Customer Pickup
- L
- Contract Carrier
- LT
- Less Than Trailer Load (LTL)
- M
- Motor (Common Carrier)
- O
- Containerized Ocean
- P
- Private Carrier
- R
- Rail
- S
- Ocean
- SR
- Supplier Truck
- T
- Best Way (Shippers Option)
- U
- Private Parcel Service
Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction
20131206 - INC982364 - Burlington Stores no longer uses the TD501
Routing Sequence Code in the Hierarchical Level (HL Loop) where HL03 = 'S'. The TD501 Routing Sequence Code is scheduled for removal on 12/31/2014 *856.S.O.2.1
- BK
- Back Ordered from Previous Order
- BP
- Shipment Partial, Back Order to Ship on (Date)
- CC
- Shipment Complete on (Date)
- PR
- Partial Shipment
- SS
- Split Shipment
Code identifying type of location
Burlington Stores uses the TD507 location qualifier on Import orders to indicate the various ports which might be used indicated on an import order in keeping with best practices for customs related operations. This field is not required for Domestic orders.
- PA
- Port of Arrival
- PB
- Port of Discharge
- PE
- Port of Entry
Code which identifies a specific location
Burlington Stores uses the TD508 location identifier on Import orders to indicate the port identified by the 'TD507'. This field is not required for Domestic orders.
Reference Identification
To specify identifying information
Burlington Stores requires the 'REF' segment at the shipment level, where HL = 'S' to specify details about the shipment or the order to aid in the cross docking and other internal processes. Several REF01 segments are expected to be received depending on the vendor and type of order. Carefully review the User Notes under each REF01 qualifier to determine which qualifiers are applicable to your business. If there are any questions about this specification contact EDI Support at (609) 387-7800 Ext 3340 (EDI-0) or EDI.Support@BurlingtonStores.com
Code qualifying the Reference Identification
- AO
- Appointment Number
Burlington Stores requires the 'REF01' segment to identify the Bill of Lading or Carrier PRO number in the 'REF02' segment and only uses this code in the Hierarchical Level (HL Loop) where HL03 = 'S'; Appointment Number is not required.
- BM
- Bill of Lading Number
Burlington Stores requires the 'REF01' segment to identify the Bill of Lading or Carrier PRO number in the 'REF02' segment and only uses this code in the Hierarchical Level (HL Loop) where HL03 = 'S'.
- CN
- Carrier's Reference Number (PRO/Invoice)
Burlington Stores requires the 'REF01' segment to identify the Bill of Lading or Carrier PRO number in the 'REF02' segment and only uses this code in the Hierarchical Level (HL Loop) where HL03 = 'S'.
- CO
- Customer Order Number
Burlington Stores requires the 'CO' qualifier in the Shipment Level detail, where HL= 'S'; as would be the case in a direct to consumer internet or web order where the shipment is direct to consumer.
Burlington Stores sends the 'CO' qualifier in the REF01 in the PO 850 to indicate the Customer Order Number for Internet generated PO's; i.e. Direct to Consumer Orders.
- DP
- Department Number
- IA
- Internal Vendor Number
- IV
- Seller's Invoice Number
Burlington Stores does not use the 'IV' qualifier, however the 'IV' qualifier is included at this time to accommodate legacy vendors who have this field coded in their EDI systems today.
- PO
- Purchase Order Number
Burlington Stores requires the Purchase Order Number in the 'PRF01' segment in the Order Level detail to identify the Purchase Order. The Purchase Order Number can be found in the 850 in the BEG03.
- SI
- Shipper's Identifying Number for Shipment (SID)
Burlington Stores requires the 'SI' qualifier in the shipment information; the Shipment Identification (SID) is sent to the vendor from the Sterling TMS system when they arrange their (pick up) transportation.
If this value is not known, for example importers who use containerized transportation, use “NOSID".
- VN
- Vendor Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Burlington Stores requires the use of the N1 segment, at the shipment level where HL= 'S'; and at the pack level where HL= 'P' if N101 = 'Z7'.
Name
To identify a party by type of organization, name, and code
Burlington Stores requires the 'N1' segment at the shipment level, where HL = 'S' to specify details about specific entities involved in the order, shipment and delivery processes Carefully review the User Notes under each REF01qualifier to determine which qualifiers are applicable to your business. If there are any questions about this specification contact EDI Support at (609) 387-7800 Ext 3340 (EDI-0) or EDI.Support@BurlingtonStores.com
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Burlington Stores requires the 'BY' qualifier in the Order Level detail if no 'ST' qualifier (Buying Party) is present in the Shipment level and the shipment is not direct to consumer.
When N101 = 'BY' and N103 = '92' then N104 = the Burlington Stores Store or DC#.
*For a complete list of stores check
http://vendor.burlingtoncoatfactory.com/lists/allStores.bcf - OB
- Ordered By
Burlington Stores requires the 'OB' qualifier in the shipment Level detail if the shipment is direct to consumer; If N101 = 'OB', then N103 and N104 are not required.
- SF
- Ship From
Burlington Stores requires the 'SF' qualifier in the Shipment Level detail along with the full address in the N3 and N4 segments.
- ST
- Ship To
Burlington Stores requires the 'ST' qualifier in the shipment Level detail if no 'BY' qualifier (Buying Party) is present in the order level and the shipment is not direct to consumer.
When N101 = 'ST', vendors have the option to send an identification code qualifier in the N103 and the associated identification code in the N104; otherwise the N3 and N4 segments become required as may be the case for some vendors on ASNs for Direct to Consumer Shipments if no 'BY' qualifier (Buying Party) is present in the purchase order.
When N101 = 'ST' and N103 = '92' then N104 = the Burlington Stores Store or DC#.
*For a complete list of stores check
http://vendor.burlingtoncoatfactory.com/lists/allStores.bcf
Code designating the system/method of code structure used for Identification Code (67)
When N101 = 'ST' and N103 = '92' then N104 = the Burlington Stores Store or DC#.
*For a complete list of stores check
http://vendor.burlingtoncoatfactory.com/lists/allStores.bcf
When N101 = 'SF', vendors have the option to send an identification code qualifier in the N103 and the associated identification code in the N104; otherwise the N3 and N4 segments become required.
If N101 = 'OB', N103 and N104 are not required.
- 1
- D-U-N-S Number, Dun & Bradstreet
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- 93
- Code assigned by the organization originating the transaction set
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
- UL
- UCC/EAN Location Code
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.
When N101 = 'ST' and N103 = '92' then N104 = the Burlington Stores Store or DC#.
*For a complete list of stores check
http://vendor.burlingtoncoatfactory.com/lists/allStores.bcf
When N101 = 'SF', vendors have the option to send an identification code qualifier of their choosing in the N103 and the associated identification code in the N104.
If N101 = 'OB', N103 and N104 are not required.
Address Information
To specify the location of the named party
Burlington Stores requires complete address information for the ship from address, minimum requirement would be the full N4 Geographic Location segment.
Geographic Location
To specify the geographic place of the named party
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)
Code identifying the country
Burlington Stores uses the ISO 3166-1 Alpha-2 Code in this field and assumes 'US' is the Country Code unless otherwise specified; Vendors should include the N404 country code when the address listed lies outside of the US.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
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.
- O
- Order
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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Burlington Stores requires the 'PRF' segment in the Order Level detail.
20140120-TS- MAP remediated under INC990143, where ASNs were not rejected when missing the PRF or PRF01, ASNs will now reject when the PRF is missing.
Identifying number for Purchase Order assigned by the orderer/purchaser
Burlington Stores requires the 'PRF01' segment in the Order Level detail to identify the Purchase Order. The Purchase Order Number can be found in the 850 in the BEG03 segment.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Burlington Stores uses the TD1 segment in the Hierarchical Level (HL Loop) where HL03 = 'S'.
Burlington Stores uses the TD1 segment in the Hierarchical Level (HL Loop) where HL03 = 'O'.
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
- 01
- Aluminum
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
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.
- P
- Pack
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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Burlington Stores requires the use of the N1 segment, at the shipment level where HL= 'S'; and at the pack level where HL= 'P' if N101 = 'Z7'.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- Z7
- Mark-for Party
Burlington Stores requires the 'Z7' qualifier in the Order Level detail, when the shipment is ship to warehouse and specified for store delivery (Ship to Mark For). This indicates the receiving location for the order where the location is neither the buying party nor the ship to location and the mark-for party is specified on the shipping label
When N101 = 'Z7' and N103 = '92' then N104 = the Burlington Stores Store or DC#.
*For a complete list of stores check
http://vendor.burlingtoncoatfactory.com/lists/allStores.bcf
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- 93
- Code assigned by the organization originating the transaction set
- 94
- Code assigned by the organization that is the ultimate destination of the transaction set
- UL
- UCC/EAN Location Code
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.
When N101 = 'Z7' and N103 = '92' then N104 = the Burlington Stores Store or DC#.
*For a complete list of stores check
http://vendor.burlingtoncoatfactory.com/lists/allStores.bcf
Address Information
To specify the location of the named party
Burlington Stores requires complete address information for the ship from address, minimum requirement would be the full N4 Geographic Location segment.
Geographic Location
To specify the geographic place of the named party
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)
Code identifying the country
Burlington Stores uses the ISO 3166-1 Alpha-2 Code in this field and assumes 'US' is the Country Code unless otherwise specified; Vendors should include the N404 country code when the address listed lies outside of the US.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
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.
- I
- Item
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.
Item Identification
To specify basic item identification data
Burlington Stores requires the use of the LIN segment, at the item level where HL= 'I', in order to clarify the pack structure when ordered as such. This is indicated in the PO in the PO1 segment.
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
Burlington Stores requires the presence of a 'Style' in the Item Level detail as across reference to 'SKU' or Item code; the 'IT' qualifier or the 'VA' Qualifier must therefore be present in the SLN09.
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Burlington Stores requires the presence of a 'SKU' or Item code in the Item Level detail; the 'IN' qualifier or the 'UP' Qualifier must therefore be present in the SLN09.
If choosing to use the UPC Code please make sure that this is known to your buyer prior to the issuance of the PO, in short, PO’s MUST be transmitted with the UPCs that you intend to send back on the ASN, there is a risk that the ASN will be rejected as the cross reference is unknown in the host system.
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
NOTE: When SN103 = ‘AS’ (Prepack order) LIN03 = PO107 from the PO,
LIN04 and LIN05 can be excluded.
- IT
- Buyer's Style Number
Burlington Stores requires the presence of a 'Style' in the Item Level detail as across reference to 'SKU' or Item code; the 'IT' qualifier or the 'VA' Qualifier must therefore be present in the SLN09.
- VA
- Vendor's Style Number
Burlington Stores requires the presence of a 'Style' in the Item Level detail as across reference to 'SKU' or Item code ; the 'IT' qualifier or the 'VA' Qualifier must therefore be present in the SLN09. Use Vendor Style (VA) ONLY when LIN02 =UP, EA, or EN.
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BO
- Buyers Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IZ
- Buyer's Size Code
Identifying number for a product or service
Item Detail (Shipment)
To specify line-item detail relative to shipment
Burlington Stores requires the use of the SN1 segment, at the Item level where HL= 'I', in order to clarify the item details.
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Burlington Stores requires the SN102 element at the item level details of the shipment.
Burlington Stores requires the value sent in the SN102 to be a whole number (integer). SN102 values that contain decimal equivalents will be rejected. For example if shipping 100 items; 100 should be the value sent in the SN102, a value of 100.00 is not a valid value and will be rejected.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
NOTE: When SN103 = ‘AS’ (Prepack order) LIN03 = PO107 from the PO,
LIN04 and LIN05 can be excluded.
- AS
- Assortment
Burlington Stores requires the 'AS' qualifier in the SN103 segment to clarify the pack structure when ordered as such. This is indicated in the PO with the use of 'AS' in the PO103. The 'AS' qualifier in the SN103 segment indicates to the seller that the use of the SLN segment will also be required at the item level where HL='I', in order to clarify the pack structure also indicated in the PO with the use of 'AS' in the PO103. In other words, the ASN should describe 'what's in the box' to a level that indicates the contents of the 'AS' (assortment) which was ordered.
- EA
- Each
Subline Item Detail
To specify product subline detail item data
Burlington Stores requires the use of the SLN segment, at the item level where HL= 'I', in order to clarify the pack structure when ordered as such. This is indicated in the PO with the user of 'AS' in the PO103.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
Numeric value of quantity
Burlington Stores requires the value sent in the SLN04 to be a whole number (integer). SLN04 values that contain decimal equivalents will be rejected. For example if shipping 100 items; 100 should be the value sent in the SLN04, a value of 100.00 is not a valid value and will be rejected.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Burlington Stores requires the presence of a 'SKU' or Item code in the Item Level detail; the 'IN' qualifier or the 'UP' Qualifier must therefore be present in the SLN09.
If choosing to use the UPC Code please make sure that this is known to your buyer prior to the issuance of the PO, in short, PO’s MUST be transmitted with the UPCs that you intend to send back on the ASN, there is a risk that the ASN will be rejected as the cross reference is unknown in the host system.
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT
- Buyer's Style Number
Burlington Stores requires the presence of a 'Style' in the Item Level detail as across reference to 'SKU' or Item code; the 'IT' qualifier or the 'VA' Qualifier must therefore be present in the SLN09.
- VA
- Vendor's Style Number
Burlington Stores requires the presence of a 'Style' in the Item Level detail as across reference to 'SKU' or Item code; the 'IT' qualifier or the 'VA' Qualifier must therefore be present in the SLN09.
If choosing to use the Vendor Style (VA) please make sure that this is known to your buyer or the cross reference will not work and the ASN will have problem.
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BO
- Buyers Color
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IZ
- Buyer's Size Code
Identifying number for a product or service
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of HL segments.
If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Total number of line items in the transaction set
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
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.