2.6 862 Shipping Schedule: Scope

2.
6 862 Shipping Schedule

INFORMATION TMM REQUIRES FROM TRADING PARTNER
SCOPE THIS INFORMATION INCLUDES START-UP INFORMATION SPECIFIC TO TRADING

PARTNER.
APPROACH THE FOLLOWING INFORMATION WILL BE REQUIRED BEFORE THE TRADING

PARTNER CAN COMPLETE CERTIFICATION TO EXCHANGE INFORMATION WITH
TMM.
1. PRIMARY CONTACT NAME, ADDRESS, AND NUMBER
2. ALTERNATE CONTACT NAME, ADDRESS, AND TELEPHONE NO.
3. PLANT NAME, ADDRESS, DUNS NUMBER
4. CONFIRM START-UP DATE
Toyota EDI Master Implementation Manual -1- Ver 1.4

DATA REQUIREMENTS
MISCELLANEOUS STANDARD: ANSI X12 - AIAG
EDI ACKNOWLEDGMENT FUNCTIONAL ACKNOWLEDGMENT – TMMK,

TMMI, TMMWV ALL EXPECT TO RECEIVE A
FUNCTIONAL ACKNOWLEDGMENT (997) IN
RESPONSE TO THE 862 BEING SENT TO THE
TRADING PARTNER. THE FUNTIONAL
ACKNOWLEDGMENT SHOULD BE GENERATED
AND SENT AT THE TRANSACTION LEVEL WITHIN
12 HOURS OF THE TIME THE SHIPPING SCHEDULE
LEFT TOYOTA.
DOCUMENTATION TMM WILL GIVE TRADING PARTNERS A MINIMUM
CHANGES OF FOUR WEEKS NOTICE BEFORE IMPLEMENTING
FORMAT CHANGES.
SEPARATORS FOR STERLING VAN CUSTOMERS AND THOSE

OTHERS NOT LISTED BELOW:
HEX VALUES:
SEGMENT : 65
ELEMENT : 64
SUB-ELEMENT : 66
FOR GEIS, ADVANTIS AND AT&T VAN

CUSTOMERS:
HEX VALUES:
SEGMENT : 5B OR “$”
ELEMENT : 5C OR “*”
SUB-ELEMENT : 7B OR “#”
WRAPPED ALL DATA WILL BE TRANSMITTED / RECEIVED IN

AN 80 BYTE RECORD LENGTH.
DATA FREQUENCY DAILY
VALUE ADDED NETWORK STERLING INFORMATION BROKER

(VAN) DIVISION OF SBC
4600 LAKEHURST CT.
P. O. BOX 7160
COLUMBUS, OH. 43017-0760
TOLL FREE NUMBERS FOR NETWORK

NON-STERLING CUSTOMERS: 800-688-3704
STERLING CUSTOMERS: 877-432-4300

HOW TO BECOME CERTIFIED
SCOPE BEFORE A TRADING PARTNER CAN DO PRODUCTION EDI WITH TMM, THEY MUST
BE CERTIFIED THAT THEY ARE COMPATIBLE WITH TMM'S EDI ENVIRONMENT.
APPROACH EVERY TRADING PARTNER MUST SHOW COMPATIBILITY WITH TMM’S:
1. NETWORK
2. COMMUNICATION SOFTWARE
3. DATA FORMAT
CERTIFICATION IS FORMALLY COMPLETED WHEN TMM'S INFORMATION SYSTEMS

SECTION HAS COMPLETED ALL NETWORK AND TRANSACTION TESTING.
TRANSACTION TESTING WILL NOT BE COMPLETE UNTIL EACH SUPPLIER

COMPLETES PARALLEL TESTING WITH TMM INVOLVING RECEIVING THE PAPER
MATERIAL RELEASE AND THE ORDER VIA EDI.
THE LENGTH OF THE PARALLEL TESTING WILL BE DETERMINED BY TMM.

