Flexport
/
Motor Carrier Load Tender (Carrier)
  • Specification
  • EDI Inspector
Import guide into your account
Flexport logo

X12 204 Motor Carrier Load Tender (Carrier)

X12 Release 4010
Flexport Docs

This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Load Tender Transaction Set (204) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to allow shippers or other interested parties to offer (tender) a shipment to a full load (truckload) motor carrier including detailed scheduling, equipment requirements, commodities, and shipping instructions pertinent to a load tender. It is not to be used to provide a motor carrier with data relative to a Less-than-Truckload bill of lading, pick-up notification, or manifest.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    https://www.stedi.com/app/guides/view/flexport/motor-carrier-load-tender-carrier/01GGCVWKZH9E0N3QXY3JXFPA2D
    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
    B2
    020
    Beginning Segment for Shipment Information Transaction
    Max use 1
    Required
    B2A
    030
    Set Purpose
    Max use 1
    Required
    L11
    080
    Business Instructions and Reference Number
    Max use 50
    Optional
    AT5
    110
    Bill of Lading Handling Requirements
    Max use 6
    Optional
    0100 Loop
    0200 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
    String (AN)
    Min 10Max 10

    Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

    ISA-03
    I03
    Security Information Qualifier
    Required

    Code to identify the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    String (AN)
    Min 10Max 10

    This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

    ISA-05
    I05
    Interchange ID Qualifier
    Required
    Identifier (ID)
    Min 2Max 2

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

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    String (AN)
    Min 15Max 15

    Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

    ISA-07
    I05
    Interchange ID Qualifier
    Required
    Identifier (ID)
    Min 2Max 2

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

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    String (AN)
    Min 15Max 15

    Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

    ISA-09
    I08
    Interchange Date
    Required
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

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

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

    This version number covers the interchange control segments

    00401
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
    ISA-13
    I12
    Interchange Control Number
    Required
    Numeric (N0)
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Identifier (ID)
    Min 1Max 1

    Code sent by the sender to request an interchange acknowledgment (TA1)

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

    Code to indicate whether data enclosed by this interchange envelope is test, production or information

    I
    Information
    P
    Production Data
    T
    Test Data
    ISA-16
    I15
    Component Element Separator
    Required
    String (AN)
    Min 1Max 1

    Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

    >
    Component Element Separator

    Functional Group Header

    RequiredMax use 1

    To indicate the beginning of a functional group and to provide control information

    Example
    GS-01
    479
    Functional Identifier Code
    Required

    Code identifying a group of application related transaction sets

    SM
    Motor Carrier Load Tender (204)
    GS-02
    142
    Application Sender's Code
    Required
    String (AN)
    Min 2Max 15

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

    GS-03
    124
    Application Receiver's Code
    Required
    String (AN)
    Min 2Max 15

    Code identifying party receiving transmission. Codes agreed to by trading partners

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    GS-06
    28
    Group Control Number
    Required
    Numeric (N0)
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Identifier (ID)
    Min 1Max 2

    Code used in conjunction with Data Element 480 to identify the issuer of the standard

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

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

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

    Heading

    ST
    010
    Heading > ST

    Transaction Set Header

    RequiredMax use 1

    To indicate the start of a transaction set and to assign a control number

    Example
    ST-01
    143
    Transaction Set Identifier Code
    Required

    Code uniquely identifying a Transaction Set

    • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
    204
    Motor Carrier Load Tender
    ST-02
    329
    Transaction Set Control Number
    Required
    Numeric (N)
    Min 4Max 9

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

    B2
    020
    Heading > B2

    Beginning Segment for Shipment Information Transaction

    RequiredMax use 1

    To transmit basic data relating to shipment information

    Example
    B2-02
    140
    Standard Carrier Alpha Code
    Required
    Identifier (ID)
    Min 2Max 4

    Standard Carrier Alpha Code

    • B202 contains the Standard Carrier Alpha Code (SCAC) of the carrier that will receive the bill of lading.
    • B202 is mandatory for transaction set 204.
    B2-04
    145
    Shipment Identification Number
    Optional
    String (AN)
    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)

    B2-06
    146
    Shipment Method of Payment
    Required

    Code identifying payment terms for transportation charges

    CC
    Collect
    B2A
    030
    Heading > B2A

    Set Purpose

    RequiredMax use 1

    To allow for positive identification of transaction set purpose

    Example
    B2A-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    01
    Cancellation
    04
    Change
    21
    Transaction on Hold
    L11
    080
    Heading > L11

    Business Instructions and Reference Number

    OptionalMax use 50

    To specify instructions in this business relationship or a reference number

    Example
    At least one of Reference Identification (L11-01) or Description (L11-03) is required
    L11-01
    127
    Reference Identification
    Optional
    String (AN)
    Min 1Max 30

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

    L11-02
    128
    Reference Identification Qualifier
    Optional

    Code qualifying the Reference Identification

    4B
    Shipment Origin Code
    4C
    Shipment Destination Code
    ABS
    Vessel Name
    BM
    Bill of Lading Number
    BN
    Booking Number
    ETA
    Estimated time of arrival
    V3
    Voyage Number
    ZZ
    Mutually Defined
    L11-03
    352
    Description
    Optional
    String (AN)
    Min 1Max 80

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

    AT5
    110
    Heading > AT5

    Bill of Lading Handling Requirements

    OptionalMax use 6

    To identify Bill of Lading handling and service requirements

    Example
    AT5-01
    152
    Special Handling Code
    Optional

    Code specifying special transportation handling instructions

    IP
    Import Shipment
    XP
    Export
    0100 Loop
    RequiredMax >1
    N1
    140
    Heading > 0100 Loop > N1

    Name

    RequiredMax use 1

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

    • Loop 0100 is used to convey name and address detail relative to bill-to, party controlling freight, or other shipment level name and address information. It is not used to convey ship from or ship to detail which should be handled within loop 0300 in table 2.
    Example
    N1-01
    98
    Entity Identifier Code
    Required

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

    BT
    Bill-to-Party
    CN
    Consignee
    SF
    Ship From
    SH
    Shipper
    ST
    Ship To
    N1-02
    93
    Name
    Required
    String (AN)
    Min 1Max 60

    Free-form name

    N3
    160
    Heading > 0100 Loop > N3

    Address Information

    RequiredMax use 2

    To specify the location of the named party

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

    Address information

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

    Address information

    N4
    170
    Heading > 0100 Loop > N4

    Geographic Location

    RequiredMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    String (AN)
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Identifier (ID)
    Min 2Max 2

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

    • N402 is required only if city name (N401) is in the U.S. or Canada.
    N4-03
    116
    Postal Code
    Optional
    Identifier (ID)
    Min 3Max 15

    Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

    N4-04
    26
    Country Code
    Optional
    Identifier (ID)
    Min 2Max 3

    Code identifying the country

    G61
    190
    Heading > 0100 Loop > G61

    Contact

    OptionalMax use 3

    To identify a person or office to whom communications should be directed

    Example
    If either Communication Number Qualifier (G61-03) or Communication Number (G61-04) is present, then the other is required
    G61-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    DC
    Delivery Contact
    ST
    Service Technician
    G61-02
    93
    Name
    Required
    String (AN)
    Min 1Max 60

    Free-form name

    G61-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    • G6103 qualifies G6104.
    TE
    Telephone
    G61-04
    364
    Communication Number
    Optional
    String (AN)
    Min 1Max 80

    Complete communications number including country or area code when applicable

    0100 Loop end
    0200 Loop
    OptionalMax >1
    N7
    200
    Heading > 0200 Loop > N7

    Equipment Details

    RequiredMax use 1

    To identify the equipment

    Example
    If either Weight (N7-03) or Weight Qualifier (N7-04) is present, then the other is required
    N7-01
    206
    Equipment Initial
    Optional
    String (AN)
    Min 1Max 4

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

    • N701 is mandatory for rail transactions.
    N7-02
    207
    Equipment Number
    Required
    String (AN)
    Min 1Max 10

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

    N7-03
    81
    Weight
    Optional
    Decimal number (R)
    Min 1Max 10

    Numeric value of weight

    N7-04
    187
    Weight Qualifier
    Optional

    Code defining the type of weight

    G
    Gross Weight
    N7-11
    40
    Equipment Description Code
    Optional

    Code identifying type of equipment used for shipment

    CN
    Container
    N7-15
    567
    Equipment Length
    Optional
    Numeric (N0)
    Min 4Max 5

    Length (in feet and inches) of equipment ordered or used to transport shipment (The format is FFFII where FFF is feet and II is inches; the range for II is 00 through 11)

    N7-17
    188
    Weight Unit Code
    Optional

    Code specifying the weight unit

    K
    Kilograms
    L
    Pounds
    N7-18
    761
    Equipment Number Check Digit
    Optional
    Numeric (N0)
    Min 1Max 1

    Number which designates the check digit applied to a piece of equipment

    N7-22
    24
    Equipment Type
    Optional
    Identifier (ID)
    Min 4Max 4

    Code identifying equipment type

    M7
    210
    Heading > 0200 Loop > M7

    Seal Numbers

    OptionalMax use 2

    To record seal numbers used and the organization that applied the seals

    Example
    M7-01
    225
    Seal Number
    Required
    String (AN)
    Min 2Max 15

    Unique number on seal used to close a shipment

    0200 Loop end
    Heading end

    Detail

    0300 Loop
    RequiredMax >1
    S5
    010
    Detail > 0300 Loop > S5

    Stop Off Details

    RequiredMax use 1

    To specify stop-off detail reference numbers and stop reason

    Example
    S5-01
    165
    Stop Sequence Number
    Required
    Numeric (N0)
    Min 1Max 3

    Identifying number for the specific stop and the sequence in which the stop is to be performed

    S5-02
    163
    Stop Reason Code
    Required

    Code specifying the reason for the stop

    CL
    Complete
    LD
    Load
    PA
    Pick-up Pre-loaded Equipment
    UL
    Unload
    NTE
    065
    Detail > 0300 Loop > NTE

    Note/Special Instruction

    OptionalMax use 20

    To transmit information in a free-form format, if necessary, for comment or special instruction

    Example
    NTE-01
    363
    Note Reference Code
    Optional

    Code identifying the functional area or purpose for which the note applies

    APN
    Application Notes
    NTE-02
    352
    Description
    Required
    String (AN)
    Min 1Max 80

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

    0300 Loop end
    Detail end

    Summary

    SE
    020
    Summary > SE

    Transaction Set Trailer

    RequiredMax use 1

    To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

    Example
    SE-01
    96
    Number of Included Segments
    Required
    Numeric (N0)
    Min 1Max 10

    Total number of segments included in a transaction set including ST and SE segments

    SE-02
    329
    Transaction Set Control Number
    Required
    Numeric (N)
    Min 4Max 9

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

    Summary end

    Functional Group Trailer

    RequiredMax use 1

    To indicate the end of a functional group and to provide control information

    Example
    GE-01
    97
    Number of Transaction Sets Included
    Required
    Numeric (N0)
    Min 1Max 6

    Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

    GE-02
    28
    Group Control Number
    Required
    Numeric (N0)
    Min 1Max 9

    Assigned number originated and maintained by the sender

    Interchange Control Trailer

    RequiredMax use 1

    To define the end of an interchange of zero or more functional groups and interchange-related control segments

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Numeric (N0)
    Min 1Max 5

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

    IEA-02
    I12
    Interchange Control Number
    Required
    Numeric (N0)
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample 1

    ST*204*0001~
    B2**COSU**FLEX-544899A-794441**CC~
    B2A*21~
    L11*COSU6214910444*BM~
    L11*0PG43E4*V3~
    L11*CMA CGM LA SCALA*ABS~
    L11*COSU6214910444*BN~
    L11*CNNGB*4B~
    L11*USHOU*4C~ L11**ZZ*c3e2109a7763df527c7b44926461a930~ L11*20190716170000*ETA~
    AT5*IP~
    N1*BT*FLEXPORT INTERNATIONAL LLC~
    N3*760 MARKET ST FLOOR 8~
    N4*SAN FRANCISCO*CA*94106*US~
    N1*SF*BAYPORT CONTAINER TERMINAL~
    N3*12619 PORT ROAD FIRMS: V136~ N4*PASADENA*TX*77586*US~
    N1*ST*PLEASE HOLD THIS UNTIL FURTHER NOTICE~
    N3*528 BAY AREA BLVD FIRMS:~
    N4*WEBSTER*TX*77598~ N7*TEMU*804774*30605*G*******CN****4500**K*5****L5G1~ M7*10944426~
    S5*1*PA~
    S5*2*UL~
    SE*26*0001~

    Sample 2

    ST*204*0001~
    B2**COSU**FLEX-510619A-802060**CC~
    B2A*01~
    L11*COSU6205729800*BM~
    L11*039E*V3~
    L11*COSCO ISTANBUL*ABS~
    L11*6205461100*BN~
    L11*CNYTN*4B~
    L11*USHOU*4C~
    L11**ZZ*d5ce972953af48a1c3b419505bd95ae9~
    L11*20190717160000*ETA~
    AT5*IP~
    N1*BT*FLEXPORT INTERNATIONAL LLC~
    N3*760 MARKET ST FLOOR 8~
    N4*SAN FRANCISCO*CA*94106*US~
    N1*SF*PORT OF HOUSTON AUTHORITY BARBOURS~
    N3*1515 E BARBOURS CUT BLVD FIRMS: S787~
    N4*LA PORTE*TX*77571*US~
    N1*ST*Misc Retailers~
    N3*528 Bay Area Blvd FIRMS:~
    N4*Webster*TX*77598*US~ N7*TGHU*698819*9560*G*******CN****4000**K*5****45G1~
    M7*11515100~
    S5*1*PA~
    NTE*APN*DELIVERY NOTES Facility can accept 1 container / day. Please pr~ NTE*APN*e-pull / space out shipments as needed. Please include liftgate.~ S5*2*UL~
    SE*28*0001~

    Sample 3

    ST*204*0001~
    B2**MAEU**FLEX-520057A-780217**CC~
    B2A*00~
    L11*MAEU962007188*BM~
    L11*086E*V3~
    L11*HYUNDAI BANGKOK*ABS~
    L11*969207008*BN~
    L11*TWTXG*4B~
    L11*USHOU*4C~ L11**ZZ*91541006ee29f9cb9d4e9441e926a65d~ L11*20190722070000*ETA~
    AT5*IP~
    N1*BT*FLEXPORT INTERNATIONAL LLC~
    N3*760 MARKET ST FLOOR 8~
    N4*SAN FRANCISCO*CA*94106*US~
    N1*SF*SANTA FE RAMP~
    N3*214 BRISBANE ST FIRMS: S639~ N4*HOUSTON*TX*77061*US~
    N1*ST*Misc Retailers~
    N3*528 Bay Area Blvd FIRMS:~
    N4*Webster*TX*77598*US~ N7*HASU*496163*11285*G*******CN****4000**K*5****45G1~ M7*ML-TW2320085~
    S5*1*PA~
    S5*2*UL~
    SE*26*0001~

    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.