EDI Implementation Manual For - iConnecticonnect-corp.com/specs/vendors/toyotaboshoku/tba_edi...1. R0203 - At least one of REF02, REF03 is required Notes: 1. TBA Card Code. The REF02

EDI Implementation Manual For:ARJATS

BARTMTA

MTMC (Chavez)MTMT (Torreon)

TBAETBCATBDBTBDNTBINTBMKTBMSTBMXTISA

TMIBTTMIELTMIHBTMILFTMIMOTMINVTMITX

(ALL TBA Manufacturing locations referred to as TBA in this EDI manual)

TBA EDI Help Desk (859) 817-4050

revision 07/25/2008

Pos: 140 Max: 12

Detail - OptionalLoop: LIN Elements: 4

830 - Material Release

REF - Reference Identification User Option(Usage): Used

To specify identifying information

Element Summary: REF*MR*M201~

TBA REQ. Ref Id Element Name Req Type Min/Max Value

REF01 128 Reference Identification Qualifier M ID 2/2 MR Description:

Code qualifying the Reference Identification

X12 ANSI REQUIREMENTS Ver. 4010

Syntax: 1. R0203 - At least one of REF02, REF03 is required

Notes: 1. TBA Card Code.

The REF02 Element Will Be Used In The IT101 Element Of The 810 Transaction. Valid codes are;

Will Only Send Code MR REF02 127 Reference Identification X AN 4/4 M201

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

Refer To Note 1

M201 Raw Material ShipmentM401 Direct SupplyM301 Prototype/Pre-ProductionM211 Supplemental Manifest/MaterialM210 DMR (Discrepant Material Report)M411 Direct Supply Replacement MaterialM231 Service Order Material

REF-MR 830.25

1.0 Toyota Boshoku's EDI Program

Toyota Boshoku’s EDI Philosophy 1.0. 7

Benefits of Implementing EDI with Toyota Boshoku 1.0. 7

Toyota Boshoku EDI Transactions with Suppliers 1.1. 8

Supplier Implementation Expectations 1.2. 9

2.0 Toyota Boshokus’s EDI Program Contacts

Business Issue Contacts 2.0. 10

EDI Implementation Issue Contacts 2.0. 10

EDI Production Issue Contacts 2.0. 10

3.0 EDI Implementation Process

Comments 3.0. 11

Overview of EDI Implementation Process 3.0. 11

EDI Implementation Milestones 3.1. 12

EDI Transaction Testing Process 3.1. 12

4.0 Moving EDI Transactions Into Production

Key Concerns 4.0. 14

Moving the 820, 824, 830, and 862 Into Production Use 4.1. 15

Moving the 810, 856 and 997 Into Production Use 4.2. 16

5.0 Toyota Boshoku's EDI Technical Specifications

830 (Order Forecast)

830 - Planning Schedule with Release Capability 830. 1

DATA REQUIREMENTS 830. 2

HOW TO BECOME CERTIFIED 830. 3

PS - Functional Group 830. 4

ISA - Interchange Control Header 830. 5

GS - Functional Group Header 830. 7

ST - Transaction Set Header 830. 9

BFR - Beginning Segment for Planning Schedule 830. 10

Loop N1 830. 12

N1 - Names 830. 13

830. 14

PER - Administrative Communications (SC) Schedule Contact 830. 15

Loop LIN 830. 16

LIN - Item Identification - Buyer's Part Number, Returnable Container Number 830. 17

UIT - Unit Detail Description 830. 19

PID - Product/Item Description 830. 20

PO4 - Item Physical Details 830. 21

PRS - Part Release Status 830. 22

REF - Reference Identification (DK) Dock Number 830. 23

REF - Reference Identification (LU) Location Number 830. 24

REF - Reference Identification (MR) Merchandise Type Code (Card Code) 830. 25

TD5 - Carrier Details (Routing Sequence/Transit Time) - Sub-Routing 830. 26

TD5 - Carrier Details (Routing Sequence/Transit Time) - Main Route 830. 27

Loop SDP 830. 28

SDP - Ship/Delivery Pattern 830. 29

FST - Forecast Schedule - First Date, Last Date, Quantity 830. 30

Table of Contents

Forward A. 2

Table of Contents A.3

ATH - Recource Authorization 830. 32

Loop SHP 830. 33

SHP - Shipped/Received Information 830. 34

REF - Reference Identifications (Last Shipper Number) 830. 35


CTT - Transaction Totals 830. 37

SE - Transaction Set Trailer 830. 38

GE - Functional Group Trailer 830. 39

IEA - Interchange Control Trailer 830. 40

EXAMPLE OF A MATERIAL RELEASE (830) 830. 41

856 (Advanced Shipping Notice)

856 - Ship Notice/Manifest 856. 1

DATA REQUIREMENTS HOW TO BECOME CERTIFIED 856. 2


SH - Functional Group 856. 4

ISA – Interchange Control Header 856. 6

GS – Functional Group Header 856. 8


BSN - Beginning Segment for Ship Notice 856. 11

DTM - Date/Time Reference 856. 12

Loop HL - Shipping 856. 13

HL - Hierarchical Level - Shipping 856. 14

MEA - Measurements and weights 856. 15

TD1 - Carrier Details (Quantity and Weight) 856. 16

TD5 - Carrier Details (Routing Sequence/Transit Time) 856. 17

TD3 - Carrier Details (Equipment) 856. 19

TD4 - Carrier Details (Special Handling, or Hazardous Materials, or Both) 856. 20

REF - Reference Identification (BM) Bill of Lading Number 856. 21

Loop N1 856. 22

N1 - Ship To Name 856. 23

N3 - Ship To Address Information 856. 24

N4 - Ship To Geographic Location 856. 25

N1 - Name (SU) Supplier/Manufacturer Name & Supplier Code 856. 26

N1 - Name (SF) Ship-To Name and DUNs Number 856. 27

Loop HL - Order 856. 28

HL - Hierarchical Level – Order 856. 29

PRF - Purchasing Order Reference 856. 30

REF - Reference Identification (MH) - Manufacturing Order Number 856. 31

Loop HL - Item 856. 32

HL - Hierarchical Level - Item 856. 33

LIN - Item Identification - Buyer's Part Number, Kanban Number, Vendor's Part Number 856. 34

SN1 - Item - Number of Units Shipped 856. 35

SLN - Item - Subline Item Detail (Shipment) - Unit Price 856. 37

REF - 22, 55, JS, LF, LS, LT, LU, MR, RE, VT 856. 38

CUR - Currency - Currency Code 856. 40



GE – Functional Group Trailer 856. 43

IE – Interchange Control Header 856. 44

EXAMPLE OF AN 856 856. 45


862 (Shipping Schedule)

862 - Shipping Schedule 862. 1

DATA REQUIREMENTS HOW TO BECOME CERTIFIED 862. 2


SS - Functional Group 862. 4




BSS - Beginning Segment for Shipping Schedule/Production Sequence 862. 11

Loop N1 862. 12

N1 - Name (MI) Planning Schedule / Material Release Issuer | (OB) Ordered By 862. 13

N1 - Name (ST) Ship To Name & Plant Code 862. 13

N1 - Name (SU) Supplier Name & Supplier Code 862. 13

N1 - Name (SF) Planning Schedule / Material Release Issuer 862. 13

N3 - Ship To Address Information 862. 14

N4 - Ship To Geographic Location 862. 15

PER - Administrative Communications Contact 862. 16

Loop LIN 862. 17

LIN - Item Identification 862. 18

UIT - Unit Detail 862. 20

PO4 - Item Physical Details 862. 21

PRS - Part Release Status 862. 22

REF - Reference Identification (55) Line Sequence Number or [SPARC Serial Number],(DK) Dock Number 862. 23

REF - Reference Identification (JS) Job Sequence 862. 23

REF - Reference Identification (LF) TBA Assembly Line Feed Location, (LS) Barcode Serial Number 862. 23

REF - Reference Identification (LU) Location Number 862. 23

REF - Reference Identification (MR) Merchandise Type Code (Card Code), (MY) Model Year 862. 23

REF - Reference Identification (PRT) Product Type 862. 23

REF - Reference Identification (VT) Chassis Number 862. 23

SDP - Ship/Delivery Pattern 862. 24

Loop SHP 862. 25


REF - Reference Identification (MK) Manifest Key Number 862. 27

REF - Reference Identification (UL) Cross Dock 1 862. 28

REF - Reference Identification (60) Cross Dock 2 862. 29

REF - Reference Identification (ZZ) Main Route 862. 30

TD5 - Carrier Details (Routing Sequence/Transit Time) 862. 31





EXAMPLE OF A SHIPPING SCHEDULE (862) DOCUMENT 862. 38

997 (Functional Acknowledgement)

997 - Functional Acknowledgement 997. 1

DATA REQUIREMENET 997. 2

HOW TO BECOME CERTIFIED 997. 3FA - Functional Group 997. 4





AK1 - Functional Group Response Header 997. 10

Loop AK2 997. 11

AK2 - Transaction Set Response Header 997. 12

Loop AK3 997. 13

AK3 - Data Segment Note 997. 14

AK4 - Data Element Note 997. 15

AK5 - Transaction Set Response Trailer 997. 16

AK9 - Functional Group Response Trailer 997. 17




EXAMPLE OF AN OUTBOUND FUNCTIONAL ACKNOWLEDGMENT - 997 997. 21

EXAMPLE OF AN INBOUND FUNCTIONAL ACKNOWLEDGMENT - 997 997. 22


1.0 Toyota Boshoku’s EDI Program Toyota Boshoku’s EDI Philosophy

Toyota Boshoku is committed to improving the business relationship we have with our suppliers. The Toyota Boshoku’s EDI program was put in place for this purpose – to improve our business relationship. As part of the EDI program, Toyota Boshoku is committed to providing our suppliers with the necessary resources and support needed to comply with the program’s expectations. Toyota Boshoku also realizes that the success of the EDI program is highly dependent on suppliers making Toyota Boshoku’s EDI efforts an integral part of our business relationship. Therefore, Toyota Boshoku’s EDI program is being implemented with the belief that through a cooperative effort between Toyota Boshoku and the supplier, a common improvement in our business relationship will evolve from the EDI program.

Benefits of Implementing EDI with Toyota Boshoku

Three key benefits should be evident when a supplier implements EDI with Toyota Boshoku. They are:

• Improved costs 0

• Improved transaction cycle timing

• Improved transaction accuracy

EDI is a protocol which improves transaction costs for both Toyota Boshoku and the supplier. Handling transactions by manual methods requires human time spent producing the transaction, costs in mailing or faxing the transaction, and further human time in receiving and utilizing the transaction. EDI transactions eliminate much of the non-value added resources required to handle transactions. This is especially the case when suppliers incorporate EDI transactions into a fully integrated application system.

EDI also reduces transaction cycle timing. This enables Toyota Boshoku and it's suppliers to see the end result of the transaction sooner than with manually handled transactions. The reason for reduced transaction cycle timing is that the transaction is not dependent on a human to fax or mail the transaction between trading partners. EDI is an aspect of Electronic Commerce that improves the speed of doing business.

Perhaps the most important benefit of doing EDI with Toyota Boshoku is the increase in accuracy of the transactions being sent and received by TBA. An integrated EDI program is not reliant on human input of data or legibility of a fax. The preciseness of TBA’s manufacturing processes requires accuracy of the order forecast to our suppliers, and EDI assures a high level of accuracy. NOTE:Toyota Direct Controlled Suppliers will be required to send TBA ASNs for each shipment along with their ASN to Toyota. 1.0 1.0.7

TBA EDI Transactions with Suppliers

Figure 1. TBA Transaction Routing

830 (Order Forecast)

Sent weekly for 13 week forecast


Sent after receipt of 830

862 (Firm Order)

Sent daily with order informationT 997 (Functional Acknowledgement) r Sent after receipt of 862i 856 (Advance Shipping Notice)

m Must be sent within 20 minutes of shipment

997 (Functional Acknowledgement) M Sent after receipt of 856 (Only verifies EDI validity & receipt) a 824 (Application Advice) s Sent within 1 hour of receipt of the 856 when there’s a t discrepancy between the 862 and 856. Supplier must resend e an updated 856 within 2 hours of TBA sending the 824 r 810 (Invoice) s Must be sent within 24 hours of shipment


Sent after receipt of 810 (Only verifies EDI validity & receipt) 820 (Remittance Advice)

Sent on 25th of each month, if 25th falls on a weekend or

TBA holiday, it will be sent the next business day

S U P P L I E R S

TBA currently uses seven EDI transactions with suppliers. They are:

• 830 (Order Forecast)

• 862 (Firm Order)

• 856 (Advanced Shipping Notice)

• *824 (Application Advice) • *810 (Accounts Receivable Detail List) • *820 (Remittance Advice) • 997 (Functional Acknowledgment)

*These documents will be implemented in the future after all TBA Suppliers have set up the initial EDI documents listed in this manual. All Suppliers will be notified when these documents are needed and their specifications. This manual will indicate references to these documents but will be greyed out with strikethrough font thus indicating this status.

1.1 1.1.8

Supplier Implementation Expectations

Supplier EDI implementation expectations for each project will follow the same standard guidelines. The goal for each EDI implementation project is to achieve 100% supplier EDI implementation of all transactions by their first use date.

Therefore, each project will be assigned the following milestones to be met by suppliers while implementing their

applicable EDI transactions. They are:

• Supplier returns EDI survey to TBA

• Supplier sets test date (as referenced on survey)

• Supplier begins testing

• Supplier completes testing

TBA’s North American suppliers are required to comply with TBA’s EDI implementation efforts as stated in the terms and conditions for suppliers. Therefore, TBA expects full cooperation by our North American suppliers with TBA’s EDI program. EDI compliance is a fundamental expectation of our commercial relationship. Any supplier who has an issue with EDI compliance by the set milestone should consult the TBA buyer with details. NOTE:Toyota Direct Controlled Suppliers will be required to send TBA ASNs for each shipment along with their ASN to Toyota. 1.2 1.2.9

2.0 TBA’s EDI Program ContactsBusiness Issue Contacts

EDI Implementation Issue Contacts

EDI Production Issue Contacts

Toyota Boshoku Production Control Managers:

Toyota Boshoku Vendor Release contacts:

Toyota Boshoku Vendor Receipts contacts:

TBA Purchasing Corporate Office Erlanger, Kentucky Russ Brown 859-734-8802 [email protected]

Toyota Boshoku EDI Help Desk [email protected] Phone: 859-817-4050

Bardstown, Kentucky Pat McDowell 502-349-2262 [email protected] Chavez, Mexico Juan Luna 011-52-871-729-2531 [email protected] Elmira, Ontario, Canada 519-880-4116 Harrodsburg, Kentucky Bonnie Murphy 859-734-8137 [email protected] Lawrenceville, Illinois 618-943-7115 Leitchfield, Kentucky Denise Wyman 270-259-7606 [email protected] Modesto, California Christine Boughton 209 527-6000 ext 105 [email protected], Kentucky Mike Ledford 859-887-6442 [email protected] San Antonio, Texas Larry Best 210-271-2402 [email protected] Torreon, Mexico Juan Luna 011-52-871-729-2531 [email protected]

Bardstown, Kentucky Lisa Hamilton 502-349-2203 [email protected] Chavez, Mexico Edgar Martinez 011-52-872-762-5024 [email protected] Elmira, Ontario, Canada Midori Asada 519-880-4113 [email protected] Harrodsburg, Kentucky Sarah Gritton 859-734-8156 [email protected] Lawrenceville, Illinois Primary 618-943-7145

Secondary Mark Arnot 618-943-7116 [email protected] Leitchfield, Kentucky Darla Johnson 270-259-7615 [email protected] Modesto, California Randall Gaberel 209-527-6000 ext 128 [email protected]

Brenda Gonzalez 210-527-6000 ext 142 [email protected] Nicholasville, Kentucky 859-887-6427 San Antonio, Texas Not Available Torreon, Mexico Cinthia Nava 011-52-871-729-2548 [email protected]

Veronica Alvarado 011-52-871-729-2549 [email protected]

Bardstown, Kentucky Gary Hayden 502-349-2220 [email protected] Chavez, Mexico Rolando Campa 011-52-872-762-5024 [email protected] Elmira, Ontario, Canada 519-880-4142 Harrodsburg, Kentucky Bill Moore 859-734-8502 [email protected] Lawrenceville, Illinois Blue Sue Vennard 618-943-5300 ext 6111 (no e-mail)

Gold Mick Murphy 618-943-5300 ext 6111 [email protected] Leitchfield, Kentucky Heidi Dills 270-259-7633 [email protected] Modesto, California 1st Umesh Nand 210-527-6000 ext 111

2nd Pablo Palominos 211-527-6000 ext 111 Nicholasville, Kentucky 1st Mary Blakeman 859-887-6432 [email protected]

2nd 859-887-6432 San Antonio, Texas Not Available Torreon, Mexico Jesus Rios 011-52-871-729-2536 [email protected]

2.0 2.0.10

Dena Sullivan Smith

Text Box

Full TBA contact information will be added to this manual at a later time. Toyota Boshoku Canada, Inc.; Gordon Niznik Sr. Manager, Finance & Corporate Planning [email protected] Tel: 519-602-2107 Fax: 519-421-9958 Mark Overton I.T. Assistant Manager [email protected] Tel: 519-602-2103 Fax: 519-320-0600 Denise Eighteen Manager, Production Control [email protected] Tel: 519-421-7556 x2118 Fax: 519-421-9958

The EDI implementation process is driven by TBA’s goal to achieve 100% supplier EDI implementation by the required first use dates of each transaction. Please pay special attention to the three areas of the EDI implementation process below. A strong commitment to these three areas will be vital to your company’s successful implementation of each transaction by the milestone dates.

1. Supplier Preparation: The success of the TBA EDI Program is dependent on each supplier’s preparation for each transaction’s implementation. Each supplier needs to assess their ability to comply with TBA’s transaction guidelines immediately and inform TBA of their assessment in the EDI survey.

2. Communications: TBA uses the Sterling Commerce VAN. Ensure that your company has the capability to send and receive EDI through this VAN.

3. Testing Transactions: Ensure that your company is ready to test by the scheduled test date for each transaction. Work diligently to resolve problems with your VAN or EDI software provider in order to complete testing by the required “testing completed” milestone. Also, keep your TBAbuyer informed of your company’s EDI implementation status. Notify TBA with the test results.

3.0 EDI Implementation ProcessComments

Overview of EDI Implementation Process

Figure 3. EDI Transaction Implementation Process

Supplier InformsAssess Capability of Set Test Date with

TBA of EDIImplementing EDI TBA (Milestone) (if

Readiness PerTransactions with TBA not on survey)

Transaction

Return Survey to TBA Begin Testing Each TBA and Supplier Purchasing Applicable Change EDI (Milestone) Transaction Transaction Settings

(Milestone) for Production Use

Complete Testing (Milestone)

Supplier Preparation Testing Production Implementation

Receive Notice from TBA of Need to

Implement EDI * Contact TBA

TBA Contacts Supplier to Verify EDI Readiness Per

Transaction

The EDI implementation process requires the suppliers’ strong commitment for proactive implementation of each transaction. TBA expects all supplier’s to utilize the resources available to them, including the EDI Implementation Manual and EDI contacts, to prepare for and complete all phases of the EDI implementation process by the milestone date requirements. The figure below provides a general flow of the implementation process..

* In the event that you have not been contacted by TBA, and are in need of an EDI transaction implementation,

please contact your purchasing representative at TBA.

NOTE: Toyota Direct Controlled Suppliers will be required to send TBA ASNs for each shipment along with the

ASN to Toyota.

3.0 3.0.11

EDI Implementation Milestones

EDI Transaction Testing Process

810, 856 and 997 Inbound Transactions

The purpose of TBA’s EDI implementation milestones is to ensure each supplier’s timely progress towards reaching EDI implementation for production. Milestone timings are unique for each EDI implementation project and are decided depending on the amount of suppliers involved in the project, the required implementation timing for the transactions involved, and the amount of transactions being implemented. The milestones reflect key points in the implementation process and incorporate proper lead times between each milestone for supplier preparation activity.