GENERAL INFORMATION AND PROBLEM REPORTING
SCOPE INCLUDES TRADING PARTNERS PROBLEMS AND INQUIRIES CONCERNING

TMM’S MAILBOX, NETWORK, OR DATA FORMAT.
EDI SYSTEMS & NETWORK CONTROL
PROBLEMS INDICATED DURING TESTING &

CERTIFICATION
ALL INQUIRIES - COMMERCE NETWORK
PHONE: 1-877-401-7374

862 - Shipping Schedule
Functional Group= SS
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.
X12 ANSI REQUIREMENTS Ver. 4010 TOYOTA REQ.

Pos Id Segment Name Req Max Use Repeat Notes Usage
ISA Interchange Control Header M 1 Must use
GS Functional Group Header M 1 Must use
Heading:
010 ST Transaction Set Header M 1 Must use
020 BSS Beginning Segment for Shipping M 1 Must use
Schedule/Production Sequence
LOOP ID - N1 200
050 N1 Name O 1 Used
Detail:
LOOP ID - LIN 10000
010 LIN Item Identification M 1 Must use
020 UIT Unit Detail M 1 Must use
040 PO4 Item Physical Details O >1 Used
045 PRS Part Release Status O 1 Used
050 REF Reference Identification O 12 Used
060 PER Administrative Communications O 1 Used
Contact
070 SDP Ship/Delivery Pattern O 1 Used
LOOP ID - SHP 10
140 SHP Shipped/Received Information O 1 Used
180 TD5 Carrier Details (Routing O 1 Used
Sequence/Transit Time)
Summary:
010 CTT Transaction Totals O 1 N3/010 Used
020 SE Transaction Set Trailer M 1 Must use
GE Functional Group Trailer M 1 Must use
IEA Interchange Control Trailer M 1 Must use

ISA - Interchange Control Header Pos: Max: 1
Not Defined - Mandatory
Loop: N/A Elements: 16
User Option(Usage): Must use
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Element Summary:
Ref Id Element Name Req Type Min/Max Usage
ISA01 I01 Authorization Information Qualifier M ID 2/2 Must use
Description:
Code to identify the type of information in the
Authorization Information
Will Only Send Code 00
ISA02 I02 Authorization Information M AN 10/10 Must use
Description:
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)
Will Only Send Senders Name – “TOYOTA ”
ISA03 I03 Security Information Qualifier M ID 2/2 Must use
Description:
Code to identify the type of information in the Security
Information
Will only send code - 01
ISA04 I04 Security Information M AN 10/10 Must use
Description:
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)
Will Only Send Senders DUNS # (See Note 1)
ISA05 I05 Interchange ID Qualifier M ID 2/2 Must use
Description:
Qualifier to designate the system/method of code
structure used to designate the sender or receiver ID
element being qualified
ISA06 I06 Interchange Sender ID M AN 15/15 Must use
Description:
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
Will Only Send DUNS
ISA07 I05 Interchange ID Qualifier M ID 2/2 Must use
Description:
Qualifier to designate the system/method of code
structure used to designate the sender or receiver ID
element being qualified
Will Typically Send Code ZZ
ISA08 I07 Interchange Receiver ID M AN 15/15 Must use
Description:
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
Will typically send DUNS - Supplier Code
(i.e. 123456789-12345)
ISA09 I08 Interchange Date M DT 6/6 Must use
Description:
Date of the interchange
ISA10 I09 Interchange Time M TM 4/4 Must use
Description:

Time of the interchange
ISA11 I10 Interchange Control Standards Identifier M ID 1/1 Must use
Description:
Code to identify the agency responsible for the control
standard used by the message that is enclosed by the
interchange header and trailer
Will Only Send Code U
ISA12 I11 Interchange Control Version Number M ID 5/5 Must use
Description:
Code specifying the version number of the interchange
control segments
ISA13 I12 Interchange Control Number M N0 9/9 Must use
Description:
A control number assigned by the interchange sender
ISA14 I13 Acknowledgment Requested M ID 1/1 Must use
Description:
Code sent by the sender to request an interchange
acknowledgment (TA1)
Will Only Send 0 – “No”
ISA15 I14 Usage Indicator M ID 1/1 Must use
Description:
Code to indicate whether data enclosed by this
interchange envelope is test, production or information
Will Only Send Codes T,P – “Test” or “Production”
ISA16 I15 Component Element Separator M ID 1/1 Must use
Description:
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
Notes:
1. Valid Codes are:
TMM’S DUNS NUMBER:
961659588 - TEMA
107978962 - TMMAL
821678378 - TMMBC
002121064 - TMMI
161955380 - TMMK
781098897 - TMMNK
170114776 - TMMTX
965703366 - TMMWV

GS - Functional Group Header Pos: Max: 1
To indicate the beginning of a functional group and to provide control information
Element Summary:
GS01 479 Functional Identifier Code M ID 2/2 Must use
Description:
Code identifying a group of application related
transaction sets
Only use code SS – “Remittance Advice”
GS02 142 Application Sender's Code M AN 2/15 Must use
Description:
Code identifying party sending transmission; codes
agreed to by trading partners
Will Only Send Senders DUNS (See Note 1)
GS03 124 Application Receiver's Code M AN 2/15 Must use
Description:
Code identifying party receiving transmission; codes
agreed to by trading partners
Will Send Receivers DUNS
GS04 373 Date M DT 8/8 Must use
Description:
Date expressed as CCYYMMDD
GS05 337 Time M TM 4/8 Must use
Description:
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)
GS06 28 Group Control Number M N0 1/9 Must use
Description:
Assigned number originated and maintained by the
sender
GS07 455 Responsible Agency Code M ID 1/2 Must use
Description:
Code identifying the issuer of the standard; this code is
used in conjunction with Data Element 480
Will Only Send Code X
GS08 480 Version / Release / Industry Identifier Code M AN 1/12 Must use
Description:
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

Semantics:
1. GS04 is the group date.
2. GS05 is the group time.
3. The data interchange control number GS06 in this header must be identical to the same data element in the associated
functional group trailer, GE02.
Comments:
1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar
transaction sets enclosed by a functional group header and a functional group trailer.
Notes:
1. Valid Codes are:
TMM’S DUNS NUMBER:
961659588 - TEMA
107978962 - TMMAL
821678378 - TMMBC
002121064 - TMMI
161955380 - TMMK
781098897 - TMMNK
170114776 - TMMTX
965703366 - TMMWV

ST - Transaction Set Header Pos: 010 Max: 1
Heading - Mandatory
To indicate the start of a transaction set and to assign a control number
Element Summary:
ST01 143 Transaction Set Identifier Code M ID 3/3 Must use
Description:
Code uniquely identifying a Transaction Set
All valid standard codes are used.
ST02 329 Transaction Set Control Number M AN 4/9 Must use
Description:
Identifying control number that must be unique within
the transaction set functional group assigned by the
originator for a transaction set
Semantics:
1. 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).
Toyota EDI Master Implementation Manual - 10 - Ver 1.4

BSS - Beginning Segment for Shipping Pos: 020 Max: 1
Heading - Mandatory
Schedule/Production Sequence Loop: N/A Elements: 11
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Element Summary:
BSS01 353 Transaction Set Purpose Code M ID 2/2 Must use
Description:
Code identifying purpose of transaction set
BSS02 127 Reference Identification M AN 1/30 Must use
Description:
Reference information as defined for a particular
Transaction Set or as specified by the Reference
Identification Qualifier
Will Only Send Value ORIGINAL
BSS03 373 Date M DT 8/8 Must use
Description:
Begin Date
BSS04 675 Schedule Type Qualifier M ID 2/2 Must use
Description:
Code identifying the type of dates used when defining a
shipping or delivery time in a schedule or forecast
Will Only Send Code DL
Description:
End Date
Description:
Generated Date
BSS07 328 Release Number X AN 1/30 Used
Description:
Number identifying a release against a Purchase Order
previously placed by the parties involved in the
transaction
Will Only Send Value 001
Semantics:
1. Use BSS02 to indicate a document number.
2. Use BSS03 to indicate the date of this document.
3. Use BSS05 to indicate the schedule horizon start date (the date when the schedule begins).
4. Use BSS06 to indicate the schedule horizon end date (the date when the schedule ends).

