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

X12 856 Ship Notice/Manifest

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 samples
    View the latest version of this implementation guide as an interactive webpage
    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
    MEA
    080
    Measurements
    Max use 40
    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
    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

    Usage notes

    The segment is used to communicate the shipment ID number (SID). This shipment ID number represents the total contents of the materials from one destination to another destination. Often the Bill of Lading number is used, but it can be any number which is not repeated for 13 months by the supplier. The transaction purpose code associated indicates an original shipment. If a replacement ship notice is sent, then Deere requires the entire contents of the shipment data re-transmitted.

    Example
    BSN-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    01
    Cancellation
    05
    Replace
    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

    John Deere requires a unique shipment ID for 13 months. John Deere uses only the 13 left most characters for the ship ID. If packlist references are not sent in a reference segment, the SID will be used as the invoice number for ERS.

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

    Use format of HHMMSSDD.

    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

    0003
    Shipment, Packaging, Order, Item
    DTM
    040

    Estimated Delivery

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Deere requires at least one DTM segment to communicate the time of shipment or the estimated time of arrival at the ship to location.

    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

    017
    Estimated Delivery
    DTM-02
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    DTM-03
    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)

    DTM-04
    623
    Time Code
    Optional
    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

    DTM
    040

    Shipped

    OptionalMax use 10

    To specify pertinent dates and times

    Usage notes

    Deere requires at least one DTM segment to communicate the time of shipment or the estimated time of arrival at the ship to location.

    Example
    Variants (all may be used)
    DTMEstimated 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

    DTM-03
    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)

    DTM-04
    623
    Time Code
    Optional
    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

    Detail

    HL Loop
    RequiredMax >1
    Usage notes

    John Deere will use Shipment/Package/Order/Item hierarchical structure, and BSN 05 should reflect this ASN structure.

    The first 'Hierarchical Level - Shipment' is number 1, and all segments until the next HL, segment relate to the header information; all information applies to the entire content of the shipment.

    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
    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.
    MEA
    080

    Measurements

    OptionalMax use 40

    To specify physical measurements or counts, including dimensions, tolerances, variances, and weights

    (See Figures Appendix for example of use of C001)

    Usage notes

    This is an optional segment at the shipment level containing total weight of the total shipment quantity.

    Example
    MEA-01
    737
    Measurement Reference ID Code
    Optional

    Code identifying the broad category to which a measurement applies

    PD
    Physical Dimensions
    MEA-02
    738
    Measurement Qualifier
    Optional

    Code identifying a specific product or process characteristic to which a measurement applies

    G
    Gross Weight
    N
    Actual Net Weight
    MEA-03
    739
    Measurement Value
    Optional
    Min 1Max 15

    The value of the measurement

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

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

    01
    Actual Pounds

    Only used by Worldwide Logistics.

    24
    Theoretical Pounds

    Only used by Worldwide Logistics.

    50
    Actual Kilograms

    Only used by Worldwide Logistics.

    53
    Theoretical Kilograms

    Only used by Worldwide Logistics.

    KG
    Kilogram
    LB
    Pound
    TD5
    120

    Carrier Details (Routing Sequence/Transit Time)

    OptionalMax use 12

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

    Usage notes

    John Deere uses segment at the shipment level only.

    The primary information Deere requires from this segment is the code for the transportation company moving the material.

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

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

    B
    Origin/Delivery Carrier (Any Mode)
    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
    Min 2Max 80

    Code identifying a party or other code

    Usage notes

    SCAC code of carrier.

    TD5-04
    91
    Transportation Method/Type Code
    Optional
    Min 1Max 2

    Code specifying the method or type of transportation for the shipment

    TD5-05
    387
    Routing
    Optional
    Min 1Max 35

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

    TD5-07
    309
    Location Qualifier
    Optional

    Code identifying type of location

    OR
    Origin (Shipping Point)
    PP
    Pool Point
    TD5-08
    310
    Location Identifier
    Optional
    Min 1Max 30

    Code which identifies a specific location

    TD3
    130

    Carrier Details (Equipment)

    OptionalMax use 12

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

    Usage notes

    John Deere uses segment at the shipment level only.

    The trailer number (or other ID number of the carrier) is provided here within the equipment number field. If trailer number is not available, do not use the TD3 segment.

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

    Code identifying type of equipment used for shipment

    TD3-02
    206
    Equipment Initial
    Optional
    Min 1Max 4

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

    Usage notes

    John Deere expects the SCAC code of the Carrier.

    TD3-03
    207
    Equipment Number
    Optional
    Min 1Max 10

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

    REF
    150

    Reference Identification

    OptionalMax use >1

    To specify identifying information

    Usage notes

    John Deere requires the "2I" at the Shipment level for the shipment's logistic provider tracking number.

    Other information related to the shipment may also be provided in additional Shipment level REF segments.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    2I
    Tracking Number
    AW
    Air Waybill Number
    BM
    Bill of Lading Number

    This number must not repeat within 13 months.

    FR
    Freight Bill Number
    IK
    Invoice Number

    Manufacturer's invoice number for vehicle/component.

    Required by Deere Mexican units at header-level or item-level location depending on shipment makeup for invoice matching.

    OC
    Ocean Container Number
    PK
    Packing List Number

    This number must not repeat within 13 months.

    SN
    Seal Number
    REF-02
    127
    Reference Identification
    Optional
    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

    Name

    RequiredMax use 1

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

    Usage notes

    John Deere uses segment at the shipment level only to communicate business partner or location information.

    There will be an associated DUNS number or another Deere unique number to cross reference entity information.

    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

    CS
    Consolidator
    SF
    Ship From
    ST
    Ship To
    SU
    Supplier/Manufacturer
    N1-02
    93
    Name
    Optional
    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
    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Optional
    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.
    REF
    260

    Reference Identification

    OptionalMax use 12

    To specify identifying information

    Usage notes

    John Deere uses this optional segment at the shipment level for N1 loop.

    This REF segment is used to communicate the dock code "DK" if the ordering transaction included corresponding dock information.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    DK
    Dock Number
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    SAC Loop
    OptionalMax >1
    SAC
    320

    Service, Promotion, Allowance, or Charge Information

    RequiredMax use 1

    To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

    Usage notes

    John Deere uses this optional segment at the shipment level only for special charges related to the shipment.

    Example
    SAC-01
    248
    Allowance or Charge Indicator
    Required

    Code which indicates an allowance or charge for the service specified

    • If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
    C
    Charge
    SAC-02
    1300
    Service, Promotion, Allowance, or Charge Code
    Optional

    Code identifying the service, promotion, allowance, or charge

    C040
    Delivery
    D240
    Freight
    D500
    Handling
    G760
    Set-up
    H550
    Surcharge
    I260
    Transportation Direct Billing
    I280
    Transportation Vendor Provided
    SAC-05
    610
    Amount
    Optional
    Min 1Max 15

    Monetary amount

    • SAC05 is the total amount for the service, promotion, allowance, or charge.
    • If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
    HL Loop
    RequiredMax >1
    Usage notes

    If BSN 05 indicates Shipment/Package/Order/Item hierarchical structure, then the first 'Hierarchical Level - Pallet/Master Package' occurrence will start with 2 and all segments until the next Package level HL relate to the outer-most container/carton or pallet.

    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.
    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.
    MEA
    080

    Measurements

    OptionalMax use 40

    To specify physical measurements or counts, including dimensions, tolerances, variances, and weights

    (See Figures Appendix for example of use of C001)

    Usage notes

    This is an optional segment containing total weight of the shipped quantity for the container/carton.

    Example
    MEA-01
    737
    Measurement Reference ID Code
    Optional

    Code identifying the broad category to which a measurement applies

    PD
    Physical Dimensions
    MEA-02
    738
    Measurement Qualifier
    Optional

    Code identifying a specific product or process characteristic to which a measurement applies

    G
    Gross Weight
    N
    Actual Net Weight
    WT
    Weight
    MEA-03
    739
    Measurement Value
    Optional
    Min 1Max 15

    The value of the measurement

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

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

    01
    Actual Pounds

    Only used by Worldwide Logistics.

    24
    Theoretical Pounds

    Only used by Worldwide Logistics.

    50
    Actual Kilograms

    Only used by Worldwide Logistics.

    53
    Theoretical Kilograms

    Only used by Worldwide Logistics.

    KG
    Kilogram
    LB
    Pound
    REF
    150

    Invoice Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    This optional segment at the Package level may be included to provide additional information depending on the makeup of the shipment.

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

    Code qualifying the Reference Identification

    IK
    Invoice Number

    Manufacturer's invoice number for vehicle/component.

    Required by Deere Mexican units at header-level or item-level location depending on shipment makeup for invoice matching.

    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    REF
    150

    Packing List Number

    OptionalMax use >1

    To specify identifying information

    Usage notes

    This optional segment at the Package level may be included to provide additional information depending on the makeup of the shipment.

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

    Code qualifying the Reference Identification

    PK
    Packing List Number

    This number must not repeat within 13 months.

    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    Usage notes

    The packing list reference, when provided, will be used as the invoice number ERS.

    CLD Loop
    OptionalMax >1
    CLD
    170

    Load Detail

    RequiredMax use 1

    To specify the number of material loads shipped

    Usage notes

    A Package level CLD segment is required when identifying a container/carton of shippable items, an outermost container/carton, or pallet with sub containers/cartons.

    The Package level CLD number of loads must be 1 and the quantity equal either the number of shippable items or number of sub containers/cartons in the case of outer packaging or pallet.

    Example
    CLD-01
    622
    Number of Loads
    Required
    Min 1Max 5

    Number of customer-defined loads shipped by the supplier

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

    REF
    180

    Container/Packaging Specification Number

    OptionalMax use 200

    To specify identifying information

    Usage notes

    John Deere uses a Packaging level REF to provide additional references for each container/carton.

    The "98" qualifier replaces the TD101 Packaging Code. If the containers loaded have an associated cost within Deere unit systems, the containers are paid with the material payment when the ERS process is in effect. The external packaging value is required when the shipment is a mix or master pallet/pack.

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

    Code qualifying the Reference Identification

    98
    Container/Packaging Specification Number

    A numeric or alphanumeric identification assigned to a unique packaging/container configuration.

    Used to communicate Deere packaging code.

    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    REF
    180

    Shipping Label Serial Number

    OptionalMax use 200

    To specify identifying information

    Usage notes

    John Deere uses a Packaging level REF to provide additional references for each container/carton.

    The "LA" qualifier identifies the Shipping Label (License plate) for the container/carton. At the Pack level this "LA" refers to the outermost License Plate Number for the Master or Mix container.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    LA
    Shipping Label Serial Number
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    HL Loop
    RequiredMax >1
    Usage notes

    If BSN 05 indicates Shipment/Package/Order/Item hierarchical structure, then the first 'Hierarchical Level - Order' occurrence will start with 3 and all segments until the next Order level HL identifies an order.

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

    Purchase Order Reference

    OptionalMax use 1

    To provide reference to a specific purchase order

    Usage notes

    This segment contains the Deere purchase order number for the material being shipped. John Deere requires this segment at the HL order level.

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

    Identifying number for Purchase Order assigned by the orderer/purchaser

    HL Loop
    RequiredMax >1
    Usage notes

    If BSN 05 indicates Shipment/Package/Order/Item hierarchical structure, then the first 'Hierarchical Level - Item' occurrence will start with 4 and all segments until the next HL relate to an item.

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

    Item Identification

    OptionalMax use 1

    To specify basic item identification data

    Usage notes

    This segment contains the Deere material number being shipped. John Deere requires this segment at the item level.

    The Purchase Order Line Number is required. The value can be retrieved from the 830 LIN01, the 850 PO101 or the 862 LIN segment in one of the value/pair segments with a "PL" qualifier. The Purchase Order Line Number is sent in one of the 856 LIN value/pair segments with a "PL" qualifier.

    Paired elements starting at LIN02/LIN03 can be sent in any order. The qualifier identifies the business relevance of the value.

    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
    LIN-01
    350
    Assigned Identification
    Optional
    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.
    BP
    Buyer's Part Number
    CH
    Country of Origin Code
    PL
    Purchaser's Order Line Number
    SN
    Serial 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)

    BP
    Buyer's Part Number
    CH
    Country of Origin Code
    PL
    Purchaser's Order Line Number
    SN
    Serial Number
    LIN-05
    234
    Product/Service ID
    Optional
    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)

    BP
    Buyer's Part Number
    CH
    Country of Origin Code
    PL
    Purchaser's Order Line Number
    SN
    Serial Number
    LIN-07
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    SN1
    030

    Item Detail (Shipment)

    OptionalMax use 1

    To specify line-item detail relative to shipment

    Usage notes

    John Deere requires this segment at the item level.

    The total shipped quantity is specified, along with the unit of measure. The segment is required of each part number (LIN segment). If this quantity does not agree with the total of all load quantities below, an EDI 824 error message is generated to the supplier and the lesser of the two quantities is assumed to be correct.

    Example
    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

    Usage notes

    Deere uses this segment for communicating configurable options on a base whole good machines identified at the line-item. Quantities, part number and descriptions should always be sent. Option pricing may be included in this segment, but the item price should include these costs.

    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-02
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
    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.
    A
    Add
    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

    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.
    BP
    Buyer's Part Number
    PD
    Part Number Description
    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)

    BP
    Buyer's Part Number
    PD
    Part Number Description
    SLN-12
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    MEA
    080

    Measurements

    OptionalMax use 40

    To specify physical measurements or counts, including dimensions, tolerances, variances, and weights

    (See Figures Appendix for example of use of C001)

    Usage notes

    This is an optional segment containing total weight of the shipped quantity for the line item.

    Example
    MEA-01
    737
    Measurement Reference ID Code
    Optional

    Code identifying the broad category to which a measurement applies

    PD
    Physical Dimensions
    MEA-02
    738
    Measurement Qualifier
    Optional

    Code identifying a specific product or process characteristic to which a measurement applies

    G
    Gross Weight
    N
    Actual Net Weight
    WT
    Weight
    MEA-03
    739
    Measurement Value
    Optional
    Min 1Max 15

    The value of the measurement

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

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

    01
    Actual Pounds

    Only used by Worldwide Logistics.

    24
    Theoretical Pounds

    Only used by Worldwide Logistics.

    50
    Actual Kilograms

    Only used by Worldwide Logistics.

    53
    Theoretical Kilograms

    Only used by Worldwide Logistics.

    KG
    Kilogram
    LB
    Pound
    REF
    150

    Reference Identification

    OptionalMax use >1

    To specify identifying information

    Usage notes

    This optional segment at the item level may be included to provide additional information/references for the identified material.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    DP
    Department Number
    IK
    Invoice Number

    Manufacturer's invoice number for vehicle/component.

    Required by Deere Mexican units at header-level or item-level location depending on shipment makeup for invoice matching.

    KB
    Beginning Kanban Serial Number
    LF
    Assembly Line Feed Location
    PK
    Packing List Number

    This number must not repeat within 13 months.

    SE
    Serial Number

    Used for whole good or component serial numbers.

    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

    Usage notes

    The packing list reference, when provided, will be used as the invoice number ERS.

    CLD Loop
    OptionalMax >1
    CLD
    170

    Load Detail

    RequiredMax use 1

    To specify the number of material loads shipped

    Usage notes

    Each containers/cartons should be referenced in a CLD segment with the sum of those CLD quantities equaling the SN1 quantity.

    Use one CLD loop for each license plate number.

    Example
    CLD-01
    622
    Number of Loads
    Required
    Min 1Max 5

    Number of customer-defined loads shipped by the supplier

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

    REF
    180

    Reference Identification

    OptionalMax use 200

    To specify identifying information

    Usage notes

    This segment may be included to provide additional detail information.

    The "KB" qualifier indicates the Kanban serial number for the load. If part is on Controlled Delivery (862 Shipping Schedule), a 'KB' (trigger number) qualifier in the REF segment is required for each load or container and cannot be duplicated. If used at this level the quantity in the CLD equals trigger quantity.

    The "98" qualifier replaces the CLD03 Packaging Code. The internal packaging value is required for each CLD.

    The "LA" qualifier identifies the Shipping Label (License plate) for the container/carton and is required for each CLD.

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    97
    Package Number

    A serial number indicating unit shipped.

    98
    Container/Packaging Specification Number
    CR
    Customer Reference Number
    IK
    Invoice Number

    Manufacturer's invoice number for vehicle/component.

    Required by Deere Mexican units at header-level or item-level location depending on shipment makeup for invoice matching.

    KB
    Beginning Kanban Serial Number
    LA
    Shipping Label Serial Number
    LT
    Lot Number
    PC
    Production Code
    RS
    Returnable Container Serial Number
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

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

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

    John Deere requires CTT segment, the count all hierarchical levels used.

    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    Usage notes

    Number of line items (CTT01) is the accumulation of the number of HL segments.

    CTT-02
    347
    Hash Total
    Optional
    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.

    Usage notes

    Hash Total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.

    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

    Master Pallet/Pack

    ST*856*0021
    BSN*00*3660239*20190308*13450196*0003
    DTM*011*20190306*13380000
    HL*1**S
    REF*2I*JDGV1234567
    N1*ST*RYDER INTEGRATED LOGISTICS*1*964475974
    HL*2*1*P
    CLD*1*3
    REF*98*PALLET1
    REF*LA* DESUPPLIERID000A0641
    HL*3*2*O
    PRF*5500000002
    HL*4*3*I
    LIN**BP*Part345*PL*0020
    SN1**30*PC
    REF*DP*LSC
    REF*PK*30601
    CLD*1*10
    REF*98*BOX25
    REF*RS*RC123
    REF*LA* DESUPPLIERID000A0642
    CLD*1*10
    REF*98*BOX25
    REF*LA* DESUPPLIERID000A0643
    CLD*1*10
    REF*98*BOX25
    REF*LA* DESUPPLIERID000A0644
    CTT*1
    SE*29*0021

    Mixed Pallet/Pack

    ST*856*0021
    BSN*00*3660239*20190308*13450196*0003
    DTM*011*20190306*13380000
    HL*1**S
    REF*2I*JDGV1234567
    N1*ST*RYDER INTEGRATED LOGISTICS*1*964475974
    HL*2*1*P
    CLD*1*2
    REF*98*PALLET3
    REF*LA* DESUPPLIERID000A0645
    HL*3*2*O
    PRF*5500000003
    HL*4*3*I
    LIN**BP*Part678*PL*00010
    SN1**15*PC
    REF*DP*LSC
    REF*PK*30601
    CLD*1*15
    REF*98*BOX90
    REF*LA* DESUPPLIERID000A0646
    HL*5*2*O
    PRF*5500000004
    HL*6*5*I
    LIN**BP*Part901*PL*00020
    SN1**10*PC
    REF*DP*LSC
    REF*PK*30601
    CLD*1*10
    REF*98*BOX25
    REF*LA* DESUPPLIERID000A0647
    CTT*2
    SE*32*0021

    Single Order

    ST*856*0021
    BSN*00*3660239*20190308*13450196*0003
    DTM*011*20190306*13380000
    HL*1**S
    MEA*PD*G*22*KG
    TD5*B*2*IDENTIFICATIONCODE
    TD3*TL*XXXX*XXXXXXXXXX
    REF*2I*JDGV1234567
    N1*ST*RYDER INTEGRATED LOGISTICS*1*964475974
    HL*2*1*P
    CLD*1*1
    HL*3*2*O
    PRF*5500000001
    HL*4*3*I
    LIN**BP*Part123*PL*0010
    SN1**5*PC
    REF*DP*LSC
    REF*PK*30601
    CLD*1*5
    REF*98*CB101008
    REF*KB*00000000001
    REF*LA*DESUPPLIERID000A0640
    REF*RS*PD6776
    CTT*1
    SE*25*0021

    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.