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

ISA Interchange Control Header

Required · Max use 1

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

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 10 Max 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 10 Max 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 2 Max 2

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

Codes

• 01: Duns (Dun & Bradstreet)
• 02: SCAC (Standard Carrier Alpha Code)
• 03: FMC (Federal Maritime Commission)
• 04: IATA (International Air Transport Association)
• 07: Global Location Number (GLN)
• 08: UCC EDI Communications ID (Comm ID)
• 09: X.121 (CCITT)
• 10: Department of Defense (DoD) Activity Address Code
• 11: DEA (Drug Enforcement Administration)
• 12: Phone (Telephone Companies)
• 13: UCS Code (The UCS Code is a Code Used for UCS Transmissions; it includes the Area Code and Telephone Number of a Modem; it Does Not Include Punctuation, Blanks or Access Code)
• 14: Duns Plus Suffix
• 15: Petroleum Accountants Society of Canada Company Code
• 16: Duns Number With 4-Character Suffix
• 17: American Bankers Association (ABA) Transit Routing Number (Including Check Digit, 9 Digit)
• 18: Association of American Railroads (AAR) Standard Distribution Code
• 19: EDI Council of Australia (EDICA) Communications ID Number (COMM ID)
• 20: Health Industry Number (HIN)
• 21: Integrated Postsecondary Education Data System, or (IPEDS)
• 22: Federal Interagency Commission on Education, or FICE
• 23: National Center for Education Statistics Common Core of Data 12-Digit Number for Pre-K-Grade 12 Institutes, or NCES
• 24: The College Board's Admission Testing Program 4-Digit Code of Postsecondary Institutes, or ATP
• 25: ACT, Inc. 4-Digit Code of Postsecondary Institutions.
• 26: Statistics of Canada List of Postsecondary Institutions
• 27: Carrier Identification Number as assigned by Health Care Financing Administration (HCFA)
• 28: Fiscal Intermediary Identification Number as assigned by Health Care Financing Administration (HCFA)
• 29: Medicare Provider and Supplier Identification Number as assigned by Health Care Financing Administration (HCFA)
• 30: U.S. Federal Tax Identification Number
• 31: Jurisdiction Identification Number Plus 4 as assigned by the International Association of Industrial Accident Boards and Commissions (IAIABC)
• 32: U.S. Federal Employer Identification Number (FEIN)
• 33: National Association of Insurance Commissioners Company Code (NAIC)
• 34: Medicaid Provider and Supplier Identification Number as assigned by individual State Medicaid Agencies in conjunction with Health Care Financing Administration (HCFA)
• 35: Statistics Canada Canadian College Student Information System Institution Codes
• 36: Statistics Canada University Student Information System Institution Codes
• 37: Society of Property Information Compilers and Analysts
• 38: The College Board and ACT, Inc. 6-Digit Code List of Secondary Institutions
• AM: Association Mexicana del Codigo de Producto (AMECOP) Communication ID
• NR: National Retail Merchants Association (NRMA) - Assigned
• SA: User Identification Number as assigned by the Safety and Fitness Electronic Records (SAFER) System
• SN: Standard Address Number
• ZZ: Mutually Defined

ISA-06 · I06 · Interchange Sender ID · Required · String (AN) · Min 15 Max 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)

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

• 08: UCC EDI Communications ID (Comm ID)
• ZZ: Mutually Defined

ISA-08 · I07 · Interchange Receiver ID · Required · String (AN) · Min 15 Max 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

Example values

• BUCKLETEST     

• 6127770000     

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 1 Max 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 9 Max 9

A control number assigned by the interchange sender

ISA-14 · I13 · Acknowledgment Requested · Required · Identifier (ID) · Min 1 Max 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 1 Max 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 1 Max 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

GS Functional Group Header

Required · Max use 1

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

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 2 Max 15

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

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

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

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

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

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

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

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

Assigned number originated and maintained by the sender

GS-07 · 455 · Responsible Agency Code · Required · Identifier (ID) · Min 1 Max 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

0100 Heading > ST

ST Transaction Set Header

Required · Max use 1

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

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 4 Max 9

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

0200 Heading > BSN

BSN Beginning Segment for Ship Notice

Required · Max use 1

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

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

Code identifying purpose of transaction set

• 00: Original
• 07: Duplicate

