Big Lots
/
Ship Notice/Manifest
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Big Lots. Contact Big Lots for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Big Lots logo

X12 856 Ship Notice/Manifest

X12 Release 5010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
  • Floor Carton Load Example
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/big-lots/ship-noticemanifest/01GZGXM3KDXKFSQFHS3426CV98
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
detail
Shipment
HL
0100
Hierarchical Level
Max use 1
Required
TD1
1100
Carrier Details (Quantity and Weight)
Max use 20
Required
TD5
1200
Carrier Details (Routing Sequence/Transit Time)
Max use 12
Optional
TD3 Loop
TD4
1400
Carrier Details (Special Handling, or Hazardous Materials, or Both)
Max use 5
Optional
REF
1500
ASN Match Number
Max use 1
Required
REF
1500
Bill of Lading Number
Max use 1
Required
REF
1500
Internal Vendor Number
Max use 1
Required
Order
HL
0100
Hierarchical Level
Max use 1
Required
PRF
0500
Purchase Order Reference
Max use 1
Required
REF
1500
Reference Information
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

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

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

Code identifying the type of information in the Authorization Information

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

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

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

Code identifying the type of information in the Security Information

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

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

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

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

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

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

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

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

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

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

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

Date of the interchange

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

Time of the interchange

ISA-11
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

Code specifying the version number of the interchange control segments

00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

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

Code indicating sender's request for an interchange acknowledgment

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

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

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

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

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

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

Code identifying a group of application related transaction sets

SH
Ship Notice/Manifest (856)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

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

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

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

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

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

Assigned number originated and maintained by the sender

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

Code 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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

005010
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

Heading

ST
0100
Heading > ST

Transaction Set Header

RequiredMax use 1

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

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

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) 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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

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

BSN
0200
Heading > BSN

Beginning Segment for Ship Notice

RequiredMax use 1

To transmit identifying numbers, dates, and other basic data relating to the transaction set

Usage notes

The BSN02 should be a shipper assigned shipment reference.

Example: BSN\00\E8613002\20100101\1032\0001~

Example
BSN-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
05
Replace
BSN-02
396
Shipment Identification
Required
String (AN)
Min 2Max 30

A unique control number assigned by the original shipper to identify a specific shipment

Required
Date (DT)
CCYYMMDD format

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.
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

  • BSN04 is the time the shipment transaction set is created.
Usage notes

Time (HHMM) ship notice is created

BSN-05
1005
Hierarchical Structure Code
Required
Identifier (ID)

Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

Usage notes

0001 Pick and Pack Structure
Shipment, Order, Tare, Packing, Item (Pallet)
Shipment, Order, Packing, Item (Carton / Floor)

0001
Shipment, Order, Packaging, Item
DTM
0400
Heading > DTM

Date/Time Reference

RequiredMax use 10

To specify pertinent dates and times

Usage notes

Example: DTM\011\20000101\1032\ET~

Example
If Time Code (DTM-04) is present, then Time (DTM-03) is required
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

011
Shipped
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

Optional
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Usage notes

Time (HHMM)

DTM-04
623
Time Code
Optional
Identifier (ID)
Min 2Max 2

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

Usage notes

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.

Heading end

Detail

HL Shipment
RequiredMax >1
Usage notes

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~

HL
0100
Detail > Shipment > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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

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

Code defining the characteristic of a level in a hierarchical structure

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

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

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
TD1
1100
Detail > Shipment > TD1

Carrier Details (Quantity and Weight)

RequiredMax use 20

To specify the transportation details relative to commodity, weight, and quantity

Usage notes

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~

Example
TD1-01
103
Packaging Code
Required
String (AN)

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

Usage notes

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.

Part 1/2
CTN
Carton
MIX
Mixed Container Types
PLT
Pallet
SLP
Slip Sheet
Part 2/2
25
Corrugated or Solid
71
Not Otherwise Specified
90
Standard
TD1-02
80
Lading Quantity
Required
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

Usage notes

Total number of pallets when TD101 is PLT90.

Total number of cartons when TD101 is CTN25, SLP25, MIX71.

TD1-06
187
Weight Qualifier
Required
Identifier (ID)

Code defining the type of weight