The EDI implementation milestones are: • Supplier returns EDI survey to TBA • Supplier sets test date (supplier calls TBA, if date is not specified on survey) • Supplier begins testing • Supplier completes testing

The testing process varies slightly according to the type of transaction routing:

• Inbound to TBA (810, 856 and 997)

• Outbound from TBA (820, 824, 830, and 862)

TBA will evaluate the 810, 856 and 997 transactions for two basic requirements. One requirement is the supplier’s ability to establish a connection and properly route each transaction to Sterling Commerce. Another requirement is the supplier’s ability to send the proper data in the correct format. Technical details for the transaction are provided in the next section.

To test the 810, 856 and 997 transactions, the supplier must follow these steps:

1. Assess your company’s ability to implement the 810, 856 and 997 EDI transactions toTBA’s standards immediately after receiving notice from TBA of your company’s need toimplement these transactions.

2. Call TBA to confirm understanding of the testing process and transaction guidelines.

3. Schedule a date with TBA to test each transaction. The scheduled test date should bedetermined by your ability to test successfully. TBA is ready to test all suppliers andtransactions at any point after informing suppliers of the project.

4. Send the EDI transaction mapped in a test mode format to TBA on the scheduled testdate for that transaction. The supplier is not supposed to wait for TBA to ask for a teston this date. Instead, TBA is prepared to receive and evaluate the test on that date.Suppliers that miss their test date must reschedule a new date immediately with TBA.

5. TBA will contact the supplier with the results of the test. The supplier will either becomecertified or will be informed of why the test cannot be certified.

6. Suppliers that must resolve technical problems are required to inform TBA of whatcountermeasures will be taken and commit to a completion date for the problem. Thiscompletion date will be the new date when suppliers will be expected to test thattransaction again.

7. TBA will contact suppliers that successfully certify each transaction at a specified timeto move the EDI transaction into a production mode.

3.1 3.1.12

4.0 Moving EDI Transactions Into ProductionKey Concerns Implementing an EDI transaction with TBA requires several steps to take place. The final step, moving the EDI transaction into a production mode, is certainly a critical step in the implementation process. TBA’s confidence in our supplier’s ability to correctly utilize EDI in their business processes stems from your company’s past successes with TBA.

EDI does, however, present several challenges to suppliers and TBA. Often suppliers must acquire new software, train employees, and even reengineer processes to incorporate EDI into their company. Stemming from change is a tendency for mistakes and a period of time for adaptation to the change. Although TBA does recognize the challenges that EDI presents, our suppliers are still expected to be ready to successfully use EDI at the time suppliers are to use them at a production level with TBA. Our supplier’s ability to successfully use EDI at a transaction’s production timing is vital to TBA for several reasons.

1. TBA cannot handle the EDI transactions in another format besides EDI. TBA has engineered the business processes involving the EDI transaction to be driven by that EDI transaction. EDI transactions are integrated into both our production and accounting systems to ensure accuracy and efficiency within each system.

2. The efficiency of TBA’s business processes requires accurate information throughout each process. EDI is incorporated into TBA’s business processes also as a business efficiency strategy. EDI is meant to improve TBA's just-in-time business processes and accounting’s invoice matching procedures. Therefore, suppliers must correctly generate a transaction (810, 856, 997) and have the capability to correctly process a transaction when received (820, 824, 830 and 862). Those suppliers that cause TBA to use unplanned resources to handle transactions are recognized by TBA and then undergo countermeasures to ensure vitality for the affected business process.

3 Penalties - (to be determined)

4.0 4.0.14

Moving the 820, 824, 830 and 862 Into Production Use

Figure 4. 820, 824, 830 and 862 Move to Production Process

Ensure TBA of readiness to receive EDI transactions S

Call supplier to ensure readiness to receive EDI transactions

U Move supplier’s EDI settings to production mode P

T P Send 820/824/830/862 EDI transactions to supplier

I I LM

Supplier notifies TBA of 820/824/830/862 test status E R

Confirm receipt of 820/824/830/862 S

The 820, 824, 830 and 862 transactions are generated and sent by TBA, and then received and processed by the supplier. In order to successfully use the 820, 824, 830 and 862 for TBA, the supplier must demonstrate these three general capabilities when the 820, 824, 830 and 862 are in production use.

• Be capable of receiving production 820’s, 824’s, 830’s and 862’s from TBA• Be capable of processing the data in the 820, 824, 830 and 862 • Be capable of producing an AIAG label for each TBA Plant from the 862

TBA recognizes that suppliers may not have the current capability to integrate the 820, 824, 830, and 862 into their business processes in order to accomplish the three capabilities above through an automated system. A supplier’s level of ability to process 820, 824, 830 and 862 information does not determine the extent to which a supplier is expected to perform the above capabilities. In the event that TBA’s order data can not be processed in an automated system, the supplier should be prepared to process the information manually and create the AIAG label correctly in a temporary manual process. The supplier must demonstrate all 820, 824, 830 and 862 capabilities at the time of production use start-up.

4.1 4.1.15

Moving the 810, 856 and 997 Into Production Use

Figure 5. 810, 856 and 997 Move to Production Process

Call supplier to ensure readiness to receive EDI transactions

S

P Ensure TBA of readiness to receive EDI transactions U

Move supplier’s EDI settings to production mode PT M L

Send 810/856/997 EDI transactions

E II

Receive 820/824/830/862 EDI transactions R S

The 810, 856 and 997 EDI transactions are generated and sent by the supplier, and then received and processed by TBA. In order to successfully use the 810, 856 and 997 transactions with TBA, the supplier must demonstrate these three general capabilities when the 810, 856 and 997 are in production use.

• Be capable of acquiring the correct information for each transaction • Be capable of processing each transaction’s information requirements into an EDI transaction • Be capable of producing and sending each transaction at the proper timing

TBA recognizes that suppliers may not have the current capability to process the information required for the 810, 856 and 997 transactions to accomplish the three capabilities above through an automated system. A supplier’s level of ability to process 810, 856 and 997 transactions does not determine the extent to which a supplier is expected to perform the above capabilities. In the event that an 810, 856 and/or 997 transaction cannot be processed in an automated system, the supplier should be prepared to process and create the EDI transactions correctly in a temporary manual process. The supplier must demonstrate all 810, 856 and 997 capabilities at the time of production use start-up.

4.2 4.2.16


revision: 2/01/2008

(859) 817-4050

July 28, 2008

FOR

830 - Planning Schedule with Release CapabilityINBOUND

TOYOTA BOSHOKU'S CONTACT

INFORMATION SYSTEMS

TOYOTA BOSHOKU

EDI TECHNICAL SPECIFICATIONS

EDI SUPPORT LINE

830 830.1


DATA REQUIREMENTS

MISCELLANEOUS STANDARD: ANSI X12 - AIAG EDI ACKNOWLEDGMENT FUNCTIONAL ACKNOWLEDGMENT -TBA

DOES WANT TO RECEIVE A FUNCTIONAL ACKNOWLEDGMENT OF THE 830 BY THE TRADING PARTNER

DOCUMENTATION CHANGES TBA WILL GIVE TRADING PARTNERS A MINIMUM OF FOUR WEEKS NOTICE BEFORE IMPLEMENTING FORMAT CHANGES.

SEPARATORS SEGMENT : ~ ELEMENT : * SUB-ELEMENT : >

WRAPPED ALL DATA WILL BE TRANSMITTED / RECEIVED IN AN 80 BYTE RECORD LENGTH.

DATA FREQUENCY DAILY, WEEKLY VALUE ADDED NETWORK (VAN) COMMERCE NETWORK

DIVISION OF SBC 4600 LAKEHURST CT. P. O. BOX 7160 COLUMBUS, OH. 43017-0760

DATA REQUIREMENTS 830.2


HOW TO BECOME CERTIFIED

SCOPE BEFORE A TRADING PARTNER CAN DO PRODUCTION EDI WITH TBA, THEY MUST BE CERTIFIED, THAT IS COMPATIBLE WITH TBA'S EDI ENVIRONMENT.

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

1. NETWORK 2. COMMUNICATION SOFTWARE 3. DATA FORMAT

CERTIFICATION IS FORMALLY COMPLETED WHEN TBA'S INFORMATION SYSTEMS SECTION HAS COMPLETED ALL NETWORK AND TRANSACTION TESTING.

TRANSACTION TESTING WILL NOT BE COMPLETE UNTIL EACH SUPPLIER COMPLETES PARALLEL TESTING WITH TBA INVOLVING RECEIVING THE PAPER MATERIAL RELEASE AND THE ORDER VIA EDI.

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

HOW TO BECOME CERTIFIED 830.3


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

Pos Id Segment Name Req Max Use Repeat Notes Usage 010 ST Transaction Set Header M 1 Must use 020 BFR Beginning Segment for M 1 Must use

Planning Schedule 200

230 N1 Name O 1 Used 250 N3 Address Information O 2 Used 260 N4 Geographic Location O 1 Used 280 PER Administrative Communications Contact O 3 Used

TBA REQ. Pos Id Segment Name Req Max Use Repeat Notes Usage

>1 010 LIN Item Identification M 1 Must use 020 UIT Unit Detail O 1 Used 080 PID Product/Item Description O 1000 Used 120 PO4 Item Physical Details O 1 Used 130 PRS Part Release Status O 1 Used 140 REF Reference Identification O 12 Used 250 TD5 Carrier Details (Routing Sequence/Transit Time) O 12 Used

260 450 SDP Ship/Delivery Pattern O 1 Used 460 FST Forecast Schedule O 260 N2/410 Used

25 470 SHP Last Receipt/Cum Data O 1 Used 480 REF Last Shipper Number O 5 Used

TBA REQ. Pos Id Segment Name Req Max Use Repeat Notes Usage 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

2/410 At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. These two loops are mutually exclusive.

3/010 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.

Functional Group=PS

Heading:

Detail:

Summary:

Notes:


LOOP ID - SDP

LOOP ID - HL

LOOP ID - LIN

LOOP ID - SHP


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.

PS 830.4


ISA - Interchange Control Header Pos: Max: 1 User Option(Usage): Must use Not Defined - Mandatory

Loop: N/A Elements: 16 Start and identify an interchange of zero or more functional groups and interchange-related control segments

Element Summary: ISA*00*TOYOTA *01*796567667 *01*796567667 *ZZ*999999999-20600*060608*0606*U*00400*000000001*0*P*>~


ISA01 I01 Authorization Information Qualifier M ID 2/2 0 Description:

Code to identify the type of information in the Authorization Information


Only Send Code 00 ISA02 I02 Authorization Information M AN 10/10 'TOYOTA '

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)

ISA03 I03 Security Information Qualifier M ID 2/2 1 Description:

Code to identify the type of information in the Security Information

ISA04 I04 Security Information M AN 10/10 796567667 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)

ISA05 I05 Interchange ID Qualifier M ID 2/2 01 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 9/15 796567667 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

ISA07 Interchange ID Qualifier M ID 2/2 ZZ Description: Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

ISA08 I07 Interchange Receiver ID M AN 15/15 999999999-12345 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

ISA 830.5

Only Send Senders Name - 'TOYOTA '

Only Send Code – 01

Refer To Note 1

Will only Send Code 01

Refer To Note 1

Will Typically Send Code ZZ

830 - Material Release 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 YYMMDD Description: 060608

Date of the interchange ISA10 I09 Interchange Time M TM 4/4 HHMM

Description: 0606 Time of the interchange

ISA11 I10 Interchange Control Standards Identifier M ID 1/1 U Description:

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

Only Send Code U ISA12 I11 Interchange Control Version Number M ID 5/5 00400

Description: Code specifying the version number of the interchange control segments Only Send Code 00400

ISA13 I12 Interchange Control Number M N0 9/9 000000001 Description:

A control number assigned by the interchange sender ISA14 I13 Acknowledgment Requested M ID 1/1 0

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 USE P FOR

Description: PRODUCTION Code to indicate whether data enclosed by this T FOR TEST 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 >

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 Values That Will Be Sent Are:

Code Plant Name and Location

096 Trim Masters, Inc. Harrodsburg, KY USA139 Trim Masters, Inc. Bardstown, KY USA 192 Trim Masters, Inc. Nicholasville, KY USA 193 Trim Masters, Inc. Leitchfield, KY USA 194 Trim Masters, Inc. Modesto, CA USA 199 Automotive Technology Systems LLC. Lawrenceville,592 Master Trim de Mexico Torreon Mexico 572 Trim Masters, Inc. Bartlett, IN USA 650 Master Trim de Mexico Chavez Mexico 705 Trim Masters, Inc. Elmira Ontario Canada 873 Trim Masters, Inc. San Antonio, TX USA

ISA

(1) DUNs # (92) Plant Abbrev.

063844752 TMIHB 796567667 TMIBT 825946353 TMINV 967532524 TMILF 806416004 TMIMO 877899695 ATS 812596419 MTMT 052922697 BART 812749414 MTMC 201047177 TMIEL 626731827 TMITX

830.6


GS - Functional Group Header Pos: Max: 1 User Option(Usage): Must use Not Defined - Mandatory

Loop: N/A Elements: 8 To indicate the beginning of a functional group and to provide control information

Element Summary: GS*PS*796567667*999999999*20060608*0606*1200*X*004010


GS01 479 Functional Identifier Code M ID 2/2 PS Description:

Code identifying a group of application related transaction sets


Only use code PS - "Planning Schedule" GS02 142 Application Sender's Code M AN 9/12 796567667

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

GS03 124 Application Receiver's Code M AN 9/15 ‘999999999’ Description:

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

GS04 373 Date M DT 8/8 20060608 Description:

Date expressed as CCYYMMDD GS05 337 Time M TM 4/4 0606

Description: Time expressed in 24-hour clock time as follows: HHMM, where H = hours (00-23), M = minutes (00-59)

GS06 28 Group Control Number M N0 1/9 1200 Description:

Assigned number originated and maintained by the sender GS07 455 Responsible Agency Code M ID 1/2 X

Description: Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

GS08 480 Version / Release / Industry Identifier Code M AN 1/12 004010 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

Refer To Note 1

Will send Receivers DUNS (Refer to Note 2)

Will only Send Code X


Semantics: 1. GS04 is the group date. 2. GS05 is the group time. 3. The group control number GS06 in this header must be identical to the same data element

in the associated functional group trailer, GE02.

GS 830.7


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.


Code Plant Name and Location (1) DUNs # (92) Plant Abbrev.

096 Trim Masters, Inc. Harrodsburg, KY USA 063844752 TMIHB 139 Trim Masters, Inc. Bardstown, KY USA 796567667 TMIBT 192 Trim Masters, Inc. Nicholasville, KY USA 825946353 TMINV 193 Trim Masters, Inc. Leitchfield, KY USA 967532524 TMILF 194 Trim Masters, Inc. Modesto, CA USA 806416004 TMIMO 199 Automotive Technology Systems LLC. Lawrenceville, IL USA 77899695 ATS 592 Master Trim de Mexico Torreon Mexico 812596419 MTMT 572 Trim Masters, Inc. Bartlett, IN USA 052922697 BART 650 Master Trim de Mexico Chavez Mexico 812749414 MTMC 705 Trim Masters, Inc. Elmira Ontario Canada 201047177 TMIEL 873 Trim Masters, Inc. San Antonio, TX USA 626731827 TMITX

GS 830.8

2. For Toyota Direct Suppliers only, TBA will send 'Receivers DUNs Number - Supplier Code' in the GS03 Element.i.e. 999999999-12345. The data will match the ISA07


Pos: 010 Max: 1

Heading - MandatoryLoop: N/A Elements: 2


ST01 143 Transaction Set Identifier Code M ID 3/3 830 Description:

Code uniquely identifying a Transaction Set Will only send code 830

ST02 329 Transaction Set Control Number M AN 4/9 000000001 Description:

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


ST - Transaction Set Header User Option(Usage): Must Use

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

Element Summary: ST*830*000000001

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).

ST 830.9


BFR - Beginning Segment for Planning Schedule Pos: 020 Max: 1 User Option(Usage): Must use Heading - Mandatory

Loop: N/A Elements: 12

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

Element Summary: BFR*00**06072006*DL*A*20060703*20061009*20040918***S10706~


BFR01 353 Transaction Set Purpose Code M ID 2/2 00 Description:

Code identifying purpose of transaction set


BFR02 127 Reference Identification O AN 0/30 '' Description:

Refer To Note 1

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

Will Not Send This Element BFR03 328 Release Number O AN 3/30 06072006

Description: Number identifying a release against a Purchase Orderpreviously placed by the parties involved in the transaction

BFR04 675 Schedule Type Qualifier M ID 2/2 DL Description:

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

Will Only Send Code DL – “ Delivery/Ship Date ” BFR05 676 Schedule Quantity Qualifier M ID 1/1 A

Description: Code identifying the type of dates used whendefining a shipping or delivery time in a schedule or forecast

Will Only Send Code A – “Actual” BFR06 373 Start Date M DT 8/8 20060703

Description: Start Date expressed as CCYYMMDD

BFR07 373 End Date M DT 8/8 20061009 Description:

End Date expressed as CCYYMMDDBFR08 373 Date Generated M DT 8/8 20040918

Description: Issue Date expressed as CCYYMMDD

BFR09 373 Date O DT 0/8 '' Description:

Date expressed as CCYYMMDD Will Not Send This Element

BFR10 Contract Number O AN 8/8 20060102 Description:

Date expressed as CCYYMMDD Date of Purchase Order

BFR11 324 Purchase Order Number O AN 1/22 S10706 Description:

Identifying number for Purchase Orderassigned by the orderer/purchaser

Syntax:

BFR 830.10

830 - Material Release 1. R0203 - At least one of BFR02, BFR03 is required

Semantics: 1. BFR02 is the identifying number for a forecast assigned by the orderer/purchaser. 2. BFR06 is the forecast horizon start date 3. BFR07 is the forecast horizon end date 4. BFR08 is the date forecast generated 5. BFR09 is not used. 6. BFR10 is the Purchase Order Date 7. BFR11 is the Purchase Order Number

Notes: 1. Valid Codes are;

00 = ORIGINAL01 = CANCELLATION04 = CHANGE

BFR 830.11

Pos: 230 Repeat: 200 Optional

Loop: N1 Elements: N/A


Loop N1

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

Loop Summary: TBA REQ.

Ref Id Element Name Req Type Min/Max Value 230 N1 Name M 1 Used 240 N2 Additional Name Information O 2 Used 250 N3 Address Information O 2 Used 260 N4 Geographic Location O 1 Used 280 PER Administrative Communications Contact M 3 Used


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.

N1 LOOP 830.12


N1 - NameUser Option(Usage): Used


N1*MI*TMIHB*1*063844752~N1*ST*TMIHB*92*096~N1*SU*ABC Manufacturing*92*12345~N1*SF*ABC Manufacturing*1*999999999~N1*OB*ABC Manufacturing*1*999999999~

TBA REQ.Ref Id Element Name Req Type Min/Max Value

N101 98 Entity Identifier Code M ID 2/2 MIDescription: ST

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

SUSF

Refer To Note 1 OBN102 93 Name X AN 1/30 TMIHB

Description: TMIHBFree-form name SUPPLIERNAME

SUPPLIERNAMERefer To Note 2 ORDERED BY NAME

N103 66 Identification Code Qualifier X ID 1/2 1Description: 92

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

Refer To Note 3 1N104 67 Identification Code X AN 3/9 063844752

Description: 096Code identifying a party or other code 12345

999999999Refer To Note 4 999999999

Syntax:1. 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.

Notes:1. Valid Codes are;

Code Name Type Sample segment data

MI Planning Schedule/Material Release Issuer N1*MI*TMIHB*1*063844752~ST Ship To N1*ST*TMIHB*92*096~SU Supplier/Manufacturer N1*SU*SUPPLIER NAME*92*12345~SF Ship From N1*SF*SUPPLIER NAME*1*999999999OB Ordered By N1*OB*ORDERED BY NAME*1*999999999

2. Valid Values That Will Be Sent Are:Code Plant Name and Location (1) DUNs #(92) Plant Abbrev.