BSN-02 · 396 · Shipment Identification · Required · String (AN) · Min 2 Max 30

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

Usage notes

BSN02 – This is a unique control number that cannot be repeated for seven years. Duplicate ship ID’s will create a non-compliance issue. Non-compliance issues may result in chargebacks.

BSN-03 · 373 · Date · 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.

BSN-04 · 337 · Time · Required · Time (TM) · HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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

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

BSN-05 · 1005 · Hierarchical Structure Code · Optional · 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

• 0001: Shipment, Order, Packaging, Item

Detail

HL Loop Required Max >1

0100 Detail > HL Loop > HL

HL Hierarchical Level

Required · Max 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.

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

1100 Detail > HL Loop > TD1

TD1 Carrier Details (Quantity and Weight)

Required · Max use 20

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

If Packaging Code (TD1-01) is present, then Lading Quantity (TD1-02) is required

If Weight Qualifier (TD1-06) is present, then Weight (TD1-07) is required

If either Weight (TD1-07) or Unit or Basis for Measurement Code (TD1-08) is present, then the other is required

TD1-01 · 103 · Packaging Code · Optional · 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

Part 1/2

• CTN: Carton

Part 2/2

• 25: Corrugated or Solid

TD1-02 · 80 · Lading Quantity · Optional · Numeric (N0) · Min 1 Max 7

Number of units (pieces) of the lading commodity

TD1-06 · 187 · Weight Qualifier · Optional · Identifier (ID)

Code defining the type of weight

• G: Gross Weight

TD1-07 · 81 · Weight · Optional · Decimal number (R) · Min 1 Max 10

Numeric value of weight

TD1-08 · 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

• LB: Pound

1200 Detail > HL Loop > TD5

TD5 Carrier Details (Routing Sequence/Transit Time)

Required · Max use 12

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

If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required

TD5-01 · 133 · Routing Sequence Code · Optional · Identifier (ID)

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

• 1: 1st Carrier after Origin Carrier
• 2: 2nd Carrier after Origin Carrier
• 3: 3rd Carrier after Origin Carrier
• 4: 4th Carrier after Origin Carrier
• 5: 5th Carrier after Origin Carrier
• 6: 6th Carrier after Origin Carrier
• 7: 7th Carrier after Origin Carrier
• 8: 8th Carrier after Origin Carrier
• 9: 9th Carrier after Origin Carrier
• A: Origin Carrier, Agent's Routing (Rail)
• B: Origin/Delivery Carrier (Any Mode)
• O: Origin Carrier (Air, Motor, or Ocean)
• S: Origin Carrier, Shipper's Routing (Rail)

TD5-02 · 66 · Identification Code Qualifier · Optional · 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)
• 91: Assigned by Seller or Seller's Agent
• 92: Assigned by Buyer or Buyer's Agent

TD5-03 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 80

Code identifying a party or other code

1500 Detail > HL Loop > REF

REF Reference Information Bill of Lading

Optional · Max use >1

To specify identifying information

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 1 Max 50

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

2000 Detail > HL Loop > DTM

DTM Date/Time Reference Scheduled Delivery Date

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference Shipped Date

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

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

• 067: Current Schedule Delivery

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

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

2000 Detail > HL Loop > DTM

DTM Date/Time Reference Shipped Date

Optional · Max use 1

To specify pertinent dates and times

Variants (all may be used)

DTMDate/Time Reference Scheduled Delivery Date

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID)

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

• 011: Shipped

DTM-02 · 373 · Date · Required · Date (DT) · CCYYMMDD format

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

N1 Loop Ship From Required Max 1

Variants (all may be used)

N1 Loop Ship To

2200 Detail > HL Loop > N1 Loop Ship From > N1

N1 Party Identification

Required · Max use 1

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

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

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

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID) · Min 1 Max 2

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

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 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.

2400 Detail > HL Loop > N1 Loop Ship From > N3

N3 Party Location

Required · Max use 2

To specify the location of the named party

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

Address information

2500 Detail > HL Loop > N1 Loop Ship From > N4

N4 Geographic Location

Required · Max use 1

To specify the geographic place of the named party

N4-01 · 19 · City Name · Optional · String (AN) · Min 2 Max 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 · Optional · Identifier (ID) · Min 2 Max 2

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

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