G
Gross Weight
TD1-07
81
Weight
Required
Decimal number (R)
Min 1Max 10

Numeric value of weight

Usage notes

Gross Weight of Load.

TD1-08
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

LB
Pound
TD5
1200
Detail > Shipment > TD5

Carrier Details (Routing Sequence/Transit Time)

OptionalMax use 12

To specify the carrier and sequence of routing and provide transit time information

Usage notes

Example: TD5\O\2\RDWY\M\ROADWAY~

Example
TD5-01
133
Routing Sequence Code
Required
Identifier (ID)

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

O
Origin Carrier (Air, Motor, or Ocean)
TD5-02
66
Identification Code Qualifier
Required
Identifier (ID)

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)
TD5-03
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

Usage notes

Use SCAC code or IATA code depending on TD502.

TD5-04
91
Transportation Method/Type Code
Required
Identifier (ID)

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)
TD5-05
387
Routing
Optional
String (AN)
Min 1Max 35

Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

TD3 Loop
OptionalMax >1
TD3
1300
Detail > Shipment > TD3 Loop > TD3

Carrier Details (Equipment)

RequiredMax use 1

To specify transportation details relating to the equipment used by the carrier

Usage notes

This segment is used to specify the trailer number for a truckload shipment. Required only for truckload shipments.

Example: TD3\TL\RDWY\12345\\\SEAL123~

Example
TD3-01
40
Equipment Description Code
Required
Identifier (ID)

Code identifying type of equipment used for shipment

CC
Container resting on a Chassis
CN
Container
TL
Trailer (not otherwise specified)
TD3-02
206
Equipment Initial
Optional
String (AN)
Min 1Max 4

Prefix or alphabetic part of an equipment unit's identifying number

Usage notes

This element is required only if the Equipment initial is physically on the trailer with the number.

TD3-03
207
Equipment Number
Required
String (AN)
Min 1Max 15

Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

TD3 Loop end
TD4
1400
Detail > Shipment > TD4

Carrier Details (Special Handling, or Hazardous Materials, or Both)

OptionalMax use 5

To specify transportation special handling requirements, or hazardous materials information, or both

Usage notes

Example: TD4\CODE\CLASS\DESCRIPTION~

Example
If Hazardous Material Code Qualifier (TD4-02) is present, then Hazardous Material Class Code (TD4-03) is required
TD4-02
208
Hazardous Material Code Qualifier
Optional
Identifier (ID)

Code which qualifies the Hazardous Material Class Code (209)

D
Hazardous Materials ID, DOT
X
Hazard Class or Division
TD4-03
209
Hazardous Material Class Code
Optional
String (AN)

Code specifying the kind of hazard for a material

FG
Flammable Gas
FL
Flammable
FP
Flammable Poisonous Gas
HZD
Hazardous Cargo on Deck
TD4-04
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

REF
1500
Detail > Shipment > REF

ASN Match Number

RequiredMax use 1

To specify identifying information

Usage notes

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~

Example
Variants (all may be used)
REFBill of Lading NumberREFInternal Vendor Number
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

2I
ASN Match Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 50

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

REF
1500
Detail > Shipment > REF

Bill of Lading Number

RequiredMax use 1

To specify identifying information

Usage notes

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~

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

Code qualifying the Reference Identification

BM
Bill of Lading Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 50

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

REF
1500
Detail > Shipment > REF

Internal Vendor Number

RequiredMax use 1

To specify identifying information

Usage notes

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~

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

Code qualifying the Reference Identification

IA
Internal Vendor Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 50

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

N1 Ship From
RequiredMax 1
Variants (all may be used)
Ship To
N1
2200
Detail > Shipment > Ship From > N1

Party Identification

RequiredMax use 1

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

Usage notes

N101-N104 may be used as defined by the Seller to provide information about the Selling Party.

Example: N1\SF\XYZ CORPORATION

Example
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

SF
Ship From
Required
String (AN)
Min 1Max 60

Free-form name

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

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

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
N3
2400
Detail > Shipment > Ship From > N3

Party Location

RequiredMax use 2

To specify the location of the named party

Usage notes

Example: N3\44523 LAKESIDE PARKWAY

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

