Whirlpool
/
Carrier Shipment Status Message
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Whirlpool. Contact Whirlpool for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Whirlpool logo

X12 214 Carrier Shipment Status Message

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Transportation Carrier Shipment Status Message Transaction Set (214) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used by a transportation carrier to provide shippers, consignees, and their agents with the status of shipments in terms of dates, times, locations, route, identifying numbers, and conveyance.

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
    ST
    010
    Transaction Set Header
    Max use 1
    Required
    B10
    020
    Beginning Segment for Transportation Carrier Shipment Status Message
    Max use 1
    Required
    L11
    030
    Business Instructions and Reference Number
    Max use 300
    Required
    L11
    030
    Run Number
    Max use 300
    Optional
    L11
    030
    Ship Notice/Manifest Number
    Max use 300
    Optional
    0100 Loop
    MS3
    120
    Interline Information
    Max use 12
    Optional
    0200 Loop
    SE
    610
    Transaction Set Trailer
    Max use 1
    Required
    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

    QM
    Transportation Carrier Shipment Status Message (214)
    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).
    214
    Transportation Carrier Shipment Status Message
    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

    B10
    020

    Beginning Segment for Transportation Carrier Shipment Status Message

    RequiredMax use 1

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

    Usage notes

    The B10-03 is from the 204 Load Tender element B2-02.

    Example
    B10-01
    127
    Reference Identification
    Required
    Min 1Max 30

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

    • B1001 is the carrier assigned reference number.
    • B1001 is the carrier's PRO (invoice number) that identifies the shipment.
    B10-02
    145
    Shipment Identification Number
    Required
    Min 1Max 30

    Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)

    Usage notes

    The B10-02 is from the 204 Load Tender element B2-04.

    B10-03
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    • B1003 is required when used in Transaction Set 214.
    L11
    030

    Business Instructions and Reference Number

    RequiredMax use 300

    To specify instructions in this business relationship or a reference number

    Usage notes

    The L11 with the “11” qualifier is required and is from the 204 Load Tender.

    Example
    Variants (all may be used)
    L11Run NumberL11Ship Notice/Manifest Number
    L11-01
    127
    Reference Identification
    Required
    Min 1Max 30

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

    L11-02
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    11
    Account Number
    L11
    030

    Run Number

    OptionalMax use 300

    To specify instructions in this business relationship or a reference number

    Example
    L11-01
    127
    Reference Identification
    Required
    Min 1Max 30

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

    Usage notes

    The L11-01 is from the 204 Load Tender element L11-01 with the L11-02 “RN” qualifier.

    L11-02
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    RN
    Run Number
    L11
    030

    Ship Notice/Manifest Number

    OptionalMax use 300

    To specify instructions in this business relationship or a reference number

    Example
    L11-01
    127
    Reference Identification
    Required
    Min 1Max 30

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

    Usage notes

    The L11-01 is from the 204 Load Tender element L11-01 with the L11-02 “MA” qualifier

    L11-02
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    MA
    Ship Notice/Manifest Number
    0100 Loop
    OptionalMax >1
    N1
    050

    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

    RL
    Reporting Location
    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)

    93
    Code assigned by the organization originating the transaction set
    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.
    MS3
    120

    Interline Information

    OptionalMax use 12

    To identify the interline carrier and relevant data

    Example
    MS3-01
    140
    Standard Carrier Alpha Code
    Optional
    Min 2Max 4

    Standard Carrier Alpha Code

    • MS301 is the Standard Carrier Alpha Code (SCAC) of the interline carrier.
    MS3-02
    133
    Routing Sequence Code
    Optional
    Min 1Max 2

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

    MS3-03
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name

    • MS303 is the city where the interline was performed.
    0200 Loop
    RequiredMax 999999
    Usage notes

    Penske will only accept one AT7 status (Loop 0205) per LX Loop 0200.

    LX
    130

    Assigned Number

    RequiredMax use 1

    To reference a line number in a transaction set

    Example
    LX-01
    554
    Assigned Number
    Required
    Min 1Max 6

    Number assigned for differentiation within a transaction set

    0205 Loop
    RequiredMax 1
    AT7
    140

    Shipment Status Details

    RequiredMax use 1

    To specify the status of a shipment, the reason for that status, the date and time of the status and the date and time of any appointments scheduled.

    Example
    AT7-01
    1650
    Shipment Status Code
    Required

    Code indicating the status of a shipment

    • If AT701 is present, AT705 is the date the status occurred. If AT703 is present, AT705 is a date related to an appointment.
    • If AT701 is present, AT706 is the time of the status. If AT703 is present, AT706 is the time of the appointment.
    Usage notes

    A minimum of four statuses should be sent for each 204 Load Tender X3, AF, X1, & D1; all statuses must be received in their respective order. i.e. you can not send a delivery status before you send a pickup status, and you can not depart before you arrive Whirlpool is requesting an AG – ETA delivery update after the last PU

    AF
    Carrier Departed Pick-up Location with Shipment
    AG
    Estimated Delivery
    CL
    Trailer Closed Out
    D1
    Completed Unloading at Delivery Location
    X1
    Arrived at Delivery Location
    X3
    Arrived at Pick-up Location
    AT7-02
    1651
    Shipment Status or Appointment Reason Code
    Required

    Code indicating the reason a shipment status or appointment reason was transmitted

    Usage notes

    The reason code should always be 'NS' Normal Status except when LATE. When a carrier is late for a pickup or delivery, one of the “LATE” status codes should be sent to identify the reason for being late.

    AF
    Accident
    AH
    Driver Related
    AI
    Mechanical Breakdown
    AL
    Previous Stop
    AM
    Shipper Related
    AO
    Weather or Natural Disaster Related
    BD
    Border Clearance
    BH
    Insufficient Time to Complete Delivery
    BO
    Railroad Failed to Meet Schedule
    D1
    Carrier Dispatch Error
    NS
    Normal Status
    AT7-05
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    AT7-06
    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)

    Usage notes

    All times are reported in local time

    AT7-07
    623
    Time Code
    Required
    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

    • If AT707 is not present then AT706 represents local time of the status.
    Usage notes

    Sent valid Time Zone for when status occurred otherwise we assume it was reported in local time.

    MS1
    143

    Equipment, Shipment, or Real Property Location

    OptionalMax use 1

    To specify the location of a piece of equipment, a shipment, or real property in terms of city and state or longitude and latitude

    Example
    If City Name (MS1-01) is present, then at least one of State or Province Code (MS1-02) or Country Code (MS1-03) is required
    If Country Code (MS1-03) is present, then City Name (MS1-01) is required
    MS1-01
    19
    City Name
    Required
    Min 2Max 30

    Free-form text for city name

    MS1-02
    156
    State or Province Code
    Required
    Min 2Max 2

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

    MS1-03
    26
    Country Code
    Optional
    Min 2Max 3

    Code identifying the country

    Usage notes

    Only used if location is not within the United States of America.

    MS2
    146

    Equipment or Container Owner and Type

    RequiredMax use 1

    To specify the owner, the identification number assigned by that owner, and the type of equipment

    Example
    MS2-01
    140
    Standard Carrier Alpha Code
    Required
    Min 2Max 4

    Standard Carrier Alpha Code

    MS2-02
    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)

    L11
    150

    Bill of Lading Number

    OptionalMax use 10

    To specify instructions in this business relationship or a reference number

    Example
    L11-01
    127
    Reference Identification
    Required
    Min 1Max 30

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

    Usage notes

    L11 segment & L11-01 is mandatory with L11-02Reference qualifier “QN”.

    L11-02
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    The L11 with the “QN” qualifier is required and is from the 204 Load Tender S5-01. This is the STOP number for the status that is being reported.

    BM
    Bill of Lading Number
    L11
    150

    Stop Sequence Number

    OptionalMax use 10

    To specify instructions in this business relationship or a reference number

    Example
    L11-01
    127
    Reference Identification
    Required
    Min 1Max 30

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

    Usage notes

    L11 segment & L11-01 is mandatory with L11-02Reference qualifier “QN”.

    L11-02
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    The L11 with the “QN” qualifier is required and is from the 204 Load Tender S5-01. This is the STOP number for the status that is being reported.

    QN
    Stop Sequence Number
    L11
    150

    Tracking Number

    OptionalMax use 10

    To specify instructions in this business relationship or a reference number

    Example
    L11-01
    127
    Reference Identification
    Required
    Min 1Max 30

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

    Usage notes

    L11 segment & L11-01 is mandatory with L11-02Reference qualifier “QN”.

    L11-02
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    Usage notes

    The L11 with the “QN” qualifier is required and is from the 204 Load Tender S5-01. This is the STOP number for the status that is being reported.

    2I
    Tracking Number
    AT8
    200

    Shipment Weight, Packaging and Quantity Data

    OptionalMax use 10

    To specify shipment details in terms of weight, and quantity of handling units

    Example
    If either Weight Qualifier (AT8-01), Weight Unit Code (AT8-02) or Weight (AT8-03) are present, then the others are required
    If either Volume Unit Qualifier (AT8-06) or Volume (AT8-07) is present, then the other is required
    AT8-01
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

    G
    Gross Weight
    AT8-02
    188
    Weight Unit Code
    Optional

    Code specifying the weight unit

    K
    Kilograms
    L
    Pounds
    AT8-03
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    AT8-04
    80
    Lading Quantity
    Optional
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    • AT804 is the quantity of handling units that are not unitized (for example a carton). When added to the quantity in AT805, it is the total quantity of handling units in the shipment.
    AT8-06
    184
    Volume Unit Qualifier
    Optional
    Min 1Max 1

    Code identifying the volume unit

    AT8-07
    183
    Volume
    Optional
    Min 1Max 8

    Value of volumetric measure

    SE
    610

    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

    AF – PU Status

    ST*214*000000001~
    B10*123123123*LOADNBR*SCAC~
    L11*WHRLLP-CT*11~
    LX*1~
    AT7*AF*NS***20090316*0800*PT~
    MS1*PERRIS*CA*USA~
    MS2*SCAC*TRL###~
    L11*1*QN~
    AT8*G*L*382*2~
    SE*10*000000001~

    D1 – Delivery Status

    ST*214*000000001~
    B10*123123123*LOADNBR*SCAC~
    L11*WHRLLP-CT*11~
    LX*1~
    AT7*D1*NS***20090317*2300*PT~
    MS1*MESA*AZ*USA~
    MS2*SCAC*TRL###~
    L11*2*QN~
    AT8*G*L*382*2~
    SE*10*000000001~

    Empty Trailer from Penske to Carrier

    ST*214*000000001~
    B10*123123123*LOADNBR*SCAC~
    L11*WHRLLP-CT*11~
    N1*RL*Denver RDC 457*93*WHRR457~
    LX*1~
    AT7*CL*NS***20090316*0730*LT~
    MS2*SCAC*TRL###~
    SE*8*000000001~

    X1 – Delivery Status

    ST*214*000000001~
    B10*123123123*LOADNBR*SCAC~
    L11*WHRLLP-CT*11~
    LX*1~
    AT7*X1*NS***20090317*2200*PT~
    MS1*MESA*AZ*USA~
    MS2*SCAC*TRL###~
    L11*2*QN~
    AT8*G*L*382*2~
    SE*10*000000001~

    X3 – PU Statuse

    ST*214*000000001~
    B10*123123123*LOADNBR*SCAC~
    L11*WHRLLP-CT*11~
    LX*1~
    AT7*X3*NS***20090316*0730*PT~
    MS1*PERRIS*CA*USA~
    MS2*SCAC*TRL###~
    L11*1*QN~
    AT8*G*L*382*2~
    SE*10*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.