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

X12 204 Motor Carrier Load Tender

X12 Release 4010

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
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/red-classic/motor-carrier-load-tender/01H0FG53PQFZPP3GXZVWZBR11J
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
Required
G62
090
Must Respond By
Max use 1
Optional
G62
090
Requested Delivery Date
Max use 1
Optional
G62
090
Requested Ship Date/Pick-up Date
Max use 1
Optional
0100 Loop
detail
0300 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
Optional
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.
Usage notes

Receiver SCAC code.

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
DF
Defined by Buyer and Seller
NC
Service Freight, No Charge
PP
Prepaid (by Seller)
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

1
Original
2
Cancellation
4
Change
5
Replace
6
Confirmation
B2A-02
346
Application Type
Optional

Code identifying an application

LT
Load Tender - Truckload (TL) Carrier Only

Used by a shipper to inform carrier that a particular load is available or becoming available for movement; also signifies an advance pick-up notification.

L11
080
Heading > L11

Business Instructions and Reference Number

RequiredMax use 50

To specify instructions in this business relationship or a reference number

Example
L11-01
127
Reference Identification
Required
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
Required

Code qualifying the Reference Identification

BM
Bill of Lading Number
PO
Purchase Order Number
SI
Shipper's Identifying Number for Shipment (SID)

A unique number (to the shipper) assigned by the shipper to identify the shipment.

ZZ
Order Identifier

Will be sent and must be returned on 990 Load Tender Response in the N9 CN segment and 214 Shipment Status in the Header L11 ZZ segment.

G62
090
Heading > G62

Must Respond By

OptionalMax use 1

To specify pertinent dates and times

  • Segment G62 in header is used to convey the must-respond-by date and time when responding to a 204 transaction.
Example
If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
G62-01
432
Date Qualifier
Required

Code specifying type of date

64
Must Respond By
G62-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

G62-03
176
Time Qualifier
Optional

Code specifying the reported time

1
Must Respond By
G62-04
337
Time
Optional
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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

Usage notes

Time format at header level only will be sent as HHMM

G62
090
Heading > G62

Requested Delivery Date

OptionalMax use 1

To specify pertinent dates and times

  • Segment G62 in header is used to convey the must-respond-by date and time when responding to a 204 transaction.
Example
If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
G62-01
432
Date Qualifier
Required

Code specifying type of date

68
Requested Delivery Date
G62-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

G62-03
176
Time Qualifier
Optional

Code specifying the reported time

Z
Requested Delivery Time
G62-04
337
Time
Optional
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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

Usage notes

Time format at header level only will be sent as HHMM

G62
090
Heading > G62

Requested Ship Date/Pick-up Date

OptionalMax use 1

To specify pertinent dates and times

  • Segment G62 in header is used to convey the must-respond-by date and time when responding to a 204 transaction.
Example
If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
G62-01
432
Date Qualifier
Required

Code specifying type of date

10
Requested Ship Date/Pick-up Date
G62-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

G62-03
176
Time Qualifier
Optional

Code specifying the reported time

Y
Requested Pick Up Time
G62-04
337
Time
Optional
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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

Usage notes

Time format at header level only will be sent as HHMM

0100 Loop
OptionalMax >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
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

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

Free-form name

N1-03
66
Identification Code Qualifier
Optional

Code designating the system/method of code structure used for Identification Code (67)

ZZ
Location ID
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 17

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

Location ID (2 to 17 alphanumeric).

N3
160
Heading > 0100 Loop > N3

Address Information

OptionalMax use 2

To specify the location of the named party

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

Address information

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

Address information

N4
170
Heading > 0100 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

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

Free-form text for city name

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

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

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

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

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

Code identifying the country

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

CN
General Contact
SH
Shipper Contact
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

Usage notes

Phone Number no dashes.

0100 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
If either Weight (S5-03) or Weight Unit Code (S5-04) is present, then the other is required
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
CU
Complete Unload
LD
Load
PL
Part Load
PU
Part Unload
UL
Unload
S5-03
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

S5-04
188
Weight Unit Code
Optional

