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

X12 862 Shipping Schedule

X12 Release 3040

This Draft Standard for Trial Use contains the format and establishes the data contents of the Shipping Schedule Transaction Set (862) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a customer to convey precise shipping schedule requirements to a supplier, and is intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will supersede certain shipping and delivery information transmitted in a previous planning schedule transaction, but it does not replace the 830 transaction set. The shipping schedule transaction set shall not be used to authorize labor, materials or other resources.

The use of this transaction set will facilitate the practice of Just-In-Time (JIT) manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the issuance of a planning schedule transaction, e.g., daily shipping schedules versus weekly planning schedules. The shipping schedule transaction also provides the ability for a customer location to issue shipping requirements independent of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization.

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/toyota-motor-sales/shipping-schedule/01HRZ4H5EGYY1TGTJV856439MC
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
BSS
020
Beginning Segment For Shipping Schedule/Production Sequence.
Max use 1
Required
N1 Loop Buying Party (Purchaser)
N1 Loop Customer Name
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 one or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

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 sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier.

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

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 sender or the data in the interchange. The type of information is set by the Security Information Qualifier.

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 number 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
Date (DT)
YYMMDD format

Date of the interchange.

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange.

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
Identifier (ID)

This version number covers the interchange control segments.

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

This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.

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

Code sent by the sender to request an interchange acknowledgment.

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

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

P
Production Data
T
Test Data
ISA-16
I15
Subelement Separator
Required
String (AN)
Min 1Max 1

This is a field reserved for future expansion in separating data element subgroups. (In the interest of a migration to international standards, this must be different from the data element separator).

>
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
Identifier (ID)

Code identifying a group of application related Transaction Sets.

SS
Shipping Schedule (862)
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
Date (DT)
YYMMDD format

Date (YYMMDD).

GS-05
337
Time
Required
Time (TM)
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
String (AN)

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.

003040
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1993

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
Identifier (ID)

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).
862
X12.37 Shipping Schedule
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

BSS
020
Heading > BSS

Beginning Segment For Shipping Schedule/Production Sequence.

RequiredMax use 1

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

Example
BSS-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set.

00
Original
BSS-02
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

  • Use BSS02 to indicate a document number.
Usage notes

TMS purchase order number.

BSS-03
373
Date
Required
Date (DT)
YYMMDD format

Date (YYMMDD).

  • Use BSS03 to indicate the date of this document.
BSS-04
675
Schedule Type Qualifier
Required
Identifier (ID)

Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast.

SH
Shipment Based
BSS-05
373
Date
Required
Date (DT)
YYMMDD format

Date (YYMMDD).

  • Use BSS05 to indicate the schedule horizon start date (the date when the schedule begins.)
BSS-06
373
Date
Required
Date (DT)
YYMMDD format

Date (YYMMDD).

  • Use BSS06 to indicate the schedule horizon end date (the date when the schedule ends.)
BSS-07
328
Release Number
Required
String (AN)
Min 1Max 30

Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.

Usage notes

TMS Purchase order number.

BSS-11
676
Schedule Quantity Qualifier
Required
Identifier (ID)

Code identifying the type of quantities used when defining a schedule or forecast.

A
Actual Discreet Quantities
N1 Loop Buying Party (Purchaser)
RequiredMax 1
Usage notes

The first 3 iterations of this segment are mandatory. The fourth iteration is optional and can occur only in case of direct-ship orders.

Variants (all may be used)
N1 Loop Customer NameN1 Loop Ship ToN1 Loop Supplier/Manufacturer
N1
050
Heading > N1 Loop Buying Party (Purchaser) > N1

Name

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

BY
Buying Party (Purchaser)
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
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

If N101 = BY:
TMS assigned supplier code.

N2
060
Heading > N1 Loop Buying Party (Purchaser) > N2

Additional Name Information

OptionalMax use 2

To specify additional names or those longer than 35 characters in length

Example
N2-01
93
Name
Required
String (AN)
Min 1Max 35

Free-form name.

Usage notes

Dealer Name

N2-02
93
Name
Required
String (AN)
Min 1Max 35

Free-form name.

Usage notes

Dealer Street Address

N4
080
Heading > N1 Loop Buying Party (Purchaser) > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
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
Required
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 USA or Canada.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 9

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

REF
090
Heading > N1 Loop Buying Party (Purchaser) > REF

Reference Numbers

OptionalMax use 12

To specify identifying numbers.

Example
REF-01
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

CR
Customer Reference Number
REF-02
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

Usage notes

Dealer/distributor order number.

N1 Loop Buying Party (Purchaser) end
N1 Loop Customer Name
OptionalMax 1
Usage notes

The first 3 iterations of this segment are mandatory. The fourth iteration is optional and can occur only in case of direct-ship orders.

N1
050
Heading > N1 Loop Customer Name > N1

Name

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

MA
Customer Name
N1-02
93
Name
Required
String (AN)
Min 1Max 35

Free-form name.

Usage notes

Identifies the customer name (if available) in case of direct-ship orders only.

N2
060
Heading > N1 Loop Customer Name > N2

Additional Name Information

OptionalMax use 2

To specify additional names or those longer than 35 characters in length

Example
N2-01
93
Name
Required
String (AN)
Min 1Max 35

Free-form name.

Usage notes

Dealer Name

N2-02
93
Name
Required
String (AN)
Min 1Max 35

Free-form name.

Usage notes

Dealer Street Address

N4
080
Heading > N1 Loop Customer Name > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
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
Required
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 USA or Canada.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 9

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

REF
090
Heading > N1 Loop Customer Name > REF

Reference Numbers

OptionalMax use 12

To specify identifying numbers.

Example
REF-01
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

CR
Customer Reference Number
REF-02
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