Address information

Usage notes

First Line of Address

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

Usage notes

2nd Line of Address

N4
2500
Detail > Shipment > Ship From > N4

Geographic Location

RequiredMax use 1

To specify the geographic place of the named party

Usage notes

Example: N4\CHICAGO\IL\60681

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

Free-form text for city name

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

Code (Standard State/Province) as defined by appropriate government agency

  • N402 is required only if city name (N401) is in the U.S. or Canada.
Usage notes

State Abbr. (ANSI A-22)

N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

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

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

Code identifying the country

N1 Ship From end
N1 Ship To
RequiredMax 1
Variants (all may be used)
Ship From
N1
2200
Detail > Shipment > Ship To > N1

Party Identification

RequiredMax use 1

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

Usage notes

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

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

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

ST
Ship To
Required
String (AN)
Min 1Max 60

Free-form name

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

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

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

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

N3
2400
Detail > Shipment > Ship To > N3

Party Location

RequiredMax use 2

To specify the location of the named party

Usage notes

Example: N3\44523 LAKESIDE PARKWAY

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

Address information

Usage notes

First Line of Address

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

Usage notes

2nd Line of Address

N4
2500
Detail > Shipment > Ship To > N4

Geographic Location

RequiredMax use 1

To specify the geographic place of the named party

Usage notes

Example: N4\CHICAGO\IL\60681

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

Free-form text for city name

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

Code (Standard State/Province) as defined by appropriate government agency

  • N402 is required only if city name (N401) is in the U.S. or Canada.
Usage notes

State Abbr. (ANSI A-22)

N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

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

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

Code identifying the country

N1 Ship To end
HL Order
RequiredMax >1
Usage notes

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~

HL
0100
Detail > Shipment > Order > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

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

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

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
0
No Subordinate HL Segment in This Hierarchical Structure.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
PRF
0500
Detail > Shipment > Order > PRF

Purchase Order Reference

RequiredMax use 1

To provide reference to a specific purchase order

Usage notes

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~

Example
PRF-01
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Big Lots Purchase Order Number, numeric only (no special characters or prefixes/suffixes added).

Required
Date (DT)
CCYYMMDD format

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.
Usage notes

PO Date

REF
1500
Detail > Shipment > Order > REF

Reference Information

RequiredMax use >1

To specify identifying information

Usage notes

Example: REF\IA\19864

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

Code qualifying the Reference Identification

Usage notes

Vendor Compliance Required.

IA
Internal Vendor Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 50

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

N1 Buying Party (Purchaser)
OptionalMax 1
Variants (all may be used)
Mark-for Party
N1
2200
Detail > Shipment > Order > Buying Party (Purchaser) > N1

Party Identification

RequiredMax use 1

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

Usage notes

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

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

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

BY
Buying Party (Purchaser)
Required
String (AN)
Min 1Max 60

Free-form name

N3
2400
Detail > Shipment > Order > Buying Party (Purchaser) > N3

Party Location

OptionalMax use 2

To specify the location of the named party

Usage notes

Example: N3\44523 LAKESIDE PARKWAY

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

Address information

Usage notes

First Line of Address

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

Usage notes

2nd Line of Address

N4
2500
Detail > Shipment > Order > Buying Party (Purchaser) > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Usage notes

Example: N4\CHICAGO\IL\60681

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

Free-form text for city name

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

Code (Standard State/Province) as defined by appropriate government agency

  • N402 is required only if city name (N401) is in the U.S. or Canada.
Usage notes

State Abbr. (ANSI A-22)

N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

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

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

Code identifying the country

N1 Buying Party (Purchaser) end
N1 Mark-for Party
OptionalMax 1
Variants (all may be used)
Buying Party (Purchaser)
N1
2200
Detail > Shipment > Order > Mark-for Party > N1

Party Identification

RequiredMax use 1

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

Usage notes

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

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

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

Z7
Mark-for Party
Required
String (AN)
Min 1Max 60

Free-form name

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

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

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

Big Lots Location Code (maximum of 5 digits).

N3
2400
Detail > Shipment > Order > Mark-for Party > N3

Party Location

OptionalMax use 2

To specify the location of the named party

Usage notes