Pos: 050 Repeat: 200
Loop N1 Optional
Loop: N1 Elements: N/A
To identify a party by type of organization, name, and code
Loop Summary:
Pos Id Segment Name Req Max Use Repeat Usage
050 N1 Name O 1 Used

N1 - Name Pos: 050 Max: 1
Heading - Optional
Loop: N1 Elements: 6
User Option(Usage): Used
Element Summary:
N101 98 Entity Identifier Code M ID 2/3 Must use
Description:
Code identifying an organizational entity, a physical
location, property or an individual
Will Only Send Code MI
N102 93 Name X AN 1/60 Used
Description:
Free-form name
Refer To Notes 1,2
Syntax:
1. R0203 - At least one of N102,N103 is required
2. P0304 - If either N103,N104 is present, then all are required
Comments:
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.
Notes:
1. Valid Values Are:
TMMK
TMMI
TMMWV
2. This Element Is To Be Printed On The AIAG Label

N1 - Name Pos: 050 Max: 1
Heading - Optional
Loop: N1 Elements: 6
Element Summary:
N101 98 Entity Identifier Code M ID 2/3 Must use
Description:
Code identifying an organizational entity, a physical
location, property or an individual
Will Only Send Code SU
N102 93 Name X AN 1/60 Used
Description:
Free-form name
Suppliers Name; Refer To Note 1
N103 66 Identification Code Qualifier X ID 1/2 Used
Description:
Code designating the system/method of code structure
used for Identification Code (67)
N104 67 Identification Code X AN 2/80 Used
Description:
Code identifying a party or other code
Supplier Code Allotted by TMM; Refer To Note 1
Syntax:
1. R0203 - At least one of N102,N103 is required
2. P0304 - If either N103,N104 is present, then all are required
Comments:
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.
Notes:

Pos: 010 Repeat: 10000
Loop LIN Mandatory
Loop: LIN Elements: N/A
To specify basic item identification data
Loop Summary:
010 LIN Item Identification M 1 Must use
020 UIT Unit Detail M 1 Must use
040 PO4 Item Physical Details O >1 Used
045 PRS Part Release Status O 1 Used
060 PER Administrative Communications Contact O 1 Used
070 SDP Ship/Delivery Pattern O 1 Used
140 Loop SHP O 10 10 Used
180 TD5 Carrier Details (Routing Sequence/Transit Time) O 1 Used

Pos: 010 Max: 1
LIN - Item Identification Detail - Mandatory
Loop: LIN Elements: 31
To specify basic item identification data
Element Summary:
LIN01 350 Assigned Identification O AN 1/20 Not Used
Description:
Alphanumeric characters assigned for differentiation
within a transaction set
LIN02 235 Product/Service ID Qualifier M ID 2/2 Must use
Description:
Code identifying the type/source of the descriptive
number used in Product/Service ID (234)
Will Only Send Code BP – “Buyers Part Number”
LIN03 234 Product/Service ID M AN 1/48 Must use
Description:
Identifying number for a product or service
Buyers Part Number; Refer To Notes 1,2,3
LIN04 235 Product/Service ID Qualifier X ID 2/2 Used
Description:
Will Only Send Code RC
LIN05 234 Product/Service ID X AN 1/48 Used
Description:
LIN06 235 Product/Service ID Qualifier X ID 2/2 Used
Description:
Will Only Send Code ZZ
LIN07 234 Product/Service ID X AN 1/17 Used
Description:
Refer To Note 4
Syntax:
1. P0405 - If either LIN04,LIN05 is present, then all are required
2. P0607 - If either LIN06,LIN07 is present, then all are required
Notes:
2. The Part Number Does Not Have Any Imbedded Dashes Or Spaces
3. “NO SHIP” Is Valid In The LIN03 When There Is A Zero Quantity
4. Values That Will Be Sent Are:
'A- SCHEDULED ORDER'
'B- SEQUENCED ORDER'
'C -KANBAN ORDER'
‘D-EKANBAN ORDER’

