Implementation Guidelines for EDI Conventions

Transcription

1 Implementation Guidelines for EDI Conventions 1/6

2 The IGEC (Implementation Guidelines for EDI Conventions) from Hayashi Telempu North America Corp. (call HTNA) describes the Electronic Data Interchange (EDI) conventions and how it will be applied at HTNA. It includes data formats and communication specifications which will be necessary for the transmittal of data between the supplier and all HTNA facilities: Summary of EDI Procedures HTNA, Plymouth, MI HTNA, Lebanon, OH HTNA, Jasper, AL HTNA, Frankfort, KY HTNA, Lexington, KY HTNA, El Paso, TX HTNA, Los Angeles, CA Hayashi of Canada, Stratford, ON Reyes Amtex Automotive, San Antonio, TX EDI refers to the electronic exchange of information which follows specific standards. When interacting with HTNA, EDI involves the following basic steps: 1. The sender transmits EDI data to the Connect mailbox that resides at HTNA. 2. The receiver accesses the EDI Connect mailbox and retrieves the data that has been transmitted by the sender. 3. The receiver then translates the retrieved EDI data into a format that is usable by the appropriate application depending on the type of data transmitted. Requirements for HTNA Trading Partners While many standards exist for data transmission, HTNA will recognize only those which meet the ANSI X12 standards version 3060 for our EDI applications. Specifically, HTNA uses the Automotive Industry Action Group (AIAG) substandards of the ANSI X12 standards. The HTNA transaction version number correlates to the AIAG implementation guidelines used in developing each transaction set. HTNA may use any code specified in the AIAG standard as well as any additional codes that are not specified in the AIAG standard as the need may arise. 2/6

3 HTNA will transmit all EDI data through the Covisint Connect Data Network. If you choose a Network other than Covisint, you must establish an interconnect with Covisint. 3/6

4 Transaction set Requirements for HTNA Trading Partners HTNA will transmit the following electronic documents to the Supplier 830 Planning Schedule with Release Capability. The 830 is usually sent at the first business day (Monday) of every week. This is usually weekly forecast and the first week is usually firm order. 862 Shipping / Production schedule, daily (where applicable). ** No longer use the 862 transaction. 997 Functional Acknowledgment. This 997 transaction set will be available within 30 minutes. For ASN's passing syntactical validation, it will be up to the supplier to indicate to HTNA if the supplier wishes to receive a 997 upon syntactical acceptance of their ASN transmission. (Default ASN's passing syntactical validation = OFF) 824 Application Advice will be sent for each ASN received, and passing syntactical requirements. The 824 will indicate either the acceptance of the ASN, or the rejection, with appropriate reason(s) for the rejection. This 824 transaction set will be available within 30 minutes. The ASN must be corrected and retransmitted within 2 hours if 824 indicated rejection. and will receive the following electronic documents from the Supplier: 856 Ship notice / manifest (ASN) one for each shipment. This ASN transaction must be transmitted by the supplier at the time the shipment leaves the ship-from facility, or within 20 minutes. The ASN must arrive within HTNA s mailbox prior to delivery of product. SPECIFIC information for each container must be included in the ASN, and generated by scanning the AIAG bar coded container labels. Please note, Supplier will eventually be required to generate the ASN by scanning AIAG bar coded container labels. 997 Functional Acknowledgment. This 997 transaction set must be transmitted by the supplier within 30 minutes. 4/6

5 HTNA Suppliers 830 (Planning Schedule) Sent wkly order on Monday 997 (Functional Acknowledgement) 862 (Shipping Schedule) Sent daily order where applicable 997 (Functional Acknowledgement) 856 (Advanced Ship Notice) Must be transmitted by the Supplier at the time the shipment leaves the ship-from facility, or within 20 minutes 997 (Functional Acknowledgement) 824 (Application Advice) Sent within 30 minutes receipt of 856. Supplier must resend an updated 856 within 2 hours. 5/6

6 Implementation process Hayashi Telempu North America Corp. The following general guidelines will be followed for EDI implementation: START Phase I Phase II Phase III END Phase I Preparation for Testing 1 - Create all documents maps (830, 862, 856, 824, and 997) 2 - Set up communications (if using a VAN) 3 - Complete EDI Profile for Supplier.doc by each supplier ship-from location and fax/send to HTNA EDI coordinator listed in the HTNA Divisional Contacts List which can be found in Section 2 of IGEC (Implementation Guidelines for EDI Conventions). HTNA EDI coordinator will send EDI Profile for Supplier.doc back to you with assign supplier code if necessary. Phase II Communication and mapping test for all documents 1 - Follow IGEC.3 (Implementation Instructions).doc to test all documents (830, 862, 856, 824, and 997) ** All EDI questions during the testing process should be directed to the HTNA EDI coordinator for the HTNA facility. Any unanswered questions, however, can be directed to the HTNA Information Technology Department or Materials contact listed in the HTNA Divisional Contacts List which can be found in Section 2 of IGEC (Implementation Guidelines for EDI Conventions). Phase III Move all documents change to production 1 HTNA EDI Coordinator will contact to the supplier when we move the changes to production. All future questions should be directed to the Information Technology Department or Materials contact for the HTNA facility we are supplying. 6/6