Example: N3\44523 LAKESIDE PARKWAY

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

Address information

Usage notes

First Line of Address

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

Usage notes

2nd Line of Address

N4
2500
Detail > Shipment > Order > Mark-for Party > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Usage notes

Example: N4\CHICAGO\IL\60681

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

Free-form text for city name

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

Code (Standard State/Province) as defined by appropriate government agency

  • N402 is required only if city name (N401) is in the U.S. or Canada.
Usage notes

State Abbr. (ANSI A-22)

N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

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

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

Code identifying the country

N1 Mark-for Party end
HL Pack
OptionalMax >1
Variants (all may be used)
Shipping Tare
HL
0100
Detail > Shipment > Order > Pack > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

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

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

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
PO4
0600
Detail > Shipment > Order > Pack > PO4

Item Physical Details

RequiredMax use 1

To specify the physical qualities, packaging, weights, and dimensions relating to the item

Usage notes

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~

Example
If either Gross Volume per Pack (PO4-08) or Unit or Basis for Measurement Code (PO4-09) is present, then the other is required
If Length (PO4-10) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Width (PO4-11) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Height (PO4-12) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Unit or Basis for Measurement Code (PO4-13) is present, then at least one of Length (PO4-10), Width (PO4-11) or Height (PO4-12) is required
Required
Numeric (N0)
Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

Usage notes

Master Pack from the EDI PO Line Item PO4 segment element 01.

PO4-05
187
Weight Qualifier
Optional
Identifier (ID)

Code defining the type of weight

G
Gross Weight
PO4-06
384
Gross Weight per Pack
Required
Decimal number (R)
Min 1Max 9

Numeric value of gross weight per pack

Usage notes

Weight of master pack/carton.

PO4-07
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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
PO4-08
385
Gross Volume per Pack
Optional
Decimal number (R)
Min 1Max 9

Numeric value of gross volume per pack

Usage notes

Volume of master pack/carton.

PO4-09
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

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
PO4-10
82
Length
Optional
Decimal number (R)
Min 1Max 8

Largest horizontal dimension of an object measured when the object is in the upright position

Usage notes

Length of master pack/carton.

Optional
Decimal number (R)
Min 1Max 8

Shorter measurement of the two horizontal dimensions measured with the object in the upright position

Usage notes

Width of master pack/carton.

PO4-12
65
Height
Optional
Decimal number (R)
Min 1Max 8

Vertical dimension of an object measured when the object is in the upright position

Usage notes

Height of master pack/carton.

PO4-13
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

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
PO4-14
810
Inner Pack
Required
Numeric (N0)
Min 1Max 6

The number of eaches per inner container

Usage notes

Inner Pack from the EDI PO Line Item PO4 segment element 14.

MAN
1900
Detail > Shipment > Order > Pack > MAN

Marks and Numbers Information

OptionalMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

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~

Example
MAN-01
88
Marks and Numbers Qualifier
Required
Identifier (ID)

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
MAN-02
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

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.
DTM
2000
Detail > Shipment > Order > Pack > DTM

Expiration

OptionalMax use 1

To specify pertinent dates and times

Usage notes

This segment, at the pack level, is used to communicate expiration information.

This segment will be required for consumable items.

Example: DTM\036\20030101~

Example
Variants (all may be used)
DTMShelf Life Expiration
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

036
Expiration
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

DTM
2000
Detail > Shipment > Order > Pack > DTM

Shelf Life Expiration

OptionalMax use 1

To specify pertinent dates and times

Usage notes

This segment, at the pack level, is used to communicate expiration information.

This segment will be required for consumable items.

Example: DTM\511\20030101~

Example
Variants (all may be used)
DTMExpiration
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

511
Shelf Life Expiration
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

HL Loop
RequiredMax >1
HL
0100
Detail > Shipment > Order > Pack > HL Loop > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

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

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

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
0
No Subordinate HL Segment in This Hierarchical Structure.
LIN
0200
Detail > Shipment > Order > Pack > HL Loop > LIN

Item Identification

RequiredMax use 1

To specify basic item identification data