N4-03 · 116 · Postal Code · Optional · Identifier (ID) · Min 3 Max 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 2 Max 3

Code identifying the country

N1 Loop Ship To Required Max 1

Variants (all may be used)

N1 Loop Ship From

2200 Detail > HL Loop > N1 Loop Ship To > N1

N1 Party Identification

Required · Max use 1

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

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

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

• ST: Ship To

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 60

Free-form name

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID) · Min 1 Max 2

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

N1-04 · 67 · Identification Code · Optional · String (AN) · Min 2 Max 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.

2400 Detail > HL Loop > N1 Loop Ship To > N3

N3 Party Location

Required · Max use 2

To specify the location of the named party

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

Address information

2500 Detail > HL Loop > N1 Loop Ship To > N4

N4 Geographic Location

Required · Max use 1

To specify the geographic place of the named party

N4-01 · 19 · City Name · Optional · String (AN) · Min 2 Max 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 · Optional · Identifier (ID) · Min 2 Max 2

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

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

N4-03 · 116 · Postal Code · Optional · Identifier (ID) · Min 3 Max 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 2 Max 3

Code identifying the country

HL Loop Required Max >1

0100 Detail > HL Loop > HL Loop > HL

HL Hierarchical Level

Required · Max 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.

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

• 1: Additional Subordinate HL Data Segment in This Hierarchical Structure.

0500 Detail > HL Loop > HL Loop > PRF

PRF Purchase Order Reference

Required · Max use 1

To provide reference to a specific purchase order

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

Identifying number for Purchase Order assigned by the orderer/purchaser

PRF-04 · 373 · Date · Optional · 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.

1500 Detail > HL Loop > HL Loop > REF

REF Reference Information Seller's Invoice Number

Optional · Max use 1

To specify identifying information

Usage notes

REF*IV – though optional now, this is your invoice number and will tie back to the future 810 document. It must be unique and may need to be all numeric.

Variants (all may be used)

REFReference Information Vendor Number

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

Code qualifying the Reference Identification

• IV: Seller's Invoice Number

REF-02 · 127 · Reference Identification · Required · String (AN) · Min 1 Max 50

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

1500 Detail > HL Loop > HL Loop > REF

REF Reference Information Vendor Number

Required · Max use 1

To specify identifying information

Usage notes

REF*IT – Your Buckle vendor number. Again necessary for receipts/invoices.

Variants (all may be used)

REFReference Information Seller's Invoice Number

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

Code qualifying the Reference Identification

• IT: Internal Customer Number

REF-02 · 127 · Reference Identification · Required · String (AN) · Min 1 Max 50

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

N1 Loop Buying Party Required Max >1

2200 Detail > HL Loop > HL Loop > N1 Loop Buying Party > N1

N1 Party Identification

Required · Max use 1

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

At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required

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

• BY: Buying Party (Purchaser)

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 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 2 Max 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.

HL Loop Required Max >1

0100 Detail > HL Loop > HL Loop > HL Loop > HL

HL Hierarchical Level

Required · Max 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.

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

1900 Detail > HL Loop > HL Loop > HL Loop > MAN

MAN Marks and Numbers Information

Required · Max use >1

To indicate identifying marks and numbers for shipping containers

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 1 Max 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.

Usage notes

MAN02 – This is a unique Carton ID number and cannot be duplicated for seven years. Sending duplicate Carton ID numbers can result in chargebacks per incorrect ID.

HL Loop Required Max >1

0100 Detail > HL Loop > HL Loop > HL Loop > HL Loop > HL

HL Hierarchical Level

Required · Max 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.

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

0200 Detail > HL Loop > HL Loop > HL Loop > HL Loop > LIN

LIN Item Identification

Required · Max use 1

To specify basic item identification data

LIN-01 · 350 · Assigned Identification · Optional · String (AN) · Min 1 Max 20

Alphanumeric characters assigned for differentiation within a transaction set

• LIN01 is the line item identification

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

LIN-03 · 234 · Product/Service ID · Required · String (AN) · Min 1 Max 48

Identifying number for a product or service

Usage notes

LIN03 – This must contain a UPC or a valid Buckle SKU. Sending invalid data here is a serious non-compliance issue.

0300 Detail > HL Loop > HL Loop > HL Loop > HL Loop > SN1

SN1 Item Detail (Shipment)

Required · Max use 1

