Toyota Motor Manufacturing
/
Planning Schedule with Release Capability
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Toyota Motor Manufacturing. Contact Toyota Motor Manufacturing for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Toyota Motor Manufacturing logo

X12 830 Planning Schedule with Release Capability

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with Release Capability Transaction Set (830) for use within the context of an Electronic Data Interchange (EDI) environment.
The transaction set can be used to provide for customary and established business practice relative to the transfer of forecasting/material release information between organizations.

The planning schedule transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in "buckets," such as weekly, monthly, or quarterly. The order release forecast may also contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders.

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-manufacturing/planning-schedule-with-release-capability/01HPHWY4AXDANYHTKXB2ZHYQC2
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
BFR
020
Beginning Segment for Planning Schedule
Max use 1
Required
N1 Loop Contracted Service Provider
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
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 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
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 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
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

00400
Standard Issued as ANSI X12.5-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
Identifier (ID)

Code identifying a group of application related transaction sets

PS
Planning Schedule with Release Capability (830)
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

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

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

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
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).
830
Planning Schedule with Release Capability
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

BFR
020
Heading > BFR

Beginning Segment for Planning Schedule

RequiredMax use 1

To indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast; and related forecast envelope dates

Example
At least one of Reference Identification (BFR-02) or Release Number (BFR-03) is required
BFR-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

  • If BFR01 contains the value "04" (Net Change), BFR09 is required.
00
Original
BFR-02
127
Reference Identification
Optional
String (AN)

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

  • BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.
C
D
BFR-03
328
Release Number
Optional
String (AN)

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

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

DL
Delivery Based
BFR-05
676
Schedule Quantity Qualifier
Required
Identifier (ID)

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

A
Actual Discrete Quantities
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BFR06 is the forecast horizon start date: The date when the forecast horizon (envelope) begins.
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends.
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BFR08 is the date forecast generated: The date the forecast data was generated.
N1 Loop Contracted Service Provider
RequiredMax >1
N1
230
Heading > N1 Loop Contracted Service Provider > 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)
Min 2Max 3

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

Usage notes
  1. This Segment Is Not Used By TMMK
  2. Will Only Send Code MI
Required
String (AN)

Free-form name

TABC
TMMAL
TMMBC
TMMI
TMMK
TMMMS
TMMNA
TMMNK
TMMTX
TMMWV
N1 Loop Contracted Service Provider end
N1 Loop Foreign Supplier
RequiredMax 1
N1
235
Heading > N1 Loop Foreign Supplier > N1

Name

RequiredMax use 1

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

Example
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

Usage notes
  1. 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.
  2. N105 and N106 further define the type of entity in N101.
SU
Supplier/Manufacturer
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes
  1. This Segment Is Not Used By TMMK
  2. Will Only Send Code MI
N1-03
66
Identification Code Qualifier
Optional
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
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

Usage notes

Send supplier code by TMM

N1 Loop Foreign Supplier 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
If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
LIN-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

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

Identifying number for a product or service

Usage notes

The LIN03 Element As Found Here Will Be Used In The PRF01 Element of The 856 Transaction.
The First 8 Bytes Of The LIN03 Will Be Used In The REF02 Element Of The
810 Transaction.

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

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

Usage notes

Not Sent For TMMNA Export Parts

RC
Returnable Container Number
LIN-05
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Not Sent For TMMNA Export Parts

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

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

ZZ
Mutually Defined
LIN-07
234
Product/Service ID
Optional
String (AN)

Identifying number for a product or service

A
SCHEDULE ORDER
B
SEQUENCED ORDER
C
KANBAN ORDER
D
EKANBAN ORDER
UIT
020
Detail > LIN Loop > UIT

Unit Detail

RequiredMax use 1

To specify item unit data

Example
UIT-01
C001
Composite Unit of Measure
RequiredMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-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
PID
080
Detail > LIN Loop > PID

Product/Item Description

RequiredMax use 1000

To describe a product or process in coded or free-form format