Example
If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
If either Product/Service ID Qualifier (LIN-08) or Product/Service ID (LIN-09) is present, then the other is required
If either Product/Service ID Qualifier (LIN-10) or Product/Service ID (LIN-11) is present, then the other is required
LIN-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
Usage notes

Line item number from the original EDI PO. Must be unique for each LIN01 segment on ASN.

LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

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
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Item UPC number must be 12 digits.

Big Lots SKU Number (always numeric 10 digits max.).

Vendor Item number (Mfg Code 30 characters).

LIN-04
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Usage notes

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
LIN-05
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-06
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Usage notes

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
LIN-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Usage notes

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
LIN-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Usage notes

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
LIN-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

SN1
0300
Detail > Shipment > Order > Pack > HL Loop > SN1

Item Detail (Shipment)

RequiredMax use 1

To specify line-item detail relative to shipment

Usage notes

This segment should contain information about the number of units ordered and shipped.

Example: SN1\1500\EA\1500\1500\EA

Example
If either Quantity (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required
SN1-02
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

Usage notes

Each Quantity Shipped, per pallet or carton, for this PO line item as it pertains to the type of shipment.

SN1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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
SN1-05
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

  • SN105 is quantity ordered.
Usage notes

Quantity ordered (Optional for Big Lots).

SN1-06
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA
Each
PID
0700
Detail > Shipment > Order > Pack > HL Loop > PID

Product/Item Description

RequiredMax use 200

To describe a product or process in coded or free-form format

Example
PID-01
349
Item Description Type
Required
Identifier (ID)

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
PID-05
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

TD4
1400
Detail > Shipment > Order > Pack > HL Loop > TD4

Carrier Details (Special Handling, or Hazardous Materials, or Both)

OptionalMax use 5

To specify transportation special handling requirements, or hazardous materials information, or both

Usage notes

Populate where applicable.

Example: TD4\CODE\CLASS\DESCRIPTION~

Example
If Hazardous Material Code Qualifier (TD4-02) is present, then Hazardous Material Class Code (TD4-03) is required
TD4-02
208
Hazardous Material Code Qualifier
Optional
Identifier (ID)

Code which qualifies the Hazardous Material Class Code (209)

D
Hazardous Materials ID, DOT
X
Hazard Class or Division
TD4-03
209
Hazardous Material Class Code
Optional
String (AN)

Code specifying the kind of hazard for a material

FG
Flammable Gas
FL
Flammable
FP
Flammable Poisonous Gas
HZD
Hazardous Cargo on Deck
TD4-04
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

DTM
2000
Detail > Shipment > Order > Pack > HL Loop > DTM

Expiration

OptionalMax use 1

To specify pertinent dates and times

Usage notes

This segment, at the item level, is used to communicate expiration information.

This segment will be required for consumable items.

Example: DTM\036\20030101~

Example
Variants (all may be used)
DTMShelf Life Expiration
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

036
Expiration
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

DTM
2000
Detail > Shipment > Order > Pack > HL Loop > DTM

Shelf Life Expiration

OptionalMax use 1

To specify pertinent dates and times

Usage notes

This segment, at the item level, is used to communicate expiration information.

This segment will be required for consumable items.

Example: DTM\511\20030101~

Example
Variants (all may be used)
DTMExpiration
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

511
Shelf Life Expiration
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

HL Loop end
HL Pack end
HL Shipping Tare
OptionalMax >1
Usage notes

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~

Variants (all may be used)
Pack
HL
0100
Detail > Shipment > Order > Shipping Tare > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

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

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

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
MAN
1900
Detail > Shipment > Order > Shipping Tare > MAN

Marks and Numbers Information

RequiredMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

Must be unique number; cannot be the same as other pallets/cartons in the same shipment.

Example: MAN\GM\99999999999999999999~

Example
MAN-01
88
Marks and Numbers Qualifier
Required
Identifier (ID)

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
MAN-02
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

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.
HL Pack
RequiredMax >1
Usage notes

This HL segment is used to indicate that this is the start of information at the pack level.

Example: HL\4\3\P~

HL
0100
Detail > Shipment > Order > Shipping Tare > Pack > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

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

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

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
1
Additional Subordinate HL Data Segment in This Hierarchical Structure.
PO4
0600
Detail > Shipment > Order > Shipping Tare > Pack > PO4

Item Physical Details

RequiredMax use 1

To specify the physical qualities, packaging, weights, and dimensions relating to the item

Usage notes

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~

Example
If either Gross Volume per Pack (PO4-08) or Unit or Basis for Measurement Code (PO4-09) is present, then the other is required
If Length (PO4-10) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Width (PO4-11) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Height (PO4-12) is present, then Unit or Basis for Measurement Code (PO4-13) is required
If Unit or Basis for Measurement Code (PO4-13) is present, then at least one of Length (PO4-10), Width (PO4-11) or Height (PO4-12) is required
Required
Numeric (N0)
Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

Usage notes

Master Pack from the EDI PO Line Item PO4 segment element 01.

PO4-05
187
Weight Qualifier
Optional
Identifier (ID)

Code defining the type of weight

G
Gross Weight
PO4-06
384
Gross Weight per Pack
Required
Decimal number (R)
Min 1Max 9

Numeric value of gross weight per pack

Usage notes

Weight of master pack/carton.

PO4-07
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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
PO4-08
385
Gross Volume per Pack
Optional
Decimal number (R)
Min 1Max 9

Numeric value of gross volume per pack

Usage notes

Volume of master pack/carton.

PO4-09
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

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
PO4-10
82
Length
Optional
Decimal number (R)
Min 1Max 8

Largest horizontal dimension of an object measured when the object is in the upright position

Usage notes

Length of master pack/carton.

Optional
Decimal number (R)
Min 1Max 8

Shorter measurement of the two horizontal dimensions measured with the object in the upright position

Usage notes

Width of master pack/carton.

PO4-12
65
Height
Optional
Decimal number (R)
Min 1Max 8

Vertical dimension of an object measured when the object is in the upright position

Usage notes

Height of master pack/carton.

PO4-13
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

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.
Usage notes

Defines UOM for PO410, PO411, PO412.

IN
Inch
PO4-14
810
Inner Pack
Required
Numeric (N0)
Min 1Max 6

The number of eaches per inner container

Usage notes

Inner Pack from the EDI PO Line Item PO4 segment element 14.

MAN
1900
Detail > Shipment > Order > Shipping Tare > Pack > MAN

Marks and Numbers Information

OptionalMax use >1

To indicate identifying marks and numbers for shipping containers

Usage notes

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~

Example
MAN-01
88
Marks and Numbers Qualifier
Required
Identifier (ID)

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
MAN-02
87
Marks and Numbers
Required
String (AN)
Min 1Max 48

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.
DTM
2000
Detail > Shipment > Order > Shipping Tare > Pack > DTM

Expiration

OptionalMax use 1

To specify pertinent dates and times

Usage notes

This segment, at the pack level, is used to communicate expiration information.

This segment will be required for consumable items.

Example: DTM\036\20030101~

Example
Variants (all may be used)
DTMShelf Life Expiration
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

036
Expiration

Date product is no longer consumable or usable.

Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

DTM
2000
Detail > Shipment > Order > Shipping Tare > Pack > DTM

Shelf Life Expiration

OptionalMax use 1

To specify pertinent dates and times

Usage notes

This segment, at the pack level, is used to communicate expiration information.

This segment will be required for consumable items.

Example: DTM\511\20030101~

Example
Variants (all may be used)
DTMExpiration
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

511
Shelf Life Expiration

Date product is no longer available for sale.

Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

HL Item
RequiredMax >1
Usage notes

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~

HL
0100
Detail > Shipment > Order > Shipping Tare > Pack > Item > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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

  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

Code defining the characteristic of a level in a hierarchical structure

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

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

  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
0
No Subordinate HL Segment in This Hierarchical Structure.
LIN
0200
Detail > Shipment > Order > Shipping Tare > Pack > Item > LIN

Item Identification

RequiredMax use 1

To specify basic item identification data

Usage notes

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~

Example
If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
If either Product/Service ID Qualifier (LIN-08) or Product/Service ID (LIN-09) is present, then the other is required
If either Product/Service ID Qualifier (LIN-10) or Product/Service ID (LIN-11) is present, then the other is required
LIN-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
Usage notes

Line item number from the original EDI PO. Must be unique for each LIN01 segment on ASN.

LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

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
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Item UPC number must be 12 digits.

Big Lots SKU Number (always numeric 10 digits max.).

Vendor Item number (Mfg Code 30 characters).

LIN-04
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Usage notes

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
LIN-05
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-06
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Usage notes

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
LIN-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Usage notes

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
LIN-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Usage notes

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
LIN-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

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.

SN1
0300
Detail > Shipment > Order > Shipping Tare > Pack > Item > SN1

Item Detail (Shipment)

RequiredMax use 1

To specify line-item detail relative to shipment

Usage notes

This segment should contain information about the number of units ordered and shipped.

Example: SN1\1500\EA\1500\1500\EA

Example
If either Quantity (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required
SN1-02
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

Usage notes

Each Quantity Shipped, per pallet or carton, for this PO line item as it pertains to the type of shipment.

SN1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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
SN1-05
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

  • SN105 is quantity ordered.
Usage notes

Quantity ordered (Optional for Big Lots).

SN1-06
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA
Each
PID
0700
Detail > Shipment > Order > Shipping Tare > Pack > Item > PID

Product/Item Description

RequiredMax use 200

To describe a product or process in coded or free-form format

Usage notes

This segment, at the item level, is used to describe a product.

Example: PID\F\\FW-PHOTO WED SCENE~

Example
PID-01
349
Item Description Type
Required
Identifier (ID)

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
PID-05
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

TD4
1400
Detail > Shipment > Order > Shipping Tare > Pack > Item > TD4

Carrier Details (Special Handling, or Hazardous Materials, or Both)

OptionalMax use 5

To specify transportation special handling requirements, or hazardous materials information, or both

Usage notes

Populate where applicable.

Example: TD4\CODE\CLASS\DESCRIPTION~

Example
If Hazardous Material Code Qualifier (TD4-02) is present, then Hazardous Material Class Code (TD4-03) is required
TD4-02
208
Hazardous Material Code Qualifier
Optional
Identifier (ID)

Code which qualifies the Hazardous Material Class Code (209)

D
Hazardous Materials ID, DOT
X
Hazard Class or Division
TD4-03
209
Hazardous Material Class Code
Optional
String (AN)

Code specifying the kind of hazard for a material

FG
Flammable Gas
FL
Flammable
FP
Flammable Poisonous Gas
HZD
Hazardous Cargo on Deck
TD4-04
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

DTM
2000
Detail > Shipment > Order > Shipping Tare > Pack > Item > DTM

Expiration

OptionalMax use 1

To specify pertinent dates and times

Usage notes

This segment, at the item level, is used to communicate expiration information.

This segment will be required for consumable items.

Example: DTM\036\20030101~

Example
Variants (all may be used)
DTMShelf Life Expiration
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

036
Expiration

Date product is no longer consumable or usable.

Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

DTM
2000
Detail > Shipment > Order > Shipping Tare > Pack > Item > DTM

Shelf Life Expiration

OptionalMax use 1

To specify pertinent dates and times

Usage notes

This segment, at the item level, is used to communicate expiration information.

This segment will be required for consumable items.

Example: DTM\511\20030101~

Example
Variants (all may be used)
DTMExpiration
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

511
Shelf Life Expiration

Date product is no longer available for sale.

Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

HL Item end
HL Pack end
HL Shipping Tare end
HL Order end
HL Shipment end
Detail end

Summary

CTT
0100
Summary > CTT

Transaction Totals

RequiredMax use 1

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.
Usage notes

Example: CTT\4\1500

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

Usage notes

Number of "HL"' segments in the transaction set.

CTT-02
347
Hash Total
Optional
Decimal number (R)
Min 1Max 10

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.

## Example:
-.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

Usage notes

Sum of number of units shipped (SN102).

SE
0200
Summary > SE

Transaction Set Trailer

RequiredMax use 1

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

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

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

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

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

Summary end

Functional Group Trailer

RequiredMax use 1

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

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

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

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

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

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

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

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

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

A control number assigned by the interchange sender

EDI Samples

Floor Carton Load Example

ST*856*0001~
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

ST*856*6880001~
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.