Boscov's
/
Retail Ship Notice/Manifest (Pick & Pack)
  • Specification
  • EDI Inspector
Import guide into your account
Boscov's logo

X12 856 Retail Ship Notice/Manifest (Pick & Pack)

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information.

The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    https://www.stedi.com/app/guides/view/boscovs/retail-ship-noticemanifest-pick-pack/01HBREAG1RTZNTYYYTRH6MQTSW
    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
    HL Loop
    HL
    010
    Hierarchical Level
    Max use 1
    Required
    TD1
    110
    Carrier Details (Quantity and Weight)
    Max use 20
    Optional
    TD5
    120
    Carrier Details (Routing Sequence/Transit Time)
    Max use 12
    Optional
    TD3
    130
    Carrier Details (Equipment)
    Max use 12
    Optional
    REF
    150
    Bill of Lading Number
    Max use 1
    Optional
    REF
    150
    Carrier's Reference Number (PRO/Invoice)
    Max use 1
    Optional
    REF
    150
    Load Planning Number
    Max use 1
    Optional
    DTM
    200
    Current Schedule Delivery
    Max use 10
    Optional
    DTM
    200
    Shipped
    Max use 10
    Optional
    FOB
    210
    F.O.B. Related Instructions
    Max use 1
    Optional
    Ship From
    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

    Code to identify 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

    Code to identify 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

    Qualifier to designate 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

    Qualifier to designate 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
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

    U
    U.S. EDI Community of ASC X12, TDCC, and UCS
    ISA-12
    I11
    Interchange Control Version Number
    Required

    This version number covers the interchange control segments

    00401
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
    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 sent by the sender to request an interchange acknowledgment (TA1)

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

    Code to indicate 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

    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

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    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 used in conjunction with Data Element 480 to identify the issuer of the standard

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

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

    004010
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

    Heading

    ST
    010
    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

    Code uniquely identifying a Transaction Set

    • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
    856
    Ship Notice/Manifest
    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
    020
    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

    In some implementations, it may be appropriate to omit the unit load level and packaging levels, i.e., tare and pack, from the transaction set. Depending on the retailer's receiving systems, carton identification may not be required. Code 0004 in BSN05 indicates the use of a hierarchical structure that does not include a unit load level or any packaging levels.

    Example: BSN00007111200010310745*0001~

    Example
    BSN-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    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

    BSN-03
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BSN03 is the date the shipment transaction set is created.
    BSN-04
    337
    Time
    Required
    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
    Required

    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

    Pick and Pack Structure

    Heading end

    Detail

    HL Loop
    RequiredMax >1
    Usage notes

    The HL segment is used to identify levels of detail information using a hierarchical structure.

    HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

    HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

    Example: HL*1**S~

    HL
    010
    Detail > 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-03
    735
    Hierarchical Level Code
    Required

    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

    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
    110
    Detail > HL Loop > TD1

    Carrier Details (Quantity and Weight)

    OptionalMax use 20

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

    Usage notes

    This segment, at the shipment level, is used to specify total containers and gross weight of the shipment.

    Example: TD1CTN2524***G147*LB~

    Example
    TD1-01
    103
    Packaging Code
    Required
    String (AN)
    Min 3Max 5

    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

    First 3 characters:

    • BAG Bag
    • CTN Carton
    • MIX Mixed Container Types
      More than one type of container is included in a shipment (shipment could consist of 3 pieces that include 1 box, 1 crate, and 1 basket).
      Can be used only with code 71 in Part 2.
    • PLT Pallet
    • SLP Slip Sheet
      Shipping containers utilizing slip sheets, which are cardboard platforms used to hold product for storage or transportation.
    • SRW Shrink Wrap
      In packaging, a method of securing a unit load by placing a large "bag" of plastic film over the components and applying heat to induce shrinkage and cause the bag to tighten around the contents.

    Last 2 characters:

    • 01 Aluminum
    • 25 Corrugated or Solid
    • 31 Fiber
    • 58 Metal
    • 71 Not Otherwise Specified
    • 76 Paper
    • 79 Plastic
    • 91 Stainless Steel
      -94 Wood
    TD1-02
    80
    Lading Quantity
    Required
    Numeric (N0)
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    Usage notes

    The number of packages in the shipment as described in TD101.

    TD1-06
    187
    Weight Qualifier
    Required

    Code defining the type of weight

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

    Numeric value of weight

    TD1-08
    355
    Unit or Basis for Measurement Code
    Required

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

    Usage notes

    See Section III for code list.

    LB
    Pound
    TD5
    120
    Detail > HL Loop > 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

    This segment is used to specify every carrier in the routing sequence or a specific routing sequence that has been previously identified (usually from a routing guide). The segment can also be used to indicate estimated transit time in days. Only use TD501 if needed for clarity; this is not a requirement in most retail applications. When referring to a preestablished routing guide, use code 91 or 92 in TD502 and identify the routing sequence, from the routing guide, in TD503. To identify a specific private parcel service, TD502 will contain code 2 and TD503 will contain the corresponding SCAC. TD510 and TD511 are used to specify transit time.

    When using a small package service provider as the carrier, TD502 will contain code 2, TD503 will contain the carrier's SCAC, and TD504 will contain code U to inform the receiver of a small package service shipment.

    Example: TD5O2CENF**CC~

    Example
    TD5-01
    133
    Routing Sequence Code
    Required

    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

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

    Code identifying a party or other code

    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

    TD5-06
    368
    Shipment/Order Status Code
    Optional

    Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction

    BK
    Back Ordered from Previous Order
    BP
    Shipment Partial, Back Order to Ship on (Date)
    CC
    Shipment Complete on (Date)
    CM
    Shipment Complete with Additional Quantity
    CP
    Partial Shipment on (Date), Considered No Backorder
    CS
    Shipment Complete with Substitution
    DE
    Deleted Order
    IC
    Item Canceled
    IS
    Item Represents Substitution from Original Order
    PR
    Partial Shipment
    SS
    Split Shipment
    TD3
    130
    Detail > HL Loop > TD3

    Carrier Details (Equipment)

    OptionalMax use 12

    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.

    Example: TD3*TL**123456~

    Example
    TD3-01
    40
    Equipment Description Code
    Required

    Code identifying type of equipment used for shipment

    CV
    Closed Van
    FT
    Flat Bed Trailer
    RT
    Controlled Temperature Trailer (Reefer)
    TL
    Trailer (not otherwise specified)
    TD3-03
    207
    Equipment Number
    Required
    String (AN)
    Min 1Max 10

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

    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

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

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

    REF
    150
    Detail > HL Loop > REF

    Carrier's Reference Number (PRO/Invoice)

    OptionalMax use >1

    To specify identifying information

    Usage notes

    Example: REFCN13828700000A~

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    CN
    Carrier's Reference Number (PRO/Invoice)
    REF-02
    127
    Reference Identification
    Required
    String (AN)
    Min 1Max 30

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

    REF
    150
    Detail > HL Loop > REF

    Load Planning Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    Shipping Routing Request (SRR) is generated from Boscov’s TMS System to route all our inbound shipments.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    LO
    Load Planning Number
    REF-02
    127
    Reference Identification
    Required
    String (AN)
    Min 1Max 30

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

    DTM
    200
    Detail > HL Loop > DTM

    Current Schedule Delivery

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Example: DTM06720000202~

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

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

    067
    Current Schedule Delivery
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    DTM
    200
    Detail > HL Loop > DTM

    Shipped

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Example: DTM01120000202~

    Example
    Variants (all may be used)
    DTMCurrent Schedule Delivery
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    011
    Shipped
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    FOB
    210
    Detail > HL Loop > FOB

    F.O.B. Related Instructions

    OptionalMax use 1

    To specify transportation instructions relating to shipment

    Usage notes

    Example: FOB*PP~

    Example
    If Transportation Terms Qualifier Code (FOB-04) is present, then Transportation Terms Code (FOB-05) is required
    FOB-01
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    • FOB01 indicates which party will pay the carrier.
    CC
    Collect
    CF
    Collect, Freight Credited Back to Customer
    DF
    Defined by Buyer and Seller
    PC
    Prepaid but Charged to Customer
    PO
    Prepaid Only
    PP
    Prepaid (by Seller)
    TP
    Third Party Pay
    FOB-02
    309
    Location Qualifier
    Optional

    Code identifying type of location

    • FOB02 is the code specifying transportation responsibility location.
    OR
    Origin (Shipping Point)
    FOB-04
    334
    Transportation Terms Qualifier Code
    Optional

    Code identifying the source of the transportation terms

    01
    Incoterms

    See External Code Source 35 in Section III for the source reference document of INCOTERMS codes, which will appear in FOB05.

    FOB-05
    335
    Transportation Terms Code
    Optional
    Identifier (ID)
    Min 3Max 3

    Code identifying the trade terms which apply to the shipment transportation responsibility

    N1 Ship From
    OptionalMax >1
    Variants (all may be used)
    Ship To
    N1
    220
    Detail > HL Loop > Ship From > N1

    Name

    RequiredMax use 1

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

    Usage notes

    N103 and N104 are required except when N101 contains code MA or OB.

    When the ship to is the end consumer (customer of retailer), N103 and N104 are not required.;

    In some EDI implementations, it may be necessary to identify the sender and/or receiver of the transaction set within each transaction set. To identify the sender of the transaction set, N101 will contain code FR, N103 will contain code 93, and N104 will contain the actual identification number. To identify the receiver of the transaction set, N101 will contain code TO, N103 will contain code 94, and N104 will contain the actual identification number. These four codes may be used only in the combination listed above and may be used only to identify the sender and/or receiver of the transaction set.

    Example: N1SF**1123456789~

    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

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

    SF
    Ship From
    N1-02
    93
    Name
    Required
    String (AN)
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    1
    D-U-N-S Number, Dun & Bradstreet
    91
    Assigned by Seller or Seller'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.
    Usage notes

    This is the location code as defined by N103. The location code may be a formal number, e.g., DUNS, or it may be assigned by either the buyer or seller. The location refers to a store, warehouse, distribution center, plant, etc. Location codes are used to alleviate the need to send complete names and addresses.

    N3
    240
    Detail > HL Loop > Ship From > N3

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Usage notes

    Example: N3*100 MAIN ST~

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

    Address information

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

    Address information

    N4
    250
    Detail > HL Loop > Ship From > N4

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Usage notes

    N401 and N402 are required unless N405 and N406 are used.

    Example: N4SAN FRANCISCOCA*94111~

    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.
    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
    OptionalMax >1
    Variants (all may be used)
    Ship From
    N1
    220
    Detail > HL Loop > Ship To > N1

    Name

    RequiredMax use 1

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

    Usage notes

    N103 and N104 are required except when N101 contains code MA or OB.

    When the ship to is the end consumer (customer of retailer), N103 and N104 are not required.;

    In some EDI implementations, it may be necessary to identify the sender and/or receiver of the transaction set within each transaction set. To identify the sender of the transaction set, N101 will contain code FR, N103 will contain code 93, and N104 will contain the actual identification number. To identify the receiver of the transaction set, N101 will contain code TO, N103 will contain code 94, and N104 will contain the actual identification number. These four codes may be used only in the combination listed above and may be used only to identify the sender and/or receiver of the transaction set.

    Example: N1STBOSCOV9200015~

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    ST
    Ship To
    N1-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

    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 5Max 5

    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

    Boscov’s five digit store number (may have leading zeroes).

    N3
    240
    Detail > HL Loop > Ship To > N3

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    Usage notes

    Example: N3*100 MAIN ST~

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

    Address information

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

    Address information

    N4
    250
    Detail > HL Loop > Ship To > N4

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Usage notes

    N401 and N402 are required unless N405 and N406 are used.

    Example: N4SAN FRANCISCOCA*94111~

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

    The HL segment is used to identify levels of detail information using a hierarchical structure.

    HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

    HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

    Example: HL21*O~

    HL
    010
    Detail > HL Loop > 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

    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

    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
    050
    Detail > HL Loop > HL Loop > PRF

    Purchase Order Reference

    OptionalMax use 1

    To provide reference to a specific purchase order

    Usage notes

    Example: PRF835490**20000114~

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

    Identifying number for Purchase Order assigned by the orderer/purchaser

    Usage notes

    Boscov's 6-digit purchase order number (may use leading zeros).

    PRF-04
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • PRF04 is the date assigned by the purchaser to purchase order.
    Usage notes

    Retailer's original purchase order date.

    REF
    150
    Detail > HL Loop > HL Loop > REF

    Department Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    Example: REFDP00131~

    Example
    Variants (all may be used)
    REFSeller's Invoice Number
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    DP
    Department Number
    REF-02
    127
    Reference Identification
    Required
    String (AN)
    Min 5Max 5

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

    Usage notes

    Boscov’s 5 digit Department Number (must use leading zeroes).

    REF
    150
    Detail > HL Loop > HL Loop > REF

    Seller's Invoice Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    Example: REFIV807764626~

    Example
    Variants (all may be used)
    REFDepartment Number
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    IV
    Seller's Invoice Number
    REF-02
    127
    Reference Identification
    Required
    String (AN)
    Min 1Max 30

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

    N1 Loop
    OptionalMax >1
    N1
    220
    Detail > HL Loop > HL Loop > N1 Loop > N1

    Name

    RequiredMax use 1

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

    Usage notes

    There will be at least one occurrence, of this segment, to identify the buying party by using code BY in N101.

    N103 and N104 are required except when N101 contains code CT, MA or OB.

    Example: N1BY**9200014~

    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    BY
    Buying Party (Purchaser)
    N1-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Required

    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

    Boscov’s five digit store # (must use leading zeroes).

    N1 Loop end
    HL Pack
    OptionalMax >1
    Usage notes

    The HL segment is used to identify levels of detail information using a hierarchical structure.

    HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

    HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

    Example: HL43*P~

    Variants (all may be used)
    Shipping Tare
    HL
    010
    Detail > HL Loop > HL Loop > 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

    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

    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
    190
    Detail > HL Loop > HL Loop > Pack > MAN

    Marks and Numbers

    OptionalMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    When the shipping container is the same as the consumer unit, the U.P.C. may be the only UCC 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.

    Example: MANGM00007000320000113906~

    Example
    MAN-01
    88
    Marks and Numbers Qualifier
    Required

    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
    SSCC-18 and Application Identifier

    This is a twenty-character UCC/EAN-128 Serial
    Shipping Container Code (SSCC-18) that includes the two digit application identifier. The symbology code and the modulo 103 check digit are not included.

    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 Loop
    RequiredMax >1
    Usage notes

    The HL segment is used to identify levels of detail information using a hierarchical structure.

    HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

    HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

    Example: HL54*I~

    HL
    010
    Detail > HL Loop > HL Loop > 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

    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

    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
    020
    Detail > HL Loop > HL Loop > Pack > HL Loop > LIN

    Item Identification

    OptionalMax use 1

    To specify basic item identification data

    Usage notes

    The codes listed for LIN02 apply to every occurrence of Data Element 235 in the LIN segment.

    See Section III for complete U.P.C. and EAN code definitions.

    Example: LIN*UP700032591261VA20191~

    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-02
    235
    Product/Service ID Qualifier
    Required

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

    • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    EN
    European Article Number (EAN) (2-5-5-1)
    SZ
    Vendor Alphanumeric Size Code (NRMA)

    This is the code assigned by the vendor.

    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VA
    Vendor's Style Number
    VE
    Vendor Color
    LIN-03
    234
    Product/Service ID
    Required
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    EN
    European Article Number (EAN) (2-5-5-1)
    SZ
    Vendor Alphanumeric Size Code (NRMA)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VA
    Vendor's Style Number
    VE
    Vendor Color
    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

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

    EN
    European Article Number (EAN) (2-5-5-1)
    SZ
    Vendor Alphanumeric Size Code (NRMA)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VA
    Vendor's Style Number
    VE
    Vendor Color
    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

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

    EN
    European Article Number (EAN) (2-5-5-1)
    SZ
    Vendor Alphanumeric Size Code (NRMA)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VA
    Vendor's Style Number
    VE
    Vendor Color
    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

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

    EN
    European Article Number (EAN) (2-5-5-1)
    SZ
    Vendor Alphanumeric Size Code (NRMA)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VA
    Vendor's Style Number
    VE
    Vendor Color
    LIN-11
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    SN1
    030
    Detail > HL Loop > HL Loop > Pack > HL Loop > SN1

    Item Detail (Shipment)

    OptionalMax use 1

    To specify line-item detail relative to shipment

    Usage notes

    This segment is used to specify the quantities associated with the item identified in the LIN at the item level.

    When specifying an item, which is comprised of two or more components that are in unique shipping containers, SN103 will contain code ST for set and the quantity specified in SN102 is the number of sets as identified in the LIN segment. Each different component is identified in one pack level. See the VICS Note, on the SLN segment, at the pack level.

    Example: SN1*1EA~

    Example
    SN1-01
    350
    Assigned Identification
    Optional
    String (AN)
    Min 1Max 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 1Max 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

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

    See Section III for code list.

    CA
    Case
    DZ
    Dozen
    EA
    Each
    PK
    Package
    PR
    Pair
    HL Loop end
    HL Pack end
    HL Shipping Tare
    OptionalMax >1
    Usage notes

    The HL segment is used to identify levels of detail information using a hierarchical structure.

    HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

    HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

    Example: HL32*T~

    Variants (all may be used)
    Pack
    HL
    010
    Detail > HL Loop > HL Loop > 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

    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

    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.
    TSD
    145
    Detail > HL Loop > HL Loop > Shipping Tare > TSD

    Trailer Shipment Details

    OptionalMax use 1

    To specify details of shipments on a trailer

    Usage notes

    This segment may be used to indicate the location of the pallet within the trailer/container.

    Example: TSD0011

    Example
    TSD-01
    350
    Assigned Identification
    Optional
    String (AN)
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • TSD01 indicates the loading sequence and relative shipment position on the trailer.
    Usage notes

    Indicates the loading sequence.

    TSD-02
    219
    Position
    Required

    Relative position of shipment in car, trailer, or container (mutually defined)

    1
    First quarter of the trailer/container
    2
    Second quarter of the trailer/container
    3
    Third quarter of the trailer/container
    4
    Fourth quarter of the trailer/container
    MAN
    190
    Detail > HL Loop > HL Loop > Shipping Tare > MAN

    Marks and Numbers

    OptionalMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    This segment, at the tare level, is used to specify the identification numbers for the pallet.;

    Example: MANGM00107000320000113901~

    Example
    MAN-01
    88
    Marks and Numbers Qualifier
    Required

    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
    SSCC-18 and Application Identifier

    This is a twenty-character UCC/EAN-128 Serial
    Shipping Container Code (SSCC-18) that includes the two digit application identifier. The symbology code and the modulo 103 check digit are not included.

    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.
    PAL
    215
    Detail > HL Loop > HL Loop > Shipping Tare > PAL

    Pallet Information

    OptionalMax use 1

    To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet

    Usage notes

    Example: PAL44936

    Example
    PAL-01
    883
    Pallet Type Code
    Required

    Code indicating the type of pallet

    4
    Standard
    PAL-02
    884
    Pallet Tiers
    Optional
    Numeric (N0)
    Min 1Max 3

    The number of layers per pallet

    PAL-03
    885
    Pallet Blocks
    Optional
    Numeric (N0)
    Min 1Max 3

    The number of pieces (cartons) per layer on the pallet

    PAL-04
    356
    Pack
    Required
    Numeric (N0)
    Min 1Max 6

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

    • PAL04 (Pack) is the number of pieces on the pallet.
    Usage notes

    Number of cartons on pallet.

    HL Loop
    RequiredMax >1
    Usage notes

    The HL segment is used to identify levels of detail information using a hierarchical structure.

    HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

    HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

    Example: HL43*P~

    HL
    010
    Detail > HL Loop > HL Loop > Shipping Tare > 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

    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

    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
    190
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > MAN

    Marks and Numbers

    OptionalMax use >1

    To indicate identifying marks and numbers for shipping containers

    Usage notes

    When the shipping container is the same as the consumer unit, the U.P.C. may be the only UCC 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.

    Example: MANGM00007000320000113906~

    Example
    MAN-01
    88
    Marks and Numbers Qualifier
    Required

    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
    SSCC-18 and Application Identifier

    This is a twenty-character UCC/EAN-128 Serial
    Shipping Container Code (SSCC-18) that includes the two digit application identifier. The symbology code and the modulo 103 check digit are not included.

    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 Loop
    RequiredMax >1
    Usage notes

    The HL segment is used to identify levels of detail information using a hierarchical structure.

    HL01 shall contain a unique number for each occurrence of the HL segment within the transaction set. The value assigned to the first HL segment will be 1, and is incremented by one for each subsequent HL segment within the transaction set.

    HL02 identifies the hierarchical ID of the HL segment to which it is subordinate (child of). HL02 will be omitted for the first occurrence of the HL segment in the transaction set, since it has no parent. HL03 identifies the application content of the series of segments following the current HL segment up to the next occurrence of an HL segment, or the CTT or SE segment, e.g., Shipment, Unit Load, Order, Tare, Pack and Item.

    Example: HL54*I~

    HL
    010
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > 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

    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

    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
    020
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > HL Loop > LIN

    Item Identification

    OptionalMax use 1

    To specify basic item identification data

    Usage notes

    The codes listed for LIN02 apply to every occurrence of Data Element 235 in the LIN segment.

    See Section III for complete U.P.C. and EAN code definitions.

    Example: LIN*UP700032591261VA20191~

    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-02
    235
    Product/Service ID Qualifier
    Required

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

    • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    EN
    European Article Number (EAN) (2-5-5-1)
    SZ
    Vendor Alphanumeric Size Code (NRMA)

    This is the code assigned by the vendor.

    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VA
    Vendor's Style Number
    VE
    Vendor Color
    LIN-03
    234
    Product/Service ID
    Required
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    EN
    European Article Number (EAN) (2-5-5-1)
    SZ
    Vendor Alphanumeric Size Code (NRMA)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VA
    Vendor's Style Number
    VE
    Vendor Color
    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

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

    EN
    European Article Number (EAN) (2-5-5-1)
    SZ
    Vendor Alphanumeric Size Code (NRMA)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VA
    Vendor's Style Number
    VE
    Vendor Color
    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

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

    EN
    European Article Number (EAN) (2-5-5-1)
    SZ
    Vendor Alphanumeric Size Code (NRMA)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VA
    Vendor's Style Number
    VE
    Vendor Color
    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

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

    EN
    European Article Number (EAN) (2-5-5-1)
    SZ
    Vendor Alphanumeric Size Code (NRMA)
    UP
    U.P.C. Consumer Package Code (1-5-5-1)
    VA
    Vendor's Style Number
    VE
    Vendor Color
    LIN-11
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    SN1
    030
    Detail > HL Loop > HL Loop > Shipping Tare > HL Loop > HL Loop > SN1

    Item Detail (Shipment)

    OptionalMax use 1

    To specify line-item detail relative to shipment

    Usage notes

    This segment is used to specify the quantities associated with the item identified in the LIN at the item level.

    When specifying an item, which is comprised of two or more components that are in unique shipping containers, SN103 will contain code ST for set and the quantity specified in SN102 is the number of sets as identified in the LIN segment. Each different component is identified in one pack level. See the VICS Note, on the SLN segment, at the pack level.

    Example: SN1*1EA~

    Example
    SN1-01
    350
    Assigned Identification
    Optional
    String (AN)
    Min 1Max 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 1Max 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

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

    See Section III for code list.

    CA
    Case
    DZ
    Dozen
    EA
    Each
    PK
    Package
    PR
    Pair
    HL Loop end
    HL Loop end
    HL Shipping Tare end
    HL Loop end
    HL Loop end
    Detail end

    Summary

    CTT
    010
    Summary > CTT

    Transaction Totals

    OptionalMax 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*9~

    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

    The number of HL segments present in the transaction set.

    SE
    020
    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

    Sample 1

    ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231002*1457*U*00401*000000001*0*T*>~
    GS*SH*SENDERGS*RECEIVERGS*20231002*145758*000000001*X*004010~
    ST*856*856000706~
    BSN*00*007111*20001031*0745*0001~
    HL*1**S~
    TD1*BAG*7****G*147*LB~
    TD5*O*2*CENF~
    TD3*TL**123456~
    REF*BM*13828700000A~
    REF*LO*123456~
    DTM*011*20000202~
    DTM*067*20000202~
    FOB*PP~
    N1*ST*BOSCOV*92*00015~
    HL*2*1*O~
    PRF*835490***20000114~
    REF*DP*00482~
    REF*IV*807764626~
    N1*BY**92*00014~
    HL*3*2*T~
    TSD*001*1~
    MAN*GM*00107000320000113901~
    PAL*4*4*9*36~
    HL*4*3*P~
    MAN*GM*00007000320000113906~
    HL*5*4*I~
    LIN**UP*700032591261*VA*20191~
    SN1**1*EA~
    HL*6*2*T~
    MAN*GM*00107000320000113831~
    HL*7*6*P~
    MAN*GM*00007000320000113838~
    HL*8*7*I~
    LIN**UP*700032591285*VA*20195~
    SN1**2*EA~
    HL*9*7*I~
    LIN**UP*700032591339*VA*20205~
    SN1**1*EA~
    CTT*9~
    SE*38*856000706~
    GE*1*000000001~
    IEA*1*000000001~

    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.