3M
/
Ship Notice
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from 3M. Contact 3M for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
3M logo

X12 856 Ship Notice

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
    Powered by
    Build free 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
    Required
    TD3
    130
    Carrier Details (Equipment)
    Max use 12
    Required
    REF
    150
    Reference Identification
    Max use 1
    Required
    DTM
    200
    Date/Time Reference
    Max use 10
    Required
    FOB
    210
    F.O.B. Related Instructions
    Max use 1
    Required
    N1 Loop
    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
    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
    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
    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
    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
    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
    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
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    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
    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
    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
    Min 2Max 15

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

    GS-03
    124
    Application Receiver's Code
    Required
    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
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    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

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

    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
    BSN-02
    396
    Shipment Identification
    Required
    Min 2Max 30

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

    Usage notes

    3M allows for 16 character shipment number. If shipment number sent is
    longer, 3M will use the first 16 characters

    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.
    DTM
    040

    Date/Time Reference

    RequiredMax use 10

    To specify pertinent dates and times

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    Usage notes

    Date material is expected to be delivered at 3M
    destination.

    002
    Delivery Requested
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Detail

    HL Loop
    RequiredMax 200000
    HL
    010

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

    Carrier Details (Quantity and Weight)

    RequiredMax use 20

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

    Example
    TD1-01
    103
    Packaging Code
    Required

    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

    CTN
    Carton
    MIX
    Mixed Container Types
    PKG
    Package
    PLT
    Pallet
    TD1-02
    80
    Lading Quantity
    Required
    Min 1Max 5

    Number of units (pieces) of the lading commodity

    Usage notes

    3M restricts length of this field to 5 digits.
    Number of packages.

    TD3
    130

    Carrier Details (Equipment)

    RequiredMax use 12

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

    Example
    TD3-01
    40
    Equipment Description Code
    Required

    Code identifying type of equipment used for shipment

    2B
    20 ft. IL Container (Closed Top)
    4B
    40 ft. IL Container (Closed Top)
    AF
    Air Freight (Break Bulk)
    FT
    Flat Bed Trailer
    TA
    Trailer, Heated/Insulated/Ventilated
    TF
    Trailer, Dry Freight
    TN
    Tank Car
    TV
    Truck, Van
    TW
    Trailer, Refrigerated
    TD3-03
    207
    Equipment Number
    Required
    Min 1Max 10

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

    Usage notes

    If equipment number exceeds 10 characters, please send in Shipment level REF
    segment with REF01 = EQ

    REF
    150

    Reference Identification

    RequiredMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    Required by 3M.
    Bill of Lading cannot have any special characters.
    If there isn't a Bill of Lading Number, for the freight types
    below use the following information as Bill of Lading:
    Small Parcel –tracking number
    Full Truckload –trailer and seal number
    Less-than-Truckload –pro number
    Ocean –container number
    Air –airway bill

    Use EQ: Use only if the equipment number exceeds the 10
    characters allowed in the TD303.

    BM
    Bill of Lading Number
    EQ
    Equipment Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    DTM
    200

    Date/Time Reference

    RequiredMax use 10

    To specify pertinent dates and times

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    Usage notes

    Represents the Vendor's best estimate of the delivery
    date to 3M warehouse/location.

    017
    Estimated Delivery
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    FOB
    210

    F.O.B. Related Instructions

    RequiredMax use 1

    To specify transportation instructions relating to shipment

    Example
    If Description (FOB-03) is present, then Location Qualifier (FOB-02) is required
    If Description (FOB-07) is present, then Location Qualifier (FOB-06) is required
    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
    PP
    Prepaid (by Seller)
    FOB-02
    309
    Location Qualifier
    Optional

    Code identifying type of location

    • FOB02 is the code specifying transportation responsibility location.
    DE
    Destination (Shipping)
    FV
    Free Alongside Vessel (Free On Board [F.O.B.] Point)
    OR
    Origin (Shipping Point)
    OV
    On Vessel (Free On Board [FOB] point)
    PB
    Port of Discharge
    PD
    Place of Delivery
    ZZ
    Mutually Defined
    FOB-03
    352
    Description
    Optional
    Min 1Max 80

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

    FOB-04
    334
    Transportation Terms Qualifier Code
    Optional

    Code identifying the source of the transportation terms

    01
    Incoterms
    FOB-05
    335
    Transportation Terms Code
    Optional

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

    Usage notes

    Used if the incoterms code is DAP or DAT. These
    incoterms codes were added in 2010 and are not
    available in the ANSI 004010 standard. The incoterms
    codes "DAP" or "DAT" is sent in the FOB07

    CFR
    Cost and Freight
    CIF
    Cost, Insurance, and Freight
    CIP
    Carriage and Insurance Paid To
    CPT
    Carriage Paid To
    DDP
    Delivered Duty Paid
    EXW
    Ex Works
    FAS
    Free Alongside Ship
    FCA
    Free Carrier
    FOB
    Free on Board
    ZZZ
    Mutually Defined
    FOB-06
    309
    Location Qualifier
    Optional

    Code identifying type of location

    • FOB06 is the code specifying the title passage location.
    ZZ
    Mutually Defined
    FOB-07
    352
    Description
    Optional
    Min 1Max 80

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

    Usage notes

    This field will only be populated if the incoterms code = "DAP" or "DAT".
    These incoterms codes were added in 2010 and are not available in the ANSI
    004010 standard. Send "ZZZ" in the FOB05 to indicate that the FOB07 field
    contains the incoterms code.

    N1 Loop
    OptionalMax 200
    Usage notes
    • Required by 3M if 3M will pay freight charges.
    • Highly recommended if vendor will pay freight
      charges and carrier is on the 3M carrier list.
    • Not required if vendor is paying freight and carrier is
      not on the 3M carrier list.
    Variants (all may be used)
    N1N1 Loop
    N1
    220

    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
    N1-01
    98
    Entity Identifier Code
    Required

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

    CA
    Carrier
    N1-02
    93
    Name
    Optional
    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
    Min 2Max 10

    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

    3M restricts the length of this field to 10 characters.

    N1 Loop
    RequiredMax 200

    Required by 3M. Return value sent on PO.

    Variants (all may be used)
    N1N1 Loop
    N1
    220

    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
    N1-01
    98
    Entity Identifier Code
    Required

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

    VN
    Vendor
    N1-02
    93
    Name
    Optional
    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
    Min 2Max 10

    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

    3M restricts the length of this field to 10 characters.

    HL Loop
    RequiredMax 200000
    HL
    010

    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
    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
    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
    PRF
    050

    Purchase Order Reference

    RequiredMax use 1

    To provide reference to a specific purchase order

    Example
    PRF-01
    324
    Purchase Order Number
    Required
    Min 1Max 22

    Identifying number for Purchase Order assigned by the orderer/purchaser

    REF
    150

    Reference Identification

    OptionalMax use >1

    To specify identifying information

    Usage notes

    Required if material is crossing international borders.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    CT
    Contract Number
    IV
    Seller's Invoice Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    HL Loop
    RequiredMax >1
    HL
    010

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

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

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

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    Usage notes

    Return the item number sent in PO.

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

    If the PO line item did not contain a buyer part number (BP) or a vendor part number
    (VP), please send VP in LIN02 and NA in LIN03.

    BP
    Buyer's Part Number
    VP
    Vendor's (Seller's) Part Number
    LIN-03
    234
    Product/Service ID
    Required
    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)

    VP
    Vendor's (Seller's) Part Number
    LIN-05
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    SN1
    030

    Item Detail (Shipment)

    RequiredMax use 1

    To specify line-item detail relative to shipment

    Example
    SN1-01
    350
    Assigned Identification
    Optional
    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
    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
    Min 2Max 2

    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.
    SLN
    040

    Subline Item Detail

    OptionalMax use 1000

    To specify product subline detail item data

    Example
    If either Product/Service ID Qualifier (SLN-09) or Product/Service ID (SLN-10) is present, then the other is required
    If either Product/Service ID Qualifier (SLN-11) or Product/Service ID (SLN-12) is present, then the other is required
    SLN-01
    350
    Assigned Identification
    Required
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • SLN01 is the identifying number for the subline item.
    • SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
    SLN-03
    662
    Relationship Code
    Required

    Code indicating the relationship between entities

    • SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
    I
    Included
    SLN-04
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SLN-05
    C001
    Composite Unit of Measure
    To identify a composite unit of measure (See Figures Appendix for examples of use)
    C001-01
    355
    Unit or Basis for Measurement Code
    Required
    Min 2Max 2

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

    SLN-09
    235
    Product/Service ID Qualifier
    Optional
    Min 2Max 2

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

    • SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    SLN-10
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    SLN-11
    235
    Product/Service ID Qualifier
    Optional

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

    B8
    Batch Number
    SLN-12
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    PID
    070

    Product/Item Description

    OptionalMax use 200

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

    Example
    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-05
    352
    Description
    Required
    Min 1Max 80

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

    TD1
    110

    Carrier Details (Quantity and Weight)

    RequiredMax use 2

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

    Example
    If either Volume (TD1-09) or Unit or Basis for Measurement Code (TD1-10) is present, then the other is required
    TD1-06
    187
    Weight Qualifier
    Required

    Code defining the type of weight

    E
    Estimated Net Weight
    G
    Gross Weight
    TD1-07
    81
    Weight
    Required
    Min 1Max 10

    Numeric value of weight

    TD1-08
    355
    Unit or Basis for Measurement Code
    Required
    Min 2Max 2

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

    TD1-09
    183
    Volume
    Optional
    Min 1Max 8

    Value of volumetric measure

    TD1-10
    355
    Unit or Basis for Measurement Code
    Optional
    Min 2Max 2

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

    REF
    150

    Reference Identification

    OptionalMax use >1

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    Vendor's Batch or Lot Number of material being
    delivered, if applicable.
    Required if material is batch managed. For 3M USA
    PO’s only, the PO line item text will advise if material
    is batch managed.

    BT
    Batch Number
    REF-02
    127
    Reference Identification
    Required
    Min 1Max 30

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

    DTM
    200

    Date/Time Reference

    OptionalMax use 10

    To specify pertinent dates and times

    Example
    DTM-01
    374
    Date/Time Qualifier
    Required

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

    094
    Manufacture
    511
    Shelf Life Expiration
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Summary

    CTT
    010

    Transaction Totals

    RequiredMax use 1

    To transmit a hash total for a specific element in the transaction set

    • Number of line items (CTT01) is the accumulation of the number of HL segments.
      If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    SE
    020

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

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

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

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    ShipNotice example from 3M

    ISA*00* *00* *ZZ*IDSENDERID *12*IDRECEIVERID *150216*1720*U*00401*650000035*0*P*>
    GS*SH* IDSENDERID * IDRECEIVERID *20150216*1720*650000035*X*004010
    ST*856*0400
    BSN*00*SHIPMENTNUMBER*20230404*0744
    DTM*002*20230404
    HL*1**S
    TD1*PKG*1
    TD3*TV**987654896
    REF*BM*BILLOFLADINGNUMBER
    DTM*017*20230404
    FOB*CC*DE*DESCRIPTION*01*EXW*ZZ*DESCRIPTION
    N1*VN*VENDOR NAME*92*VENDORNUM
    N1*CA*CARRIER NAME*92*CARRIERNUM
    HL*2*1*O
    PRF*3MPONUMBER
    HL*3*2*I
    LIN*00010*BP*3MPARTNUMBER*VP*VENDORPARTNUMBER
    SN1*00010*240*1I
    PID*F****LINE ITEM DESCRIPTION
    TD1******G*100*LB*120*LB
    TD1******E*95*LB*120*LB
    CTT*3
    SE*21*0400
    GE*1*650000035
    IEA*1*650000035

    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.