X12 856 Ship Notice/Manifest
This X12 Transaction Set 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
- ^ 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
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
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
- 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
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
- 005010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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).
- 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
The BSN02 should be a shipper assigned shipment reference.
Example: BSN\00\E8613002\20100101\1032\0001~
Code identifying purpose of transaction set
- 00
- Original
- 05
- Replace
A unique control number assigned by the original shipper to identify a specific shipment
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- 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.
Time (HHMM) ship notice 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
0001 Pick and Pack Structure
Shipment, Order, Tare, Packing, Item (Pallet)
Shipment, Order, Packing, Item (Carton / Floor)
- 0001
- Shipment, Order, Packaging, Item
Date/Time Reference
To specify pertinent dates and times
Example: DTM\011\20000101\1032\ET~
Code specifying type of date or time, or both date and time
- 011
- Shipped
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)
Time (HHMM)
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
Time zone of location where shipment is originating. Can populate with ‘LT’ for Local Time if unable to use standard time zone code. Refer to ASC X12 v. 005010 Data Element Dictionary for acceptable code values.
Detail
This HL segment is used to indicate that this is the start of information about the shipment. There should be only one Shipment level HL segment per 856 document.
Example: HL\1\S~
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
Vendor Compliance Chargeback item (required segment).
TD107 and TD108 should contain the total gross weight of goods being shipped. TD101, TD102, TD106 -TD108 are "mandatory" elements for Big Lots.
Example: TD1\PLT90\1\\G\740.00\LB~
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
If TD101=CTN25, then shipment is a carton floor load.
If TD101=SLP25, then shipment is a slip sheet load.
If TD101=PLT90, then shipment is a palletized load.
If TD101=MIX71, then shipment is pallet and carton floor load.
- CTN25
- carton floor load
- MIX71
- pallet and carton floor load
- PLT90
- palletized load
- SLP25
- slip sheet load
Number of units (pieces) of the lading commodity
Total number of pallets when TD101 is PLT90.
Total number of cartons when TD101 is CTN25, SLP25, MIX71.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Example: TD5\O\2\RDWY\M\ROADWAY~
Code describing the relationship of a carrier to a specific shipment movement
- O
- Origin Carrier (Air, Motor, or Ocean)
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.
- 2
- Standard Carrier Alpha Code (SCAC)
- 4
- International Air Transport Association (IATA)
Code identifying a party or other code
Use SCAC code or IATA code depending on TD502.
Code specifying the method or type of transportation for the shipment
- A
- Air
- E
- Expedited Truck
- H
- Customer Pickup
- LT
- Less Than Trailer Load (LTL)
- M
- Motor (Common Carrier)
- O
- Containerized Ocean
- R
- Rail
- SR
- Supplier Truck
- U
- Private Parcel Service
- X
- Intermodal (Piggyback)
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
This segment is used to specify the trailer number for a truckload shipment. Required only for truckload shipments.
Example: TD3\TL\RDWY\12345\\\SEAL123~
Code identifying type of equipment used for shipment
- CC
- Container resting on a Chassis
- CN
- Container
- TL
- Trailer (not otherwise specified)
Prefix or alphabetic part of an equipment unit's identifying number
This element is required only if the Equipment initial is physically on the trailer with the number.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
Example: TD4\CODE\CLASS\DESCRIPTION~
Code which qualifies the Hazardous Material Class Code (209)
- D
- Hazardous Materials ID, DOT
- X
- Hazard Class or Division
Code specifying the kind of hazard for a material
- FG
- Flammable Gas
- FL
- Flammable
- FP
- Flammable Poisonous Gas
- HZD
- Hazardous Cargo on Deck
A free-form description to clarify the related data elements and their content
Internal Vendor Number
To specify identifying information
This segment contains Vendor Compliance Chargeback items
(required elements): Big Lots requires at least a Vendor Number, a Bill of Lading Number and an ASN Match #.
The Big Lots TMS will require each vendor to generate their own ASN Match # value. This same value must be sent in the REF*2I segment of the ASN (or entered in the corresponding ASN webform field).
Requirements for the ASN Match # value:
- Can be up to 25 characters long
- Can be alphanumeric, but we cannot process the special character “&”
- Collect POs: value must be specific to the routing request
- Prepaid POs: value must be specific to the appointment
Note: if more than one collect PO is routed together, each PO can either have the same ASN Match # or a unique ASN Match #. If more than one prepaid PO is scheduled together on the same appointment, each PO will have the same ASN Match #. The routed or scheduled ASN Match # must appear in the REF*2I segment of the ASN.
Example: REF\IA\0000822163~
ASN Match Number
To specify identifying information
This segment contains Vendor Compliance Chargeback items
(required elements): Big Lots requires at least a Vendor Number, a Bill of Lading Number and an ASN Match #.
The Big Lots TMS will require each vendor to generate their own ASN Match # value. This same value must be sent in the REF*2I segment of the ASN (or entered in the corresponding ASN webform field).
Requirements for the ASN Match # value:
- Can be up to 25 characters long
- Can be alphanumeric, but we cannot process the special character “&”
- Collect POs: value must be specific to the routing request
- Prepaid POs: value must be specific to the appointment
Note: if more than one collect PO is routed together, each PO can either have the same ASN Match # or a unique ASN Match #. If more than one prepaid PO is scheduled together on the same appointment, each PO will have the same ASN Match #. The routed or scheduled ASN Match # must appear in the REF*2I segment of the ASN.
Example: REF\2I\1234567~
Bill of Lading Number
To specify identifying information
This segment contains Vendor Compliance Chargeback items
(required elements): Big Lots requires at least a Vendor Number, a Bill of Lading Number and an ASN Match #.
The Big Lots TMS will require each vendor to generate their own ASN Match # value. This same value must be sent in the REF*2I segment of the ASN (or entered in the corresponding ASN webform field).
Requirements for the ASN Match # value:
- Can be up to 25 characters long
- Can be alphanumeric, but we cannot process the special character “&”
- Collect POs: value must be specific to the routing request
- Prepaid POs: value must be specific to the appointment
Note: if more than one collect PO is routed together, each PO can either have the same ASN Match # or a unique ASN Match #. If more than one prepaid PO is scheduled together on the same appointment, each PO will have the same ASN Match #. The routed or scheduled ASN Match # must appear in the REF*2I segment of the ASN.
Example: REF\BM\12345~
Party Identification
To identify a party by type of organization, name, and code
N101-N104 may be used as defined by the Seller to provide information about the Selling Party.
Example: N1\SF\XYZ CORPORATION
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Party Location
To specify the location of the named party
Example: N3\44523 LAKESIDE PARKWAY
Geographic Location
To specify the geographic place of the named party
Example: N4\CHICAGO\IL\60681
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.
State Abbr. (ANSI A-22)
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Party Identification
To identify a party by type of organization, name, and code
This segment contains Vendor Compliance Chargeback items (required elements): N101, N103, and N104 are required by Big Lots for the Ship To information; these may be obtained from the N1-N4 Ship To loop on the 850 document or the original purchase order.
Example: N1\ST\LOCATION NAME\92\NNNN
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Big Lots Store Location Code - a maximum of 5 digits.
N101, N103, and N104 are required by Big Lots for the Ship To information; these may be obtained from the N1-N4 Ship To loop on the 850 document or the original purchase order.
Big Lots Usage = Big Lots DC Location Code
0890 – Columbus
0870 - Montgomery
0869 – Apple Valley
0874 - Tremont
0879 - Durant
Party Location
To specify the location of the named party
Example: N3\44523 LAKESIDE PARKWAY
Geographic Location
To specify the geographic place of the named party
Example: N4\CHICAGO\IL\60681
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.
State Abbr. (ANSI A-22)
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
This HL segment is used to indicate that this is the start of information about the Order Level. There should be at least one Order level HL segment per 856 document.
Example: HL\2\1\O~
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.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
This segment contains Vendor Compliance Chargeback items (required elements): PRF01 and PRF04 should be obtained from the originating 850 document or the original printed purchase order.
Example: PRF\0007606936\\20000102~
Identifying number for Purchase Order assigned by the orderer/purchaser
Big Lots Purchase Order Number, numeric only (no special characters or prefixes/suffixes added).
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- PRF04 is the date assigned by the purchaser to purchase order.
PO Date
Reference Information
To specify identifying information
Example: REF\IA\19864
Code qualifying the Reference Identification
Vendor Compliance Required.
- IA
- Internal Vendor Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Party Identification
To identify a party by type of organization, name, and code
N101, N103, and N104 are required by Big Lots for the Mark-for Party information; these may be obtained from the N1- N4 Ship To loop from the 850 document or the original purchase order.
Example: N1\BY\XYZ CORPORATION
Party Location
To specify the location of the named party
Example: N3\44523 LAKESIDE PARKWAY
Geographic Location
To specify the geographic place of the named party
Example: N4\CHICAGO\IL\60681
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.
State Abbr. (ANSI A-22)
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Party Identification
To identify a party by type of organization, name, and code
N101, N103, and N104 are required by Big Lots for the Mark-for Party information; these may be obtained from the N1- N4 Ship To loop from the 850 document or the original purchase order.
Example: N1\Z7\LOCATION NAME\92\NNNNN
Code identifying an organizational entity, a physical location, property or an individual
- Z7
- Mark-for Party
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
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.
Big Lots Location Code (maximum of 5 digits).
Party Location
To specify the location of the named party
Example: N3\44523 LAKESIDE PARKWAY
Geographic Location
To specify the geographic place of the named party
Example: N4\CHICAGO\IL\60681
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.
State Abbr. (ANSI A-22)
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
This HL segment is used to indicate that this is the start of information about the packs in the shipment. Specifically, it provides for the inclusion of the unique Pack/Pallet number from the GS1 128 (pallet/master carton) label.
This HL will not occur if the goods being shipped are not palletized.
Example: HL\3\2\T~
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.
- T
- Shipping Tare
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.
Marks and Numbers Information
To indicate identifying marks and numbers for shipping containers
Must be unique number; cannot be the same as other pallets/cartons in the same shipment.
Example: MAN\GM\99999999999999999999~
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
This HL segment is used to indicate that this is the start of information at the pack level.
Example: HL\4\3\P~
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.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
This segment is used to describe a single shipping unit (carton).
Examples:
PO4\24\\G\12\OZ\\\\12~
PO4\12\\G\12\LB\\12\12\12\IN\12~
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Master Pack from the EDI PO Line Item PO4 segment element 01.
Numeric value of gross weight per pack
Weight of master pack/carton.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
- OZ
- Ounce - Av
Numeric value of gross volume per pack
Volume of master pack/carton.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CF
- Cubic Feet
- CI
- Cubic Inches
- CR
- Cubic Meter
Largest horizontal dimension of an object measured when the object is in the upright position
Length of master pack/carton.
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Width of master pack/carton.
Vertical dimension of an object measured when the object is in the upright position
Height of master pack/carton.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO413 defines the unit of measure for PO410, PO411, and PO412.
Defines UOM for PO410, PO411, PO412.
- IN
- Inch
The number of eaches per inner container
Inner Pack from the EDI PO Line Item PO4 segment element 14.
Marks and Numbers Information
To indicate identifying marks and numbers for shipping containers
Big Lots Usage: must be unique number; cannot be the same as other pallets/cartons in the same shipment.
When the shipping container is the same as the consumer unit, the U.P.C. may be the only GS1 identification code on the container. In many applications, it is necessary to positively identify what identification code is to be scanned and matched at point of receipt. Since the U.P.C. is not a
unique serial shipping container code, only one pack level for each item
is required when using the pick and pack structure. The total number of
shipping units for this item is the same as the quantity for the item in the
SN1 segment at the item level.
This segment is required for floor loaded shipments.
Examples:
MAN\UC\99999999999999~
MAN\GM\99999999999999999999~
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
- UC
- U.P.C. Shipping Container Code
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
Expiration
To specify pertinent dates and times
This segment, at the pack level, is used to communicate expiration information.
This segment will be required for consumable items.
Example: DTM\036\20030101~
Shelf Life Expiration
To specify pertinent dates and times
This segment, at the pack level, is used to communicate expiration information.
This segment will be required for consumable items.
Example: DTM\511\20030101~
This HL segment is used to indicate the start of information about the items contained in the subpacks (cartons). (For single item shipments: Hierarchical loop relates to shipment parent).
Multiple item shipments: Relate line item loop to HL at the carton level.
Example: HL\5\3\I~
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
Big Lots uses the SKU, UPC and Item Number which may be provided in any Order.
Example: LIN\1\SK\123456789\UP\010731500111\EN\0123456789123VP\107315-001\UK\9999999999999~
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
Line item number from the original EDI PO. Must be unique for each LIN01 segment on ASN.
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.
- SK
- Stock Keeping Unit (SKU)
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Item UPC number must be 12 digits.
Big Lots SKU Number (always numeric 10 digits max.).
Vendor Item number (Mfg Code 30 characters).
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
EN and UK are optional.
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
EN and UK are optional.
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
EN and UK are optional.
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
EN and UK are optional.
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Item UPC number must be 12 digits.
Big Lots SKU Number (numeric only 10 digits max.).
Vendor Item number (Mfg Code 30 characters).
GTIN 14-digit Data Structure.
EAN number must be 13 digits.
Item Detail (Shipment)
To specify line-item detail relative to shipment
This segment should contain information about the number of units ordered and shipped.
Example: SN1\1500\EA\1500\1500\EA
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Each Quantity Shipped, per pallet or carton, for this PO line item as it pertains to the type of shipment.
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.
- EA
- Each
Numeric value of quantity
- SN105 is quantity ordered.
Quantity ordered (Optional for Big Lots).
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Product/Item Description
To describe a product or process in coded or free-form format
This segment, at the item level, is used to describe a product.
Example: PID\F\\FW-PHOTO WED SCENE~
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
A free-form description to clarify the related data elements and their content
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
Populate where applicable.
Example: TD4\CODE\CLASS\DESCRIPTION~
Code which qualifies the Hazardous Material Class Code (209)
- D
- Hazardous Materials ID, DOT
- X
- Hazard Class or Division
Code specifying the kind of hazard for a material
- FG
- Flammable Gas
- FL
- Flammable
- FP
- Flammable Poisonous Gas
- HZD
- Hazardous Cargo on Deck
A free-form description to clarify the related data elements and their content
Expiration
To specify pertinent dates and times
This segment, at the item level, is used to communicate expiration information.
This segment will be required for consumable items.
Example: DTM\036\20030101~
Shelf Life Expiration
To specify pertinent dates and times
This segment, at the item level, is used to communicate expiration information.
This segment will be required for consumable items.
Example: DTM\511\20030101~
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.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
This segment is used to describe a single shipping unit (carton).
Example:
PO4\24\\G\12\OZ\\\\12~
PO4\12\\G\12\LB\\12\12\12\IN\12~
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Master Pack from the EDI PO Line Item PO4 segment element 01.
Numeric value of gross weight per pack
Weight of master pack/carton.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- KG
- Kilogram
- LB
- Pound
- OZ
- Ounce - Av
Numeric value of gross volume per pack
Volume of master pack/carton.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CF
- Cubic Feet
- CI
- Cubic Inches
- CR
- Cubic Meter
Largest horizontal dimension of an object measured when the object is in the upright position
Length of master pack/carton.
Shorter measurement of the two horizontal dimensions measured with the object in the upright position
Width of master pack/carton.
Vertical dimension of an object measured when the object is in the upright position
Height of master pack/carton.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO413 defines the unit of measure for PO410, PO411, and PO412.
- IN
- Inch
The number of eaches per inner container
Inner Pack from the EDI PO Line Item PO4 segment element 14.
Marks and Numbers Information
To indicate identifying marks and numbers for shipping containers
Big Lots Usage: must be unique number; cannot be the same as other pallets/cartons in the same shipment.
When the shipping container is the same as the consumer unit, the U.P.C. may be the only GS1 identification code on the container. In many applications, it is necessary to positively identify what identification code is to be scanned and matched at point of receipt. Since the U.P.C. is not a
unique serial shipping container code, only one pack level for each item
is required when using the pick and pack structure. The total number of
shipping units for this item is the same as the quantity for the item in the
SN1 segment at the item level.
This segment is required for floor loaded shipments.
Examples:
MAN\UC\99999999999999~
MAN\GM\99999999999999999999~
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
- GM
- EAN.UCC Serial Shipping Container Code (SSCC) and Application Identifier
- UC
- U.P.C. Shipping Container Code
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
Expiration
To specify pertinent dates and times
This segment, at the pack level, is used to communicate expiration information.
This segment will be required for consumable items.
Example: DTM\036\20030101~
Shelf Life Expiration
To specify pertinent dates and times
This segment, at the pack level, is used to communicate expiration information.
This segment will be required for consumable items.
Example: DTM\511\20030101~
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
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
Line item number from the original EDI PO. Must be unique for each LIN01 segment on ASN.
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
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Item UPC number must be 12 digits.
Big Lots SKU Number (always numeric 10 digits max.).
Vendor Item number (Mfg Code 30 characters).
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
EN and UK are optional.
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
EN and UK are optional.
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
EN and UK are optional.
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
EN and UK are optional.
- EN
- EAN/UCC - 13
- SK
- Stock Keeping Unit (SKU)
- UK
- GTIN 14-digit Data Structure
- UP
- UCC - 12
- VN
- Vendor's (Seller's) Item Number
- VP
- Vendor's (Seller's) Part Number
Item Detail (Shipment)
To specify line-item detail relative to shipment
This segment should contain information about the number of units ordered and shipped.
Example: SN1\1500\EA\1500\1500\EA
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Each Quantity Shipped, per pallet or carton, for this PO line item as it pertains to the type of shipment.
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.
- EA
- Each
Numeric value of quantity
- SN105 is quantity ordered.
Quantity ordered (Optional for Big Lots).
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
A free-form description to clarify the related data elements and their content
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
Populate where applicable.
Example: TD4\CODE\CLASS\DESCRIPTION~
Code which qualifies the Hazardous Material Class Code (209)
- D
- Hazardous Materials ID, DOT
- X
- Hazard Class or Division
Code specifying the kind of hazard for a material
- FG
- Flammable Gas
- FL
- Flammable
- FP
- Flammable Poisonous Gas
- HZD
- Hazardous Cargo on Deck
A free-form description to clarify the related data elements and their content
Expiration
To specify pertinent dates and times
This segment, at the item level, is used to communicate expiration information.
This segment will be required for consumable items.
Example: DTM\036\20030101~
Shelf Life Expiration
To specify pertinent dates and times
This segment, at the item level, is used to communicate expiration information.
This segment will be required for consumable items.
Example: DTM\511\20030101~
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.
Example: CTT\4\1500
Total number of line items in the transaction set
Number of "HL"' segments in the transaction set.
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
18E2 Fifth occurrence of value being hashed.
1873 Hash Total
Sum of number of units shipped (SN102).
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
Floor Carton Load Example
BSN*00*83479*20040916*1108*0001~
DTM*011*20040916~
HL*1**S~
TD1*CTN25*3****G*1444*LB~
TD5*O*2*CSXD*M*CSXD~
TD3*TL*TRL*535090~
REF*BM*83479~
REF*IA*000217600~
REF*2I*1234567~
N1*ST*Big Lots Stores, Inc*92*0874~
N3*Tremont Dc 874*50 Rausch Creek Road~
N4*Tremont*PA*17981~
N1*SF*VENDOR NAME*~
N3*STREET ADDRESS~
N4*CITY*ST*ZIP~
HL*2*1*O~
PRF*0007606936***20100402~
REF*IA*000217600~
N1*Z7*CLOSEOUT DISTRIBUTION, IN*92*0874~
N3*TREMONT DC – 874*50 RAUSCH CREEK ROAD~
N4*TREMONT*PA*17981~
HL*3*2*P~
PO4*6****G*12*LB***12*12*12*IN*6~
MAN*GM*00200731490000193562~
HL*4*3*I~
LIN*1*EN*0123456789123*UP*073149835369*SK*170005458*VN*18353606~
SN1**6*EA~
PID*F****FW-PHOTO WED SCENE~
HL*3*2*P~
PO4*6****G*12*LB***12*12*12*IN*6~
MAN*GM*00200731490000193563~
HL*4*3*I~
LIN*1*EN*0123456789123*UP*073149835369*SK*170005458*VN*18353606~
SN1**6*EA~
PID*F****FW-PHOTO WED SCENE~
HL*3*2*P~
PO4*6****G*12*LB***12*12*12*IN*6~
MAN*GM*00200731490000193564~
HL*4*3*I~
LIN*004*EN*0123456789123*UP*073149835369*SK*170005458*VN*18353606~
SN1**6*EA~
PID*F****FW-PHOTO WED SCENE~
CTT*4~
SE*45*0001~
Pallet Load Example
BSN*00*0061741*20040916*1315*0001~
DTM*011*20040916~
HL*1**S~
TD1*PLT90*2****G*42247.5*LB~
TD5*O*2*SCAC*M*PICK 15165~
TD3*TL**15165~
REF*BM*0061741~
REF*2I*1234567~
REF*IA*000059890~
N1*SF*VENDOR NAME~
N3*STREET ADDRESS~
N4*CITY*ST*ZIP~
N1*ST*CLOSEOUT DISTRIBUTION, IN*92*0874~
N3*TREMONT DC – 874*50 RAUSCH CREEK ROAD~
N4*TREMONT*PA*17981~
HL*2*1*O~
PRF*0002361184***20120807~
REF*IA*000059890~
N1*Z7*CLOSEOUT DISTRIBUTION, IN*92*0874~
N3*TREMONT DC – 874*50 RAUSCH CREEK ROAD~
N4*TREMONT*PA*17981~
HL*3*2*T~
MAN*GM*00100111206000038094~
HL*4*3*P~
PO4*12****G*12*LB***12*12*12*IN*12~
HL*5*4*I~
LIN**SK*140000417*UP*011120669282*VN*6692M*EN*0123456789123 ~
SN1**3200*EA**7600*EA~
PID*F****FW-PHOTO WED SCENE~
HL*6*2*T~
MAN*GM*00100111206000038100~
HL*7*6*P~
PO4*12****G*12*LB***12*12*12*IN*12~
HL*8*7*I~
LIN**SK*140000417*UP*011120669282*VN*6692M*EN*0123456789123 ~
SN1**3200*EA**7600*EA~
PID*F****FW-PHOTO WED SCENE~
CTT*8~
SE*40*6880001~
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.