Flexport
/
Ship Notice/Manifest (Shipper)
  • Specification
  • EDI Inspector
Import guide into your account
Flexport logo

X12 856 Ship Notice/Manifest (Shipper)

X12 Release 4010
Flexport Docs

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 samples
    View the latest version of this implementation guide as an interactive webpage
    https://www.stedi.com/app/guides/view/flexport/ship-noticemanifest-shipper/01GGBHN31KPWRZPWFEMA7T2YK2
    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 Shipment
    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
    Reference Identification
    Max use 1
    Optional
    V1 Loop
    DTM
    200
    Date/Time Reference
    Max use 10
    Optional
    FOB
    210
    F.O.B. Related Instructions
    Max use 1
    Optional
    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

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

    ZZ
    Mutually Defined
    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

    FLEXPORTEDI(Prod) / FLEXPORTEDIQA(Test)

    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

    FLEXPORTEDI(Prod) / FLEXPORTEDIQA(Test)

    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

    Example
    BSN-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    04
    Change
    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
    Notes: Flexport Standard = FLEX-ID formarted as FLEX-#####

    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
    Optional

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

    0004
    Shipment, Order, Item
    Heading end

    Detail

    HL Loop Shipment
    RequiredMax >1
    HL
    010
    Detail > HL Loop Shipment > HL

    Hierarchical Level

    RequiredMax use 1

    To identify dependencies among and the content of hierarchically related groups of data segments

    • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    String (AN)
    Min 1Max 12

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

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

    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 Shipment > TD1

    Carrier Details (Quantity and Weight)

    OptionalMax use 20

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

    Example
    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
    If either Volume (TD1-09) or Unit or Basis for Measurement Code (TD1-10) is present, then the other is required
    TD1-01
    103
    Packaging Code
    Optional

    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

    BAG
    Bag
    BAL
    Bale
    BBL
    Barrel
    BDL
    Bundle
    BLK
    Bulk
    BOX
    Box
    CRT
    Crate
    CTN
    Carton
    DRM
    Drum
    PKG
    Package
    PLT
    Pallet
    ROL
    Roll
    SKD
    Skid
    TD1-02
    80
    Lading Quantity
    Optional
    Numeric (N0)
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    TD1-06
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

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

    Numeric value of weight

    TD1-08
    355
    Unit or Basis for Measurement Code
    Optional

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

    KG
    Kilogram
    LB
    Pound
    TD1-09
    183
    Volume
    Optional
    Decimal number (R)
    Min 1Max 8

    Value of volumetric measure

    TD1-10
    355
    Unit or Basis for Measurement Code
    Optional

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

    CF
    Cubic Feet
    CR
    Cubic Meter
    TD5
    120
    Detail > HL Loop Shipment > TD5

    Carrier Details (Routing Sequence/Transit Time)

    OptionalMax use 12

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

    Example
    If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
    TD5-01
    133
    Routing Sequence Code
    Optional

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

    Notes: Flexport Standard = main freight carrier (carrier on leg departing from port of loading)

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

    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
    Optional
    String (AN)
    Min 2Max 80

    Code identifying a party or other code

    TD5-04
    91
    Transportation Method/Type Code
    Optional

    Code specifying the method or type of transportation for the shipment

    A
    Air
    S
    Ocean
    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

    CC
    Shipment Complete on (Date)
    TD5-09
    731
    Transit Direction Code
    Optional

    The point of origin and point of direction

    SB
    Seller to Buyer
    TD3
    130
    Detail > HL Loop Shipment > TD3

    Carrier Details (Equipment)

    OptionalMax use 12

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

    Example
    If Equipment Initial (TD3-02) is present, then Equipment Number (TD3-03) is required
    TD3-01
    40
    Equipment Description Code
    Optional

    Code identifying type of equipment used for shipment

    AF
    Air Freight (Break Bulk)
    CN
    Container
    TD3-02
    206
    Equipment Initial
    Optional
    String (AN)
    Min 1Max 4

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

    TD3-03
    207
    Equipment Number
    Optional
    String (AN)
    Min 1Max 11

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

    TD3-09
    225
    Seal Number
    Optional
    String (AN)
    Min 2Max 15

    Unique number on seal used to close a shipment

    TD3-10
    24
    Equipment Type
    Optional
    Identifier (ID)
    Min 4Max 4

    Code identifying equipment type

    REF
    150
    Detail > HL Loop Shipment > REF

    Reference Identification

    OptionalMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    AW
    Air Waybill Number
    BM
    Bill of Lading Number
    BN
    Booking Number
    MA
    Ship Notice/Manifest Number
    MB
    Master Bill of Lading
    RE
    Release Number
    SN
    Seal Number
    REF-02
    127
    Reference Identification
    Optional
    String (AN)
    Min 1Max 30

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

    V1 Loop
    OptionalMax >1
    V1
    180
    Detail > HL Loop Shipment > V1 Loop > V1

    Vessel Identification

    RequiredMax use 1

    To provide vessel details and voyage number

    Example
    V1-02
    182
    Vessel Name
    Required
    String (AN)
    Min 2Max 28

    Name of ship as documented in "Lloyd's Register of Ships"

    V1-04
    55
    Flight/Voyage Number
    Required
    String (AN)
    Min 2Max 10

    Identifying designator for the particular flight or voyage on which the cargo travels

    V1-09
    91
    Transportation Method/Type Code
    Optional

    Code specifying the method or type of transportation for the shipment

    10
    LCL VES NON-CON
    11
    FULL CTNR LOAD
    R4
    370
    Detail > HL Loop Shipment > V1 Loop > R4

    Port or Terminal

    OptionalMax use >1

    Contractual or operational port or point relevant to the movement of the cargo
    R4 is required for each port to be identified.

    Example
    If either Location Qualifier (R4-02) or Location Identifier (R4-03) is present, then the other is required
    R4-01
    115
    Port or Terminal Function Code
    Required

    Code defining function performed at the port or terminal with respect to a shipment

    D
    Port of Discharge (Operational)
    L
    Port of Loading (Operational)
    R4-02
    309
    Location Qualifier
    Optional
    Identifier (ID)
    Min 1Max 2

    Code identifying type of location

    R4-03
    310
    Location Identifier
    Optional
    String (AN)
    Min 1Max 30

    Code which identifies a specific location

    R4-04
    114
    Port Name
    Optional
    String (AN)
    Min 2Max 24

    Free-form name for the place at which an offshore carrier originates or terminates (by transshipment or otherwise) its actual ocean carriage of property

    R4-05
    26
    Country Code
    Optional
    Identifier (ID)
    Min 2Max 3

    Code identifying the country

    V1 Loop end
    DTM
    200
    Detail > HL Loop Shipment > DTM

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

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

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

    011
    Shipped
    017
    Estimated Delivery
    274
    Requested Departure Date
    AA1
    Estimated Point of Arrival
    DTM-02
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    DTM-03
    337
    Time
    Optional
    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)

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

    Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow

    FOB
    210
    Detail > HL Loop Shipment > FOB

    F.O.B. Related Instructions

    OptionalMax use 1

    To specify transportation instructions relating to shipment

    Example
    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
    N1 Loop
    OptionalMax 200
    N1
    220
    Detail > HL Loop Shipment > N1 Loop > N1

    Name

    RequiredMax use 1

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

    Example
    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

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

    CN
    Consignee
    SF
    Ship From
    ST
    Ship To
    SU
    Supplier/Manufacturer
    N1-02
    93
    Name
    Optional
    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)

    9
    D-U-N-S+4, D-U-N-S Number with Four Character Suffix
    US
    Unique Supplier Identification Number (USIN)
    ZZ
    Mutually Defined
    N1-04
    67
    Identification Code
    Optional
    String (AN)
    Min 2Max 80

    Code identifying a party or other code

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

    Address Information

    OptionalMax use 2

    To specify the location of the named party

    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 Shipment > N1 Loop > N4

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    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
    Optional
    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
    Optional
    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 Loop end
    HL Loop Order
    RequiredMax >1
    HL
    010
    Detail > HL Loop Shipment > HL Loop Order > HL

    Hierarchical Level

    RequiredMax use 1

    To identify dependencies among and the content of hierarchically related groups of data segments

    • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    String (AN)
    Min 1Max 12

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

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

    Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

    • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
    HL-03
    735
    Hierarchical Level Code
    Required

    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.
    1
    Additional Subordinate HL Data Segment in This Hierarchical Structure.
    PRF
    050
    Detail > HL Loop Shipment > HL Loop Order > PRF

    Purchase Order Reference

    OptionalMax use 1

    To provide reference to a specific purchase order

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

    Identifying number for Purchase Order assigned by the orderer/purchaser

    HL Loop Item
    RequiredMax >1
    HL
    010
    Detail > HL Loop Shipment > HL Loop Order > HL Loop Item > HL

    Hierarchical Level

    RequiredMax use 1

    To identify dependencies among and the content of hierarchically related groups of data segments

    • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
    Example
    HL-01
    628
    Hierarchical ID Number
    Required
    String (AN)
    Min 1Max 12

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

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

    Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

    • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
    HL-03
    735
    Hierarchical Level Code
    Required

    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 Shipment > HL Loop Order > HL Loop Item > LIN

    Item Identification

    OptionalMax use 1

    To specify basic item identification data

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

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    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.
    VP
    Vendor's (Seller's) Part Number
    LIN-03
    234
    Product/Service ID
    Required
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    BP
    Buyer's Part Number
    LIN-05
    234
    Product/Service ID
    Optional
    String (AN)
    Min 1Max 48

    Identifying number for a product or service

    SN1
    030
    Detail > HL Loop Shipment > HL Loop Order > HL Loop Item > SN1

    Item Detail (Shipment)

    OptionalMax use 1

    To specify line-item detail relative to shipment

    Example
    If either Quantity Ordered (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required
    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.
    EA
    Each
    SN1-05
    330
    Quantity Ordered
    Optional
    Decimal number (R)
    Min 1Max 15

    Quantity ordered

    SN1-06
    355
    Unit or Basis for Measurement Code
    Optional

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

    EA
    Each
    PID
    070
    Detail > HL Loop Shipment > HL Loop Order > HL Loop Item > PID

    Product/Item Description

    OptionalMax use 200

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

    Example
    If Product Description Code (PID-04) is present, then Agency Qualifier Code (PID-03) is required
    At least one of Product Description Code (PID-04) or Description (PID-05) is required
    PID-01
    349
    Item Description Type
    Required

    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
    Optional

    Code identifying the general class of a product or process characteristic

    ZZ
    Mutually Defined
    PID-03
    559
    Agency Qualifier Code
    Optional

    Code identifying the agency assigning the code values

    • Use PID03 to indicate the organization that publishes the code list being referred to.
    ZZ
    Mutually Defined
    PID-04
    751
    Product Description Code
    Optional
    String (AN)
    Min 1Max 12

    A code from an industry code list which provides specific data about a product characteristic

    • PID04 should be used for industry-specific product description codes.
      PID04 = US Tariff Number when PID03 = ZZ
    PID-05
    352
    Description
    Optional
    String (AN)
    Min 1Max 80

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

    HL Loop Item end
    HL Loop Order end
    HL Loop Shipment 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.
    Example
    CTT-01
    354
    Number of Line Items
    Required
    Numeric (N0)
    Min 1Max 6

    Total number of line items in the transaction set

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

    Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

    ## Example:
    -.0018 First occurrence of value being hashed.
    .18 Second occurrence of value being hashed.
    1.8 Third occurrence of value being hashed.
    18.01 Fourth occurrence of value being hashed.

    1855 Hash total prior to truncation.
    855 Hash total after truncation to three-digit field.

    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

    By Container, Multiple POs

    ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231101*0102*U*00401*000000001*0*T*>~
    GS*SH*SENDERGS*RECEIVERGS*20231101*010231*000000001*X*004010~
    ST*856*0002~
    BSN*00*FLEX-555107*20190816*0136*0004~
    HL*1**S~
    TD1*PKG*18****G*35699.4*LB*18.5*CR~
    TD5*O*2*EGLV*S**CC***SB~
    TD3*CN**TEMU416058~
    REF*BM*EGLV143982064624~
    DTM*011*20190801*0400~
    DTM*017*20190902*1700~
    FOB*CC~
    N1*SF*SUPPLIER23 LTD*US*0001~
    N3*#1 QUIHA ROAD~
    N4*HAINING CITY*33*314422*CN~
    N1*ST*DISTRIBUTION*9*0754585215403~
    N3*600 LAS SPECIAL BLVD E*SUITE 400~
    N4*LOS ANGELES*TX*75039-5616*US~
    HL*2*1*O~
    PRF*9299445~
    HL*3*2*I~
    LIN*1*VP*B-4707Q*BP*Q2~
    SN1**1008*EA**11760*EA~
    PID*F****4707Q NEW STEEL SHOE~
    HL*4*1*O~
    PRF*9247816~
    HL*5*4*I~
    LIN*2*VP*B-4711Q*BP*B2~
    SN1**1512*EA**2000*EA~
    PID*F****4711Q NEW STEEL SHOE~
    CTT*5~
    SE*30*0002~
    GE*1*000000001~
    IEA*1*000000001~

    By Container, One PO

    ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231101*0104*U*00401*000000001*0*T*>~
    GS*SH*SENDERGS*RECEIVERGS*20231101*010451*000000001*X*004010~
    ST*856*0001~
    BSN*00*FLEX-555181*20190817*0227*0004~
    HL*1**S~
    TD1*PKG*24****G*37831.3*LB*9.5*CR~
    TD5*O*2*ONEY*S**CC***SB~
    TD3*CN**TCNU8408606******TW167378B*42G0~
    REF*BM*ONEYNK8GL4635600~
    DTM*011*20190801*0400~
    DTM*017*20190917*1600~
    FOB*CC~
    N1*SF*SUPPLIER1., LTD*US*0001~
    N3*PARK DISTRICT*SUITE 300~
    N4*NANJING*32**CN~
    N1*ST*DISTRIBUTION*9*0354585215427~
    N3*600 LAS COLINAS BLVD E*SUITE 400~
    N4*LOS ANGELES*CA*75039-5616*US~
    HL*2*1*O~
    PRF*694832~
    HL*3*2*I~
    LIN*1*VP*ITEM1*BP*SAMPLE1~
    SN1**250*EA**250*EA~
    PID*F*ZZ***HARDWARE KIT~
    HL*4*2*I~
    LIN*2*VP*OTR4515QHD*BP*SAMPLE2~
    SN1**6250*EA**6250*EA~
    PID*F****Q HARDWARE BRAKE KIT W/HD SPRING~
    HL*5*2*I~
    LIN*3*VP*OTR4515X*BP*SAMPLE3~
    SN1**500*EA**500*EA~
    PID*F****16.5 FRUEHAUF X3 HARDWARE KIT~
    HL*6*2*I~
    LIN*4*VP*OTR4524QM*BP*SAMPLE4~
    SN1**500*EA**500*EA~
    PID*F****MACK HARDWARE KIT W/OFFSET SPRING~
    HL*7*2*I~
    LIN*5*VP*OTR4702*BP*SAMPLE5~
    SN1**500*EA**500*EA~
    PID*F****15X4 Q-PLUS FRONT HARDWARE KIT~
    CTT*5~
    SE*40*0001~
    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.