Code specifying the weight unit

L
Pounds
S5-07
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

L11
020
Detail > 0300 Loop > L11

Business Instructions and Reference Number

OptionalMax use 50

To specify instructions in this business relationship or a reference number

Example
If either Reference Identification (L11-01) or Reference Identification Qualifier (L11-02) is present, then the other 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

ZZ
Order Identifier

Will be sent and must be returned on 214 Shipment Status in the stop detail L11 ZZ segment.

G62
030
Detail > 0300 Loop > G62

Earliest Pickup Date

OptionalMax use 1

To specify pertinent dates and times

  • Use G62 segment either in loop 0300 or loop 0350, but not both.
Example
Variants (all may be used)
G62Estimated Delivery Date
If either Date Qualifier (G62-01) or Date (G62-02) is present, then the other is required
If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
G62-01
432
Date Qualifier
Required

Code specifying type of date

EP
Earliest Pickup Date
G62-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

G62-03
176
Time Qualifier
Optional

Code specifying the reported time

W
Effective Time
G62-04
337
Time
Optional
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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

Usage notes

Time format at detail level will be sent as HHMMSS.

G62
030
Detail > 0300 Loop > G62

Estimated Delivery Date

OptionalMax use 1

To specify pertinent dates and times

  • Use G62 segment either in loop 0300 or loop 0350, but not both.
Example
Variants (all may be used)
G62Earliest Pickup Date
If either Date Qualifier (G62-01) or Date (G62-02) is present, then the other is required
If either Time Qualifier (G62-03) or Time (G62-04) is present, then the other is required
G62-01
432
Date Qualifier
Required

Code specifying type of date

17
Estimated Delivery Date
G62-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

G62-03
176
Time Qualifier
Optional

Code specifying the reported time

W
Effective Time
G62-04
337
Time
Optional
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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

Usage notes

Time format at detail level will be sent as HHMMSS.

AT8
040
Detail > 0300 Loop > AT8

Shipment Weight, Packaging and Quantity Data

OptionalMax use 1

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

  • Segment AT8 in loop 0300 is intended for the transmitting of total weight, quantity, and volume relative to the specific stop-off. Should weight, quantity, and volume also be sent in segment AT8 in loop 0320 and tied to commodity detail, then the accumulated amounts of weight, quantity, and volume in the AT8 segment in loop 0320 should equal the amounts in the single AT8 occurrence in loop 0300.
Example
If either Weight Qualifier (AT8-01), Weight Unit Code (AT8-02) or Weight (AT8-03) are present, then the others are 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

L
Pounds
AT8-03
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

AT8-04
80
Lading Quantity
Optional
Numeric (N0)
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.
0310 Ship From
OptionalMax 1
Variants (all may be used)
Ship To
N1
070
Detail > 0300 Loop > Ship From > N1

Name

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required

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

SF
Ship From
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N3
090
Detail > 0300 Loop > Ship From > N3

Address Information

OptionalMax use 2

To specify the location of the named party

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

Address information

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

Address information

N4
100
Detail > 0300 Loop > Ship From > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

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

Free-form text for city name

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

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

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

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

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

Code identifying the country

0310 Ship From end
0310 Ship To
OptionalMax 1
Variants (all may be used)
Ship From
N1
070
Detail > 0300 Loop > Ship To > N1

Name

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required

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

ST
Ship To
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N3
090
Detail > 0300 Loop > Ship To > N3

Address Information

OptionalMax use 2

To specify the location of the named party

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

Address information

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

Address information

N4
100
Detail > 0300 Loop > Ship To > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

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

Free-form text for city name

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

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

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

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

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

Code identifying the country

0310 Ship To end
0300 Loop end
Detail end

Summary

L3
010
Summary > L3

Total Weight and Charges

OptionalMax use 1

To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items

Example
If either Weight (L3-01) or Weight Qualifier (L3-02) is present, then the other is required
L3-01
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

L3-02
187
Weight Qualifier
Optional

Code defining the type of weight

G
Gross Weight
L3-11
80
Lading Quantity
Optional
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

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

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.