Example
PID-01
349
Item Description Type
Required
Identifier (ID)

Code indicating the format of a description

  • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
Usage notes

This Segment Is Not Used By TMMK.

F
Free-form
PID-05
352
Description
Optional
String (AN)
Min 1Max 80

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

PO4
120
Detail > LIN Loop > PO4

Item Physical Details

RequiredMax use 1

To specify the physical qualities, packaging, weights, and dimensions relating to the item

Example
Optional
Numeric (N0)
Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

PRS
130
Detail > LIN Loop > PRS

Part Release Status

RequiredMax use 1

To indicate the status of the part being ordered or forecast with respect to this material release or planning document

Example
PRS-01
682
Part Release Status Code
Required
Identifier (ID)

Code identifying the status of the specific part number being released or forecast or being used in an engineering change

Usage notes

This Segment Is Not Sent For TMMNA Export Parts

1
Non-Carryover
4
Carryover
5
New Item
REF
140
Detail > LIN Loop > REF

Reference Identification

RequiredMax use 12

To specify identifying information

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

Code qualifying the Reference Identification

Usage notes

IF REF-01 = DK:

  1. This Segment Is Not Sent For TMMNA Export Parts
  2. The Dock Code Will Be Used In the IT111 Element Of The 810
    Transaction.

IF REF-01 = LU:

  1. This Segment Is Not Sent For TMMNA Export Parts
    or TMMK.

IF REF-01 = MR:

  1. This Segment Is Not Sent For TMMNA Export Parts Or TMMK
DK
Dock Number
LU
Location Number
MR
Merchandise Type Code
REF-02
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

Usage notes

IF REF-01 = MR:
Toyota Card Code.

The REF02 Element Will Be Used In The IT101 Element Of The 810
Transaction.

PER
150
Detail > LIN Loop > PER

Administrative Communications Contact

RequiredMax use 3

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

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

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

Usage notes

This Segment Is Not Sent for TMMNA Export Parts.

SC
Schedule Contact
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

Name of TMM's specialist in P/C

PER-03
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

TE
Telephone
PER-04
364
Communication Number
Optional
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

Usage notes

Tele # of TMM's specialist in P/C

TD5
250
Detail > LIN Loop > TD5

Carrier Details (Routing Sequence/Transit Time)

RequiredMax use 12

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

Example
If Location Qualifier (TD5-07) is present, then Location Identifier (TD5-08) is required
If Identification Code Qualifier (TD5-02) is present, then Identification Code (TD5-03) is required
At least one of Identification Code Qualifier (TD5-02), Transportation Method/Type Code (TD5-04), Routing (TD5-05) or Shipment/Order Status Code (TD5-06) is required
TD5-01
133
Routing Sequence Code
Optional
Identifier (ID)

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

Usage notes
  1. Not Sent For Parts And Components.
    This Segment Will Only Appear If There Is A Sub-Route.
    This Segment Is Not Used By TMMK
  2. Not Sent For TMMNA Export Parts
1
1st Carrier after Origin Carrier
TD5-02
66
Identification Code Qualifier
Optional
Identifier (ID)
Min 1Max 2

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

  • When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
TD5-03
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

TD5-04
91
Transportation Method/Type Code
Optional
Identifier (ID)

Code specifying the method or type of transportation for the shipment

ZZ
Mutually defined
TD5-05
387
Routing
Optional
String (AN)
Min 1Max 35

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

TD5-06
368
Shipment/Order Status Code
Optional
Identifier (ID)
Min 2Max 2

Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction

TD5-07
309
Location Qualifier
Optional
Identifier (ID)

Code identifying type of location

Usage notes

Not Sent For TMMNA Export Parts.
This Segment Is Optional. It Will Only Appear If There Is A
Sub-Route.

DE
Destination (Shipping)
IT
Intermediate FOB Point
TD5-08
310
Location Identifier
Optional
String (AN)
Min 1Max 30

Code which identifies a specific location

Usage notes

Sub-route cross dock code OR Main route code.