Pos: 020 Max: 1
UIT - Unit Detail Detail - Mandatory
To specify item unit data
Element Summary:
UIT01 C001 Composite Unit of Measure M Comp Must use
Description:
To identify a composite unit of measure(See Figures
Appendix for examples of use)
Will Only Send Code PC – “Pieces”

PO4 - Item Physical Details Pos: 040 Max: >1
Detail - Optional
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Element Summary:
PO401 356 Pack O N0 1/6 Used
Description:
The number of inner containers, or number of eaches if
there are no inner containers, per outer container
This Element Is To Be Printed On The AIAG Label

PRS – Part Release Status Pos: 045 Max: 1
Detail - Optional
To indicate the status of the part being ordered or forecast with respect to this material release or planning document
Element Summary:
PRS01 682 Part Release Status Code M ID 1/2 Must use
Description:
Code identifying the status of the specific part number
being released or forecast or being used in an
engineering change
Refer To Notes 1
Notes:
1. Valid Codes Are:
1 – “Non-Carryover”
4 – “Carryover”
5 – “New Item”

Pos: 050 Max: 12
REF - Reference Identification Detail - Optional
To specify identifying information
Element Summary:
REF01 128 Reference Identification Qualifier M ID 2/3 Must use
Description:
Code qualifying the Reference Identification
Will Only Send Code DK
REF02 127 Reference Identification X AN 1/30 Used
Description:
Toyota Dock Code; Refer To Notes 1,2
Notes:
2. The Dock Code Will Be Used In The IT111 Element Of The 810 Transaction

REF - Reference Identification Pos: 050 Max: 12
Detail - Optional
Element Summary:
Description:
Will Only Send Code SF
Description:
Suppliers Shipping Dock; Refer To Notes 1
Notes:
1. This Segment Is Sent For Ekanban Orders Only

Detail - Optional
Element Summary:
Description:
Will Only Send Code LF
Description:
Toyota Lineside Address; Refer To Note 1
Notes:

Pos: 050 Max: 12
Element Summary:
Description:
Will Only Send Code LU
Description:
Stores Address; Refer To Note 1
Notes:

Pos: 050 Max: 12
Element Summary:
Description:
Will Only Send Code MR
Description:
Toyota Card Code; Refer To Notes 1,2
Notes:
1. The REF02 Element Will Be Used In The IT101 Element Of The 810 Transaction
2. The Card Code Will Be A “M390” For All Original Order North American Parts

Detail - Optional
Element Summary:
Description:
Will Only Send Code PRT
Description:
Product Description; Refer To Notes 1,2
Notes:

Detail - Optional
Element Summary:
Description:
Will Only Send Code RU
Description:
Toyota Dock Code; Refer To Notes 1,2
Notes:
3. This Segment Is Optional. It Will Only Appear If There Is A Sub-Route.