096 Trim Masters, Inc. Harrodsburg, KY USA 063844752 TMIHB139 Trim Masters, Inc. Bardstown, KY USA 796567667 TMIBT192 Trim Masters, Inc. Nicholasville, KY USA 825946353 TMINV193 Trim Masters, Inc. Leitchfield, KY USA 967532524 TMILF194 Trim Masters, Inc. Modesto, CA USA 806416004 TMIMO199 Automotive Technology Systems LLC. Lawrenceville, IL 877899695 ATS592 Master Trim de Mexico Torreon Mexico 812596419 MTMT

Max: 1Pos: 230


Element Summary:

Heading - OptionalElements: 6Loop: N1

N1 830.13

830 - Material Release572 Trim Masters, Inc. Bartlett, IN USA 052922697 BART650 Master Trim de Mexico Chavez Mexico 812749414 MTMC705 Trim Masters, Inc. Elmira Ontario Canada 201047177 TMIEL873 Trim Masters, Inc. San Antonio, TX USA 626731827 TMITX

3. Valid Values That Will Be Sent Are:1 - Dun and Bradstreet (Credit Reporting) (DUNs)92 - Assigned by Buyer (Trim Master's Plant Abbreviation)

4. MI Planning Schedule/Material Release IssuerWill Send TBA Plant's DUNs number.

ST Ship ToWill Send TBA's Plant Number.

SU Supplier/ManufacturerSupplier Code Issued by TBA

SF Ship FromWill Send Supplier DUNs number.

OB Ordered ByWill Send Customer DUNs number.

N1 830.14


PER - Administrative Communications Contact Pos: 280 Max: 3 User Option(Usage): Used Detail - Optional

Loop: N1 Elements: 9 To identify a person or office to whom administrative communications should be directed

TBA REQ.X12 ANSI REQUIREMENTS Ver. 4010

Element Summary: PER*SC*BONNIE SMITH*TE*8597346000~

Ref Id Element Name Req Type Min/Max Value PER01 366 Contact Function Code M ID 2/2 SC

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

PER02 93 Name O AN 1/40 BONNIE SMITH Description:

Free-form name

PER03 365 Communication Number Qualifier X ID 2/2 TE Description:

Code identifying the type of communication number

PER04 364 Communication Number X AN 1/30 555-555-5555 Description:

Complete communications number including country or area code when applicable

Will Only Send Code SC - Supplier Contact

Name Of TBA’s Specialist In P/C

Will Only Send Code TE - Telephone Number

Telephone Number Of TBA's Specialist In P/C

Syntax: 1. P0304 - If either PER03, PER04 is present, then all are required

PER 830.15


Loop LIN Pos: 010 Repeat: >1 Mandatory

Loop: LIN Elements: N/A

TBA REQ. Pos Id Segment Name Req Max Use Repeat Usage 010 LIN Item Identification M 1 Must use 020 UIT Unit Detail M 1 Must use080 PID Product/Item Description M 1000 Must use 120 PO4 Item Physical Details M 1 Must use130 PRS Part Release Status M 1 Must use140 REF Reference Identifications O 12 Used 250 TD5 Carrier Details (Routing Sequence/Transit Time O 12 Used


To specify basic item identification data

Loop Summary:

Semantics: 1. LIN01 is the line item identification

Comments: 1. See the Data Dictionary for a complete list of IDs. 2. 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.

LIN LOOP 830.16


Pos: 010 Max: 1

Detail – MandatoryLoop: LIN Elements: 31

LIN - Item Identification User Option(Usage): Used


Element Summary: LIN**BP*82411-0C050-B0*VP*0C050-B0*DR*A*KP*KNBN1*ZZ*A~


LIN01 350 Assigned Identification O AN 0/20 " Description:

Alphanumeric characters assigned for differentiation within a transaction set

LIN02 235 Product/Service ID Qualifier M ID 2/2 BP 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/20 82411-0C050-B0

Description: Identifying number for a product or service

TBA's Part Number, Refer To Note 1 LIN04 235 Product/Service ID Qualifier X ID 2/2 VP

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

Will Only Send Code VP - Vendor's Part Number LIN05 234 Product/Service ID X AN 1/48 0C050-B0


Vendor's Part Number if available LIN06 235 Product/Service ID Qualifier X ID 0/2 DR


Will Only Send Code DR - Drawing Revision Number LIN07 234 Product/Service ID X AN 0/10 A


Revision Level LIN08 235 Product/Service ID Qualifier X ID 2/2 KP


Will Only Send Code KP - TBA's Kanban Number LIN09 Product/Service ID X AN 4/10 KNBN1


TBA's Kanban Number LIN10 235 Product/Service ID Qualifier X ID 2/2 ZZ


Will Only Send Code ZZ LIN11 234 Product/Service ID X AN 1/50 A


Refer To Note 2


LIN 830.17


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

Semantics: 1. LIN01 is the line item identification 2. SEQUENCED ORDER (WEEKLY) - 13 WEEKS PRE-NOTICE

KANBAN ORDER (WEEKLY) - 13 WEEKS PRE-NOTICEEKANBAN ORDER (WEEKLY) - 13 WEEKS PRE-NOTICE

Notes: 1. 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 Transactions. 2. Valid Values That Will Be Sent Are:

A = SCHEDULE ORDER | B = SEQUENCED ORDER C = KANBAN ORDER | D = EKANBAN ORDER

LIN 830.18


UIT - Unit Detail User Option(Usage): Used

To specify item unit data

Pos: 020 Max: 1

Detail - MandatoryLoop: LIN Elements: 3

Ref Id UIT01 C001

UIT*EA~ TBA REQ.

Element Name Req Type Min/Max Value Composite Unit of Measure M Comp 2/2 EA Description:

To identify a composite unit of measure (See Figures Appendix for examples of use)

Refer To Note 1


EA EACH LB POUND PC PIECE YD YARD


Element Summary:

UIT 830.19

Pos: 080 Max: 1000



PID - Product/Item Description User Option(Usage): Used

To describe a product or process in free-form format

Element Summary: PID*F****CHANGE ME PART~


PID01 349 Item Description Type M ID 1/1 F Description:

Code indicating the format of a description


Will Only Send Code F - FREE-FORM PID02 750 Product/Process Characteristic Code X ID 0/3 ''

Description: Code identifying the general class of a product or process characteristic

'' PID03 559 Agency Qualifier Code X ID 0/2

Description: Code identifying the agency assigning the code values

PID04 751 Product Description Code X AN 0/12 Description:

A code from an industry code list which provides specific data about a product characteristic

PID05 352 Description M AN 1/50 TEST PART Description:

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

Will Not Send This Element



Will send Product Description

PID 830.20


PO4 - Item Physical Details Pos: 120 Max: 1 User Option(Usage): Used Detail – Mandatory

Loop: LIN Elements: 18 To specify the physical qualities, packaging, weights, and dimensions relating to the item

PO4*6~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value PO401 356 Pack M N0 1/6 6

Description: The number of inner containers, or number of eaches if there are no inner containers, per outer container. Kanban quantity


Element Summary:

PO4 830.21


PRS - Part Release Status Pos: 130 Max: 1 User Option(Usage): Used Detail - Mandatory

Loop: LIN Elements: 2 To indicate the status of the part being ordered or forecast with respect to this material release or planning document.

Ref Id PRS01 682

PRS*1~ TBA REQ.

Element Name Req Type Min/Max Value Part Release Status Code M ID 1/1 1 Description:

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

Refer To Note 1

Notes: 1. Valid Codes Are:

1 – “Non-Carryover ” 4 – “Carryover ” 5 – “New Item ”


Element Summary:

PRS 830.22




REF*DK*S24~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value REF01 128 Reference Identification Qualifier M ID 2/2 DK

Description: Code qualifying the Reference Identification

Will Only Send Code DK; Buyers dock code REF02 127 Reference Identification X AN 2/10 for DK S24


Notes: 1.

Max: 12Pos: 140

Elements: 4Loop: LIN

The Dock Code Will Be Used In the IT111 Element Of The 810 Transaction. (Only for suppliers that have implemented the 810


Element Summary:

Detail - Optional

REF-DK 830.23

Pos: 140 Max: 12















Refer To Note 1


REF-MR 830.25

Pos: 140 Max: 12















Refer To Note 1


REF-MR 830.25

Pos: 140 Max: 12















Refer To Note 1


REF-MR 830.25


TD5 - Carrier Details (Routing Sequence/Transit Time) Pos: 250 Max: 12 User Option(Usage): Used Detail - Optional

Loop: LIN Elements: 15 To specify the carrier and sequence of routing and provide transit time information

Element Summary: TD5*****MAIN ROUTE**DE*1~


TD501 133 Routing Sequence Code X ID 0/2 '' Description:

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


Will Not Send This Element TD502 66 Identification Code Qualifier X ID 0/2 ''

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

TD503 67 Identification Code X AN 0/80 '' Description:

Code identifying a party or other code

TD504 91 Transportation Method/Type Code X ID 0/2 '' Description:

Code specifying the method or type of transportation for the shipment

TD505 387 Routing X AN 1/35 MAIN ROUTE Description:

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

TD506 368 Shipment/Order Status Code X ID 0/2 '' 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

TD507 309 Location Qualifier O ID 2/2 DE Description:

Code identifying type of location

TD508 310 Location Identifier X AN 1/30 1 Description:

Code which identifies a specific location




Will Send “ ROUTING ” Or “MAIN ROUTE ”


Will Only Send Code DE - Destination Shipping

Main Route Code (SHIP ROUTE CODE)

Syntax: 1. C0708 - If TD507 is present, then all of TD508 are required

Comments: 1. 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 (DE) 830.27


Loop SDP Pos: 450 Repeat: 260 Optional

Loop: SDP Elements: N/A

TBA REQ. Ref Id Element Name Req Type Min/Max Usage 450 SDP Ship/Delivery Pattern O 1 Used 460 FST Forecast Schedule O 260 Used


To identify specific ship/delivery requirements

Loop Summary:

Comments: 1. The intent of this segment is to define the routine ship or delivery patterns, as

required, when order quantities are in "buckets", such as weekly, monthly. Ship/delivery patterns eliminate the need to transmit discrete quantities and dates for each required shipment or delivery. It is assumed that a "bucketed" quantity is to be divided equally by the ship/delivery pattern. For example, a weekly quantity of 100 with a delivery pattern of Monday and Wednesday would result in 50 to be delivered on Monday and 50 to be delivered on Wednesday.

SDP LOOP 830.28


SDP - Ship/Delivery Pattern User Option(Usage): Used


SDP*N*F~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value SDP01 678 Ship/Delivery or Calendar Pattern Code M ID 1/1 N

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 F

Description: Code which specifies the time for routine shipments or deliveries

Will Only Send Code F – As Directed

Comments: 1. The intent of this segment is to define the routine ship or delivery patterns, as

required, when order quantities are in "buckets", such as weekly, monthly. Ship/delivery patterns eliminate the need to transmit discrete quantities and dates for each required shipment or delivery. It is assumed that a "bucketed" quantity is to be divided equally by the ship/delivery pattern. For example, a weekly quantity of 100 with a delivery pattern of Monday and Wednesday would result in 50 to be delivered on Monday and 50 to be delivered on Wednesday.


Element Summary:

Detail – Optional Pos: 450 Max: 1

Loop: SDP Elements: 8

SDP 830.29

Pos: 460 Max: 260

Detail - OptionalLoop: SDP Elements: 10


FST - Forecast Schedule User Option(Usage): Used

To specify the forecasted dates and quantities

Element Summary: FST*840*D*W*20041018*20050110***DO*0443~ FST*846*D*W*20041025*20050110***DO*0444~ FST*738*D*W*20041101*20050110***DO*0445~ FST*750*D*W*20041108*20050110***DO*0446~ FST*756*D*W*20041115*20050110***DO*0447~ FST*450*D*W*20041122*20050110***DO*0448~ FST*774*D*W*20041129*20050110***DO*0449~ FST*648*D*W*20041206*20050110***DO*0450~ FST*666*D*W*20041213*20050110***DO*0451~ FST*510*D*W*20041220*20050110***DO*0452~ FST*636*D*W*20050103*20050110***DO*0502~ FST*642*D*W*20050110*20050110***DO*0503~ FST*840*D*W*20041018*20050110***DO*0443~


FST01 380 Quantity M R 1/10 3055 Description:

Numeric value of quantity


NOTE: Toyota Raw Material Suppliers Please be aware that TBA will not send zero FST segments. This will include shut-down periods in both December and July. Otherwise, you will see FST looping 13 times for each part if the time periods above are not involved.

Total Pieces; Refer To Note 8 FST02 680 Forecast Qualifier M ID 1/1 D

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

FST03 681 Forecast Timing Qualifier M ID 1/1 W Description:

Code specifying interval grouping of the forecast

FST04 373 Date M DT 8/8 20060905 Description:

Date expressed as CCYYMMDD

FST05 373 Date O DT 8/8 20060908 Description:


FST06 Date/Time Qualifier X ID 0/3 '' Description:

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

FST07 337 Time X TM 0/4 '' Description:

Time expressed in 24-hour clock time as follows: HHMM, where H = hours (00-23), M = minutes (00-59)

FST08 128 Reference Identification Qualifier X ID 2/2 DO Description:

FST 830.30

Refer To Note 1

Refer To Note 2

Refer To Note 3

Refer To Note 4



830 - Material Release Code qualifying the ReferenceIdentification

FST09 127 X AN 4/30 0636

Syntax: 1. P0607 - If either FST06, FST07 is present, then all are required 2. P0809 - If either FST08, FST09 is present, then all are required

Comments:

Refer To Note 5 Reference Identification Description:


Refer To Notes 6,7

1. As qualified by FST02 and FST03, FST04 represents either a discrete forecastdate or first date of a forecasted bucket (weekly, monthly, quarterly, etc.).

Notes: 1. The Only Codes That Will Be Sent Are:

D - “PRE-NOTICE”D - “BUILD OUT ”

2. The Only Codes That Will Be Sent Are:W - “WEEKLY”F - “BUILD OUT ”

3. FST04 Date Value Descriptions:

4. FST05 Date Value Descriptions:

5. The Only Codes That Will Be Sent Are: MA – Build-Out DO – Pre-Notice

6. Format Will Be In The Form Of: YYWW – Where YY Is The Year, And WW Is The Week.

7. Will Only Contain The Year/Week. 8. BUILD OUT Quantities Will Always Be the FORECAST Segments For A Part Number

FST 830.31


ATH - Resource Authorization Pos: 470 Max: 3 User Option(Usage): Used Detail - Optional

Loop: LIN Elements: 15 To specify resource authorizations (i.e., Finished Labor, Material, etc.) in the planning schedule.

Element Summary: ATH*PQ*20050701*12630**20040101~ ATH*FI**20208**20040101~ ATH*MT**37890**20040101~


ATH01 672 Resource Authorization M ID 2/2 PQ Description:

Code identifying the resource which the buyer is authorizing the seller to commit to


Refer To Note 1 ATH02 373 Resource Authorization Thru Date C ID 8/8 20050701

Description: The date through which the buyer authorized the seller to commit the resource defined in element ATH01

ATH03 380 Current Cumulative Requirements Quantity M R 1/10 12630 Description:

The cumulative quantity that has been authorized to-date from the cumulative start-date (ATH05) through the resource authorization thru-date (ATH02).

ATH04 380 Maximum Cumulative Requirements Quantity O R 0/10 '' Description:

The maximum cumulative quantity that's has been authorized to-date from the cumulative start-date (ATH05) through resource authorization thru-date (ATH02). A high water mark. If forecast decreases, current cumulative requirements quantity also decreases, but maximum cumulative requirements quantity does not.

ATH05 373 Cumulative Start Date C ID 8/8 20040101 Description:

The date where the cumulative quantity count starts. This date might be the start-date of a contract period, a calendar or fiscal year, or other.

Required ONLY if ATH01 = PQ (Same as BFR06)

Refer To Note 2


Syntax: 1. At least one of ATH02 or ATH03 is required. 2. If ATH03 is present, then ATH05 is required. 3. If ATH04 is present, then ATH05 is required.

Notes: 1. Only three Resource Authorization Codes are used;

PQ Cumulative Quantity Required Prior to First Schedule Period FI Finished (Labor, Material, and Overhead/Burden - FAB) MT Material (RAW)

2. If ATH01 = PQ Cumulative qty that has been authorized from Start Date (ATH05) through End Date (ATH02). FI Sum total of "FAB" authorization for all ultimate destinations locations within this part/model year loop. MT Sum total of "RAW" authorization for all ultimate destinations within this part/model year loop.

ATH 830.32


Loop SHP Pos: 470 Repeat: 25 Optional

Loop: SDP Elements: N/A To identify last receipt and cum quantity.


Ref Id Element Name Req Type Min/Max Usage 470 SHP Last Receipt/Cum Data O 1 Used 480 REF Last Shipper Number O 5 Used


SHP LOOP 830.33

01

Pos: 470 Max: 25

Detail - OptionalLoop: N/A Elements: 7


SHP - Shipped/Received Information User Option(Usage): Used

To specify shipment and/or receipt information.

Element Summary: SHP*01*16840*050*20041017~


SHP01 673 Quantity Qualifier O ID 2/2 Description:

Qualifier for value of quantity


Will Only Send Code 01 - Discrete Quantity SHP02 380 Discrete Quantity X R 1/15 16840

Description: Quantity

SHP03 374 Date/Time Qualifier X ID 3/3 050 Description:

Qualifier for transaction date. Will Only Send Code 050 - Last Received date.

SHP04 373 Last Received Date O DT 8/8 20041017 Description:

Last receipt date expressed as CCYYMMDD. Supplier Last Ship Date

Refer To Note 1

Syntax: 1. If SHP01 is present, then SHP02 is required. 2. If SHP04 is present, then SHP03 is required.

Comments: 1. The SHP segment is used to communicate shipment, delivery, or receipt information and may

include discrete or cumulative quantities, dates, and times.

2. SHP04 - The date shipped, delivered, received, or the cumulative quantity start date (as qualified by SHP03).

3. SHP06 - The cumulative quantity end date.

Notes: 1. This is "TBA's Last Received Date" from a Supplier's shipment.

SHP-01 830.34


REF - Reference Numbers User Option(Usage): Used

To specify identifying numbers.

REF*SI*1000060498~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value REF01 128 Reference Number Qualifier M ID 2/2 SI

Description: Qualifier for Reference Number

Will Only Send Code SI - Shipper Number REF02 127 Reference Number X AN 1/30 1000060498

Description: Reference Number - Last Shipper Received

Element Summary:


Pos: 480 Max: 5 Detail - Optional

Loop: N/A Elements: 4

REF-SI 830.35

Pos: 470 Max: 25

Detail - OptionalLoop: N/A Elements: 7


SHP - Shipped/Received Information User Option(Usage): Used

To specify shipment and/or receipt information.

Element Summary: SHP*02*12626*051*20041018**20041017~


SHP01 673 Quantity Qualifier O ID 2/2 02 Description:

Qualifier for value of quantity


Will Only Send Code 02 - Cum Quantity. SHP02 380 Cumulative Quantity X R 1/15 12626

Description: Quantity

SHP03 374 Date/Time Qualifier X ID 3/3 51 Description:

Qualifier for transaction date.

SHP04 373 Cumulative Quantity Start Date O DT 8/8 20041018 Description:

Cum date expressed as CCYYMMDD. ”, This is beginning inventory “Date” for this ultimate destination.

SHP05 337 Time O TM 4/4 Description:


SHP06 373 Supplier Last Ship Date O DT 8/8 20041017 Description:

Last receipt date expressed as CCYYMMDD. This is the “Supplier Last Ship Date” from TBA.

SHP07 337 Time O TM 4/4 Description:


Will Send Code 051 - Cumulative Quantity Start Date.

Syntax: 1. If SHP01 is present, then SHP02 is required. 2. If SHP04 is present, then SHP03 is required.

1. The SHP segment is used to communicate shipment, delivery, or receipt information and may include discrete or cumulative quantities, dates, and times.

2. SHP04 - The date shipped, delivered, received, or the cumulative quantity start date (as qualified by SHP03).

3. SHP06 - The cumulative quantity end date.

SHP-02 830.36

Comments:


CTT - Transaction Totals User Option(Usage): Used

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

CTT*28*197016~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value CTT01 354 Number of Line Items M N0 1/6 28

Description: Total Number of LIN Segments Total Number of LIN Segments

CTT02 347 Hash Total O R 1/10 197016 Description: Total Of Net Quantity On The FST

Segments. 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 Quantity

Comments: 1. This segment is intended to provide hash totals to validate transaction

completeness and correctness.

Notes: 1. Total Of Net Quantity On The FST Segments.

Pos: 010 Max: 1


Element Summary:

Summary – Optional Elements: 7Loop: N/A

CTT 830.37


TBA REQ. Ref Id Element Name Req Type Min/Max Value SE01 96 Number of Included Segments M N0 1/10 823

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 000000001 Description:



SE - Transaction Set Trailer Pos: 020 Max: 1 User Option(Usage): Must Use Summary - Mandatory

Loop: N/A Elements: 2 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: SE*823*000000001

Comments: 1. SE is the last segment of each transaction set.

SE 830.38


Pos: Max: 1

Not Defined - MandatoryLoop: N/A Elements: 2

GE - Functional Group Trailer User Option(Usage): Must Use

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

GE*1*1200 TBA REQ.

Ref Id Element Name Req Type Min/Max Value GE01 97 Number of Transaction Sets Included M N0 1/6 1

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 1200 Description:

Assigned number originated and maintained by the sender


Element Summary:

Semantics: 1. The group 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 group 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.

GE 830.39


IEA - Interchange Control Trailer Pos: Max: 1 User Option(Usage): Must Use Not Defined - Mandatory

Loop: N/A Elements: 2 To define the end of an interchange of zero or more functional groups and interchange-related control segments

Element Summary: IEA*1*000000001


IEA01 I16 Number of Included Functional Groups M N0 1/5 1 Description:

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

IEA02 I12 Interchange Control Number M N0 9/9 000000001 Description:

A control number assigned by the interchange sender


IEA 830.40

830 - Material Release EXAMPLE OF A MATERIAL RELEASE (830)

WEEKLY DOCUMENT (FOR PARTS AND COMPONENTS) ISA*00*TOYOTA *01*796567667*01*796567667 *ZZ*999999999-20600*060608

*0606*U*00400*000000001*0*P*>~

GS*PS*796567667*999999999*20060608*0606*1200*X*004010~

ST*830*000000001~

BFR*00**06072006*DL*A*20060703*20061009*20040918***S10706~

N1*MI*TMIHB*1*063844752~

N1*ST*TMIHB*92*096~

N1*SU*ABC Manufacturing*92*12345~

N1*SF*ABC Manufacturing*1*999999999~

PER*SC*BONNIE SMITH*TE*8597346000~

LIN**BP*82411-0C050-B0*VP*0C050-B0*DR*A*KP*KNBN1*ZZ*A~

UIT*EA~

PID*F****CHANGE ME PART~

PO4*6~

PRS*1~

REF*DK*S24~

REF*LU*LOCN1~

REF*MR*M621~

TD5*****MAIN ROUTE**IT*SUB ROUTE~

TD5*****MAIN ROUTE**DE*1~

SDP*N*F~

FST*840*D*W*20041018*20050110***DO*0443~

FST*846*D*W*20041025*20050110***DO*0444~

FST*738*D*W*20041101*20050110***DO*0445~

FST*750*D*W*20041108*20050110***DO*0446~

FST*756*D*W*20041115*20050110***DO*0447~

FST*450*D*W*20041122*20050110***DO*0448~

FST*774*D*W*20041129*20050110***DO*0449~

FST*648*D*W*20041206*20050110***DO*0450~

FST*666*D*W*20041213*20050110***DO*0451~

FST*510*D*W*20041220*20050110***DO*0452~

FST*636*D*W*20050103*20050110***DO*0502~

FST*642*D*W*20050110*20050110***DO*0503~

ATH*PQ*20050701*12630**20040101~

ATH*FI**20208**20040101~

ATH*MT**37890**20040101~

SHP*01*16840*050*20041017~

REF*SI*1000060498~

SHP*02*12626*051*20041018**20041017~

LIN**BP*82411-0C050-E0*VP*0C050-E0*DR*B*KP*KNBN2*ZZ*A~

UIT*EA~


PO4*6~

PRS*1~

REF*DK*S24~

REF*LU*WHSE10~

REF*MR*M621~


WEEKLY 830.41

830 - Material Release TD5*****MAIN ROUTE**DE*2~

SDP*N*F~

FST*624*D*W*20041018*20050110***DO*0443~

FST*618*D*W*20041025*20050110***DO*0444~

FST*546*D*W*20041101*20050110***DO*0445~

FST*534*D*W*20041108*20050110***DO*0446~

FST*528*D*W*20041115*20050110***DO*0447~

FST*312*D*W*20041122*20050110***DO*0448~

FST*510*D*W*20041129*20050110***DO*0449~

FST*498*D*W*20041206*20050110***DO*0450~

FST*474*D*W*20041213*20050110***DO*0451~

FST*402*D*W*20041220*20050110***DO*0452~

FST*444*D*W*20050103*20050110***DO*0502~

FST*432*D*W*20050110*20050110***DO*0503~

ATH*PQ*20050701*9390**20040101~

ATH*FI**15024**20040101~

ATH*MT**28170**20040101~

SHP*01*12520*050*20041017~

REF*SI*1000060498~

SHP*02*9386*051*20041018**20041017~ (Cut to end)

LIN**BP*ABCDE-0C500-E0*VP*0C500-E0***KP*KNBN29*ZZ*A~

UIT*EA~


PO4*6~

PRS*1~

REF*DK*S24~

REF*LU*WHSE11~

REF*MR*M621~


TD5*****MAIN ROUTE**DE*29~

SDP*N*F~

FST*222*D*W*20041018*20050110***DO*0443~

FST*222*D*W*20041025*20050110***DO*0444~

FST*210*D*W*20041101*20050110***DO*0445~

FST*216*D*W*20041108*20050110***DO*0446~

FST*210*D*W*20041115*20050110***DO*0447~

FST*120*D*W*20041122*20050110***DO*0448~

FST*210*D*W*20041129*20050110***DO*0449~

FST*228*D*W*20041206*20050110***DO*0450~

FST*246*D*W*20041213*20050110***DO*0451~

FST*204*D*W*20041220*20050110***DO*0452~

FST*258*D*W*20050103*20050110***DO*0502~

FST*264*D*W*20050110*20050110***DO*0503~

ATH*PQ*20050701*3375**20040101~

ATH*FI**5400**20040101~

ATH*MT**10125**20040101~

SHP*01*4500*050*20041017~

REF*SI*1000060498~

SHP*02*3371*051*20041018**20041017~

CTT*28*197016~

SE*823*000000001~

GE*1*1200~

IEA*1*000000001~

WEEKLY 830.42

856 - Ship Notice/Manifest

TOYOTA BOSHOKU

INFORMATION SYSTEMS


FOR

ADVANCE SHIPMENT NOTIFICATIONS (856)OUTBOUND

TOYOTA BOSHOKU CONTACT EDI SUPPORT LINE

(859) 817-4050

Saturday, April 01, 2006

revision: 2/01/2008

856 856.1


DATA REQUIREMENTS

MISCELLANEOUS STANDARD: ANSI X12 - AIAG EDI ACKNOWLEDGMENT FUNCTIONAL ACKNOWLEDGMENT -TBA WILL SEND

A FUNCTIONAL ACKNOWLEDGMENT UPON RECEIPT OF THE 856.




DATA FREQUENCY ANYTIME VALUE ADDED NETWORK (VAN) STERLING INFORMATION BROKER






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






Functional Group=SH This establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment.

The transaction set enables the sender to packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information. The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.


Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage 010 ST Transaction Set Header M 1 Must use 020 BSN Beginning Segment for Ship Notice M 1 Must use 040 DTM Date/Time Reference O 10 Used

Detail: TBA REQ.X12 ANSI REQUIREMENTS Ver. 4010

Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level – “Shipping” M 1 C2/010 Must use 080 MEA Measurements O 40 Used 110 TD1 Carrier Details (Quantity and O 20 Used

Weight) Used 120 TD5 Carrier Details (Routing O 12 Used

Sequence/Transit Time) Used 130 TD3 Carrier Details (Equipment) O 12 Used 140 TD4 Carrier Details (Special Handling, or O 5 Used

Hazardous Materials, or Both) Used 150 REF Reference Identification O >1 Used 220 N1 Name O 1 Used

LOOP ID - HL 200000 C2/010L 010 HL Hierarchical Level – “Order” M 1 C2/010 Must use 050 PRF Purchase Order Reference O 1 Used 150 REF Reference Identification O >1 Used 220 N1 Name O 1 Used

LOOP ID - HL 200000 C2/010L 010 HL Hierarchical Level – “Item” M 1 C2/010 Must use 020 LIN Item Identification O 1 Used 030 SN1 Item Detail (Shipment) O 1 Used

Summary: TBAREQ.X12 ANSI REQUIREMENTS Ver. 4010

Pos Id Segment Name Req Max Use Repeat Notes Usage 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

SH 856.4

856 - Ship Notice/Manifest IEA Interchange Control Trailer M 1 Must use

Notes: 3/010 Number of line items (CTT01) is the accumulation of the number of HL segments. If used, hash total

(CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.

Comments: 2/010L The HL segment is the only mandatory segment within the HL loop,

and by itself, the HL segment has no meaning. 2/010 The HL segment is the only mandatory segment within the HL loop,

and by itself, the HL segment has no meaning.

SH 856.5

856 - Ship Notice/Manifest ISA - Interchange Control Header Pos: Max: 1 User Option(Usage): Must use Not Defined - Mandatory


Element Summary: ISA*00*SUPPLIERNA*01*0123456789*ZZ*123456789-12345*01*123456789 *060706*1030*U*00400*000000001*0*P*>~


ISA01 I01 Authorization Information Qualifier M ID 2/2 00 Description:



Only Send Code 00 ISA02 I02 Authorization Information M AN 10/10 SUPPLIERNA

Description: Information used for additional identification or authorization ofthe interchange sender or the data in the interchange; the typeof information is set by the Authorization Information Qualifier (I01)

Only Send Senders Name ISA03 I03 Security Information Qualifier M ID 2/2 01

Description: Code to identify the type of information in the Security Information

Only Send Code – 01 ISA04 I04 Security Information M AN 10/10 0123456789

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)

Sender Duns # ISA05 I05 Interchange ID Qualifier M ID 2/2 ZZ

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

Typically Send Code ZZ ISA06 I06 Interchange Sender ID M AN 15/15 123456789-12345

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

Typically Send DUNS - Supplier Code (i.e. 123456789-12345)

ISA07 I05 Interchange ID Qualifier M ID 2/2 01 Description:


Only Send Code 01 ISA08 I07 Interchange Receiver ID M AN 9/15 '123456789 '

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

Refer To Note 1 ISA09 I08 Interchange Date M DT 6/6 60706

ISA 856.6

1030

U

Only Send Code U 00400

Only Send Code 00400 XXXXXXXXX

0

Only Send 0 – “No” USE 'P' FOR

PRODUCTION

'T' FOR TEST

> Only Send Codes T,P – “Test” or “Production”

856 - Ship Notice/ManifestDescription:

Date of the interchange

ISA10 I09 Interchange TimeDescription:

Time of the interchange

ISA11 I10 Interchange Control Standards Identifier Description:


M TM 4/4

M ID 1/1

ISA12 I11 Interchange Control Version Number M ID 5/5Description:

Code specifying the version number of the interchange control segments

ISA13 I12 Interchange Control Number M N0 9/9 Description:


ISA14 I13 Acknowledgment Requested M ID 1/1 Description:

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

ISA15 I14 Usage Indicator M ID 1/1Description:

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

ISA16 I15 Component Element Separator M ID 1/1 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



096 Trim Masters, Inc. Harrodsburg, KY USA139 Trim Masters, Inc. Bardstown, KY USA 192 Trim Masters, Inc. Nicholasville, KY USA 193 Trim Masters, Inc. Leitchfield, KY USA 194 Trim Masters, Inc. Modesto, CA USA 199 Automotive Technology Systems LLC. Lawrenceville, I 592 Master Trim de Mexico Torreon Mexico 572 Trim Masters, Inc. Bartlett, IN USA 650 Master Trim de Mexico Chavez Mexico 705 Trim Masters, Inc. Elmira Ontario Canada 873 Trim Masters, Inc. San Antonio, TX USA



ISA 856.7

856 - Ship Notice/Manifest GS - Functional Group Header Pos: Max: 1 User Option(Usage): Must use Not Defined - Mandatory


Element Summary: GS*SH*123456789*063844752*20060706*1030*000000001*X*004010~


GS01 479 Functional Identifier Code M ID 2/2 SH Description:



Only Send Code SH GS02 142 Application Sender's Code M AN 2/15 123456789


GS03 124 Application Receiver's Code M AN 2/15 063844752 Description:


GS04 373 Date M DT 8/8 20060706 Description:


GS05 337 Time M TM 4/4 1030 Description:

Time expressed in 24-hour clock time as follows: 1030, where H = hours (00-23), M = minutes (00-59)

GS06 28 Group Control Number M N0 1/9 000000001 Description:


GS07 455 Responsible Agency Code M ID 1/2 X Description:

Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

GS08 480 Version / Release / Industry Identifier Code M AN 1/12 004010 Description:


Senders DUNS (see Note 2)

Refer To Note 1

Only Send Code X

Only Send Code 004010

Semantics:

1. GS04 is the group date. 2. GS05 is the group time. 3. The group control number GS06 in this header must be identical to the

same data element in the associated functional group trailer, GE02.

GS 856.8


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.



096 Trim Masters, Inc. Harrodsburg, KY USA139 Trim Masters, Inc. Bardstown, KY USA 192 Trim Masters, Inc. Nicholasville, KY USA 193 Trim Masters, Inc. Leitchfield, KY USA 194 Trim Masters, Inc. Modesto, CA USA 199 Automotive Technology Systems LLC. Lawrenceville, IL USA592 Master Trim de Mexico Torreon Mexico 572 Trim Masters, Inc. Bartlett, IN USA 650 Master Trim de Mexico Chavez Mexico 705 Trim Masters, Inc. Elmira Ontario Canada 873 Trim Masters, Inc. San Antonio, TX USA



GS 856.9

2. The GS03 Element for Toyota Direct Suppliers only, use Receivers DUNs Number - Supplier Code.i.e. 999999999-12345. The data will match the ISA07

856 - Ship Notice/Manifest ST - Transaction Set Header User Option(Usage): Must Use


ST*856*000000001~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value ST01 143 Transaction Set Identifier Code M ID 3/3 856

Description: Code uniquely identifying a Transaction Set

Only send code 856 ST02 329 Transaction Set Control Number M AN 4/9 0001

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




Max: 1Pos: 010 Heading - Mandatory

Elements: 2Loop: N/A

Element Summary:

ST 856.10

00

856 - Ship Notice/Manifest BSN - Beginning Segment for Ship Notice Pos: 020 Max: 1 User Option(Usage): Must use Heading - Mandatory

Loop: N/A Elements: 7 To transmit identifying numbers, dates, and other basic data relating to the transaction set

Element Summary: BSN*00*0962468*20060706*1030~


BSN01 353 Transaction Set Purpose Code M ID 2/2 Description:



Only use codes 00 (Original) or 05 (REPLACE) BSN02 396 Shipment Identification M AN 2/16 0962468

Description: A unique control number assigned by the original shipper to identify a specific shipment

BSN03 373 Date M DT 8/8 20060706 Description:

Date expressed as CCYYMMDD BSN04 337 Time M TM 4/8 1030

Description: Time expressed in 24-hour clock time as follows: 1030, or 1030SS, or 1030SSD, or 1030SSDD, 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)

BSN05 1005 Hierarchical Structure Code O ID 4/4 NOT USED Description:

Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set

BSN06 640 Transaction Type Code X ID 2/2 NOT USED Description:

Code specifying the type of transaction

BSN07 641 Status Reason Code O ID 3/3 NOT USED Description:

Code indicating the status reason

Not Used

Not Used

Not Used

Syntax: 1. C0706 - If BSN07 is present, then all of BSN06 are required

Semantics: 1. BSN03 is the date the shipment transaction set is created. 2. BSN04 is the time the shipment transaction set is created.

Comments: 1. TBA is requesting that the shipment number be limited to 16 positions

BSN 856.11

011

Pos: 040 Max: 10

Heading - MandatoryLoop: N/A Elements: 6

856 - Ship Notice/Manifest DTM - Date/Time Reference User Option(Usage): Used

To specify pertinent dates and times

Element Summary: DTM*011*20060706*1030*ET~


DTM01 374 Date/Time Qualifier M ID 3/3 Description:

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


Only use code 011 (Shipment Date Qual) DTM02 373 Date X DT 8/8 20060706

Description: Date expressed as CCYYMMDD

DTM03 337 Time X TM 4/8 1030 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)

DTM04 623 Time Code O ID 2/2 ET Description:

Code identifying the time. In accordance with International Standards Organization standard 8601

DTM05 1250 Date Time Period Format Qualifier X ID 2/3 NOT USED Description:

Code indicating the date format, time format, or date and time format

DTM06 1251 Date Time Period X AN 1/35 NOT USED Description:

Expression of a date, a time, or range of dates, times or dates and times

Refer to Note 1

Do not send

Do not send

Syntax: 1. R020305 - At least one of DTM02,DTM03,DTM05 is required 2. C0403 - If DTM04 is present, then all of DTM03 are required 3. P0506 - If either DTM05,DTM06 is present, then all are required

Notes: 1. Time Code:

ET = Eastern Time Code2. TBA is expecting for all Ship times to be in eastern standard or eastern daylight time (based on

what time of year it is)

DTM 856.12

856 - Ship Notice/Manifest Loop HL - Shipping Pos: 010 Repeat: 200000

Mandatory Loop: HL Elements: N/A

To identify dependencies among and the content of hierarchically related groups of data segments

TBA REQ. Ref Id Element Name Req Type Min/Max Value 010 HL Hierarchical Level M 1 1 Must use 080 MEA Measurements M 40 40 Must use110 TD1 Carrier Details (Quantity and Weight) M 20 20 Must use 120 TD5 Carrier Details (Routing Sequence/Transit Time M 12 12 Must use130 TD3 Carrier Details (Equipment) M 12 12 Must use 140 TD4 Carrier Details (Special Handling, or Haz. Mate O 5 5 Used 150 REF Reference Identification M >1 >1 Must use 220 N1 Name O 1 1 Used


Loop Summary:

Comments: 1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item

data to shipment data, and packaging data to line-item data. 2. The HL segment defines a top-down/left-right ordered structure. 3. HL01 shall contain a unique number for each occurrence of the HL segment in the transaction set. For example, HL01

could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 5. HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL

segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

HL LOOP SHIPPING 856.13

856 - Ship Notice/Manifest HL - Hierarchical Level – Shipping User Option(Usage): Must Use


HL*1**S*1~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value HL01 628 Hierarchical ID Number M N 1/12 1

Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

HL02 734 Hierarchical Parent ID Number O N 1/12 NONE Description:

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

HL03 735 Hierarchical Level Code M ID 1/2 S Description:

Code defining the characteristic of a level in a hierarchical structure

Only use code S - Shipping HL04 736 Hierarchical Child Code O ID 1/1 1

Description: Code indicating if there are hierarchical child data segments subordinate to the level being described

Only use code 1

Comments:


Pos: 010 Max: 1 Detail - Mandatory

Loop: HL Elements: 4

Element Summary:

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure. 3. HL01 shall contain a unique number for each occurrence of the HL segment in the transaction set. For example, HL01





HL SHIPPING 856.14

856 - Ship Notice/Manifest MEA - Measurements Pos: 080 Max: 40 User Option(Usage): Used Detail - Mandatory

Loop: HL Elements: 10 To specify physical measurements or counts, including dimensions, tolerances, variances, and weights.

Element Summary: MEA*PD*G*200*LB~ MEA*PD*G*200*LB~


MEA01 737 Measurement Reference ID Code O ID 2/2 PD Description:

Code identifying the broad category to which a measurement applies


Only use PD – “Physical Dimensions” MEA02 738 Measurement Qualifier O ID 1/3 G

Description: Code identifying a specific product or process characteristic to which a measurement applies

MEA03 739 Measurement Value X R 1/20 200 Description:

The value of the measurement MEA04 C001 Composite Unit of Measure OT Comp NOT USED

Description: To identify a composite unit of measure(See Figures Appendix for examples of use)

355 Unit or Basis for Measurement Code M ID 2/2 LB Description:

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

Only use codes G or N – Refer to note 1.

Only use code LB – “Pounds”.

Semantics: 1. MEA04 defines the unit of measure for MEA03.

Notes: 1. If sent, use code G – “Gross” – first, then use code N – “Net”.

MEA 856.15

856 - Ship Notice/Manifest TD1 - Carrier Details (Quantity and Weight) User Option(Usage): Must Use

To specify the transportation details relative to commodity, weight, and quantity

TD1*PLT90*9~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value TD101 103 Packaging Code M AN 5/5 PLT90

Description: Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required

Refer to Notes 1,2 TD102 80 Lading Quantity X N0 1/7 9

Description: Number of units (pieces) of the lading commodity


Notes: 1. TBA is expecting multiple TD1’s if necessary (i.e. 3 Pallets, 2 Boxes, etc.) 2. Valid values are:

BOX90 - Box CNT90 - Container CTN90 - Carton PLT90 - Pallet


Element Summary:

Detail - Mandatory Max: 20Pos: 110

Elements: 10Loop: HL

TD1 856.16

Pos: 120 Max: 12

Detail - MandatoryLoop: HL Elements: 4

856 - Ship Notice/Manifest TD5 - Carrier Details (Routing Sequence/Transit Time) User Option(Usage): Used

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

Element Summary: TD5*B*2*LCQX*M*ROUTING**IT*ABCDEF~


TD501 133 Routing Sequence Code O ID 1/1 B Description:



Only use code B – “Any Mode” TD502 66 Identification Code Qualifier X ID 1/2 2


TD503 67 Identification SCAC Code M AN 4/9 LCQX Description:


TD504 91 Transportation Method/Type Code X ID 1/2 M Description:


TD505 387 Routing X AN 1/35 ROUTING Description:


TD506 368 Shipment/Order Status Code X ID 2/2 NOT USED Description:


TD507 309 Location Qualifier O ID 1/2 IT Description:


TD508 310 Location Identifier X AN 1/30 ABCDEF Description:


Only use codes 2 or 25

Refer to Note 1

Conveyance Code Refer to Note 2

Send “ROUTING ” Or “SUB-ROUTING ”

Do Not Send.

Send Code IT or PP; Refer To Note 3

Sub-Route Cross Dock Code; Refer To Note 3

Notes: 1. If TD502 is 2 (SCAC Code), then some examples of TD503 will be:

RYDD – RYDER LCXQ – LCC VASC – VASCOR BWGL = BESTWAY DAFG = DAYTON YFSY = YELLOW HMES

TD5 856.17

856 - Ship Notice/ManifestHMES = HOLLAND

If TD502 is 25 (Carriers Supplier Code), then TD503 will be:70000 – RYDER71000 – LCC65150 - VASCOR

2. Valid Conveyance Codes are:A AIRCE CUSTOMER PICKUP / CUSTOMER'S EXPENSEE EXPEDITED TRUCK SUPPLIER'S EXPENSEJ MOTORL CONTRACT CARRIERLT LESS THAN TRAILER LOAD (LTL)M MOTOR (COMMON CARRIER)PR POOLED RAILPT POOLED TRUCKR RAILSR SUPPLIER TRUCK

3. This Segment Is Optional. It Will Only Appear If There Is A Sub-Route or Pool Point. IT INTERMEDIATE FOB POINTPP POOL POINT

Pos: 130 Max: 12

Detail – MandatoryLoop: HL Elements: 3

856 - Ship Notice/Manifest TD3 - Carrier Details (Equipment) User Option(Usage): Used

To specify transportation details relating to the equipment used by the carrier

Element Summary: TD3*TL**TL04687******S99999999~


TD301 40 Equipment Description Code M ID 2/2 TL Description:

Code identifying type of equipment used for shipment


Use code TL – “Trailer" unless otherwise specified TD302 206 Equipment Initial O AN 1/4 Not Used

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

TD303 207 Equipment Number X AN 1/10 TL04687 Description:

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

TD304 187 Weight Qualifier O ID 1/2 Not Used TD305 081 Weight O R 1/10 Not Used TD306 355 Unit of Measure Code O ID 2/2 Not Used TD307 102 Ownership Code O ID 1/1 Not Used TD308 407 Seal Status Code O ID 2/2 Not Used TD309 255 Seal Number X AN 2/15 S99999999 TD310 024 Equipement Type O ID 4/4 Not Used

Not USED

Trailer number.

Notes: 1. Valid Equipment Description Codes are:

RR - Rail Car TL - Trailer (not otherwise specified) TV - Truck, Van

TD3 856.19


User Option(Usage): Used

To specify transportation special handling requirements, or hazardous materials information, or both

TD4*CH*D*H047~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value TD401 152 Special Handling Code X ID 2/3 CH

Description: Code specifying special transportation handling instructions

Only use code CH – “Carrier” TD402 208 Hazardous Material Code Qualifier X ID 1/1 D

Description: Code which qualifies the Hazardous Material Class Code (209)

Only use code D – “DOT” TD403 209 Hazardous Material Class Code X AN 2/4 H047

Description: Code specifying the kind of hazard for a material

TD4 - Carrier Details (Special Handling, or Hazardous

Syntax: 1. R010204 - At least one of TD401 or TD402 is required 2. C0203 - If TD402 is present, then all of TD403 are required

Pos: 140 Max: 5

Materials, or Both)


Element Summary:

Detail - Optional Elements: 3Loop: HL

TD4 856.20

856 - Ship Notice/Manifest REF - Reference Identification Pos: 150 Max: >1 User Option(Usage): Used Detail - Mandatory

Loop: HL Elements: 2 To specify identifying information

Element Summary: REF*BM*156023~

Ref Id Element Name TBA REQ.

Req Type Min/Max Value X12 ANSI REQUIREMENTS Ver. 4010

REF01 128 Reference Identification Qualifier M ID 2/2 BM Description:

Code qualifying the Reference Identification Only use code BM – “Bill of Lading Number”

REF02 127 Reference Identification X AN 1/30 156023 Description:

Reference information as defined for a particularTransaction Set or as specified by the ReferenceIdentification Qualifier

REF-BM 856.21

Pos: 230 Repeat: 3 Mandatory


856 - Ship Notice/Manifest Loop N1



Ref Id Element Name Req Type Min/Max Value 230 N1 Name M 3 Must use240 N2 Additional Name Information O 2 Used 250 N3 Address Information O 2 Used 260 N4 Geographic Location O 1 Used 280 PER Administrative Communications Contact O 3 Used


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.


N1 LOOP 856.22

Pos: 220 Max: 1

Detail - MandatoryLoop: N1 Elements: 4

856 - Ship Notice/Manifest N1 - Name User Option(Usage): Used


Element Summary: N1*ST*TMIEL*92*096~


N101 98 Entity Identifier Code M ID 2/3 ST Description:



N102 93 Name M AN 1/30 TMIEL Description:

Free-form name

N103 66 Identification Code Qualifier M ID 1/2 Description:

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

Only use code 92 – “Assigned by Buyer” 705N104 67 Identification Code M AN 2/3

Description: Code identifying a party or other code

Refer to note 1

Syntax: 1. R0203 - 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.


Notes: 1. Valid Code Values To Send Are:

096 139 192 193 194 199 592 572 650 705 873

Plant Name and Location(92)Code (1)DUNs # Ship To Name

Trim Masters, Inc. Harrodsburg, KY USA 063844752 TMIHB Trim Masters, Inc. Bardstown, KY USA 796567667 TMIBT Trim Masters, Inc. Nicholasville, KY USA 825946353 TMINV Trim Masters, Inc. Leitchfield, KY USA 967532524 TMILF Trim Masters, Inc. Modesto, CA USA 806416004 TMIMO Automotive Technology Systems LLC. Lawrenceville, IL 877899695 ATS Master Trim de Mexico Torreon Mexico 812596419 MTMT Trim Masters, Inc. Bartlett, IN USA 052922697 BART Master Trim de Mexico Chavez Mexico 812749414 MTMC Trim Masters, Inc. Elmira Ontario Canada 201047177 TMIEL Trim Masters, Inc. San Antonio, TX USA 626731827 TMITX

N1-ST 856.23

92

856 - Ship Notice/Manifest N3 - Address Information User Option(Usage): Used

To specify the location of the named party


Loop: N1 Elements: 2

Element Summary: N3*45 SOUTH FIELD DRIVE~


N301 166 Address Information M AN 1/55 45 SOUTH FIELD DRIVE Description:

Address information


N3 856.24

856 - Ship Notice/Manifest N4 - Geographic Location User Option(Usage): Used

To specify the geographic place of the named party

Pos: 260 Max: 1

Detail - OptionalLoop: N1 Elements: 6

Element Summary: N4*ELMIRA*ON*N3B3L6*CAN~


N401 19 City Name O AN 2/30 ELMIRA Description:

Free-form text for city name N402 156 State or Province Code O ID 2/2 ON

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

N403 116 Postal Code O ID 3/15 N3B3L6 Description:

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

N404 116 Country Code O ID 3/15 CAN Description:

Code defining international country code


N4 856.25

Pos: 220 Max: 1




Element Summary: N1*SU*SUPPLIER NAME*92*12345~


N101 98 Entity Identifier Code M ID 2/3 SU Description:



Only use code SU – “Supplier” N102 93 Name M AN 1/60 SUPPLIER NAME

Description: Free-form name

N103 66 Identification Code Qualifier M ID 1/2 92 Description:

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

N104 67 Identification Code M AN 2/30 12345 Description:


Only use code 92 – “Assigned by Buyer”

Refer to note 1


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.


Notes: 1. Supplier Code Issued by TBA

SU Supplier/Manufacturer

N1-SU 856.26

Pos: 220 Max: 1




Element Summary: N1*SF*SUPPLIERNAME*01*123456789~


N101 98 Entity Identifier Code M ID 2/3 SF Description:



Only use code SF – “Ship From” N102 93 Name M AN 1/30 SUPPLIER NAME

Description: Free-form name Not Used

N103 66 Identification Code Qualifier M ID 1/2 01 Description:

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

N104 67 Identification Code M AN 9/9 999999999 Description:



Refer to note 1


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.


Notes: 1. Send Supplier DUNs number.

SF Ship From

N1-SF 856.27

Min/Ma

856 - Ship Notice/Manifest Loop HL - Order Pos: 010 Repeat: 200000



TBA REQ. Ref Id Element Name Req Type x Value 010 HL Hierarchical Level M 1 Must use 050 PRF Purchase Order Reference M 1 Must use 150 REF Reference Identification O >1 Used 220 N1 Name O 1 Used


Loop Summary:







HL LOOP ORDER 856.28

856 - Ship Notice/Manifest HL - Hierarchical Level - Order User Option(Usage): Must Use


HL*2*1*O*1~ TBA REQ.



HL02 734 Hierarchical Parent ID Number M N 1/12 1 Description:


HL03 735 Hierarchical Level Code M ID 1/2 O Description:


Only use codes O - Order HL04 736 Hierarchical Child Code M ID 1/1 1


Only use code 1

Comments:


Element Summary:

Max: 1

Elements: 4Loop: HL Detail - Mandatory

Pos: 010







HL ORDER 856.29

856 - Ship Notice/Manifest Pos: 050 Max: 1


PRF - Purchase Order Reference User Option(Usage): Used

To provide reference to a specific purchase order

Element Summary: PRF*70202031~


PRF01 324 Purchase Order Number M AN 1/22 70202031 Description:

Identifying number for Purchase Order assigned by the orderer/purchaser


PRF 856.30

856 - Ship Notice/Manifest REF - Reference Identification User Option(Usage): Used


REF*MH*I99999~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value REF01 128 Reference Identification Qualifier M ID 2/3 MH

Description: Code qualifying the Reference Identification

Only use code MH – “Manufacturing order number” REF02 127 Manifest Number M AN 1/30 I99999

Description: Manifest number must be unique per Purchase Order

Syntax: 1. R0203 - At least one of REF02,REF03 is required

Semantics: 1. REF04 contains data relating to the value cited in REF02.


Element Summary:

Detail - Mandatory Max: >1Pos: 150

Elements: 4Loop: HL

REF-MH 856.31

856 - Ship Notice/Manifest Loop HL - ITEM Pos: 010 Repeat: 200000



TBA REQ. Ref Id Element Name Req Type Min/Max Value 010 HL Hierarchical Level M 1 Must use 020 LIN Item Identification M 1 Used 030 SN1 Item Detail (Shipment) M 1 Used


Loop Summary:







HL LOOP ITEM 856.32

856 - Ship Notice/Manifest HL - Hierarchical Level - Item User Option(Usage): Must Use


HL*3*2*I*0~ TBA REQ.



HL02 734 Hierarchical Parent ID Number M N 1/12 2 Description:


HL03 735 Hierarchical Level Code M ID 1/2 I Description:


Only use code I - Item HL04 736 Hierarchical Child Code M ID 1/1 0


Only use code 0

Comments:


Element Summary:

Max: 1Pos: 010 Detail - Mandatory

Elements: 4Loop: HL







HL ITEM 856.33




LIN - Item Identification User Option(Usage): Used


Element Summary: LIN**BP*1234-56789*KP*N121*VP*VP96325*CA*10000246~

Ref Id Element Name Req Type Min/Max Value 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 BP Description:


LIN03 234 Product/Service ID M AN 1/25 1234-56789 Description:

Identifying number for a product or service

LIN04 235 Product/Service ID Qualifier M ID 2/2 KP Description:


LIN05 234 Product/Service ID M AN 1/30 N121 Description:

Identifying number for a product or service LIN06 235 Product/Service ID Qualifier X ID 2/2 VP


LIN07 234 Product/Service ID X AN 1/30 VP96325 Description:

Identifying number for Supplier's product or service LIN08 235 Product/Service ID Qualifier M ID 2/2 CA


LIN09 234 Product/Service ID M AN 10/10 10000246 Description:

Case number. First 5 characters (Supplier code) assigned to each supplier by TBA used to uniquely identify the case to the TBA System. Last 5 characters assigned by supplier MUST be numeric.

Only use code BP – Buyers Part Number

TBA’s Part Number

Only use Code KP – Kanban Number

Only use Code VP – Vendor's Part Number

Only use Code CA – Case Number

LIN 856.34

856 - Ship Notice/ManifestSN1 - Item Detail (Shipment)User Option(Usage): Used

Loop: HLTo specify line-item detail relative to shipment

SN1**144*EA*7488*144*EA*L*SR~TBA REQ.

Ref Id Element Name Req Type Min/Max ValueSN101 350 Assigned Identification O AN 1/20 ''

Description:Alphanumeric characters assigned for differentiation within a transaction setNot USED

SN102 382 Number of Units Shipped M R 1/10 144Description:

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

SN103 355 Unit or Basis for Measurement Code M ID 2/2 EADescription:

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

Refer to Note 1SN104 646 Quantity Shipped to Date O R 1/9 7488

Number of units shipped to dateSN105 330 Quantity Ordered O R 1/9 144

Quantity orderedSN106 355 Unit or Basis for Measurement Code X ID 2/2 EA

Code identifying the basic unit of measurement. Refer to 003020 Data Element Dictionary for acceptable code values.

Refer to Note 1SN107 728 Returnable Container Load Make-Up Code O ID 1/2 L

Code identifying the load make-up of the returnable containers in the shipment

Refer to Note 2SN108 668 Line Item Status Code O ID 2/2 SR

Code specifying the action taken by the seller on a line item requested by the buyer. Refer to 003020 Data Element Dictionary for acceptable code values.

Refer to Note 3

Semantics:1. SN101 is the ship notice line-item identification.

Comments:1. SN103 defines the unit of measurement for SN102.2. SN106 defines the unit of measurement for SN102.

Notes:1. Valid codes are:

PC PIECEEA EACHGA GALLONYD YARDS


Element Summary:

Max: 1

Elements: 3

Pos: 030Detail – Mandatory

SN1 856.35

856 - Ship Notice/Manifest2. Valid codes are:

D EMPTY CONTAINERS WITH DUNNAGEE EMPTY CONTAINERSL LOADED WITH PRODUCTION MATERIALM MIXED EMPTY AND LOADEDS SERVICE PART OBSOLETE CONTAINERZZ MUTUALLY DEFINED - RETURNABLE CONTAINER / EXPENDABLE PACKAGING

3. Valid codes are:DO DIRECT ONLYDW DIRECT AND WHOLESALERNR NONRETURNABLE (If the product is shipped in a nonreturnable

container, use REF*22 to describe the container. If there is a charge for the expendable container use an additional SLN segment for the expendable container's price.)

NS NONSERVICABLEOR ORDERINGSP SPECIAL ORDER ONLYSR SHIPPING

SN1 856.36

856 - Ship Notice/ManifestSLN - Subline Item Detail (Shipment)User Option(Usage): Used - except Toyota Direct Suppliers

Loop: HLTo specify line-item detail relative to shipment

SLN*10**O*1*EA*5.1234*CT~TBA REQ.

Ref Id Element Name Req Type Min/Max ValueSLN101 350 Assigned Identification M N 1/12 10

Description:Alphanumeric characters assigned for differentiation

Used - PO Line NumberSLN102 350 Assigned Identification O AN 1/20 NOT USED

Description:Alphanumeric characters assigned for differentiation

SLN103 662 Relationship Code M R 1/10 ODescription:

Price Relationship CodeRefer to Note 1

SLN104 380 Quantity O R 1/15 1Description:

Quantity for the unit of the priceSLN020 C001 Composite Unit Price OT Comp

0355 UNIT OR BASIS FOR MEASUREMENT CODE M ID 2/2 EADescription:

To identify a composite relationship unit to priceUnit or basis for measurement code

Refer to Note 3212 Unit Price M R 1/17 5.1234

Description:Price of Procuct based on units given in SLN020

Send decimal point with 4 decimal places.639 Basis of Unit Price Code M ID 2/2 CT

Description:Code designating the type of price.

Refer to Note 2 - Use code 'CT' - Contract

Comments:*1. This SLN segment will not be used for suppliers that have implemented the 810.

2. Suppliers that have not implemented the 810 are required to send this segment plus the REF*MR.3. If your company is a Toyota Direct Controlled Supplier, this segment is not used.

Notes:1. Valid codes are:

A ADDD DELETEI INCLUDEDO INFORMATION ONLYS SUBSTITUTED

2. Valid codes are:CT Contract

3. Valid codes are:PC PIECEEA EACHGA GALLONYD YARDS


Element Summary:

Max: 2

Elements: 7

Pos: 040Detail – Mandatory*

SLN 856.37

856 - Ship Notice/ManifestREF - Reference IdentificationUser Option(Usage): Used



REF01 128 Reference Identification Qualifier M ID SEE NOTE 1Description:

Code qualifying the Reference IdentificationOnly use codes lised in Note 1

REF02 127 Reference Identification X AN SEE NOTE 1Description:

Invoice number must be unique per Purchase Order

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. Valid REF01 Qualifiers are; Min/Max

22 Special Charge or Allowance Code REF*22*CARDBOARD BOX~ 1/3055 Line Sequence Number REF*55*48031XP~ 8/30JS Job Sequence REF*JS*F0318F0 ~ 8/30LF Line Location REF*LF*000728~ 7/30LS Barcoded Serial Number REF*LS*TMI5002046~ 10/50LT Lot Number REF*LT*LOTNUMB~ 5/30LU Location Number - Storage Address REF*LU*STORE-L1~ 3025MR Card Type Code REF*MR*M200~ 4/4MY Model Year REF*MY*2008~ 4/4RE RELEASE NUMBER REF*RE*071~ 2/30VT Chassis Number REF*VT*S0930F0~ 8/30

Each supplier will be given instructions to send a particular REF segment for their particular businessrelationship with a Toyota Boshoku. REF*22 If a TBA approved special charge or allowance is needed i.e. special packaging

charges for TBA approved non-returnables, use REF*22.If this segment is used, then REF*MR is required.REF*22 will not be used for suppliers that have implemented the 810.

REF*55 Suppliers that are line-sequenced will be required to use the REF*55. REF*JS Suppliers that are required to send a Job Sequence Number send REF*JS. REF*LF TBA suppliers that are required to include a Line Location on their AIAG labels will

also be required to use the REF*LF.REF*LS Suppliers are required to be compliant with TBA AIAG barcode labeling specifications

including serial numbers. This will require the REF*LS segment.REF*LT TBA suppliers that are required to include a Lot Number on their AIAG labels will

also be required to use the REF*LT.REF*LU TBA suppliers that are required to include a Store Location on their AIAG labels will

also be required to use the REF*LU.REF*MR If REF*22 is used then REF*MR is also required to send a Card Type to indicate the

charge type in the SLN element 212. Toyota Direct Suppliers are required to send this segment with code M401. REF*MR will not be used for suppliers that have implemented the 810Valied Card Type Codes are; (Even numbers are debits, odd numbers are credits)


Element Summary:

Detail - Optional *Max: >1Pos: 150

Elements: 4Loop: HL

REF 856.38

856 - Ship Notice/ManifestM201 Raw Material ShipmentM401 Direct SupplyM200 Return MaterialM301 Prototype/Pre-ProductionM510 FreightM520 SortingM211 Supplemental Manifest/MaterialM210 DMR (Discrepant Material Report)M530 PackagingM411 Direct Supply Replacement MaterialM231 Service Order Material

REF*MYREF*RE TBA suppliers that are required to include a Release Number on the AIAG label

will be required to use REF*RE.REF*VT Suppliers that are required to include the Chassis Number on the AIAG label

will be required to use REF*VT.

Suppliers that are required to include a Model Year will receive it in the REF*MY.

REF 856.39


User Option(Usage): Used - except Toyota Direct Suppliers (Note 2) CUR - Currency

Detail - Mandatory* Loop: HL Elements: 9

To specify currency for unit price for product being shipped

Element Summary: CUR*ZZ*USD~

Ref Id Element Name

Only use code ZZ Currency Code Description:

A three letter code representing the currency of a particular country

Refer to Note 1

TBA REQ. Req Type Min/Max Value


CUR01 0098 Entity Identifier Code M ID 2/2 ZZ Description:

Code identifying an organizational entity, a physicallocation, property or an individual

CUR02 0100 M ID 3/3 USD

Notes: 1. Valid codes are:

CAD - Canadian DollarJPY - Japanese YenMXN - Mexican PesoUSD - US Dollar

CUR 856.40

*2. This segment is not used for Toyota Direct Suppliers

856 - Ship Notice/Manifest CTT - Transaction Totals User Option(Usage): Used

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

CTT*1~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value CTT01 354 Number of Line Items M N0 1/6 4

Description: Total number of line items in the transaction set

Total number of HL Segments

Comments:

Pos: 010 Max: 1


Element Summary:

Summary – Mandatory Elements: 1Loop: N/A

1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

CTT 856.41

856 - Ship Notice/Manifest SE - Transaction Set Trailer User Option(Usage): Must Use

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

SE*34*0001~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value SE01 96 Number of Included Segments M N0 1/10 32


SE02 329 Transaction Set Control Number M AN 4/9 0001 Description:



Pos: 020 Max: 1


Element Summary:

Summary - Mandatory Elements: 2Loop: N/A

SE 856.42

856 - Ship Notice/Manifest GE - Functional Group Trailer User Option(Usage): Must Use


GE*1*000000001~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value GE01 97 Number of Transaction Sets Included M N0 1/6 1


GE02 28 Group Control Number M N0 1/9 XXXX Description:






Max: 1Pos:

Loop: N/A


Element Summary:

Not Defined - Mandatory Elements: 2

GE 856.43

856 - Ship Notice/Manifest IEA - Interchange Control Trailer Pos: Max: 1 User Option(Usage): Must Use Not Defined - Mandatory


Element Summary: IEA*1*000000001~


IEA01 I16 Number of Included Functional Groups M N0 1/5 1 Description:


IEA02 I12 Interchange Control Number M N0 9/9 000000001 Description:



IEA 856.44


EXAMPLE OF AN 856: ISA*00*SUPPLIERNA*01*0123456789*ZZ*123456789-12345*01*123456789 GS*SH*123456789*063844752*20060706*1030*000000001*X*004010~ST*856*000000001~BSN*00*0962468*20060706*1030~DTM*011*20060706*1030*ET~HL*1*0*S*1~MEA*PD*G*200*LB~MEA*PD*N*198*LB~TD1*PLT90*9~TD5*B*2*LCQX*M*ROUTING**IT*ABCDEF~TD3*TL**TL04687******S99999999~TD4*CH*D*H047~REF*BM*156023~CUR*ZZ*USD~N1*ST*TMIHB*92*096~N3*45 SOUTH FIELD DRIVE~N4*ELMIRA*ON*N3B3L6*CAN~N1*SU*SUPPLIER NAME*92*11591~N1*SF*SUPPLIERNAME*01*123456789~HL*2*0*O*1~PRF*I99999~REF*MH*70202031~HL*3*2*I*0~LIN**BP*1234-56789*KP*N121*VP*VP96325*CA*10000246~SN1**144*EA*7488*144*EA*L*SR~SLN*10**O*1*EA*5.1234*CT~REF*22*CARDBOARD BOX~REF*55*48031XP~REF*JS*F0318F0 ~REF*LF*000728~REF*LS*TMI5002046~REF*LT*LOTNUMB~REF*LU*STORE-L1~REF*MR*M391~REF*RE*071~REF*VT*S0930F0~HL*4*2*I*0~LIN**BP*2234-56789*KP*N122*VP*VP96326*CA*10000246~SN1**144*EA*7488*144*EA*L*SR~SLN*10**O*1*EA*5.1234*CT~REF*22*CARDBOARD BOX~REF*55*48032XP~REF*JS*F0318F1 ~REF*LF*000728~REF*LS*TMI5002047~REF*LT*LOTNUMB~REF*LU*STORE-L1~REF*MR*M391~REF*RE*071~REF*VT*S0930F0~HL*5*2*I*0~LIN**BP*3234-56789*KP*N123*VP*VP96327*CA*10000247~SN1**144*EA*7488*144*EA*L*SR~SLN*10**O*1*EA*5.1234*CT~REF*22*CARDBOARD BOX~REF*55*48033XP~REF*JS*F0318F2 ~REF*LF*000760~REF*LS*TMI5002048~REF*LT*LOTNUMB~REF*LU*STORE-L2~REF*MR*M391~REF*RE*071~REF*VT*S0930F1~CTT*1~SE*64*0001~GE*1*000000001~IEA*1*000000001~

EXAMPLE

*060706*1030*U*00400*000000001*0*P*>~

856.45


TOYOTA BOSHOKU

INFORMATION SYSTEMS


FOR

MATERIAL RELEASE (862)INBOUND

TOYOTA BOSHOKU CONTACT EDI SUPPORT LINE

(859) 817-4050


revision: 2/01/2008

862 862.1


DATA REQUIREMENTS

MISCELLANEOUS STANDARD: ANSI X12 - AIAG EDI ACKNOWLEDGMENT FUNCTIONAL ACKNOWLEDGMENT -TBA EXPECTS 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 TBA.




DATA FREQUENCY DAILY VALUE ADDED NETWORK (VAN) STERLING COMMERCE INFORMATION BROKER









TRANSACTION TESTING WILL NOT BE COMPLETE UNTIL EACH SUPPLIER COMPLETES PARALLEL TESTING WITH TBA INVOLVING RECEIVING THE PAPER MATERIAL RELEASE AND THE ORDER VIA EDI.




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.


Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage 010 ST Transaction Set Header M 1 Must use 020 BSS Beginning Segment for M 1 Must use

Shipping Schedule/Production Sequence

200 050 N1 Name O 1 Used 070 N3 Address Information O 2 Used 080 N4 Geographic Location O 1 Used 280 PER Administrative Communications Contact O 3 Used 050 N1 Name O 1 Used

TBA REQ. Pos Id Segment Name Req Max Use Repeat Notes Usage

10000 010 LIN Item Identification M Must use 020 UIT Unit Detail M 1 Used 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 O 1 Used

Communications Contact 070 SDP Ship/Delivery Pattern O 1 Used

10 140 SHP Ship/Received Information O 1 Used 150 REF Reference Identification O 12 Used 180 TD5 Carrier Details (Routing Sequence/Transit Time) O 1 Used

TBA REQ. Pos Id Segment Name Req Max Use Repeat Notes Usage 010 CTT Transaction Totals O 1 N3/010 Used 020 SE Transaction Set Trailer M 1 Must use




Detail:

Summary:

LOOP ID - N1

�LOOP ID - LIN

�LOOP ID - SHP

SS 862.4


Notes: 3/010 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.

SS 862.5

862 - Material Release ISA - Interchange Control Header Pos: Max: 1 User Option(Usage): Must use Not Defined - Mandatory


Element Summary: ISA*00*TOYOTA *01*796567667*01*796567667 *ZZ*999999999-20600*060320*1915*U*00400*000005675*0*P*>~


ISA01 I01 Authorization Information Qualifier M ID 2/2 '00' Description:



Only Send Code 00 ISA02 I02 Authorization Information M AN 10/10 'TOYOTA '

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)

ISA03 I03 Security Information Qualifier M ID 2/2 '01' Description:

Code to identify the type of information in the Security Information

ISA04 I04 Security Information M 10/10 '825946353' 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)

ISA05 I05 Interchange ID Qualifier M ID 2/2 '01' Description:


ISA06 I06 Interchange Sender ID M AN 15/15 '825946353' 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

ISA07 I05 Interchange ID Qualifier M ID 2/2 'ZZ' Description:


ISA08 I07 Interchange Receiver ID M AN 15/15 '123456789-12345' 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

ISA 862.6

Only Send Senders Name - 'TRIMMASTER'


Refer To Note 1


Refer To Note 1

Will Typically Send Code ZZ

862 - Material Release 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 YYMMDD Description:


Description: Time of the interchange

ISA11 I10 Interchange Control Standards Identifier M ID 1/1 'U' Description:


Only Send Code U ISA12 I11 Interchange Control Version Number M ID 5/5 '00400'

Description: Code specifying the version number of the interchange control segments

Only Send Code 00400 ISA13 I12 Interchange Control Number M N0 9/9 XXXXXXXXX

Description: A control number assigned by the interchange sender

ISA14 I13 Acknowledgment Requested M ID 1/1 '0' for No Description: '1' for Yes


Will only Send 0 - "No" ISA15 I14 Usage Indicator M ID 1/1 USE 'P' FOR

Description: PRODUCTION Code to indicate whether data enclosed by this 'T' FOR TEST 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 '>'




096 Trim Masters, Inc. Harrodsburg, KY USA139 Trim Masters, Inc. Bardstown, KY USA 192 Trim Masters, Inc. Nicholasville, KY USA 193 Trim Masters, Inc. Leitchfield, KY USA 194 Trim Masters, Inc. Modesto, CA USA 199 Automotive Technology Systems LLC. Lawrenceville, IL592 Master Trim de Mexico Torreon Mexico 572 Trim Masters, Inc. Bartlett, IN USA 650 Master Trim de Mexico Chavez Mexico 705 Trim Masters, Inc. Elmira Ontario Canada 873 Trim Masters, Inc. San Antonio, TX USA

ISA

(1) DUNs #(92) Plant Abbrev.


862.7

862 - Material Release GS - Functional Group Header Pos: Max: 1 User Option(Usage): Must use Not Defined - Mandatory


Element Summary: GS*SS*796567667*999999999*20060320*1915*5675*X*004010~


GS01 479 Functional Identifier Code M ID 2/2 'SS' Description:



Only use code SS - "Remittance Advice" GS02 142 Application Sender's Code M AN 9/12 '796567667'


GS03 124 Application Receiver's Code M AN 9/15 ‘123456789’ Description:


GS04 373 Date M DT 8/8 'CCYYMMDD' Description:

Date expressed as CCYYMMDD GS05 337 Time M TM 4/4 'HHMM'


GS06 28 Group Control Number M N0 1/9 'XXXXXXXXX' Description:

Assigned number originated and maintained by the sender GS07 455 Responsible Agency Code M ID 1/2 'X'

Description: Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

GS08 480 Version / Release / Industry Identifier Code M AN 1/12 '004010' Description:


Will Only Send Senders DUNS (See Note 1)

Will send Receivers DUNS (See Note 2)

Will only Send Code X


Semantics:

1. GS04 is the group date. 2. GS05 is the group time. 3. The group control number GS06 in this header must be identical to the

GS 862.8

862 - Material Release same data element in the associated functional group trailer, GE02.





096 Trim Masters, Inc. Harrodsburg, KY USA139 Trim Masters, Inc. Bardstown, KY USA 192 Trim Masters, Inc. Nicholasville, KY USA 193 Trim Masters, Inc. Leitchfield, KY USA 194 Trim Masters, Inc. Modesto, CA USA 199 Automotive Technology Systems LLC. Lawrenceville, IL US592 Master Trim de Mexico Torreon Mexico 572 Trim Masters, Inc. Bartlett, IN USA 052922697650 Master Trim de Mexico Chavez Mexico 705 Trim Masters, Inc. Elmira Ontario Canada 873 Trim Masters, Inc. San Antonio, TX USA


063844752 TMIHB 796567667 TMIBT 825946353 TMINV 967532524 TMILF 806416004 TMIMO 877899695 ATS 812596419 MTMT

BART 812749414 MTMC 201047177 TMIEL 626731827 TMITX

GS 862.9

2. For Toyota Direct Suppliers only, TBA will send 'Receivers DUNs Number - Supplier Code' in the GS03 Element.i.e. 999999999-12345. The data will match the ISA07

862 - Material Release ST - Transaction Set Header User Option(Usage): Must Use


ST*862*0001~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value ST01 143 Transaction Set Identifier Code M ID 3/3 '862'


Will only send code 862 ST02 329 Transaction Set Control Number M AN 4/9 'XXXXXXXXX'


Semantics:




Element Summary:

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).

ST 862.10

862 - Material Release BSS - Beginning Segment for Shipping Schedule/Production Sequence

Pos: 020 Max: 1

Heading - Mandatory User Option(Usage): Must use Loop: N/A Elements: 13

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

Element Summary: BSS*00*ORIGINAL*20060815*DL*20060815*20060815*06072006-1~


BSS01 353 Transaction Set Purpose Code M ID 2/2 '00' Description:



See Note 1 BSS02 127 Reference Identification M AN 1/30 'ORIGINAL'


BSS03 373 Date M DT 8/8 'CCYYMMDD' Description:


BSS04 675 Schedule Type Qualifier M ID 2/2 'DL' Description:

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





BSS07 328 Release Number X AN 1/30 '06072006-1' Description:

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

Will Only Send Value ORIGINAL

Begin Date

Will Only Send Code DL

End Date

Generated Date

Semantics: 1. Use BSS03 to indicate the date of this document. 2. Use BSS05 to indicate the schedule horizon start date (the date when the schedule begins). 3. Use BSS06 to indicate the schedule horizon end date (the date when the schedule ends).

Notes: 1. Valid Codes are;

00 = ORIGINAL01 = CANCELLATION04 = CHANGE

BSS 862.11

862 - Material Release Loop N1


Loop Summary:



TBA REQ. Ref Id Element Name Req Type Min/Max Value 50 N1 Name M 5/6 Used


N1 LOOP 862.12


N1 - NameUser Option(Usage): Used


N1*MI*TMIHB*1*063844752~N1*ST*TMIHB*92*096~N1*SU*ABC Manufacturing*92*12345~N1*SF*ABC Manufacturing*1*999999999~N1*OB*ABC Manufacturing*1*999999999~


N101 98 Entity Identifier Code M ID 2/2 MIDescription: ST


SUSF

Refer To Note 1 OBN102 93 Name M AN 1/30 TMIHB

Description: TMIHBFree-form name SUPPLIERNAME

SUPPLIERNAMERefer To Note 2 ORDERED BY NAME

N103 66 Identification Code Qualifier M ID 1/2 1Description: 92

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

Refer To Note 3 1N104 67 Identification Code M AN 3/9 063844752

Description: 096Code identifying a party or other code 12345

999999999Refer To Note 4 and 5 999999999

Syntax:1. 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.

Notes:1. Valid Codes are;

Code Name Type Sample segment data

MI Planning Schedule/Material Release Issuer N1*MI*TMIHB*1*063844752~ST Ship To N1*ST*TMIHB*92*096~SU Supplier/Manufacturer N1*SU*SUPPLIER NAME*92*12345~SF Ship From N1*SF*SUPPLIER NAME*1*999999999OB Ordered By N1*OB*ORDERED BY NAME*1*999999999

2. Valid Values That Will Be Sent Are:Code Plant Name and Location (1) DUNs #(92) Plant Abbrev.

096 Trim Masters, Inc. Harrodsburg, KY USA 063844752 TMIHB139 Trim Masters, Inc. Bardstown, KY USA 796567667 TMIBT192 Trim Masters, Inc. Nicholasville, KY USA 825946353 TMINV193 Trim Masters, Inc. Leitchfield, KY USA 967532524 TMILF194 Trim Masters, Inc. Modesto, CA USA 806416004 TMIMO199 Automotive Technology Systems LLC. Lawrenceville, IL 877899695 ATS592 Master Trim de Mexico Torreon Mexico 812596419 MTMT

Max: 5Pos: 050


Element Summary:

Heading - OptionalElements: 6Loop: N1

N1 862.13

862 - Material Release572 Trim Masters, Inc. Bartlett, IN USA 052922697 BART650 Master Trim de Mexico Chavez Mexico 812749414 MTMC705 Trim Masters, Inc. Elmira Ontario Canada 201047177 TMIEL873 Trim Masters, Inc. San Antonio, TX USA 626731827 TMITX

3. Valid Values That Will Be Sent Are:1 - Dun and Bradstreet (Credit Reporting) (DUNs)92 - Assigned by Buyer (Trim Master's Plant Abbreviation)

4. MI Planning Schedule/Material Release IssuerWill Send TBA Plant's DUNs number.

ST Ship ToWill Send TBA's Plant Number.

SU Supplier/ManufacturerSupplier Code Issued by TBA

SF Ship FromWill Send Supplier DUNs number.

OB Ordered ByWill Send Customer DUNs number.

5. To be printed on the AIAG label. See AIAG Label specification guidelines for your ship-to location.

N1 862.14

862 - Material Release N3 - Address Information User Option(Usage): Used

To specify the location of the named party

Pos: 052 Max: 2 Heading - Mandatory

Loop: N1 Elements: 2

Element Summary: N3*1120 Industry Road~

X12 ANSI REQUIREMENTS Ver. 4010 TBA REQ.Ref Id Element Name Req Type Min/Max Value

N301 166 Address Information for Ship To location (ST) M AN 1/55 '45 South Field Drive' Address Information for Ship From location (SF)

Description: Address information

N3 862.14

862 - Material Release N4 - Geographic Location User Option(Usage): Used

To specify the geographic place of the named party

Pos: 053 Max: 5

Heading - MandatoryLoop: N1 Elements: 6

Element Summary: N4*Harrodsburg**40330*CA*SP*ON~


N401 19 City Name for Ship To Location O AN 2/30 'ELMIRA' Description:

Free-form text for city name N402 156 State or Province Code for Ship To Location X ID 2/2 ''

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

N403 116 Postal Code for Ship To Location M ID 3/15 '40330' Description:

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


N4 862.15

N405 309 Location Qualifier M AN 1/2 'SP' Description:

Will only send Code SP (State/Province) N406 310 Location Identifier M AN 1/30 'ON'

Description: 2 or 3 Digit State/Province ISO-3166-2 Code

N404 026 Country Code M AN 2/3 'CA' Description:

2 Digit Country Code

862 - Material Release PER - Administrative Communications Contact Pos: 060 Max: 1 User Option(Usage): Used Detail - Optional

Loop: N1 Elements: 9 To identify a person or office to whom administrative communications should be directed


Element Summary: PER*SC*BONNIE MURPHY*TE*8597346000~

Ref Id Element Name Req Type Min/Max Value PER01 366 Contact Function Code M ID 2/2 'SC'

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

PER02 93 Name O AN 1/60 'NAME' Description:

Free-form name

PER03 365 Communication Number Qualifier X ID 2/2 'TE' Description:

Code identifying the type of communication number

PER04 364 Communication Number X AN 1/80 '555-555-5555' Description:

Complete communications number including country or area code when applicable

Will Only Send Code SC

Name Of TBA’s Specialist In P/C

Will Only Send Code TE

Telephone Number Of TBA's Specialist in P/C

Syntax: 1. P0304 - If either PER03, PER04 is present, then all are required

PER 862.16

862 - Material Release Loop LIN Pos: 010 Repeat: 10000

Mandatory Loop: LIN Elements: N/A



Pos Id Segment Name Req Max Use Repeat Usage 010 LIN Item Identification M 1 Must use 020 UIT Unit Detail M 1 Must use 040 PO4 Item Physical Details M >1 Must use 045 PRS Part Release Status M 1 Must use 050 REF Reference Identification M 12 Must use 060 PER Administrative Communications Contact O 1 Used 070 SDP Ship/Delivery Pattern M 1 Must use 140 Loop SHP M 10 10 Must use 180 TD5 Carrier Details (Routing Sequence/Transit Time) M 1 Must use


LIN LOOP 862.17


Pos: 010 Max: 1


LIN - Item Identification User Option(Usage): Must use


Element Summary: LIN*1*PL*29*BP*ABCDE-0C500-E0*VP*0C500-E0***KP*KNBN29*ZZ*A~


LIN01 350 Assigned Identification M AN 0/20 '1' Description:

Alphanumeric characters assigned for differentiation within a transaction set

LIN02 235 Product/Service ID Qualifier M ID 2/2 'PL' Description:


Will Only Send Code PL – PO Line Number LIN03 234 PO Line Number M N 0/12 10


LIN04 235 Product/Service ID Qualifier M ID 2/2 'BP' Description:


Will Only Send Code BP – Buyers Part Number LIN05 234 Product/Service ID M AN 1/20 '71001-51444-B1'


TBA's Part Number, Refer To Note 1 LIN06 235 Product/Service ID Qualifier O ID 0/2 'VP'


Will Only Send Code VP - Vendor's Part Number LIN07 234 Product/Service ID O AN 0/48 '7100151444B1'


Vendor's Part Number if available LIN08 235 Product/Service ID Qualifier O ID 0/2 'DR'


Will Only Send Code DR - Drawing Revision Number LIN09 234 Product/Service ID O AN 0/10 'A-10'


Revision Level LIN10 235 Product/Service ID Qualifier M ID 2/2 'KP'


Will Only Send Code KP - TBA's Kanban Number LIN11 234 Product/Service ID M AN 4/10 'N104'


TBA's Kanban Number


LIN 862.18

862 - Material Release LIN12 235 Product/Service ID Qualifier M ID 2/2 'ZZ'


Will Only Send Code ZZ LIN13 234 Order Type M AN 1/1 'D'


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

Semantics: 1. LIN01 is the line item identification 2. SEQUENCED ORDER (WEEKLY) - 13 WEEKS PRE-NOTICE

KANBAN ORDER (WEEKLY) - 13 WEEKS PRE-NOTICEEKANBAN ORDER (WEEKLY) - 13 WEEKS PRE-NOTICE

Notes: 1. This Element Is To Be Printed On The AIAG Label 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 - SCHEDULE ORDER''B - SEQUENCED ORDER''C - KANBAN ORDER''D - EKANBAN ORDER'

LIN 862.19

862 - Material Release UIT - Unit Detail User Option(Usage): Mandatory Used

To specify item unit data

Pos: 020 Max: 1

Detail - MandatoryLoop: LIN Elements: 3

Ref Id UIT01 C001

0355

UIT*EA~ TBA REQ.

Element Name Req Type Min/Max Value Composite Unit of Measure M Comp 2/2 'EA' Description:

To identify a composite unit of measure (See Figures Appendix for examples of use)

Will Only Send Code PC – “Pieces”


Element Summary:

UIT 862.20

862 - Material Release PO4 - Item Physical Details Pos: 040 Max: >1 User Option(Usage): Used Detail – Mandatory

Loop: LIN Elements: 18 To specify the physical qualities, packaging, weights, and dimensions relating to the item

Ref Id PO401 356

PO4*6~ TBA REQ.

Element Name Req Type Min/Max Value Pack M N0 1/6 '1' 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


Element Summary:

PO4 862.21

862 - Material Release PRS - Part Release Status Pos: 045 Max: 1 User Option(Usage): Used Detail - Mandatory

Loop: LIN Elements: 2 To indicate the status of the part being ordered or forecast with respect to this material release or planning document.

Ref Id PRS01 682

PRS*4~ TBA REQ.

Element Name Req Type Min/Max Value Part Release Status Code M ID 1/2 '4' Description:

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

Refer To Note 1

Notes: 1. Valid Codes Are:

1 – “Non-Carryover ” 4 – “Carryover ” 5 – “New Item ”


Element Summary:

PRS 862.22

862 - Material ReleaseREF - Reference IdentificationUser Option(Usage): Used



REF01 128 Reference Identification Qualifier M ID SEE NOTE 1Description:

Code qualifying the Reference IdentificationOnly use codes lised in Note 1

REF02 127 Reference Identification X AN SEE NOTE 1Description:

Invoice number must be unique per Purchase Order

Semantics:1. REF04 contains data relating to the value cited in REF02.

Notes:1. Valid REF01 Qualifiers are; Min/Max

55 Line Sequence Number [SPARC Serial Number] REF*55*90410EDDRA0330039~ 17/30DK Dock Code [Required if Shipping to SPARC plant] REF*DK*S24~ 2/10JS Job Sequence REF*JS*J1234567~ 8/30LF Line Location REF*LF*FN3W-16-KNBN29~ 7/30LS Barcode Serial Number REF*LS*TMI4000016~ 10/50LU Location Number - Storage Address or [Kanban Location] REF*LU*WHSE11~ 2/15MR Merchandise Card Type Code REF*MR*M201~ 4/4MY Model Year REF*MY*2008~ 4/4PRT Part Description REF*PRT*CHANGE ME PART~ 8/30VT Chassis Number REF*VT*C78SB842~ 8/30

REF*55REF*DKREF*JSREF*LF

REF*LS

REF*LU

* REF*MRValid Card Type Codes are; *This Segment is Mandatory.


REF*MY

REF*PRTREF*VT

Suppliers that are required to include a Model Year will receive it in the REF*MY.

Suppliers that are required to include the Chassis Number on the AIAG label will be receive the REF*VT.

Each supplier will be given instructions to send a particular REF segment for their particular business relationship with a Toyota Boshoku plant.

All TBA suppliers are required to be compliant with TBA AIAG barcode labeling specifications. If e-Kanban order, serial number will be sent in the REF*LS segment.

TBA suppliers that are required to include a Store Location on their AIAG labels will also be receive the REF*LU OR This may be used for Kanban Location (Also printed on AIAG label.)REF*MR - Merchandise Card Type to indicate the charge type in the SLN element 212.

Part Description - all suppliers will be receive the REF*PRT.Lin

Line Sequenced Suppliers will received REF*55.[Suppliers shipping to SPARC plants will receive SPARC SERIAL#]Dock code will be sent in the REF*DK. [Required if Shipping to SPARC plant]Suppliers that use a Job Sequence Number will receive the REF*JS. Suppliers that are required to include a Line Location on their AIAG labels will receive it in the REF*LF.


Element Summary:

Detail - OptionalMax: >1Pos: 050

Elements: 2Loop: LIN

REF 862.23

862 - Material Release SDP - Ship/Delivery Pattern User Option(Usage): Used


SDP*N*F~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value SDP01 678 Ship/Delivery or Calendar Pattern Code M ID 1/2 'N'

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 'F'

Description: Code which specifies the time for routine shipments or deliveries

Will Only Send Code F – “First Shift ”


Element Summary:

Detail – Mandatory Pos: 070 Max: 1

Loop: LIN Elements: 8

SDP 862.24

862 - Material Release Loop SHP Pos: 140 Repeat: 10

Mandatory Loop: SHP Elements: N/A

To specify shipment and/or receipt information


Ref Id Element Name Req Type Min/Max Usage 140 SHP Shipped/Received Information O 1 Used 150 REF Reference Identification M 12 Must use


SHP LOOP 862.25

862 - Material Release SHP - Shipped/Receifed Information User Option(Usage): Used

Pos: 140 Max: 1

Detail - OptionalLoop: SHP Elements: 7


To specify shipment and/or receipt information *For Suppliers that ship to TBA plants that use cums Only

Element Summary: SHP*38*90*010*20060821*1000~

Ref Id Element Name Req Type Min/Max Value SHP01 673 Quantity Qualifier O ID 2/2 '38'

Description: Code specifying the type of quantity

SHP02 380 Quantity X R 1/15 '18' Description:

Numeric value of quantity SHP03 374 Date/Time Qualifier X ID 3/3 '010'

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

SHP04 373 Date X DT 8/8 'CCYYMMDD' Description:


SHP05 337 Time X TM 4/8 'HHMM' 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)

Will Only Send Code 38

Will Only Send Code 010

Refer To Notes 1,2

Refer To Notes 1,2

Notes: 1. This Element Is To Be Printed On The AIAG Label 2. For FIRM Orders, Reflects The Pickup Date/Time 3. A Zero Quantity Is Valid For The SHP02 Element

SHP 862.26

Pos: 150 Max: 12

Detail - MandatoryLoop: SHP Elements: 4

862 - Material Release REF - Reference Identification User Option(Usage): Used To specify identifying information

Element Summary: REF*MK*0110200501102005*1-1-1*DO>01032005>PO>S10706>ZZ>15~


REF01 128 Reference Identification Qualifier M ID 2/3 'MK' Description:



Number Of Containers



Notes: 1. This Element Is To Be Printed On The AIAG Label

REF-MK 862.27

Will Send Code MK - MANIFEST NUMBER [Refer to Note 1]REF02 127 Manifest Number X AN 1/30 'XXXXXXXX'


[Refer to Note 1]REF03 352 Kanban Cycle X AN 1/80 '1-1-1'

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

[Refer to Note 1]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 2/3 'DO' Description:


127 Delivery Order Number M AN 1/30 'D12345' Description:


128 Reference Identification Qualifier X ID 2/3 PO Description:


127 Purchase Order Number X AN 1/30 'XXXXXXXX' Description:


128 Reference Identification Qualifier X ID 2/3 'ZZ' Description:


127 Reference Identification - Number of Containers X AN 1/5 'XXXX' Description:


Will Only Send Code DO (Delivery Order Number)

Will Only Send Code PO (Purchase Order Number)

Will Only Send Code ZZ (Number of Containers)

Pos: 150 Max: 12


862 - Material Release REF - Reference Identification User Option(Usage): Used


Element Summary: REF*UL*ABCDE**ZZ>20060822>ZZ>0000~


REF01 128 Reference Identification Qualifier M ID 2/3 'UL' Description:



Will Only Send Code UL - Cross-listed Course Number REF02 127 Reference Identification X AN 1/30 'XXXXXX'


REF03 352 Description X AN 1/80 Not Used Description:


REF04 C040 Reference Identifier O Comp Description:

To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier

128 Reference Identification Qualifier M 2/3 'ZZ' Description:


127 Reference Identification M AN 1/30 '20060601' Description:




127 Reference Identification X AN 1/30 'HHMM' Description:


Cross Dock 1

Will Only Send Code ZZ

Cross Dock 1 Date


Cross Dock 1 Time


Notes: 1. This Segment Is Sent For Ekanban Orders Only That Are Going Through Cross Dock

REF-UL 862.28

Pos: 150 Max: 12


862 - Material Release REF - Reference Identification User Option(Usage): Used


Element Summary: REF*6O*ABCDEF**ZZ>20060822>ZZ>0000~


REF01 128 Reference Identification Qualifier M ID 2/3 6O Description:



Will Only Send Code 6O - Cross Reference Number REF02 127 Reference Identification X AN 1/30 'XXXXXX'


REF03 352 Description X AN 1/80 Not Used Description:


REF04 C040 Reference Identifier O Comp Description:

To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier

128 Reference Identification Qualifier M 2/3 'ZZ' Description:


127 Reference Identification M AN 1/30 '20060601' Description:






Cross Dock 2


Cross Dock 2 Date


Cross Dock 2 Time


Notes: 1. This Segment Is Sent For Ekanban Orders Only That Are Going Through A Second Cross Dock

REF-6O 862.29

Pos: 150 Max: 12

Detail - MandatoryLoop: SHP Elements: 4

862 - Material Release REF - Reference Identification User Option(Usage): Used To specify identifying information

Element Summary: REF*ZZ*MAIN ROUTE**ZZ>12>ZZ>20060601>ZZ>1000~


REF01 128 Reference Identification Qualifier M ID 2/3 'ZZ' Description:



Will Only Send Code ZZ REF02 127 Reference Identification M AN 1/30 '12'


REF03 352 Description X AN 1/80 '' Description:

Free-form description to clarify related data elements and content REF04 C040 Reference Identifier O Comp

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 'ZZ' Description:

Code qualifying the Reference Identification 127 Reference Identification M AN 1/30 12




127 Reference Identification X AN 8/8 '20060601' Description:






Main Route; Refer To Note 2

Routing Order Sequence Number


Unload Date - CCYYMMDD


Unload Time - HHMM


Notes: 1. This Segment Is Sent For Ekanban Orders Only 2. This Element Is To Be Printed On The AIAG Label

REF-ZZ 862.30

862 - Material Release TD5 - Carrier Details (Routing Sequence/Transit Time) Pos: 180 Max: 12 User Option(Usage): Used Detail - Mandatory


Element Summary: TD5*****MAIN ROUTE**DE*29~


TD501 133 Routing Sequence Code X ID 0/2 '' Description:



Will Not Send This Element TD502 66 Identification Code Qualifier X ID 0/2 ''






TD505 387 Routing X AN 1/35 'MAIN ROUTE' Description:




TD507 309 Location Qualifier O ID 2/2 'DE' Description:


TD508 310 Location Identifier X AN 1/30 'KGN115' Description:





Will Send “ ROUTING ” Or “MAIN ROUTE ”


Will Only Send Code DE - Destination Shipping

Main Route Code (SHIP ROUTE CODE) Refer to Note 2


Notes: 1. This Segment Is Sent For Ekanban Orders Only 2. This Element Is To Be Printed On The AIAG Label

TD5 DE 862.31

Dena Sullivan Smith

Text Box

This section may have some slight modifications to accommodate logistics. The changes will not change the min/max of each element. But, fields that are optional now may become mandatory.

862 - Material Release TD5 - Carrier Details (Routing Sequence/Transit Time) Pos: 180 Max: 12 User Option(Usage): Used Detail - Mandatory


Element Summary: TD5*****SUB-ROUTING**IT*SUB ROUTE~


TD501 133 Routing Sequence Code O ID 0/2 '' Description:



Will Only Send Code 1, Refer To Note 1 TD502 66 Identification Code Qualifier X ID 0/0 ''






TD505 387 Routing O AN 1/35 'SUB-ROUTING' Description:




TD507 309 Location Qualifier O ID 2/2 'IT' Description:


TD508 310 Location Identifier M AN 1/30 'SUBROUTE' Description:


This Element Is Not Sent

This Element Is Not Sent


Will Only Send “ROUTING ” Or “SUB-ROUTING ”

This Element Is Not Sent.

Will Only Send Code IT, Refer To Note 2

Sub-Route Cross Dock Code, Refer To Note 2

TD5 IT 862.32


Syntax: 1. R0204050612 - At least one of TD502, TD504, TD505, or TD506 is required 2. C0203 - If TD502 is present, then all of TD503 are required 3. C0708 - If TD507 is present, then all of TD508 are required

Comments: 1. 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.

Notes: 1. This Segment Will Only Appear If There Is A Sub-Route. 2. This Segment Is Optional. It Will Only Appear If There Is A Sub-Route.

TD5 IT 862.33

Dena Sullivan Smith

Text Box

This section may have some slight modifications to accommodate logistics. The changes will not change the min/max of each element. But, fields that are optional now may become mandatory.

862 - Material Release CTT - Transaction Totals Pos: 010 Max: 1 User Option(Usage): Used Summary – Mandatory

Loop: N/A Elements: 7 To transmit a hash total for a specific element in the transaction set

Element Summary: CTT*2*186~

Ref Id Element Name

Total Number Of LIN Segments

TBA REQ. Req Type Min/Max Value


CTT01 354 Number of Line Items M N0 1/6 '33' Description:

Total number of line items in the transaction set

CTT02 347 Hash Total O R 1/10 '520' 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.

Comments: 1. This segment is intended to provide hash totals to validate transaction

completeness and correctness.

Total Of Net Qty On The SHP Segments

CTT 862.34

862 - Material Release SE - Transaction Set Trailer User Option(Usage): Must Use


SE*53*0001~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value SE01 96 Number of Included Segments M N0 1/10 '35'


SE02 329 Transaction Set Control Number M AN 4/9 'XXXXXXXXX' Description:



Pos: 020 Max: 1


Element Summary:

Summary - Mandatory Elements: 2Loop: N/A

SE 862.35

862 - Material Release Pos: Max: 1

Not Defined - MandatoryLoop: N/A Elements: 2

GE - Functional Group Trailer User Option(Usage): Must Use


GE*1*293~ TBA REQ.

Ref Id Element Name Req Type Min/Max Value GE01 97 Number of Transaction Sets Included M N0 1/6 '6'


GE02 28 Group Control Number M N0 1/9 'XXXXXXXXX' Description:



Element Summary:

Semantics: 1. The group 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 group 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.

GE 862.36

862 - Material Release IEA - Interchange Control Trailer Pos: Max: 1 User Option(Usage): Must Use Not Defined - Mandatory


Element Summary: IEA*1*000000293~


IEA01 I16 Number of Included Functional Groups M N0 1/5 '1' Description:


IEA02 I12 Interchange Control Number M N0 9/9 'XXXXXXXXX' Description:



IEA 862.37

862 - Material Release EXAMPLE OF A MATERIAL RELEASE (862)

EXAMPLE OF A SHIPPING SCHEDULE (862) DOCUMENT ISA*00*TOY0TA *01*796567667*01*796567667 *ZZ*999999999-20600*060320*1915*U*00400*000005675*0*P*>~

GS*SS*796567667*999999999*20060320*1915*5675*X*004010~

ST*862*0001~

BSS*00*ORIGINAL*20060815*DL*20060815*20060815*06072006-1~

N1*MI*TRIMMASTER*1*063844752~

N1*ST*TMIHB*92*096~

N3*1120 Industry Road~

N4*Harrodsburg*KY*40330~

N1*SU*A B Manufacturing*92*30001~

N1*SF*A B Manufacturing*1*190084635~

PER*SC*BONNIE MURPHY*TE*8597346000~

LIN*1*PL*29*BP*ABCDE-0C500-E0*VP*0C500-E0***KP*KNBN29*ZZ*A~

UIT*EA~

PO4*6~PRS*4~REF*55*12345678~REF*DK*S24~REF*JS*J1234567~REF*LF*FN3W-16-KNBN29~REF*LS*TMI4000016~REF*LU*WHSE11~REF*MR*M201~REF*PRT*CHANGE ME PART~REF*VT*C78SB842~SDP*N*F~SHP*38*90*010*20060821*1000~REF*MK*0110200501102005*1-1-1*DO>01032005>PO>S10706>ZZ>15~REF*UL*ABCDE**ZZ>20060822>ZZ>0000~REF*6O*ABCDEF**ZZ>20060822>ZZ>0000~REF*ZZ*MAIN ROUTE**ZZ>12>ZZ>>ZZ~TD5*****MAIN ROUTE**DE*29~TD5*****SUB-ROUTING**IT*SUB ROUTE~LIN*2*PL*28*BP*ABCDE-0C440-E0*VP*0C440-E0***KP*KNBN28*ZZ*A~UIT*EA~PO4*6~PRS*1~REF*55*12345677~REF*DK*S24~REF*JS*J1234567~REF*LF*FN3W-16-KNBN28~REF*LS*TMI4000015~REF*LU*WHSE11~REF*MR*M201~REF*PRT*CHANGE ME PART~REF*VT*C785B681~SDP*N*F~SHP*38*96*010*20060821*000000~REF*MK*0103200501032005*1-1-1*DO>01102005>PO>S10706>ZZ>16~REF*UL*ABCDE**ZZ>20060822>ZZ>1000~REF*6O*ABCDEF**ZZ>20060822>ZZ>1000~REF*ZZ*MAIN ROUTE**ZZ>12>ZZ>20060601>ZZ>1000~TD5*****MAIN ROUTE**DE*28~TD5*****SUB-ROUTING**IT*SUB ROUTE~CTT*2*186~SE*53*0001~GE*1*293~IEA*1*000000293~

EXAMPLE 862.38

997 - Functional Acknowledgment

revision: 2/01/2008

(859) 817-4050


FOR

FUNCTIONAL ACKNOWLEDGMENT (997)

TOYOTA BOSHOKU CONTACT

INFORMATION SYSTEMS

TOYOTA BOSHOKU


EDI SUPPORT LINE

997 997.1


DATA REQUIREMENTS

MISCELLANEOUS STANDARD: ANSI X12 - AIAG DOCUMENTATION CHANGES TBA WILL GIVE TRADING PARTNERS A MINIMUM OF

FOUR WEEKS NOTICE BEFORE IMPLEMENTING FORMAT CHANGES.



DATA FREQUENCY ANYTIME VALUE ADDED NETWORK (VAN) STERLING INFORMATION BROKER









TRANSACTION TESTING WILL NOT BE COMPLETE UNTIL EACH SUPPLIER COMPLETES TESTING WITH TBA INVOLVING RECEIVING THE FUNCTIONAL ACKNOWLEDGEMENT VIA EDI




Functional Group=FA This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional Acknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets.


Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage 010 ST Transaction Set Header M 1 N1/020 Must use 020 AK1 Functional Group Response Header M 1 N1/020 Must use

030 Used

040 AK3 Data Segment Note O 1 C1/040 Used 050 AK4 Data Element Note O 1 Used 060 AK5 Transaction Set Response Trailer M 1 Must use 070 AK9 Functional Group Response Trailer M 1 Must use 080 SE Transaction Set Trailer M 1 Must use


999999 N1/030L AK2 Transaction Set Response O 1 N1/030

999999 C1/040L

LOOP ID - AK2

LOOP ID - AK3

Notes: 1/010 These acknowledgments shall not be acknowledged, thereby preventing an endless cycle of acknowledgments of

acknowledgments. Nor shall a Functional Acknowledgment be sent to report errors in a previous Functional Acknowledgment. The Functional Group Header Segment (GS) is used to start the envelope for the Functional Acknowledgment Transaction Sets. In preparing the functional group of acknowledgments, the application sender's code and the application receiver's code, taken from the functional group being acknowledged, are exchanged; therefore, one acknowledgment functional group responds to only those functional groups from one application receiver's code to one application sender's code. There is only one Functional Acknowledgment Transaction Set per acknowledged functional group.

1/020 AK1 is used to respond to the functional group header and to start the acknowledgement for a functional group. There shall be one AK1 segment for the functional group that is being acknowledged.

1/030 AK2 is used to start the acknowledgement of a transaction set within the received functional group. The AK2 segments

L shall appear in the same order as the transaction sets in the functional group that has been received and is being acknowledged.

1/030 AK2 is used to start the acknowledgement of a transaction set within the received functional group. The AK2 segments shall appear in the same order as the transaction sets in the functional group that has been received and is being acknowledged.

Comments: 1/040 The data segments of this standard are used to report the results of the syntactical analysis of the functional groups of

transaction sets; they report the extent to which the syntax complies with the standards for transaction sets and functional groups. They do not report on the semantic meaning of the 232 transaction sets (for example, on the ability of the receiver to comply with the request of the sender).

1/040 The data segments of this standard are used to report the results of the syntactical analysis of the functional groups of transaction sets; they report the extent to which the syntax complies with the standards for transaction sets and functional groups. They do not report on the semantic meaning of the transaction sets (for example, on the ability of the receiver to comply with the request of the sender).

SH 997.4

997 - Functional Acknowledgment ISA - Interchange Control Header Pos: Max: 1 User Option(Usage): Must use Not Defined - Mandatory


Element Summary: TBA REQ.

Ref Id Element Name Req Type Min/Max Value ISA01 I01 Authorization Information Qualifier M ID 2/2 '00'

Description: Code to identify the type of information in the Authorization Information


Will only Send Code – 00, Should only receive – 00 ISA02 I02 Authorization Information M AN 10/10 'SENDERNAME'

Description: Information used for additional identification orauthorization of the interchange sender or the data inthe interchange; the type of information is set by theAuthorization Information Qualifier (I01)

Will only Send Senders Name Should only receive Senders Name

ISA03 I03 Security Information Qualifier M ID 2/2 '01' Description:

Code to identify the type of information in the SecurityInformation

Will only Send Code – 01, Should only receive – 01 ISA04 I04 Security Information M AN 9/10 '012345678'

Description: This is used for identifying the security informationabout the interchange sender or the data in theinterchange; the type of information is set by theSecurity Information Qualifier (I03)

Will only send senders duns number Should only receive senders duns number

ISA05 I05 Interchange ID Qualifier M ID 2/2 '01' Description: 'ZZ'


Will only send ‘01’, Should only receive ‘ZZ’ ISA06 I06 Interchange Sender ID M AN 15/15 '012345678'

Description: '012345678-12345' 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 senders duns number Should only receive senders duns number – supplier code

ISA07 I05 Interchange ID Qualifier M ID 2/2 'ZZ' Description: '01'


Will only send ‘ZZ’, Should only receive ‘01’ ISA08 I07 Interchange Receiver ID M AN 15/15 '012345678-12345'

Description: '012345678' Identification code published by the receiver of the data; When sending, it is used by the sender as their

ISA 997.5

096 Trim Masters, Inc. Harrodsburg, KY USA139 Trim Masters, Inc. Bardstown, KY USA

063844752

796567667

TMIHB TMIBT

192 Trim Masters, Inc. Nicholasville, KY USA 825946353 TMINV 193 Trim Masters, Inc. Leitchfield, KY USA 967532524 TMILF 194 Trim Masters, Inc. Modesto, CA USA 806416004 TMIMO 199 Automotive Technology Systems LLC. Lawrenceville, IL592 Master Trim de Mexico Torreon Mexico

877899695

812596419

ATS MTMT

572 Trim Masters, Inc. Bartlett, IN USA 052922697 BART 650 Master Trim de Mexico Chavez Mexico 812749414 MTMC 705 Trim Masters, Inc. Elmira Ontario Canada 201047177 TMIEL 873 Trim Masters, Inc. San Antonio, TX USA 626731827 TMITX

997 - Functional Acknowledgment sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

Will only send receiver’s duns number –supplier code Should only receive senders duns

ISA09 I08 Interchange Date M DT 6/6 YYMMDD Description:


Description: Time of the interchange

ISA11 I10 Interchange Control Standards Identifier M ID 1/1 'U' Description:


Only Send Code U - USA ISA12 I11 Interchange Control Version Number M ID 5/5 '00400'

Description: Code specifying the version number of the interchange control segments

Only Send Code 00400 ISA13 I12 Interchange Control Number M N0 9/9 XXXXXXXXX

Description: A control number assigned by the interchange sender

ISA14 I13 Acknowledgment Requested M ID 1/1 '0' for No Description:


Only Send 0 – “No” ISA15 I14 Usage Indicator M ID 1/1 USE 'P' FOR

Description: PRODUCTION Code to indicate whether data enclosed by this 'T' FOR TEST interchange envelope is test, production or information

Only Send Codes T,P – “Test” or “Production” ISA16 I15 Component Element Separator M ID 1/1 '>'



Code Plant Name and Location (1) DUNs # (92) Plant Abbrev.

ISA 997.6

997 - Functional Acknowledgment GS - Functional Group Header Pos: Max: 1 User Option(Usage): Must use Not Defined - Mandatory


Element Summary: TBA REQ.

Ref Id Element Name Req Type Min/Max Value GS01 479 Functional Identifier Code M ID 2/2 'FA'

Description: Code identifying a group of application related transaction sets


Only ‘FA’ will be used – Functional Acknowledgment GS02 142 Application Sender's Code M AN 2/15 '012345678'


GS03 124 Application Receiver's Code M AN 2/15 '011213141' Description:


GS04 373 Date M DT 8/8 CCYYMMDD Description:

Date expressed as CCYYMMDD GS05 337 Time M TM 4/4 HHMM


GS06 28 Group Control Number M N0 1/9 'XXXX' Description:


GS07 455 Responsible Agency Code M ID 1/2 'X' Description:

Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

GS08 480 Version / Release / Industry Identifier Code M AN 1/12 '004010' Description:


Senders DUNS

Refer To Note 1

Only ‘X’ for ANSIX12 will be used

Only ‘004010’ will be used

Semantics:

1. GS04 is the group date. 2. GS05 is the group time.

GS 997.7

997 - Functional Acknowledgment 3. The group control number GS06 in this header must be identical to the

same data element in the associated functional group trailer, GE02.





096 Trim Masters, Inc. Harrodsburg, KY USA139 Trim Masters, Inc. Bardstown, KY USA 192 Trim Masters, Inc. Nicholasville, KY USA 193 Trim Masters, Inc. Leitchfield, KY USA 194 Trim Masters, Inc. Modesto, CA USA 199 Automotive Technology Systems LLC. Lawrenceville, IL US 592 Master Trim de Mexico Torreon Mexico 572 Trim Masters, Inc. Bartlett, IN USA 650 Master Trim de Mexico Chavez Mexico 705 Trim Masters, Inc. Elmira Ontario Canada 873 Trim Masters, Inc. San Antonio, TX USA



GS 997.8

997 - Functional Acknowledgment ST - Transaction Set Header User Option(Usage): Must Use


TBA REQ. Ref Id Element Name Req Type Min/Max Value ST01 143 Transaction Set Identifier Code M ID 3/3 '997'


Will only send code 997 ST02 329 Transaction Set Control Number M AN 4/9 '9998'







Element Summary:

ST 997.9

997 - Functional Acknowledgment AK1 - Functional Group Response Header Pos: 020 Max: 1 User Option(Usage): Must use Heading - Mandatory

Loop: N/A Elements: 2 To start acknowledgment of a functional group

Element Summary:

Refer To Note 1


AK101 479 Functional Identifier Code M ID 2/2 'SH' Description:



AK102 28 Group Control Number M N0 1/9 '00224' Description:

Assigned number originated andmaintained by the sender

Semantics: 1. AK101 is the functional ID found in the GS segment (GS01) in the functional group

being acknowledged. 2. AK102 is the functional group control number found in the GS segment in the

functional group being acknowledged.

Notes: 1. Will Only Send Following Codes:

IN – Invoice Information (810)PO – Purchase Order Transaction (850)SH – Ship Notice/Manifest (856)

Should only receive:PS – Purchase Order Transaction (830)SS – Shipping Schedule (862)

AK1 997.10


Loop: AK2 Elements: N/A

997 - Functional Acknowledgment Loop AK2

To start acknowledgment of a single transaction set


Ref Id Element Name Req Max Use Repeat Usage 030 AK2 Transaction Set Response Header O 1 Used 040 Loop AK3 O 999999 999999 Used 060 AK5 Transaction Set Response Trailer Mandatory 1 Must use


Semantics: 1. AK201 is the transaction set ID found in the ST segment (ST01) in the transaction

set being acknowledged. 2. AK202 is the transaction set control number found in the ST segment in the

transaction set being acknowledged.

AK2 LOOP 997.11

997 - Functional Acknowledgment AK2 - Transaction Set Response Header Pos: 030 Max: 1 User Option(Usage): Used Detail - Mandatory

Loop: AK2 Elements: 2 To start acknowledgment of a single transaction set

Element Summary:

Refer To Note 1


AK201 143 Transaction Set Identifier Code M ID 3/3 '856' Description:

Code uniquely identifying a Transaction Set


AK202 329 Transaction Set Control Number M AN 4/9 '0001' Description:

Identifying control number that mustbe unique within the transaction setfunctional group assigned by theoriginator for a transaction set

Semantics 1. AK201 is the transaction set ID found in the ST segment (ST01) in the transaction

set being acknowledged. 2. AK202 is the transaction set control number found in the ST segment in the

transaction set being acknowledged.

Notes: 1. Will Only Send Following Codes:

810 – Invoice Information850 – Purchase Order Transaction856 – Ship Notice/Manifest

Should only receive:830– Purchase Order Transaction862– Shipping Schedule

AK2 997.12

997 - Functional Acknowledgment Loop AK3 Pos: 040 Repeat: 999999

Loop: AK3 Optional

Elements: N/A To report errors in a data segment and identify the location of the data segment

Loop Summary:TBA REQ.

Ref Id Element Name Req Max Use Repeat Usage 040 AK3 Data Segment Note O 1 Used 050 AK4 Data Element Note O 99 Used


AK3 LOOP 997.13



AK3 - Data Segment Note User Option(Usage): Used

To report errors in a data segment and identify the location of the data segment

Element Summary:

Pos: 040 Max: 1

Heading - OptionalLoop: AK3 Elements: 4

Ref Id Element Name Req Type Min/Max Value AK301 721 Segment ID Code M ID 2/3 'IT1'

Description: Code defining the segment ID of the data segment in error (See Appendix A - Number 77)

AK302 719 Segment Position in Transaction Set M N0 1/6 '7' Description:

The numerical count position of this data segment from the start of the transaction set: the transaction set header is count position 1

AK303 447 Loop Identifier Code O AN 1/6 '1' Description:

The loop ID number given on the transaction set diagram is the value for this data element in segments LS and LE

AK3 997.14

997 - Functional Acknowledgment AK4 - Data Element Note User Option(Usage): Used

To report errors in a data element or composite data structure and identify the location of the data element



Elements: 4Loop: AK3

Element Summary:

Ref Id Element Name Req Type Min/Max Value AK401 C030 Position in Segment M Comp '2'

Description: Code indicating the relative position of a simple data element,or the relative position of a composite data structure combinedwith the relative position of the component data element withinthe composite data structure, in error; the count startswith 1 for the simple data element or composite data structureimmediately following the segment ID

722 Element Position in Segment M N0 1/2 '5' Description:

This is used to indicate the relative position of a simple dataelement, or the relative position of a composite data structurewith the relative position of the component within the compositedata structure, in error; in the data segment the count startswith 1 for the simple data element or composite data structureimmediately following the segment ID

1528 Component Data Element Position in O N0 1/2 Used CompositeDescription:

To identify the component data element position within thecomposite that is in error

AK402 725 Data Element Reference Number O N0 1/4 '373' Description:

Reference number used to locate the data element in the DataElement Dictionary

AK403 723 Data Element Syntax Error Code M ID 1/3 '7' Description:

Code indicating the error found aftersyntax edits of a data element

All valid standard codes are used. AK404 724 Copy of Bad Data Element O AN 1/99 '010499'

Description: This is a copy of the data element in error

Semantics: 1. In no case shall a value be used for AK404 that would generate a syntax error,

e.g., an invalid character.

AK4 997.15

997 - Functional Acknowledgment AK5 - Transaction Set Response Trailer User Option(Usage): Must Use

To acknowledge acceptance or rejection and report errors in a transaction set


AK501 717 Transaction Set Acknowledgment Code M ID 1/1 'R' Description:

Code indicating accept or reject condition based on the syntax editing of the transaction set

All valid standard codes are used. AK502 718 Transaction Set Syntax Error Code O ID 1/3 '5'

Description: Code indicating error found based on the syntax editing of a transaction set

All valid standard codes are used.


Element Summary:

Pos: 040 Max: 1 Heading - Mandatory

Loop: AK2 Elements: 6

AK5 997.16



AK9 - Functional Groupn Response Trailer Pos: 070 Max: 1 User Option(Usage): Must Use Heading - Mandatory

Loop: N/A Elements: 9 To acknowledge acceptance or rejection of a functional group and report the number of included transaction sets from the original trailer, the accepted sets, and the received sets in this functional group

Element Summary:

Ref Id Element Name Req Type Min/Max Value AK901 715 Functional Group Acknowledge Code M ID 1/1 'R'

Description: Code indicating accept or reject condition based on the syntax editing of the functional group

All valid standard codes are used. AK902 97 Number of Transaction Sets Included M N0 1/6 '1'


AK903 123 Number of Received Transaction Sets M N0 1/6 '1' Description:

Number of Transaction Sets received AK904 2 Number of Accepted Transaction Sets M N0 1/6 '0'

Description: Number of accepted Transaction Sets in a Functional Group

Comments: 1. If AK901 contains the value "A" or "E", then the transmitted functional group is

accepted.

AK9 997.17

997 - Functional Acknowledgment SE - Transaction Set Trailer User Option(Usage): Must Use


TBA REQ. Ref Id Element Name Req Type Min/Max Value SE01 96 Number of Included Segments M N0 1/10 '30'


SE02 329 Transaction Set Control Number M AN 4/9 '0001' Description:



Pos: 080 Max: 1


Element Summary:

Heading - Mandatory Elements: 2Loop: N/A

SE 997.18

997 - Functional Acknowledgment GE - Functional Group Trailer User Option(Usage): Must Use



GE01 97 Number of Transaction Sets Included M N0 1/6 '1' 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 'XXXX' Description:






Max: 1Pos:

Loop: N/A


Element Summary:

Not Defined - Mandatory Elements: 2

GE 997.19

997 - Functional Acknowledgment IEA - Interchange Control Trailer User Option(Usage): Must Use

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


IEA01 I16 Number of Included Functional Groups M N0 1/5 Must use Description: '1'


IEA02 I12 Interchange Control Number M N0 9/9 'XXXXXXXXX' Description:


Max: 1Pos:


Element Summary:

Not Defined - Mandatory Elements: 2Loop: N/A

IEA 997.20


EXAMPLE OF AN OUTBOUND FUNCTIONAL ACKNOWLEDGEMENT - 997 (FROM TOYOTA BOSHOKU TO A SUPPLIER)

ISA*00*TOYOTA *01*796567667 *01*796567667 *ZZ*123456789-12345*060313*1350*U* 00400*000000001*0*P*>GS*FA*796567667*123456789*20060313*1350*1*X*004010 ST*997*0001 AK1*IN*12 AK2*810*000000001 AK3*DTM*7*IT1 AK4*2*373*7*010493 AK3*DTM*7*IT1 AK4*2*373*7*010499 AK3*DTM*7*IT1 AK4*2*373*7*010553 AK3*DTM*7*IT1 AK4*2*373*7*010643 AK3*DTM*7*IT1 AK4*2*373*7*010493 AK3*DTM*7*IT1 AK4*2*373*7*010499 AK3*DTM*7*IT1 AK4*2*373*7*010553 AK3*DTM*7*IT1 AK4*2*373*7*010643 AK3*IT1*5*IT1 AK4*7*234*?*010743 AK3*IT1*5*IT1 AK4*7*234*?*010743 A3*IT1*5*IT1 AK4*7*234*?*010743 AK3*IT1*5*IT1 AK4*7*234*?*010743 AK5*R*5 AK9*R*1*1*0 SE*30*0001 GE*1*1 IEA*1*000000001

EXAMPLE OUTBOUND 997.21


EXAMPLE OF AN INBOUND FUNCTIONAL ACKNOWLEDGEMENT - 997 (FROM SUPPLIER TO TOYOTA BOSHOKU)

ISA*00* SUPPLIER NAME *01*123456789 *ZZ*123456789-1234 *01*796567667*060313*1350*U* 00400*000000001*0*P*> GS*FA*123456789*796567667*20060313*1350*1*X*004010 ST*997*0001 AK1*PS*156 AK9*A*1*1*1 SE*4*0001 ST*997*0002 AK1*PS*157 AK9*A*1*1*1 SE*4*0002 GE*2*1 IEA*1*000000001

EXAMPLE INBOUND 997.22

Documents

EDI Implementation Manual For - iConnecticonnect-corp.com/specs/vendors/toyotaboshoku/tba_edi...1. R0203 - At least one of REF02, REF03 is required Notes: 1. TBA Card Code. The REF02