Not Sent For TMMNA Export Parts.
This Segment Is Optional. It Will Only Appear If There Is A
Sub-Route.

SDP Loop
RequiredMax >1
SDP
450
Detail > LIN Loop > SDP Loop > SDP

Ship/Delivery Pattern

RequiredMax use 1

To identify specific ship/delivery requirements

Example
SDP-01
678
Ship/Delivery or Calendar Pattern Code
Required
Identifier (ID)

Code which specifies the routine shipments, deliveries, or calendar pattern

Usage notes

This Segment Is Not Sent For TMMNA Export Parts.

N
As Directed
SDP-02
679
Ship/Delivery Pattern Time Code
Required
Identifier (ID)

Code which specifies the time for routine shipments or deliveries

F
As Directed
FST
460
Detail > LIN Loop > SDP Loop > FST

Forecast Schedule

RequiredMax use 260

To specify the forecasted dates and quantities

Example
If either Date/Time Qualifier (FST-06) or Time (FST-07) is present, then the other is required
If either Reference Identification Qualifier (FST-08) or Reference Identification (FST-09) is present, then the other is required
FST-01
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

Usage notes

BUILD OUT Quantities Will Always Be In The FST Segment Between The FIRM And FORECAST Segments For A Part Number.

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
D
Pre-Notice OR Build Out
FST-03
681
Forecast Timing Qualifier
Required
Identifier (ID)

Code specifying interval grouping of the forecast

  • If FST03 equals "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.
Usage notes
  1. The Only Codes That Will Be Sent Are:
    D - “DAILY”
    W - “WEEKLY”
    F - “BUILD OUT”
D
Daily
F
Build Out
W
Weekly
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

FST05 Date Value Descriptions:

If FST02 is “FIRM” Then This Date Represents "Will Be Blank"
If FST02 is “PRE-NOTICE” Then This Date Represents "Last Workday Of Week"
If FST02 is “BUILD OUT” Then This Date Represents "Will Be Value 19910816"
If FST02 is “TMMNA EXPORT PARTS” Then This Date Represents "Due Date"

FST-06
374
Date/Time Qualifier
Optional
Identifier (ID)

Code specifying type of date or time, or both date and time

  • FST06 qualifies the time in FST07. The purpose of the FST07 element is to express the specific time of day in a 24-hour clock to satisfy "just-in-time" requirements. As an alternative, the ship/delivery pattern segment (SDP) may be used to define an approximate time, such as a.m. or p.m.
Usage notes

Will Only Send For FIRM Orders

010
Requested Ship
Optional
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)

Usage notes

Will Only Send For FIRM Orders

FST-08
128
Reference Identification Qualifier
Optional
Identifier (ID)

Code qualifying the Reference Identification

DO
Pre-Notice
MA
Firm Or Build-Out
FST-09
127
Reference Identification
Optional
String (AN)
Min 4Max 30

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

Usage notes
  1. Format Will Be In The Form Of:
    XXXXXXXX-ZZZZZZZZ – Where XXXXXXXX Is The Manifest Number, And ZZZZZZZZ Is The Receiver Number, Separated By A Dash (-). The Manifest Number Is Always Listed First. Or YYWW – Where YY Is The Year, And WW Is The Week.
  2. The FST09 Element, For FIRM Orders Only, Will Be Used In The PRF01 Element Of The 856 Transaction. The First 8 Characters Of The FST09 Element Will Be Used In The REF02 Element Of The 810 Transaction.
  3. For TMMK Only, Will Only Contain Either The Manifest Number Or The Year/Week.
  4. BUILD OUT Quantities Will Always Be In The FST Segment Between The FIRM And FORECAST Segments For A Part Number.
SDP Loop end
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

  • Number of line items (CTT01) is the accumulation of the number of LIN segments.
    If used, hash total (CTT02) is the sum of the values 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

CTT-02
347
Hash Total
Optional
Decimal number (R)
Min 1Max 10

Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

## Example:
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.

1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.

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.