PER - Administrative Communications Pos: 060 Max: 1
Detail - Optional
Contact Loop: LIN Elements: 9
To identify a person or office to whom administrative communications should be directed
Element Summary:
PER01 366 Contact Function Code M ID 2/2 Must use
Description:
Code identifying the major duty or responsibility of the
person or group named
Will Only Send Code SC.
PER02 93 Name O AN 1/60 Used
Description:
Free-form name
Name Of TMM’s Specialist In P/C.
PER03 365 Communication Number Qualifier X ID 2/2 Used
Description:
Code identifying the type of communication number
Will Only Send Code TE.
PER04 364 Communication Number X AN 1/80 Used
Description:
Complete communications number including country
or area code when applicable
Telephone Number Of TMM’s Specialist in P/C.
Syntax:
1. P0304 - If either PER03,PER04 is present, then all are required

Pos: 070 Max: 1
SDP - Ship/Delivery Pattern Detail - Optional
To identify specific ship/delivery requirements
Element Summary:
SDP01 678 Ship/Delivery or Calendar Pattern Code M ID 1/2 Must use
Description:
Code which specifies the routine shipments, deliveries,
or calendar pattern
Will Only Send Code N – “As Directed”
SDP02 679 Ship/Delivery Pattern Time Code M ID 1/1 Must use
Description:
Code which specifies the time for routine shipments or
deliveries
Will Only Send Code F – “First Shift”

Pos: 140 Repeat: 10
Loop SHP Optional
Loop: SHP Elements: N/A
To specify shipment and/or receipt information
Loop Summary:
140 SHP Shipped/Received Information O 1 Used

SHP - Shipped/Received Information Pos: 140 Max: 1
Detail - Optional
Loop: SHP Elements: 7
To specify shipment and/or receipt information
Element Summary:
SHP01 673 Quantity Qualifier O ID 2/2 Used
Description:
Code specifying the type of quantity
Will Only Send Code 38.
SHP02 380 Quantity X R 1/15 Used
Description:
Numeric value of quantity
SHP03 374 Date/Time Qualifier X ID 3/3 Used
Description:
Code specifying type of date or time, or both date and
time
Will Only Send Code 010.
SHP04 373 Date X DT 8/8 Used
Description:
Refer To Notes 1,2
SHP05 337 Time X TM 4/8 Used
Description:
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)
Refer To Notes 1,2
Notes:
2. For FIRM Orders, Reflects The Pickup Date/Time
3. A Zero Quantity Is Valid For The SHP02 Element

Pos: 150 Max: 12
Element Summary:
Description:
Will Only Send Code MK
Description:
Refer To Note 1
REF03 352 Description X AN 1/80 Not Used
Description:
A free-form description to clarify the related data
elements and their content
REF04 C040 Reference Identifier O Comp Used
Description:
To identify one or more reference numbers or
identification numbers as specified by the Reference
Qualifier
128 Reference Identification Qualifier M ID 2/3 Must use
Description:
Will Only Send Code DO
127 Reference Identification M AN 1/30 Must use
Description:
Delivery Number
128 Reference Identification Qualifier X ID 2/3 Used
Description:
127 Reference Identification X AN 1/30 Used
Description:
Order Number; Refer To Note 1
Description:
Description:
Number Of Containers; Refer To Note 2
Syntax:
1. R0203 - At least one of REF02,REF03 is required

Semantics:
1. REF04 contains data relating to the value cited in REF02.
Notes:
1. Format Is XXXXXXXX-YYYYYYYY Where
XXXXXXXX Is The Manifest Number,
Then A Dash, Followed By
YYYYYYYY, Which is the Receiving Number
3. “NO SHIP” Is Valid In The REF02 Element When SHP02 Contains Zero Quantity

Detail - Optional
Element Summary:
Description:
Will Only Send Code UL
Description:
Cross Dock 1
Description:
Description:
Qualifier
Description:
Description:
Cross Dock 1 Date
Description:
Description:
Cross Dock 1 Time
Semantics:
Notes:
1. This Segment Is Sent For Ekanban Orders Only That Are Going Through Cross Dock

Detail - Optional
Element Summary:
Description:
Description:
Cross Dock 2
Description:
Description:
Qualifier
Description:
Description:
Cross Dock 2 Date
Description:
Description:
Cross Dock 2 Time
Semantics:
Notes:
1. This Segment Is Sent For Ekanban Orders Only That Are Going Through A Second Cross Dock