To specify line-item detail relative to shipment

SN1-01 · 350 · Assigned Identification · Optional · String (AN) · Min 1 Max 20

Alphanumeric characters assigned for differentiation within a transaction set

• SN101 is the ship notice line-item identification.

SN1-02 · 382 · Number of Units Shipped · Required · Decimal number (R) · Min 1 Max 10

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

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

0700 Detail > HL Loop > HL Loop > HL Loop > HL Loop > PID

PID Product/Item Description

Required · Max use 200

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

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-02 · 750 · Product/Process Characteristic Code · Required · Identifier (ID)

Code identifying the general class of a product or process characteristic

• 08: Product

PID-05 · 352 · Description · Required · String (AN) · Min 1 Max 80

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

Summary

0100 Summary > CTT

CTT Transaction Totals

Required · Max 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.

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

Total number of line items in the transaction set

0200 Summary > SE

SE Transaction Set Trailer

Required · Max 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)

SE-01 · 96 · Number of Included Segments · Required · Numeric (N0) · Min 1 Max 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 4 Max 9

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

GE Functional Group Trailer

Required · Max use 1

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

GE-01 · 97 · Number of Transaction Sets Included · Required · Numeric (N0) · Min 1 Max 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 1 Max 9

Assigned number originated and maintained by the sender

IEA Interchange Control Trailer

Required · Max use 1

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

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

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

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

A control number assigned by the interchange sender

EDI Samples

Sample 856

ST*856*0164~
BSN*00*0000279186*20230328*1649*0001~
HL*1**S~
TD1*CTN*36****G*595.76*LB~
TD5*B*2*CGMC~
REF*BM*126868846~
DTM*011*20230328~
N1*ST*KEARNEY DC*92*900~
N3*2915 W 16TH STREET~
N4*KEARNEY*NE*68845~
N1*SF*TEST*91*81955~
N3*TEST~
N4*CITY OF INDUSTRY*CA*91789~
HL*2*1*O~
PRF*0999999***20221104~
REF*IV*10740246~
REF*IT*99999~
N1*BY**92*900~
HL*3*2*P~
MAN*GM*00001902310705833794~
HL*4*3*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*5*2*P~
MAN*GM*00001902310705833800~
HL*6*5*I~
LIN*0001*UP*111111111112~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*7*2*P~
MAN*GM*00001902310705833817~
HL*8*7*I~
LIN*0001*UP*111111111112~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*9*2*P~
MAN*GM*00001902310705833824~
HL*10*9*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*11*2*P~
MAN*GM*00001902310705833831~
HL*12*11*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*13*2*P~
MAN*GM*00001902310705833848~
HL*14*13*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*15*2*P~
MAN*GM*00001902310705833855~
HL*16*15*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*17*2*P~
MAN*GM*00001902310705833862~
HL*18*17*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*19*2*P~
MAN*GM*00001902310705833879~
HL*20*19*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*21*2*P~
MAN*GM*00001902310705833886~
HL*22*21*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*23*2*P~
MAN*GM*00001902310705833893~
HL*24*23*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*25*2*P~
MAN*GM*00001902310705833909~
HL*26*25*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*27*2*P~
MAN*GM*00001902310705833916~
HL*28*27*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*29*2*P~
MAN*GM*00001902310705833923~
HL*30*29*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*31*2*P~
MAN*GM*00001902310705833930~
HL*32*31*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*33*2*P~
MAN*GM*00001902310705833947~
HL*34*33*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*35*2*P~
MAN*GM*00001902310705833954~
HL*36*35*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*37*2*P~
MAN*GM*00001902310705833961~
HL*38*37*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*39*2*P~
MAN*GM*00001902310705833978~
HL*40*39*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*41*2*P~
MAN*GM*00001902310705833985~
HL*42*41*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*43*2*P~
MAN*GM*00001902310705833992~
HL*44*43*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*45*2*P~
MAN*GM*00001902310705834005~
HL*46*45*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*47*2*P~
MAN*GM*00001902310705834012~
HL*48*47*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*49*2*P~
MAN*GM*00001902310705834029~
HL*50*49*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
HL*51*2*P~
MAN*GM*00001902310705834036~
HL*52*51*I~
LIN*0001*UP*111111111111~
SN1**4*EA~
PID*F*08***GALLERIA STATUS SATC~
CTT*56~