Usage notes

Dealer/distributor order number.

N1 Loop Customer Name end
N1 Loop Ship To
RequiredMax 1
Usage notes

The first 3 iterations of this segment are mandatory. The fourth iteration is optional and can occur only in case of direct-ship orders.

N1
050
Heading > N1 Loop Ship To > N1

Name

RequiredMax use 1

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

Usage notes

The field will contain “DIRECT SHIP” in case of a direct-ship/VOR order.

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

Usage notes

The field will contain “DIRECT SHIP” in case of a direct-ship/VOR order.

ST
Ship To
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)

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

If N101 = ST:
In case of a direct ship/VOR order, this field will contain the dealer code.

51
Ontario
KY
Kentucky
N2
060
Heading > N1 Loop Ship To > N2

Additional Name Information

OptionalMax use 2

To specify additional names or those longer than 35 characters in length

Example
N2-01
93
Name
Required
String (AN)
Min 1Max 35

Free-form name.

Usage notes

Dealer Name

N2-02
93
Name
Required
String (AN)
Min 1Max 35

Free-form name.

Usage notes

Dealer Street Address

N4
080
Heading > N1 Loop Ship To > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
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
Required
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 USA or Canada.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 9

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

REF
090
Heading > N1 Loop Ship To > REF

Reference Numbers

OptionalMax use 12

To specify identifying numbers.

Example
REF-01
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

CR
Customer Reference Number
REF-02
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

Usage notes

Dealer/distributor order number.

N1 Loop Ship To end
N1 Loop Supplier/Manufacturer
RequiredMax 1
Usage notes

The first 3 iterations of this segment are mandatory. The fourth iteration is optional and can occur only in case of direct-ship orders.

N1
050
Heading > N1 Loop Supplier/Manufacturer > N1

Name

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

SU
Supplier/Manufacturer
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
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

If N101 = SU:
TMS assigned vendor code.

N2
060
Heading > N1 Loop Supplier/Manufacturer > N2

Additional Name Information

OptionalMax use 2

To specify additional names or those longer than 35 characters in length

Example
N2-01
93
Name
Required
String (AN)
Min 1Max 35

Free-form name.

Usage notes

Dealer Name

N2-02
93
Name
Required
String (AN)
Min 1Max 35

Free-form name.

Usage notes

Dealer Street Address

N4
080
Heading > N1 Loop Supplier/Manufacturer > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
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
Required
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 USA or Canada.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 9

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

REF
090
Heading > N1 Loop Supplier/Manufacturer > REF

Reference Numbers

OptionalMax use 12

To specify identifying numbers.

Example
REF-01
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

CR
Customer Reference Number
REF-02
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

Usage notes

Dealer/distributor order number.

N1 Loop Supplier/Manufacturer end
Heading end

Detail

LIN Loop
RequiredMax >1
LIN
010
Detail > LIN Loop > LIN

Item Identification

RequiredMax use 1

To specify basic item identification data.

Example
LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

  • LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
BP
Buyer's Part Number
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

Usage notes

TMS part number.

LIN-04
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

PD
Part Number Description
LIN-05
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

Usage notes

Part description

LIN-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

PL
Purchaser's Order Line Number
LIN-07
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

Usage notes

Line item number

LIN-08
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

PO
Purchase Order Number
LIN-09
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

Usage notes

Purchase order number

UIT
020
Detail > LIN Loop > UIT

Unit Detail

RequiredMax use 1

To specify item unit data

Example
UIT-01
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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

PC
Piece
REF
050
Detail > LIN Loop > REF

Reference Numbers

RequiredMax use 12

To specify identifying numbers.

Example
REF-01
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

WS
Warehouse storage location number
REF-02
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

Usage notes

Home position of the part at the warehouse.

FST Loop
RequiredMax >1
FST
080
Detail > LIN Loop > FST Loop > FST

Forecast Schedule

RequiredMax use 1

To specify the forecasted dates and quantities

Example
FST-01
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity.

Usage notes

Scheduled quantity for this shipment date.

FST-02
680
Forecast Qualifier
Required
Identifier (ID)

Code specifying the sender's confidence level of the forecast data or an action associated with a forecast

  • As qualified by FST02 and FST03, FST04 represents either a discrete forecast date, the first date of a forecasted bucket (weekly, monthly, quarterly, etc.) or the start date of a flexible interval.
C
Firm
FST-03
681
Forecast Timing Qualifier
Required
Identifier (ID)

Code specifying interval grouping of the forecast.

  • If FST03 - "F" (indicating flexible interval), then FST04 and FST05 are required. FST04 would be used for the start date of the flexible interval and FST05 would be used for the end date of the flexible interval.
D
Specified in contract
FST-04
373
Date
Required
Date (DT)
YYMMDD format

Date (YYMMDD).

FST Loop end
TD5
180
Detail > LIN Loop > TD5

Carrier Details (Routing Sequence/Transit Time)

RequiredMax use 1

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

Example
TD5-01
133
Routing Sequence Code
Required
Identifier (ID)

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

B
Origin/Delivery Carrier (Any Mode)
TD5-04
91
Transportation Method/Type Code
Required
Identifier (ID)

Code specifying the method or type of transportation for the shipment.

A
Air
D
Parcel Post
M
Motor (Common Carrier)
R
Rail
VE
Vessel, Ocean
LIN Loop end
Detail end

Summary

CTT
010
Summary > CTT

Transaction Totals

RequiredMax use 1

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

  • The number of lines items (CTT01) is the accumulation of number of LIN segments. If used, hash total (CTT02) is the sum of the value of the quantities (FST01) for each FST segment.
Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set.

Usage notes

Number of LIN segments

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 one 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 a transmission.

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

This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.

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.