Detail - Optional
Element Summary:
Description:
Description:
Main Route; Refer To Note 2
Description:
Description:
Qualifier
Description:
Description:
Routing Order Sequence Number
Description:
Description:
Unload Date - CCYYMMDD
Description:
Description:
Unload Time - HHMM
Syntax:
1. R0203 - At least one of REF02,REF03 is required

Semantics:
Notes:

TD5 - Carrier Details (Routing Pos: 180 Max: 1
Detail - Optional
Sequence/Transit Time) Loop: LIN Elements: 15
To specify the carrier and sequence of routing and provide transit time information
Element Summary:
TD501 133 Routing Sequence Code O ID 1/2 Not Used
Description:
Code describing the relationship of a carrier to a
specific shipment movement
Not Used
TD502 66 Identification Code Qualifier X ID 1/2 Not Used
Description:
Code designating the system/method of code structure
used for Identification Code (67)
Not Used
TD503 67 Identification Code X AN 2/80 Not Used
Description:
Code identifying a party or other code
Not Used
TD504 91 Transportation Method/Type Code X ID 1/2 Not Used
Description:
Code specifying the method or type of transportation
for the shipment
Not Used
TD505 387 Routing X AN 1/35 Used
Description:
Free-form description of the routing or requested
routing for shipment, or the originating carrier's identity
Will Send “ROUTING” Or “MAIN ROUTE”
TD506 368 Shipment/Order Status Code X ID 2/2 Not Used
Description:
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
Not Used
TD507 309 Location Qualifier O ID 1/2 Used
Description:
Code identifying type of location
Will Only Send Code DE
TD508 310 Location Identifier X AN 1/30 Used
Description:
Code which identifies a specific location
Main Route Code; Refer To Note 2
Notes:

CTT - Transaction Totals Pos: 010 Max: 1
Summary - Optional
To transmit a hash total for a specific element in the transaction set
Element Summary:
CTT01 354 Number of Line Items M N0 1/6 Must use
Description:
Total number of line items in the transaction set
Total Number Of LIN Segments
CTT02 347 Hash Total O R 1/10 Used
Description:
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.
Total Of Net Qty On The SHP Segments
Comments:
1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

SE - Transaction Set Trailer Pos: 020 Max: 1
Summary - Mandatory
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE)
segments)
Element Summary:
SE01 96 Number of Included Segments M N0 1/10 Must use
Description:
Total number of segments included in a transaction set
including ST and SE segments
SE02 329 Transaction Set Control Number M AN 4/9 Must use
Description:
Identifying control number that must be unique within
the transaction set functional group assigned by the
originator for a transaction set
Comments:
1. SE is the last segment of each transaction set.

GE - Functional Group Trailer Pos: Max: 1
To indicate the end of a functional group and to provide control information
Element Summary:
GE01 97 Number of Transaction Sets Included M N0 1/6 Must use
Description:
Total number of transaction sets included in the
functional group or interchange (transmission) group
terminated by the trailer containing this data element
GE02 28 Group Control Number M N0 1/9 Must use
Description:
Assigned number originated and maintained by the
sender
Semantics:
1. The data interchange control number GE02 in this trailer must be identical to the same data element in the associated
functional group header, GS06.
Comments:
1. The use of identical data interchange control numbers in the associated functional group header and trailer is designed to
maximize functional group integrity. The control number is the same as that used in the corresponding header.

IEA - Interchange Control Trailer Pos: Max: 1
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Element Summary:
IEA01 I16 Number of Included Functional Groups M N0 1/5 Must use
Description:
A count of the number of functional groups included in
an interchange
IEA02 I12 Interchange Control Number M N0 9/9 Must use
Description:
A control number assigned by the interchange sender

2.6 862 Shipping Schedule: Scope

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2.6 862 Shipping Schedule: Scope

Uploaded by

Copyright:

Available Formats

2.

6 862 Shipping Schedule

SCOPE THIS INFORMATION INCLUDES START-UP INFORMATION SPECIFIC TO TRADING

APPROACH THE FOLLOWING INFORMATION WILL BE REQUIRED BEFORE THE TRADING

1. PRIMARY CONTACT NAME, ADDRESS, AND NUMBER

2. ALTERNATE CONTACT NAME, ADDRESS, AND TELEPHONE NO.

3. PLANT NAME, ADDRESS, DUNS NUMBER

4. CONFIRM START-UP DATE

Toyota EDI Master Implementation Manual -1- Ver 1.4

MISCELLANEOUS STANDARD: ANSI X12 - AIAG

EDI ACKNOWLEDGMENT FUNCTIONAL ACKNOWLEDGMENT – TMMK,

SEPARATORS FOR STERLING VAN CUSTOMERS AND THOSE

FOR GEIS, ADVANTIS AND AT&T VAN

WRAPPED ALL DATA WILL BE TRANSMITTED / RECEIVED IN

DATA FREQUENCY DAILY

VALUE ADDED NETWORK STERLING INFORMATION BROKER

TOLL FREE NUMBERS FOR NETWORK

Toyota EDI Master Implementation Manual -2- Ver 1.4

APPROACH EVERY TRADING PARTNER MUST SHOW COMPATIBILITY WITH TMM’S:

CERTIFICATION IS FORMALLY COMPLETED WHEN TMM'S INFORMATION SYSTEMS

TRANSACTION TESTING WILL NOT BE COMPLETE UNTIL EACH SUPPLIER

THE LENGTH OF THE PARALLEL TESTING WILL BE DETERMINED BY TMM.

Toyota EDI Master Implementation Manual -3- Ver 1.4

SCOPE INCLUDES TRADING PARTNERS PROBLEMS AND INQUIRIES CONCERNING

EDI SYSTEMS & NETWORK CONTROL

PROBLEMS INDICATED DURING TESTING &

ALL INQUIRIES - COMMERCE NETWORK

Toyota EDI Master Implementation Manual -4- Ver 1.4

X12 ANSI REQUIREMENTS Ver. 4010 TOYOTA REQ.

Toyota EDI Master Implementation Manual -5- Ver 1.4

Toyota EDI Master Implementation Manual -6- Ver 1.4

Toyota EDI Master Implementation Manual -7- Ver 1.4

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

Toyota EDI Master Implementation Manual -8- Ver 1.4

Toyota EDI Master Implementation Manual -9- Ver 1.4

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

Toyota EDI Master Implementation Manual - 10 - Ver 1.4

Toyota EDI Master Implementation Manual - 11 - Ver 1.4

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

Toyota EDI Master Implementation Manual - 12 - Ver 1.4

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

Toyota EDI Master Implementation Manual - 13 - Ver 1.4

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

Toyota EDI Master Implementation Manual - 14 - Ver 1.4

To specify basic item identification data

Toyota EDI Master Implementation Manual - 15 - Ver 1.4

To specify basic item identification data

Toyota EDI Master Implementation Manual - 16 - Ver 1.4

To specify item unit data

Toyota EDI Master Implementation Manual - 17 - Ver 1.4

Toyota EDI Master Implementation Manual - 18 - Ver 1.4

Toyota EDI Master Implementation Manual - 19 - Ver 1.4

To specify identifying information

Toyota EDI Master Implementation Manual - 20 - Ver 1.4

To specify identifying information

Toyota EDI Master Implementation Manual - 21 - Ver 1.4

To specify identifying information

Toyota EDI Master Implementation Manual - 22 - Ver 1.4

To specify identifying information

Toyota EDI Master Implementation Manual - 23 - Ver 1.4

To specify identifying information

Toyota EDI Master Implementation Manual - 24 - Ver 1.4