View EDI Barcode Specification 2008 04

Chapter 1 Introduction
EDI & Bar Code Label Implementation Requirements

Introduction
This document may not be disclosed, duplicated or used for any purpose, in whole or in part, without the prior written consent of Honda of America Mfg., Inc.
Honda of America Mfg., Inc. 2007
February 2007
1-1
Chapter Contents
This chapter contains an overview of the requirements for using Hondas EDI system.
Table of Contents
Using Electronic Data Interchange (EDI)............................................................................................ 3 How Honda's EDI Works:.................................................................................................................... 3 Special Requirements......................................................................................................................... 6
1-2
February 2007
Using Electronic Data Interchange (EDI)

How Honda's EDI Works:
1. 2. Honda sends and receives EDI transactions via HSThub, a Honda provided mailbox system. The supplier receives the Weekly Release (ANSI 830) via EDI. The Weekly Release is used as a firm and/or forecast document that provides information by part number. It contains requirements formatted into daily, weekly, or monthly buckets. The OE production requirements are loosely linked to a Ship Schedule (ANSI 862) transaction for shipment authorization. The length of the forecast may be shortened by the request of the supplier. 3. Honda transmits the Ship Schedule (ANSI 862) to authorize shipment of specific parts in specific quantities to specific destinations on specific dates and times. It is used and loosely linked by part number and quantity to a previously transmitted Weekly Release (ANSI 830). Its primary use is for OE production part requirements. Purchase Orders (ANSI 850) also authorize shipment. The supplier uses the information from the 830, 850 or 862 to print Container, Master, and Mixed Labels. Suppliers should pull data from their EDI mailbox multiple times a day to ensure they have the most recent ordering documentation. 4. Honda may send a Text Message (ANSI 864) along with any of the above transactions to electronically communicate an explanation to support the document. The 864 Text Message is used to provide electronic messages for people and is linked to the corresponding document by a reference number. The supplier sends the Functional Acknowledgments (ANSI 997) via EDI. The Functional Acknowledgment is a standard communications handshake verification. It is used to confirm that successful communication has occurred between the EDI translators of each pair of trading partners. Honda requires a Functional Acknowledgment in response to all outbound transmissions and provides it in response to all incoming transmissions.
5.
February 2007
1-3
6. A Planned Load is created from the Honda EDI Ordering Documents (850, 862). This information will be used to create an ASN. The ASN must be reconciled to the planned load, and the planned load should be verified to the physical shipment. The preferred method to verify that the physical shipment matches the planned load is through barcode scanning. This comparison identifies discrepancies between the actual and planned shipping requirements while also verifying barcode readability. Other methods must be approved by Honda. The supplier must print a master Packing List which conforms to Honda's standards. The Master Packing List is attached to the shipping papers for the load and accompanies the truck. The Quick Receive label is also printed and attached to each pallet, rack, weld basket or cart. Note - The 856 ASN number and the Master Packing List number are the same number identified as the ASN/SID number on the Master Packing List. 9. Using the data collected by scanning, the supplier sends an ASN (ANSI 856), via EDI, to Honda in conformance with Honda's standards. Honda transmits a Functional Acknowledgment (ANSI 997) and Application Advice (ANSI 824) in response to ASNs (ANSI 856) that are processed by our application system. The Application Advice provides feedback on the validity of an ASN. If the 824 indicates the ASN was rejected, the supplier should correct the ASN and retransmit it. Chapter 7, Troubleshooting, provides helpful information on correcting ASN issues. The supplier should access their EDI mailbox within 15 minutes of sending the ASN to pull the 824 and analyze the feedback. As the truck is unloaded, the barcodes are scanned for verification against the ASN. Honda will transmit a Receiving Advice (ANSI 861) if discrepancies are found; if an ASN was not sent, the shipment will be received manually. The suppliers payment for OE orders is based on confirmed receipt, rather than an invoice. A Remittance Advice (ANSI 820) with remittance details is sent to the supplier for payment purposes. Honda uses the Price/Sales Catalogue (ANSI 832) to facilitate agreement between Honda and suppliers regarding the part price on file as of a specified date. Honda uses the Invoice (ANSI 810) for DSPS relationships. Suppliers do not send an Invoice to Honda. Honda uses the Inventory Advice (ANSI 846) transaction set to request and receive inventory information from suppliers that are DSPS.
7.
8.
10.
11.
12.
13.
14. 15.
1-4
February 2007
Hondas Financial Institution

Remittance Advice (820) NOTE: The electronic transmission of the 820 is not used by all Hondas facilities. Talk to your Honda accounting contact for more information.
Suppliers Financial Institution

Remittance Advice (820)
SENDS
-Inventory Advice (846) -Advance Ship Notice (856) - Functional Acknowledgment (997)
ORDERING
-Application Advice (824) - W eekly Releases (830) - Inventory Advice (846) - Purchase Orders (850) - Ship Schedule (862) - Text (864)
CONSOLIDATION CENTERS
RECEIVES
-Invoice (810) - Remittance Advice (820) -Price/Sales Catalog(832) - Purchase Order (850) - Receiving Advice (861) - Ship Schedule (862) - Inventory Advice (846)
RECEIVING AND SHIPPING

- Master Packing List - Advance Ship Notice (ASN)
- Application Advice (824) - Weekly Releases (830) - Text (864)
- Functional Acknowledgment (997)
ASN/ RECEIVING PROCESSING

-Advance Ship Notice (856) - Application Advice (824) - Receiving Advice (861) - Master Packing List
- Sequencing/Kitting - Returnable Container - Pallet Control
PRINT AIAG BAR CODE LABELS

-Container Labels - Quick Receive Labels - Master and/or Mixed Labels
SCANNING PAYMENT
-Invoice (810) - Remittance Advice (820) - Price/Sales Catalogue (832) -Staging or Loading Areas - Bar Code Labels -100% used to create ASNs
RECONCILIATION PROCESS ACKNOWLEDGMENT

- Functional Acknowledgment (997) -Computer Generated Master Packing Lists - ASN Transmission 100% of Shipments
HONDA SYSTEM
SUPPLIER SYSTEM
February 2007
1-5
Suppliers Using a Warehouse for Delivery Services

Special Requirements
Suppliers that have elected to enter into business with a public warehouse for delivery services are required to meet Honda's EDI and Bar Code requirements. Honda requires an ASN and MPL from the public warehouse when parts are shipped to a Honda plant or consolidation center. Suppliers are required to label all containers with part identification labels, which conform to Hondas Bar Code Label Specification. In the event that a supplier makes special shipment directly to a Honda plant or consolidation center, the supplier is required to provide Honda with an ASN and MPL. These ASNs must be created by scanning and transmitted via EDI.
1-6
February 2007
Chapter 2 General Terms and Conditions

General Terms and Conditions
April 2008

Electronic Data Interchange Terms and Conditions 1) General. These Electronic Data Interchange Terms and Conditions (these EDI Terms) establish a framework for those cases in which Buyer and Seller adopt electronic means and methods of communicating some or all offers, acceptances, Orders, and/or other information relating to the purchase and sale of Goods in order to address issues peculiar to the electronic interchange of purchase, sale and other information. Seller hereby agrees to implement such electronic means and methods of communication upon Buyer's request. Capitalized terms used herein shall have the definitions given to them in the Agreement for Purchase and Sale of Goods (or other applicable or successor agreement) (the Agreement) unless otherwise defined herein. 2) Coverage. The EDI & Bar Code Label Implementation Manual (the Manual) of which theses EDI Terms are part covers only those types of transactions as are described in EDI Transaction Description documents, which are contained in the Manual or which are later released by Buyer to Seller. The Manual is a Specification as defined in the Agreement and may be adopted, discontinued, modified or amended by Buyer as described in Section 1.2 of the Agreement. No transactions or transaction types are authorized for use between Buyer and Seller except those described in the EDI Transaction Description documents. Seller assumes all miscommunication risk if transactions are sent to Buyer which are not described in the EDI Transaction Description documents, and Buyer has no responsibility with respect thereto. 3) Standards and Conventions. Each EDI Transaction Description document will contain a description of the release level or levels of each EDI standard which are accepted by Buyer for use with Electronic Data Interchange of the transactions described therein, and Buyer shall notify Seller of the EDI standard release level which it intends to use for Transmissions originated by Buyer. If more than one release level of an EDI standard is accepted by Buyer, Seller shall inform Buyer reasonably in advance of the commencement of EDI between Buyer and Seller of the particular level to be used by Seller. If Seller changes from one accepted release level to another, Seller shall give Buyer at least thirty (30) days advance written notice of the change. No EDI standard release levels other than those specified by Buyer in EDI Transaction Description documents are authorized for use with EDI between Buyer and Seller. Seller assumes all risk of transactions sent to Buyer which are not at accepted EDI standard release levels.
2-2
April 2008
Chapter 2 General Terms and Conditions 4) Exception Reporting and Acknowledgments. a. Except as otherwise set forth in the Manual, all Transmissions shall be functionally acknowledged by the recipient in accordance with the standards and within the time specified in the applicable EDI Transaction Description. Transmissions of functional acknowledgments will not be functionally acknowledged. b. When a functional acknowledgment indicates errors in a Transmission that cause part or all of the Transmission to be rejected by the recipient, the sender shall retransmit the rejected transaction(s) to the recipient within the time specified in the applicable EDI Transaction Description. In the alternative, or in addition at the request of the receiving party, the sender will transmit the information to the receiving party using a method of NonEDI Transmission directed by the receiving party or, if none is specified, using a method of Non-EDI Transmission that is timely, reasonable, and appropriate under the circumstances. c. If an EDI Transaction Description document specifies a regular schedule for such transaction(s) to be sent by one or both parties, the scheduled recipient shall promptly notify the sender via telephone or electronic facsimile whenever the transaction is not received within the time specified in the applicable EDI Transaction Description. d. The sending party will promptly notify the receiving party via telephone or electronic facsimile whenever Transmissions are sent other than on an established regular schedule if the sending party requires the recipient to receive and act on a Transmission prior to the time of next regularly scheduled Transmission.
5) Production and Use of Transmissions. Either party at any time may cause a Transmission, whether sent or received, to be reproduced in a tangible visually perceptible form and may label or identify information so reproduced in such tangible form in a manner consistent with the applicable EDI Standards and Procedures. Any such reproduction may be used for any and all purposes for which a written or printed original could be used had such Transmission been sent in a tangible visually perceptible form in the first instance, including, but not limited to, use in evidence in any court, including, for example, to prove contract terms or a debt or in regard to any dispute hereunder. Nothing herein precludes a challenge to the accuracy of such reproduction available on grounds other than that Electronic Data Interchange was involved, or any objection also available as against use of a written or printed original.
April 2008
2-3
6) Effect of Electronic Data Interchange: Special Provisions. a) In a Transmission, all non-blank Data Elements which have been specified in applicable EDI Standards and Procedures are conspicuous as defined in Section 1-201 (10) of the UCC. b) Where a Transmission is accompanied by an access or identification code peculiar to the sender and such code (i) is generally recognized in the industry as unique to the sender, (ii) was authorized or supplied in a Non-EDI Transmission by the sender, or (iii) was authorized or supplied by the receiving party in a Non-EDI Transmission (as set forth in applicable EDI Standards and Procedures), such code is deemed to be a symbol executed or adopted by the sender with a present intention to authenticate a writing under Section 1-201(39) of the UCC. c) It is the responsibility of the party originating a Transmission to include in such Transmission all required Data Elements as set forth in the applicable EDI Standards and Procedures. d) The party sending a Transmission is responsible for its content, including communication-induced or other errors, omissions of required Data Elements, or otherwise. e) Each party shall bear its own costs to send or receive Transmissions, including but not limited to, the costs of any equipment, services, and software necessary to conduct EDI according to EDI Standards and Procedures, and Seller shall bear any transaction costs of third-party mailbox computer proprietors imposed on Transmissions sent or received by either party to the extent that Seller chooses to use a third-party mailbox. 7) Scope. a. These EDI Terms are intended to facilitate the exchange between the parties of information by Electronic Data Interchange. Except to the extent specifically set forth herein, these EDI Terms do not extend to the substance, significance or effect, legal or otherwise, of the information or communications actually exchanged. The specification of Data Elements in applicable EDI Standards and Procedures is not intended to alter the applicable provisions of any agreement between Buyer and Seller with regard to the formation or construction of contracts. 8) EDI Address Designation. a. Buyer and Seller shall exchange mailbox access codes through NonEDI Transmissions. Buyer and Seller shall inform each other at least three days prior to a change in either party's mailbox access code.
2-4
April 2008
Chapter 2 General Terms and Conditions 9) Definitions. For the purposes of these EDI Terms and the EDI Transaction Description documents, the following definitions apply: a) Data Element when used in connection with EDI Standards and Procedures, means the smallest named item in EDI Standards and Procedures that can convey information or data (unless expressly otherwise defined by the parties in applicable EDI Standards and Procedures) and each non-blank Data Element which has been specified for use in an applicable EDI Standards and Procedures document contained in a Transmission is a term as defined in Section 1-201(42) of the UCC. b) Eastern Time means Eastern Standard Time or Eastern Daylight Savings Time as applicable. c) Electronic Data Interchange or EDI means confirmed and logged electronic computer to computer communication between Buyer and Seller pursuant to Electronic Data Interchange Standards and Procedures. A communication is an electronic computer to computer communication when both sender and receiver are electronic computers. An electronic computer to computer communication is confirmed when the receiving computer confirms in a manner consistent with telecommunications protocols being employed by the parties, receipt, free of transmission errors, of the information communicated by the sender. The receiving computer is the computer of the ultimate addressee or that of an intermediary (otherwise known as a mailbox computer) designated for use by the parties. The communication is logged when, after receipt of telecommunications protocol acknowledgment of communication free of transmission errors from the receiving computer, the sender stores the information communicated in a non-temporary log or data file. d) Electronic Data Interchange Standards and Procedures or EDI Standards and Procedures mean the standards, conventions and procedures governing Transmissions, including, but not limited to, descriptions of the nature and types of information and transactions to be exchanged and the rules governing interpretation and use of such information and/or transactions, as may be from time to time transmitted by Buyer to Seller or accepted by Buyer in a Non-EDI Transmission. Each such description shall govern only those types of Transmissions (such as, for example, requests for quotes, quotations, Purchase Orders, Material Releases, Advance Ship Notices, and so forth), and shall apply only to Transmissions between those specific divisions or locations of Buyer and Seller, as may be expressly set forth in such description. Each document which sets forth EDI Standards and Procedures, including but not limited to (1) the Manual, (2) these EDI Terms, and (3) specific EDI Transaction Description documents describing particular types of transmissions, shall be issued as a Specification as that term is defined in Section 1.2 of the Agreement.
April 2008
2-5

e) Non-EDI Transmission means communication of information by ordinary, registered or certified mail, telegram, telex, TWX, electronic facsimile device, courier, by any other means that automatically produces a written record confirming the receipt of the information and its content, or by verbal message if the verbal message is confirmed within three business days thereafter by one of the other methods of communication described in this paragraph. f) Production Day means a day designated by Buyer as a day on which manufacturing activities are conducted at the Buyer's facility applicable to a given EDI Transaction. g) Transmission means communication of information by Electronic Data Interchange. A Transmission hereunder shall be deemed an intentional reduction to tangible form having the effect of a writing under Section 1-201 (46) of the Uniform Commercial Code as adopted in the State of Ohio, and as amended from time to time (UCC). 10) Alternate Method of Communication. Unless otherwise specified in an applicable EDI Standards and Procedures document in the event of a failure of Electronic Data Interchange (whether by lack of confirmation as set forth above or for other reason known to the sender which would indicate that the addressee did not receive a Transmission), it is the responsibility of the sending party to transmit the contents of any pending Transmission to the receiving party using a method of Non-EDI Transmission which is timely, reasonable, and appropriate under the circumstances. Each party will notify the other party of changes, deletions, or additions to such address information which shall become effective on the date specified in the notice upon the other party's receipt thereof.
2-6
April 2008
Chapter 3 Key Contacts

Key Contacts
This document may not be disclosed, in whole or in part, without the prior written consent of Honda of America Mfg., Inc.
February 2007
3-1
Chapter Contents
This chapter contains information concerning key EDI contact information.
Table of Contents
EDI Implementation...............................................................................................................................3 EDI Task Responsibilities....................................................................................................................3 Table 3.1 EDI Key Contacts ...........................................................................................................3
3-2
February 2007
EDI Implementation
EDI Task Responsibilities
To obtain answers to questions regarding Honda's EDI procedures please use the following guidelines:
Table 3.1 EDI Key Contacts
Situation Supplier uses GXS
Contact GXS: Enabling: 1-800-655-8865 Account Support: 1-877-326-6426 HAM EC Group: HAM_ISG_EC_Support@ham.honda.com (937) 578-0447 Monday Friday 7:00 a.m. 4:00 p.m. EST For after hours & weekend support: Contact the Honda helpdesk: 1-877-606-1700 Your software provider or internal IS Support North American Logistics Systems Group: HondaEDI@ham.honda.com
Supplier uses HSThub -Establish connectivity -Data transfer issues (ASNs/997s) -Password problems -Customer Assistance
Software startup and function questions -ASN structure requirements -Bar Code Label Requirements -New supplier or trading partner setup Operational/Technical issues
HAM EC Group: HAM_ISG_EC_Support@ham.honda.com (937) 578-0447 Monday Friday 7:00 a.m. 4:00 p.m. EST For after hours & weekend support: Contact the Honda helpdesk: 1-877-606-1700
Note To contact a Honda associate directly via E-mail, please use the following address format: First Name_Last Name@ham.honda.com
February 2007
3-3
Chapter 4 Implementation Steps

Implementation Steps
This document may not be disclosed, duplicated or used for any purpose, in whole or in part, without the prior written consent of Honda of America Mfg., In.
April 2008
4-1
Chapter Contents
This chapter provides Honda Technical and Procedural EDI information including connectivity to Hondas value added network-HSThub.
Table of Contents
Overview ................................................................................................................................................3 Requirements to Use Honda Approved Software ...............................................................................4 Trading Partner Set-up ........................................................................................................................4 Data Delimiters ....................................................................................................................................5 Data Format.........................................................................................................................................5 Honda EDI System Availability............................................................................................................5 Honda Electronic Mailbox IDs .............................................................................................................6 EDI Copy .............................................................................................................................................8 EDI Copy Documents: .........................................................................................................................8 Copy Request:.....................................................................................................................................8 Honda Supply Team Hub HSThub ................................................................................................9 Files Types Supported by HSThub .....................................................................................................9 Connectivity to HSThub.....................................................................................................................10 Supplier Fire Wall Considerations .................................................................................................11 HSThub Test System Considerations............................................................................................11 HSThub Production System Considerations .................................................................................11 HSThub Passwords...........................................................................................................................12 Trading Partner Application Design Considerations .........................................................................13 FTP/s or FTP Client Design Considerations..................................................................................13 Supported FTP commands ...............................................................................................................14 Functional use of FTP commands.....................................................................................................15 Logging in to the server .................................................................................................................15 Sending data to HSThub ...................................................................................................................17 Sample Put Command...................................................................................................................17 Extracting Data from your mailbox ....................................................................................................18 Listing Mailbox contents ....................................................................................................................18 Confirm the get option .................................................................................................................19 Extracting data ...............................................................................................................................19 Sample get Commands...............................................................................................................19 Get command No data available ................................................................................................24 Closing the FTP connection .............................................................................................................24
4-2
April 2008
Overview
To implement EDI with Honda, follow these steps: 1. 2. 3. 4. 5. Contact Hondas NAL Systems team for a description of the EDI go-live process and testing requirements: HondaEDI@ham.honda.com. Choose software path. Establish a test mailbox. Honda NAL Systems will initiate the process; Hondas EC (Electronic Commerce) Group will establish the mailbox. Complete the Honda supplier testing process. Your Trading Partner information will be submitted to Honda EC to establish the production link to Hondas EDI system. NOTE: Honda NAL (North American Logistics) Systems is part of Honda Purchasing, North American Logistics group. They are responsible for supplier EDI and bar code testing, approved software provider testing, coordinating with other Purchasing departments to identify and prepare new suppliers for EDI transmissions, process related troubleshooting, and EDI and bar code related communications throughout the N.A. Purchasing organization. Hondas EC (Electronic Commerce) team is part of Honda ISG (Information Systems Group). They are responsible for Hondas translator, integration to back end systems, EDI related communication flow between the Honda plants, trading partner set-up. Both groups work closely together on items such as coordinating specification changes and solving supplier issues. In general, the EC teams expertise is on technical issues, while NALs is on business process issues.
April 2008
4-3
Requirements to Use Honda Approved Software

In order to meet Hondas EDI and Bar Code requirements, a supplier must communicate with Honda using an approved EDI and Bar Code solution. Honda does not endorse or recommend specific software providers, but does require that all EDI and Bar Code software is Honda approved to communicate with Honda. There are two different paths a supplier may choose to communicate with Honda. These paths are: 1. Standards
Used by Honda suppliers who have purchased one of the Honda approved software provider packages. (Refer to Chapter 5 for more information on these packages.) 2. Hybrid
Used by Honda suppliers who will be responsible for developing their own EDI and Bar Code systems. A supplier is required to complete the Honda supplier testing process based on the path chosen. Details of the testing process are listed in Chapter 6.
Trading Partner Set-up

During set-up, a Honda EDI analyst will contact you to clarify the following information: Supplier Mailbox ID Supplier Duns Number* *If you are not familiar with your companys 9-digit Duns number, please contact your accounting department for this information or contact Dun & Bradstreet directly at: 1-800-999-3867 (US) 1-800-463-6362 (Canada) Hondas Duns numbers are included in this chapter.
4-4
April 2008
Data Delimiters
The following table defines Hondas required data delimiters: Information 1. 2. 3. Element Delimiter Sub-element Delimiter Segment Terminator Character * ^ ~ ASCII Hex 2A 5E 7E EBCDIC Hex 5C 5F A1
Data Format
Honda requires all EDI data to be in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Honda EDI System Availability

Scheduled Downtime: Honda does not process inbound or outbound EDI data during the following times due to Honda system maintenance: Between 1:00 AM and 6:00 AM EST (actual time varies by plant) Monday through Friday 12:01 AM to 12:00 Noon EST Sunday Unscheduled Downtime: This category could include downtime due to: Unanticipated system issues or Planned downtime not following the scheduled downtime above. When unscheduled downtime occurs, Honda will make its best effort to inform the supplier base. The notification will be via email. For a supplier to be included in the email notification, they should send a group email address to HAM_ISG_EC_SUPPORT@HAM.HONDA.COM stating their desire to be included in downtime notifications. NOTE: Honda will only accept a group email address for downtime notification. The reasons are: 1) multiple associates within your company can be easily informed of downtime, 2) your company will control who gets the email and 3) your company has the flexibility to change contacts within your email system.
April 2008
4-5
Honda Electronic Mailbox IDs

The table below displays the Honda electronic mailbox IDs. These mailbox IDs are valid for inbound and outbound data from to/from Honda. They apply to HSThub data as well as data through a VAN.
System AHM Production AHM Production HAM New Model and DSPS (Star) Location American Honda Motors (AHM) American Honda Motors (AHM) Marysville Auto Plant (MAP) Marysville Motorcycle Plant (MMP) Honda de Mexico (HDM) International Parts Supply(IPS) International Parts Supply (IPS Canada) Honda of America Mfg (HAM) Honda of America Mfg (HAM) Honda of America Mfg. (HAM) Honda of America Mfg. (HAM) Honda of Canada Mfg (HCM) Honda of Canada Mfg (HCM) Honda de Mexico (HDM) Honda de Mexico (HDM) Honda Mfg of Alabama (HMA) Honda Mfg of Alabama (HMA) Honda Mfg of Indiana (HMIN) Honda Mfg of Indiana (HMIN) Honda Power Equipment (HPE) Honda Power Equipment (HPE) Honda Power Train Georgia (HPPG) Honda Power Train Georgia (HPPG) Honda South Carolina (HSC) Honda South Carolina (HSC) All Honda locations All Honda locations All Honda locations All Honda locations Account ID HAHM **HAHM HOAM User ID AHMEC AHMECG1 AHMECG2 HOAM025 DUNS# 008860389 008860389 092162643
HAM New Model and DSPS (Star) HAM Production (Delta) HAM Production (Delta) HAM Production (GPCS) HAM Production (GPCS) HCM Production (GPCS) HCM Production (GPCS) HDM Production HDM Production HMA Production (GPCS) HMA Production (GPCS) HMIN Production (GPCS) HMIN Production (GPCS) HPE Production (GPCS) HPE Production (GPCS) HPPG Production (GPCS) HPPG Production (GPCS) HSC Production (GPCS) HSC Production (GPCS) Software Approval (Delta) Software Approval (STAR) Software Approval (GPCS) Software Approval (AHM)
HOAM HOAM **HOAM HOAM **HOAM HCMH **HCMH HDMH **HDMH HMFG **HMFG HMIH **HMIH HHPE **HHPE HHPG **HHPG HSCT **HSCT HOAM HOAM HOAM HOAM
HOAM029 HAMFG HAMECG1 HAMECG2 HXMFG HXMECG1 HXMECG2 HCMEC HCMECG1 HCMECG2 HDMEC HDMECG1 HDMECG2 HMAEC HMAECG1 HMAECG2 HMIEC HMIECG1 HMIECG2 HPEEC HPEECG1 HPEECG2 HPGEC HPGECG1 HPGECG2 HSCEC HSCECG1 HSCECG2 SOFTAPP SOFTAP1 SOFTAP2 SOFTAP3
092162643 092162643 092162643 092162643 092162643 246323166NA 246323166NA 811474667 811474667 827961264 827961264 792050838 792050838 155498129 155498129 198550605 198550605 012165564 012165564 092162643 092162643 827961264 008860389
Note: There are three (3) spaces between the Acct ID and User ID
**For suppliers using GXS (old IBM GS) these mailbox accounts must be established to facilitate the volume of data being transmitted by Honda. No additional trading partner set up should be required on your system. Suppliers will not receive EDI documents with these account and user IDs. These accounts are not required for the HSThub. Example: An EDI document coming from the Honda production system would arrive at the supplier system with sender ID of HOAM HAMFG (ISA Segment 06) even though Honda transmitted the document through mailbox ID HOAM HAMECG1 or HOAM HAMECG2.
4-6
April 2008

If additional information is required, contact your Honda representative.
As HAM plants (AEP, ELP, HTM, IPS, MAP, and MMP) convert to GPCS, they will also convert to the new HAM EDI mailbox. The mailbox list is in the previous graph. Suppliers should prepare for this conversion. Note: The HAM plants will convert individually, so if a supplier ships to more than one HAM plant they will need to support both the Delta and GPCS mailboxes simultaneously. Delta to GPCS conversion timing will be communicated via the actual plant and the eCLink newsletter.
April 2008
4-7
EDI Copy
The following guidelines will be used by Honda concerning the copying of EDI documents. These guidelines are based on the following current business conditions: If Honda is responsible for the business need to copy EDI documents, Honda will provide the copy function using Honda Copy. Honda copy functionality supports both inbound and outbound documents. Examples would include: 1. DSPS relationship 2. Relationships between suppliers arranged by Honda. If Honda is NOT responsible for the business need of copying EDI documents, the supplier will be responsible for the copy function. This can be accomplished via various methods. Some possibilities include: Software Provider copy functionality Suppliers communication software A supplier could internally copy the EDI documents programming VAN provided copy
EDI Copy Documents:

In general, documents supported for copying will be: Outbound: 824, 830, 850, 862, 864 Inbound: 856 Documents other than these will be reviewed based on business need and set up accordingly.
Copy Request:
Suppliers will need to request a copy (email) from the North American Logistics Systems Group. NAL will approve (or reject) the request based on the above EDI Copy Guidelines. NAL will work with the supplier on other alternatives if the copy is not approved. Email requests should be sent to HondaEDI@ham.honda.com and include the following: Supplier Name and Honda 8-digit supplier number Which Honda plants the copy applies to Which EDI documents to be copied The Honda 8-digit supplier number to send the copy to Reason for Copy request
4-8
April 2008
Honda Supply Team Hub HSThub

Background
The Honda Supply Team Hub - HSThub facilitates the exchange of data with Honda trading partners. HSThub replaces the current Value Added Network (VAN) functionality supplied to Honda by GXS (old IBM GS) for EDI transmissions. HSThub is intended to provide a more cost efficient mechanism to exchange data for Honda and its trading partners.
Supplier Communication Overview
Numerous Honda systems create data and pass it to HSThub where it is transferred to a trading partners mailbox. Each trading partner is responsible for retrieving the data from their mailbox at intervals that support the companys relationship with Honda. Many trading partners will generate data, which needs to be communicated back to Honda. These trading partners must push their data to HSThub and place it in a designated Honda mailbox. Honda will pick up this data and transfer it to the appropriate Honda system. A list of EDI mailboxes can be found at the beginning of this chapter.
Files Types Supported by HSThub

HSThub will support the transfer of the following data types: EDI Data transaction sets as defined in the Honda EDI and Bar Code Implementation Manual Engineering Drawings Drawing data and related files Data files miscellaneous file formats (i.e. Flat Files and reports)
April 2008
4-9
Connectivity to HSThub
HSThub supports two forms of connectivity: 1. Secure File Transfer Protocol (FTP/s) via the internet. FTP/s is implemented using implicit SSL Honda recommends the use of passive mode. Requires the use of an FTP/s client** The list of approved FTP/s clients are as follows:
Vendor Ascential Software Cleo
Product Name Datastage TX Lexicom
Version/PTF Level 7.5 3.5 Win 95 2.1.3 *
Website www.ascential.com www.cleo.com
Columbia University
Kermit
C-Kermit 8.0.211 (Unix) 32 bit V3R1/3100034
www.columbia.edu/kermit
QualEDI Trailblazer
QualEDI for Windows ZMOD FTP
www.qualedi.com www.trailblazersystems.com
* set ftp command-protection-level confidential, set ftp data-protection-level confidential Note - Use of FTP/s clients/versions NOT on this list is not recommended or supported by Honda. 2. File Transfer Protocol via the Automotive Network Exchange (ANX) Requires use of an FTP client Commonly available in most operating systems Requires use of ANX TunnelZ Client used must be RFC959 compliant (support for passive mode is recommended) ** FTP/s Client Verifies secure connection through use of SSL technology and Public Key Encryption. Note: The use of standard FTP via the internet is NOT supported.
4 - 10
April 2008
Supplier Fire Wall Considerations

Honda strongly recommends that trading partners utilize URLs to access HSThub via the internet rather than IP addresses. Honda does not recommend using IP addresses, as they are not guaranteed to remain constant over time. ANX Notes: If you are using active mode FTP, be sure that your system/network/firewall properly converts your internal IP address to your ANX IP address within the ftp communications. If you have issues with active mode FTP, then Honda recommends that you use passive mode FTP. You must ensure that your FTP client supports passive mode (for example, Windows FTP does not support passive mode). In passive mode FTP, Honda will guarantee the proper ANX IP mapping.
HSThub Test System Considerations

To access EDI test data from Honda using FTP/s use the following parameters: FTP/s URL - sdataexchangethdc.hondasupplyteam.com Control port 30244 Data port - 30245-30254 These ports must be available on your firewall (in passive mode if used). To access EDI test data from Honda using ANX use the following parameters: ANX IP-166.57.29.247 Control port 30244 Data port - With Active Mode FTP, port 30245 is used With Passive Mode FTP, any port > 1024 may be used These ports must be available on your firewall (in passive mode if used).
HSThub Production System Considerations

To access EDI production data from Honda using FTP/s use the following parameters: FTP/s URL - sdataexchangehdc.hondasupplyteam.com Control port 10244 Data port - 10245-10400 These ports must be available on your firewall (in passive mode if used). To access EDI production data from Honda using ANX use the following parameters: ANX IP-166.57.29.247 Control port 10244 Data port With Active Mode FTP, port 10245 is used
With Passive Mode FTP, any port > 1024 may be used These ports must be available on your firewall (in passive mode if used).
April 2008
4-11
HSThub Passwords
HSThub requires that all suppliers use a password to access their mailbox. Access to HSThub will be denied without a valid password. Password Guidelines: Must be changed a minimum of once every 90 days May be changed a maximum of once per day Must be at least six characters (space characters are invalid) Must contain at least one numeric and one alphabetic character May contain any mixture of upper and lower case characters May not be longer than 14 characters May not contain more than three consecutive characters repeated from anywhere within the previous password May not contain more than two identical consecutive characters May not contain the current month and year, in either numeric or character representation May not be reused until after at least 12 unique passwords have been used
If your password expires, you will receive messages similar to the following when you attempt to logon to HSThub: Response: "530-Password has expired, sign on again." Response: "with new password in the following format:" Response: "old password/new password/new password/time of effect" Response: "time of effect defaults to 'I' for 'Immediate'. 'M' denotes 'Next Midday'." Response: 530 Result: "Error" Directions for changing your password are provided later in this chapter. If you have any password related questions please contact Honda at: 937-578-0447 or ham_isg_ec_support@ham.honda.com.
4 - 12
April 2008
Trading Partner Application Design Considerations

For all types of data supported by HSThub there are expectations regarding the timing of data transmissions. Trading partners should be advised to consider the following issues when considering their application design. For assistance with any of the issues below or to request a re-queue of data please contact Honda at: 937-578-0447 or ham_isg_ec_support@ham.honda.com. 1. Trading Partners may request separate mailboxes to support different data types and different Honda sources. a. Trading Partners may access their mailbox and there may not be any data available from Honda. b. Trading Partners may access the mailbox and there may be multiple files of the same document type within their mailbox. Example A supplier may have a HAM and HCM 862 in their mailbox at the same time. c. HSThub will hold your data for 14 days, after 14 days it will be deleted. Suppliers should access their mailbox at least once a day to make sure they receive all of their information. After data is deleted, Trading Partners must contact the Honda Purchasing associate that originally sent the data to request a retransmission. If you extract your data, HSThub will not allow you to extract the same data again. However, HSThub will maintain the data for 14 days from the date it was sent and data can be re-queued by request.
FTP/s or FTP Client Design Considerations

Suggested methods for managing the FTP/s or FTP sessions: Graphical User Interface (GUI) client Allows a user to access data through a graphical interface Command mode Communication script created to send/receive data Both GUI and Command driven sessions: May be used to automate the FTP/s or FTP process May be scheduled on a regular basis May be manually run as desired
Note: Many FTP/s or FTP clients support both manual and automated modes.
April 2008
4-13
Supported FTP commands

The following FTP commands are supported using either FTP/s via the internet or FTP via ANX. Command open user pw ls pwd cd put get quit close bye Description Connect to a FTP site Enter user name (mailbox name) to login Enter password for login List items such as mailbox Display the current settings Change settings Send data Extract data Terminate an FTP session Terminate an FTP session Terminate an FTP session
Note: Specific FTP/s and FTP clients may not support all of the commands listed. They may also support additional commands which are not supported by HSThub.
4 - 14
April 2008
Functional use of FTP commands Logging in to the server

1. Connect to HSThub Using FTP/s via the internet: Use sdataexchangehdc.hondasupplyteam.com as the URL to access the production FTP/s server Use port number 10244 Establish a connection through your FTP/s client (software). Depending on your client, you would likely use one of the following examples (we are using the production EDI port, 10244, in this example): ftp sdataexchangehdc.hondasupplyteam.com 10244 Or ftp open sdataexchangehdc.hondasupplyteam.com 10244 - OR Using FTP via ANX Use 166.57.29.247 to access the production FTP server Use port number 10244 Establish a connection through your FTP client (software). Depending on your FTP client software, you would likely use the following examples (we are using the production EDI port, 10244, in this example): ftp open 166.57.29.247 10244 Result: The connection is established, and you are prompted for a username.
2. The FTP/s or FTP server will prompt for a user name. Your user name is the name of your mailbox on HSThub and will be confirmed during your initial set up by Honda. Type your user name and press enter. Result: A password prompt displays.
April 2008
4-15

3. Type your password and press enter. The initial password will be provided by Honda, but must be changed by the supplier upon accessing HSThub for the first time. To change the password, perform the following steps: Type current password/new password/new password and press enter: Current password - Honda assigned password New password password assigned by supplier Set your new password according to the guidelines provided in this chapter.
Result: If the user and password entries are incorrect, you are allowed two more attempts before the connection closes. If the user and password entries are correct, you will be logged on to HSThub. If you are unable to successfully log on to HSThub please contact Honda at: 937-578-0447 or ham_isg_ec_support@ham.honda.com. Notes: The user command may be useful in an interactive session if the user makes typing mistakes and needs to re-enter the username (mailbox name). The pw (password) command may be useful in an interactive session if the user makes typing mistakes and needs to re-enter the password.
If you fail to modify your password, you will receive messages similar to the following from HSThub: Response: "530-Password has expired, sign on again." Response: "with new password in the following format:" Response: "old password/new password/new password/time of effect" Response: "time of effect defaults to 'I' for 'Immediate'. 'M' denotes 'Next Midday'." Response: 530 Result: "Error" In the response, time of effect is optional and, if omitted, defaults to Immediate. Honda recommends that you omit the time of effect parameter. When you successfully changed your password, you will see messages similar to the following from HSThub: FTP: "USER 12345605DWG" Response: "331-220 Enterprise FTP server (version 5004) ready." "331 User name okay, need password." FTP: "PASS ********" Response: "230-User logged in, proceed." Response: "New Password - SNRF: 04123116088B7P"
4 - 16
April 2008
Sending data to HSThub

The general syntax for the put command is: put filename Where: Filename is the path of the file on your system that you want to send to a Honda mailbox. Ex - C:\Documents and Settings\Desktop\Test.txt Note: The filename may not contain the % or the * characters.
Honda expects all inbound EDI data to be in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Sample Put Command

Put Example: put filename This format of the put command assumes that the data is formatted for EDI. The file may contain one or more EDI documents. If the file contains more than one EDI document, all documents must be for the same receiver and must be the same aprf (ST01) as the first document in the file. Sender, Receiver, and aprf are determined based upon the first document in the file. HSThub messages will be similar to (using a simple FTP client): ftp> put file.txt 200 Command Okay. 150 Opening data connection for transfer. 226-Closing data connection - action successful. sender=118733062 ,receiver=HOAM SOFTAP3 ,aprf=856,snrf=13230001,status=0000 226 ftp: 11434 bytes sent in 0.00Seconds Note: Filename may contain 1 to many EDI documents with various EDI document types.
April 2008
4-17
Extracting Data from your mailbox

The get command extracts files from your mailbox. You can use the get command to extract: a specific, individual file files in a sequential manner (fifo) files from a specific sender files with a specifc aprf (data type) value files from a specific sender with a specifc aprf (data type) value all files at one time
Listing Mailbox contents

HSThub stores all (extracted and not extracted) files for a period of 14 days. To list items in your mailbox, use the ls mb command. Example: ls mb Lists the contents of your mailbox. The display will be similar to the following: FTP: "ls mb" Response: "150 Opening data connection for transfer." Detail: "LocalPort: 3123 / RemotePort: 30250" level=1 Response: "226-Closing data connection - action successful." Response: " List command OK, SNRF: 04123118432230" Response: 226
Detail: "Sender ID St APRF SNRF Service Ref. Size" Detail: "-------------------------------------------------------------------------" Detail: "HOAM SOFTAP3 N 850 ZB122 003313488952405027 1 " Detail: "HOAM SOFTAP3 N 862 QH200 003313488952580414 2 " Detail: "HOAM SOFTAPP N 810 0003 003313488952778699 1 "
Result: "Success" Where: Sender ID St APRF SNRF Service Reference by HSThub Size Senders mailbox name. Status: Y = Data extracted, N= Data not extracted Data type specified when the data was sent Senders file reference Service reference number, a unique value assigned Size of the file (rounded to the next kilobyte)
4 - 18
April 2008
Confirm the get option

HSThub provides the ability to return single or multiple files with a single get command. However all files retrieved with one command are concatenated into a single file. This capability can be useful for EDI. To set (confirm) the get option: cd &s | &m Where: s - used to retrieve the first unextracted file (fifo) m - used to retrieve multiple unextracted files (fifo sequence) with one command (useful for EDI) Each time you log in to your mailbox, the get option is set to single. Once the get option is set, it remains in effect until it is changed again or the session terminates.
Extracting data
The syntax of the get command is get serviceref filename OR get %sender%aprf filename Where: Serviceref is the service reference number from the mailbox listing. Sender is the Honda mailbox name that sent the data. This value is optional. aprf is the application data type. This value is optional. HSThub also supports the * (a.k.a. - wildcard) command for use in extracting all files at one time but the data is returned to a single file at the client.
Sample get Commands

Honda sends all outbound EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment. Get Example 1: get filename Results depend upon the current get option: If the get option is single, this command will retrieve the first unextracted file (FIFO) into filename. If the get option is multiple, this command will retrieve all unextracted files (FIFO) and place them into filename.
April 2008
4-19

Assuming a get option of single, HSThub messages would be similar to: FTP: "TYPE A" Response: "200 TYPE set to A" File: "test.txt" direction="Host->Local" destination="inbox\test.txt" number=1 FTP: "PASV" Response: 227 57,69,19,22,118,44 FTP: "RETR test.txt" Response: "150 Opening data connection for transfer." Detail: "LocalPort: 3133 / RemotePort: 30252" level=1 Response: "226-Closing data connection - action successful." Response: " Extraction command SNRF: 0412311909AYVE" Response: 226 Transfer: kB/sec=2.408 kBytes=0.987 seconds=0.41 Result: "Success"
Get Example 2: get * filename Retrieves all unextracted files (FIFO) and places them into filename (a single file). HSThub messages would be similar to: FTP: "TYPE A" Response: "200 TYPE set to A" File: "Sender ID St APRF SNRF Service Ref. Size" direction="Host->Local" destination="inbox\test.txt" number=1 of 21 FTP: "PASV" Response: 227 57,69,19,22,118,40 FTP: "RETR Sender ID St APRF SNRF Service Ref. Size" Response: "150 Opening data connection for transfer." Detail: "LocalPort: 3150 / RemotePort: 30248" level=1 Response: "226-Closing data connection - action successful." Response: " Extraction command SNRF: 04123119398EYT" Response: 226 Transfer: kB/sec=9.121 kBytes=0.912 seconds=0.1 Result: "Success" File: "----------------------------------------------------------------------------------------------" direction="Host>Local" destination="inbox\test.txt" number=2 of 21 FTP: "PASV" Response: 227 57,69,19,22,118,41 FTP: "RETR ----------------------------------------------------------------------------------------------" Response: "150 Opening data connection for transfer." Detail: "LocalPort: 3151 / RemotePort: 30249" level=1 Response: "226-Closing data connection - action successful." Response: " Extraction command SNRF: 04123119399IZZ" Response: 226 Transfer: kB/sec=110.84 kBytes=1.108 seconds=0.01 Result: "Success" File: "HOAM SOFTAP3 Y 850 ZB122 003313488952405027 1 " direction="Host>Local" destination="inbox\test.txt" number=3 of 21 FTP: "PASV" Response: 227 57,69,19,22,118,42 FTP: "RETR HOAM SOFTAP3 Y 850 ZB122 003313488952405027 1 " Response: "150 Opening data connection for transfer." Detail: "LocalPort: 3152 / RemotePort: 30250" level=1 Response: "226-Closing data connection - action successful."
4 - 20
April 2008

Response: " Extraction command SNRF: 0412311939ABM6" Response: 226 Transfer: kB/sec=0.161 kBytes=0.494 seconds=3.07 Result: "Success" - File: "HOAM SOFTAP3 Y 862 QH200 003313488952580414 2 " direction="Host>Local" destination="inbox\test.txt" number=4 of 21 - FTP: "PASV" - Response: 227 57,69,19,22,118,43 - FTP: "RETR HOAM SOFTAP3 Y 862 QH200 003313488952580414 2" - Response: "150 Opening data connection for transfer." - Detail: "LocalPort: 3153 / RemotePort: 30251" level=1 - Response: "226-Closing data connection - action successful." - Response: " Extraction command SNRF: 0412311939C29C" - Response: 226 - Transfer: kB/sec=0.644 kBytes=1.346 seconds=2.09 - Result: "Success" . Repeats for each file
Result: "Success" "HOAM SOFTAPP N 862 RR77 003313488955182232 3 " direction="Host->Local" destination="inbox\test.txt" number=17 of 21 FTP: "PASV" Response: 227 57,69,19,22,118,46 FTP: "RETR HOAM SOFTAPP N 862 RR77 003313488955182232 3 " Response: "550 Requested action not taken. File unavailable" Detail: "LocalPort: 3166 / RemotePort: 30254" level=1 Result: "Error"
April 2008
4-21
Get Example 3: get serviceref filename Retrieves the file with the specified service reference number into filename. Service reference number for a particular EDI document can be determined from the mailbox listing (ls mb). HSThub messages would be similar to: File: "test.txt" direction="Host->Local" destination="inbox\test.txt" number=1 FTP: "PASV" Response: 227 57,69,19,22,118,44 FTP: "RETR 003313488952580414" Response: "150 Opening data connection for transfer." Detail: "LocalPort: 3139 / RemotePort: 30254" level=1 Response: "226-Closing data connection - action successful." Response: " Extraction command SNRF: 04123119193IZB" Response: 226 Transfer: kB/sec=7.471 kBytes=1.046 seconds=0.14 Result: "Success"
Get Example 4: get %HOAM SOFTAP3 filename Results depend upon the current get option: If the get option is single, this command will retrieve the first unextracted file (FIFO) from the specified sender into filename. If the get option is multiple, this command will retrieve all unextracted files (FIFO) from the specified sender and place them into filename. Double quotes may be required by the FTP client when the parameters contain imbedded spaces. HSThub messages would be similar to: Command: "get "%HOAM SOFTAP3" filename" type="FTP" line=2 File: "%HOAM SOFTAP3" direction="Host->Local" destination="inbox\filename" number=1 FTP: "PASV" Response: 227 57,69,19,22,118,40 FTP: "RETR %HOAM SOFTAP3" Response: "150 Opening data connection for transfer." Detail: "LocalPort: 4659 / RemotePort: 30248" level=1 Response: "226-Closing data connection - action successful." Response: " Extraction command SNRF: 0501301423BD20" Response: 226 Transfer: kB/sec=0.459 kBytes=2.033 seconds=4.43 Result: "Success"
4 - 22
April 2008
Get Example 5: get %%830 filename Results depend upon the current get option: If the get option is single, this command will retrieve the first unextracted file (FIFO) with the specified aprf into filename. If the get option is multiple, this command will retrieve all unextracted files (FIFO) with the specified aprf and place them into filename. HSThub messages would be similar to: File: "%%830" direction="Host->Local" destination="inbox\test.txt" number=1 FTP: "PASV" Response: 227 57,69,19,22,118,38 FTP: "RETR %%830" Response: "150 Opening data connection for transfer." Detail: "LocalPort: 3146 / RemotePort: 30246" level=1 Response: "226-Closing data connection - action successful." Response: " Extraction command SNRF: 04123119362HD7" Response: 226 Transfer: kB/sec=1.562 kBytes=1.703 seconds=1.09 Result: "Success"
Get Example 6: get %HOAM SOFTAP2%862 filename Results depend upon the current get option: If the get option is single, this command will retrieve the first unextracted file (FIFO) from the specified sender with the specified aprf into filename. If the get option is multiple, this command will retrieve all unextracted files (FIFO) from the specified sender with the specified aprf and place them into filename. Double quotes may be required by the FTP client when the parameters contain imbedded spaces. HSThub messages would be similar to: File: "%HOAM SOFTAP2%862" direction="Host->Local" destination="inbox\filename" number=1 FTP: "PASV" Response: 227 57,69,19,22,118,45 FTP: "RETR %HOAM SOFTAP2%862" Response: "150 Opening data connection for transfer." Detail: "LocalPort: 4666 / RemotePort: 30253" level=1 Response: "226-Closing data connection - action successful." Response: " Extraction command SNRF: 050130143636GD" Response: 226 Transfer: kB/sec=8.847 kBytes=1.504 seconds=0.17 Result: "Success" FTP: "QUIT" Response: "221 Service closing control connection." End
April 2008
4-23
Get command No data available

If the get command specified has valid syntax but no data exists in the mailbox to match the criteria you specified, HSThub will return messages similar to: Response: "550 Requested action not taken. File unavailable"
Closing the FTP connection

Any of the following commands may be used: quit close bye
4 - 24
April 2008
Chapter 5 Software Information

Software Information
This document may not be disclosed, in whole or in part, without the prior written consent of Honda of America Mfg., Inc.
April 2008
5-1
Chapter Contents
This chapter contains a list of approved software providers, information concerning changing EDI / bar code software and software design information.
Table of Contents
Software Information............................................................................................................................ 3 EDI/Bar Code Software Providers ...................................................................................................... 3 Becoming an Approved Software Provider......................................................................................... 3 Criteria for Software Provider Approval........................................................................................... 3 Approved Software Providers ............................................................................................................. 3 Changing EDI & Bar Code Software ................................................................................................. 11 Software Design Requirements and Challenges............................................................................. 12 Introduction ....................................................................................................................................... 12 ASN Creation System ....................................................................................................................... 12 Ordering Documents(850, 862) ........................................................................................................ 13 Text Message (864) .......................................................................................................................... 16 Inventory Advice (846) ...................................................................................................................... 16 Transaction/Standards Information [Delta/GPCS, AHM, STAR] ...................................................... 16 Miscellaneous ................................................................................................................................... 17 Delivery History [Delta/GPCS] .......................................................................................................... 18 Lot Traceability [Delta/GPCS] ........................................................................................................... 18 VC2 Packaging Clarification ............................................................................................................. 19
5-2
April 2008
Software Information
EDI/Bar Code Software Providers
Honda does not endorse or recommend specific software providers, but does require that all EDI and Bar Code software be Honda approved to communicate with Honda.
Becoming an Approved Software Provider

Contact the North American Logistics Systems group: HondaEDI@ham.honda.com
Criteria for Software Provider Approval

A detailed, systematic procedure document will be furnished which outlines the testing and approval process. In general, our process checks for performance to the specifications and operational procedures required. It includes linkage between EDI and Bar Code technologies and a demonstrated level of integration of the various specifications.
Approved Software Providers

The following EDI/Bar Code Software Solutions are approved for Honda specifications at versions 4010 (Star) and 4010 (DELTA/GPCS). In alphabetic order, they are: Approved Solution Contact Information David Kalinskii ADS 637 E Big Beaver Rd Application Troy, MI 48083 Development Phone: 248-619-0400 *122 Systems Fax: 586-264-2301 E-ml: david@ads.net Website: www.ads.net Approval Company Software Solution EDI: Advantage Shipping Bar Code: Advantage Shipping ERP/MRP: Advantage QSMRP EDI: AIM Vision EDI Bar Code: AIM Vision ERP/MRP: AIM Vision EDI: EDI*ASSET Bar Code: AIT **ERP/MRP:
Continued on the next page
Solution Name and Revision Advantage QSMRP, Advantage Shipping System, Version 5.1
Product Description (provided by Approval Company) Shipping, ERP/MRP/CRP, and financial applications on Windows and Linux platforms. Easy to use comprehensive EDI integrated with Bar Code scanning and shipping. Several prices and configurations are offered. Shipping System interfaces with a variety of ERP systems in addition to ours.
AIM Computer Solutions, Inc.
Ms. Teresa D'Angelo 34673 Bennett Drive Fraser, MI 48026 Phone: 586-439-0300 Fax: 586-439-0321 E-ml: sales@aimcom.com Website: www.aimcom.com Dan Craig-Paul 1423 Franklin Street Detroit, MI 48207 Phone: 866-248-5989 Fax: 313-961-7845 E-ml: dan@aitsystems.com Website: www.aitsystems.com
AIM Vision Version 9C Microsoft Dynamics integration now available
Integrated customer EDI, Customer shipping labels Scheduling /MRP/CRP and supplier EDI. Barcoded solutions for Shipping, Receiving, Production and Inventory Control. SQL or Progress based client/server package is designed for Windows 95/98/XP, NT/2000, UNIX servers. All Windows Versions; Auto Sequencing Reports; Touch Screen Operation; Single Field Scan; Voice Verification; Active Sync Interface; Pocket PC; File Export Ability.
AIT Systems Inc.
AIT-HONDA, Version 2.3 solution
April 2008
5-3
Approved Software Providers (continued)

Approval Company Approved Solution Contact Information Joe Drouillard 40928 Kingsley Ln Novi, MI 48377 Phone: 248-894-7093 Fax: 248-669-2252 Email: jad@avenuesystems.com Website: www.avenuesystems.com Russ White 1234 12th Ave. Grafton, WI 53024 Phone: 262-387-1140 Fax: 262-387-1150 E-ml: sales@Base2.com Website: www.base2.com Software Solution EDI: iConnect, Inc. Bar Code: ScanToVerify ERP/MRP: Mfg/Pro by QAD, Any other EDI: Base2 Corporation Bar Code: Base2 Corporation **ERP/MRP: Most ERP/MRP systems, including Exact Macola and Visual Mfg. Breva Systems, S.A. de C.V. Gerardo Zeron Insurgentes Sur, 1809 201 Col. Guadalupe Inn Mexico, D.F. 01020 Phone: (52-55) 5661-1150 Fax : x.102 e-mail: gerardo.zeron@breva.biz Website: www.breva.biz EDI: Inovis-Trusted Link for Windows Bar Code: Visual-Arms 1.7.2 by Edibar ERP/MRP: Integration with SAP, Oracle, MAPICS, BPICS, Infor EDI: Total EDI for QAD Bar Code: Eagle Consulting & Development Corps RF Express for MFG/PRO ERP/MRP: MFG/PRO
Avenue Systems
Solution Name and Revision ScanToVerify 3.0 (demand Mgt and Wireless Shipping modules) iExchangeweb (EDI) Base2 AutoLine Version 5 or higher
Product Description (provided by Approval Company) Complete shipping, labeling, scanning and EDI. Successfully interfaced with QADs Mfg/Pro. Uses iConnect as a single provider of EDI mapping and VAN services through a seamless Web interface. (www.iconnectcorp.com) Complete EDI & release management solution for automotive and retail. No enduser mapping. Automatically translates and prints documents; integrated bar code printing; batch or RF scanning; supply chain; lineside labeling; ERP/VAN independent.
Base2 Corporation
Breva Honda Suppliers EDI Integration
Honda Approved Software provider with Edibar Visual ARMS, Sterling Commerce, CLEO and Inovis products for Mexico, USA and South American suppliers to the Automotive Industry. We provide outsourcing, training, installation and IT Value-Added consulting services.
Ecbridges Inc.
Terry Magovern 3470 Buskirk Avenue Pleasant Hill, CA 94523 Phone: 925-771-5516 Main: 925-771-5500 Fax: 925-771-5501 E-ml: tmagovern@ecbridges.com Website: ecbridges.com
Total-EDI for MFG/PRO
Total EDI is a fully integrated complete EDI solution for QADs MFG-PRO version 7 through EB for UNIX or Windows platforms supporting many types of communications. Ecbridges performs EDI mapping & communications for most of the automotive world.
5-4
April 2008

Approval Company Approved Solution Contact Information Wayne Metcalfe 51520 Regency Center Dr. Macomb, MI 48042 Phone: 800-633-3210 Fax: 586-677-8801 E-ml: wayne_metcalfe@edibar.com Website: www.edibar.com Software Solution EDI: Sterling Commerce Gentran: -Director for Windows -Server NT Bar Code: Edibar -RMS **ERP/MRP: Glovia.com, JD Edwards, Macola, and others Edict Systems Incorporated 2680 Indian Ripple Rd. Dayton, OH 45440 Phone: 1-800-443-3428 Fax: 937-429-4309 solutions@edictsystems.com www.webedi.com www.automotiveEC.com EDI: WebEDI.com AutomotiveEC .com and EDI: Edict Systems Hosted Data Translation (HDT) Bar Code: Edibar-Visual Arms EDI: Genzlinger Bar Code: Genzlinger ERP/MRP: Genzlinger WebEDI.com Hondas Alternative EDI System Solution Name and Revision Visual ARMS Version 1.7.2 or EDIbar-RMS Product Description (provided by Approval Company) PC, LAN and WAN based release management solutions designed to meet all automotive shipping requirements. Automatic and lineside printing capabilities provide error free shipping labels. Real-time RF and batch scanning, as well as full ERP integration capabilities. Simple/efficient hosted supply chain management solution specifically for small/medium size suppliers as an alternative to softwarebased electronic commerce applications. EDI module supports all industry electronic transactions including forecasting, ordering, shipping, ASNs and bar code labeling. Operates on Windows, UNIX PCs. Singleuser or multi-user EDI system, integrates bar code printing and scanning. Integrated with Genzlinger, repetitive ERP software. Custom ERP interfaces available. glovia.com V-ARMS is a fully integrated ERP/automotive shipping solution with EDI. ASN, bar coding and RF scanning functionality. The solution also includes lot and serial traceability .
Edibar Systems, Inc. (formerly Bar Code Solutions)
Genzlinger Associates Inc.
Brent Genzlinger 5700 Crooks Road Suite 212 Troy, MI 48098 Phone: 248-879-7070 Fax: 248-879-6352 E-ml: brent@genzlinger.com Website: www.genzlinger.com
Release/ Shipment Communications Version 7.0
Glovia International Inc.
1940 East Mariposa Avenue El Segundo, CA 90245-3457 Toll Free: 800-713-1450 Phone: 310-563-7000 Fax: 310-563-7300 Email: usa@glovia.com Web: www.glovia.com
Glovia.com VARMS
Glovia.com (version 7.1) V-ARMS (version 1.7.4) or Edibar-RMS
April 2008
5-5

Approval Company Approved Solution Contact Information Eric Swanson Chief Technology Officer iConnect , Inc. 24 Frank Lloyd Wright Dr PO Box 452 Ann Arbor, Michigan 48106 (v) 734.930.4269 (f) 734.930.4261 eswanson@iconnect-corp.com Infor Global Solutions 41780 Six Mile Road Northville, MI 48167 Phone: 248-697-3200 Fax: 248-697-3201 Sales: salesmkt.fax@infor.com Website: www.infor.com Infor Global Solutions 3223 Kraft Ave. Grand Rapids, MI 49512 Phone: 616-942-7444 Fax: 616-942-8167 Sales: salesmkt.fax@infor.com Website: www.infor.com Software Solution EDI: iExchangeWeb by iConnect Bar Code: Visual-Arms 1.7.2 by Edibar Solution Name and Revision iExchangeWeb Product Description (provided by Approval Company) iExchangeWeb is an internet-based, fully hosted solution that offers simple, cost-effective answers for communicating business-critical information with global partners securely and efficiently regardless of data format, platform, language, complexity or application. AutoRelease provides a fully integrated EDI, release accounting, shipping control and invoicing system.
iConnect Inc.
INFOR Global Solutions
EDI: Infor Global Solutions, Inc. Bar Code: Infor Global Solutions, Inc. EDI: Infor Global Solutions, Inc. Bar Code: Infor Global Solutions, Inc.
INFOR Global Solutions
Infor AutoRelease w/ AutoScan ARS Version 12.25 AutoScan Version 2.2 VendorRelease Infor ACManager/ Trans4M Version 8.24
ACManager/Trans4M is a product within Infors Customer Relationship Management (CRM) solution created or automotive suppliers. Its a fully automated front-end communications, EDI order processing and shipping solution.
Inovis, Inc.
John Tucker 11720 AmberPark Dr. Alpharetta, GA 30004 Phone: 404-467-3817 Fax: 404-467-3817 Email: john.tucker@inovis.comWebsite: www.inovis.com
EDI: Trusted Link, Windows Edition 6.1.3 Bar Code: Visual-Arms 1.7.2 by Edibar **ERP/MRP: EDI: IQ EDI Bar Code: IQ WMS ERP/MRP: EnterpriseIQ
Honda Integration Kit v. 6.1
TrustedLink Windows provides everything needed to run a sophisticated e-commerce program on your desktop. Use the Honda Integration Kit to meet the requirements for handling Delta, GPCS, VC2, and Star transactions.
IQMS
Sales Department 2231 Wisteria Lane Paso Robles, CA 93446 Toll Free: 1-866-FOR-ERP2 Fax: 805-227-1120 Email: sales@iqms.com Website: www.iqms.com
EnterpriseIQ
EnterpriseIQ seamlessly integrates EDI and bar coding/WMS into a single-source, single database ERP system that also manages quality systems, financials, manufacturing and distribution. Ideal for automotive manufacturers with multiple plants or business units.
Continued on the next pa
5-6
April 2008

Approval Company Approved Solution Contact Information Software Solution Solution Name and Revision EDI-Link v. 5.4 C.Core v.7.0 Product Description (provided by Approval Company)
Lexon Corporation
Chris Minnie 250 East Wilson Bridge Rd Suite 230 Columbus, OH 43085 Phone: 614-540-9300 Fax: 614-417-9300 E-ml: ctminnie@mail.lexoncorp. com Website: www.lexoncorp.com
EDI: Gentran X Bar Code: Label Matrix **ERP/MRP:
Deployment: Stand alone; Multi-user (WAN/WEB); Batch/RF scanning. Functionality: Integrated EDI & barcode printing; Shipping functions; Line-side labeling & verification; Managing small-lots; Sequencing; Inventory Management, Product Traceability. Integration: Data Repository & Flat file.
Peartree Software Inc.
Glenn Lyons - Manager, EDI 550 Parkside Dr. Unit 8A Waterloo, ON N2L 5V4 Phone: 519-743-2444 Fax: 519-743-3656 E-ml: gml@ptsoft.com, swh@ptsoft.com Website: www.ptsoft.com
EDI: Peartree EDI Bar Code: Peartree BAR ERP/MRP: Peartree MMS (Manufacturing Manage-ment Systems) EDI: Plexus Online EDI & Release Accounting Bar Code: Plexus Online Flexible Barcoding ERP/MRP: Plexus Online
Peartree MMS Software
Stand alone or fully integrated UNIX or Windows O/S multi-user solution. Supports X12 or EDIFACT; dialup or ANX connections. Peartree EDI is one of the modules that make up the Peartree ERP solution.
Plexus Systems
Mark Symonds 1731 Harmon Rd. Auburn Hills, MI 48326 Phone: 248-391-8001 888-454-PLEX Fax: 248-393-1799 E-ml: info@plex.com Website: www.plex.com
Plexus Online
Full-featured ERP solution, integrated EDI, Release Accounting, Barcoding, Quality and more. EDI/Release Acctg/Barcoding can be purchased separately and integrated with existing ERP solutions. Many other trading partners and transactions supported.
April 2008
5-7

Approval Company PMC America, Inc Approved Solution Contact Information Brian Jolley One Towne Square, Suite 1580 Southfield, MI 48076 Phone: 248-359-3000 Fax: 248-359-3010 E-ml: brian.jolley@pmcamerica.com Website: www.pmcamerica.com Software Solution EDI: pmc America Bar Code: pmc America (SAP) ERP/MRP: all SAP Business Suite versions (including automotive solution) EDI: SmartEDI Bar Code: SmartEDI **ERP/MRP: Microsoft Dynamics NAV Solution Name and Revision pmcConnect 3.2 Product Description (provided by Approval Company) pmcConnect is a complete SAP automotive eValue Chain implementation, covering EDI, Barcode Labeling, Business Process Automation and User Notification. The solution addresses all elements of true business process integration.
Productive Systems, Inc.
Ron Oates 3974 Brown Park Dr., Suite E Hilliard, OH 43026 Phone: 614-777-8020 *42 Fax: 614-777-0278 E-ml: ROates@ProductiveSyst ems.com Website: www.ProductiveSystems. com Ann Holwey 10000 Midlantic Dr. Suite 1000 East Mt. Laurel, NJ 08054 Phone:317-536-2464 Fax: 614-573-6376 E-ml: aoh@qad.com Website: www.qad.com
SmartEDI 4.2.39
Windows/NT based, multiuser. Automatic processing of EDI with minimal data entry, Virtually a point and click system. Mappings are built-in, no setup required.
QAD Inc.
EDI: QAD's EDI ECommerce with Trinarys EDI Windows Bar Code: Eagle Consulting & Development Corp's RF Express for MFG/PRO. ERP/MRP: QAD MFG/PRO
EDI ECommerce MFG/PRO Vsn 9.0 and above
This totally integrated solution runs on the NT/2000, Unix, Linux platforms. EDI Windows is used to communicate/translate EDI data while EDI Ecommerce performs application integration to Honda specifications in conjunction with RF Express bar coding.
5-8
April 2008

Approval Company Approved Solution Contact Information Ann Holwey 10000 Midlantic Dr. Suite 1000 East Mt. Laurel, NJ 08054 Phone:317-536-2464 Fax: 614-573-6376 E-ml: aoh@qad.com Website: www.qad.com Software Solution EDI: QAD's EDI ECommerce with Sterling's Gentran Bar Code: Eagle Consulting & Development Corp's RF Express for MFG/PRO. ERP/MRP: QAD MFG/PRO EDI: iCARaS Bar Code: iCARaS **ERP/MRP: Solution Name and Revision EDI ECommerce MFG/PRO Vsn 9.0 and above Product Description (provided by Approval Company) This totally integrated solution runs on the NT/2000, Unix, Linux platforms. Gentran is used to communicate/translate EDI data while EDI ECommerce performs the application integration to Honda specifications in conjunction with RF Express bar coding.
QAD Inc.
Radley Corporation
Will Soutar 23077 Greenfield Suite 440 Southfield, MI 48075 Phone: 248-559-6858 *114 Fax: 248-559-6822 E-ml: wsoutar@radley.com Website: www.radley.com
iCARaS V7.0
Complete turnkey e-commerce solution with integrated scanning/labeling and guaranteed trading partner compliance. iCaras supports 250+ trading partners EDI/XML/Proprietary data exchange programs. Standardized import/export gateways ensure seamless integration with any ERP application. Proven in over 3,000 global automotive projects. Seeburger fully integrates all B2B/EDI processes with backend ERP/MRP systems to meet the specific trading requirements of every OEM and distribute data through the entire supply chain.
Seeburger
Aaron Geiger 5 Concourse Parkway Atlanta, GA 30328 Phone: 770-604-3888 Fax: 770-604-3885 E-ml: a.geiger@seeburge.com Website: www.seeburger.com
EDI: Seeburger Business Integration Server Bar Code: Edibar ERP/MRP: All ERP systems including all versions of SAP, QAD, Baan, etc EDI: Inovis-Trusted Link for Windows Bar Code: iVP ERP/MRP: iVP v. 5.2
Seeburger Business Integration Server
Solarsoft Business Systems
Andrew Robling 45 Vogell Road, Ste 700 Richmond Hill, ON L4B 3P6 Phone: 905-224-2222 Fax: 905-224-2221 E-ml: andrew.robling@solarsoft. com Website: www. solarsoft. com
Solarsoft iVP v. 5.2
Solarsoft Business Systems provides fully integrated ERP for automotive suppliers. Solarsoft integrated automotive functionality, including EDI/Release Accounting, promotes resource and efficiency optimization and increased customer satisfaction.
April 2008
5-9

Approval Company Approved Solution Contact Information Sales Department 30553 Wixom Road Suite 100 Wixom, MI 48393 Phone:248-926-6777 Toll free: 800-377-9120 Fax: 248-926-8247 E-ml: sales@trinary.com Website: www.trinary.com Software Solution EDI: EDX & EDI WINDOWS Bar Code: Eagle Consulting & Development Corp's RF Express for MFG/PRO. ERP/MRP: MFG/PRO Solution Name and Revision Trinary Systems: EDX & EDI Windows 5.2 & higher MFG/PRO BPI B7.1 & higher Eagle: RF Express for MFG/PRO Version 8.5x through Current Release QAD: MFG/PRO 8.5d & higher Trinary Systems: EDX & EDI Windows 5.2 & higher MFG/PRO BPI B7.1 & higher Freedom: ERP Bridge QAD: MFG/PRO 8.5d & higher Product Description (provided by Approval Company) Trinary provides complete EDI translation with full integration to MFG/PRO and RF Express on NT and Unix Client/Server platforms.
Trinary Systems, Inc.
Trinary Systems, Inc.
Sales Department 30553 Wixom Road Suite 100 Wixom, MI 48393 Phone:248-926-6777 Toll free: 800-377-9120 Fax: 248-926-8247 E-ml: sales@trinary.com Website: www.trinary.com
EDI: EDX & EDI WINDOWS Bar Code: Freedom Technologies ERP Bridge ERP/MRP: MFG/PRO
Trinary provides complete EDI translation with full integration to MFG/PRO and ERP Bridge on NT and Unix Client/Server platforms. Freedom Technologies provides a complete labeling and shop floor system including production error proofing.
*Approval must be at this level or higher. Revision levels will only be updated in this manual on an as needed basis. **May be able to map data outbound to your ERP/MRP system. Please contact approved company for detailed information.
5 - 10
April 2008
Changing EDI & Bar Code Software

If your company is 1) planning on changing from an existing approved EDI software installation to a new software solution (whether standard or hybrid) or 2) is changing MRP/ERP systems, the following guidelines apply: Do not destroy the capability to use the EDI software on which your facility was previously approved. Immediately contact Honda North American Logistics at: HondaEDI@ham.honda.com
The Honda North American Logistics Systems Group contact will: Confirm that the new EDI solution you are considering is Honda approved. Develop a test plan (if necessary.) Assist in the development of a project plan (if necessary.) Provide test information, data and feedback (if necessary.)
April 2008
5 - 11
Software Design Requirements and Challenges

Introduction
The following items have proven difficult for suppliers and software providers during approval testing. This list highlights potential challenges suppliers or software providers considering Hondas custom approval process will need to address. This is not meant as an all-inclusive list. If you are a Honda supplier considering EDI approval using a custom path, or a software provider considering approval, please review this list and make sure your firm has the capability, workforce, and time to meet these expectations.
ASN Creation System

1. Bar code integration with respect to ASN creation. [Delta/GPCS & STAR] The only hand-keyed items should be trailer number and shipment time (in some cases). Other data should be populated from the ordering documents. 2. ASN Creation from Ordering Requirements. [Delta/GPCS & STAR] The goal is to minimize hand keying. Provide for the proper edits. 3. Reconciliation: [Delta/GPCS] 862/850 to pick list & pick list to ASN. Over multiple trucks (if applicable). Over and under ship notification (should have override). Design change level difference notification (should have override). Unknown part number notification (terminal). Unknown Ship-To location (terminal). Order quantity linked to an order number (should have override). When allowing for adjustments to internal tables or data, caution should be taken so that the operator cannot accept automatic updates without warning and/or review. 4. Small Lot/Delivery Batch: [Delta/GPCS] Items with a common Batch Number may need to be packed together. These items should be controlled outside the staging area. Scanning Reconciliation to Batch Requirements to insure proper configuration of the container/pack. Batch requirements quantities may need to be allocated across multiple containers (some quantities may need to be split to allow for proper maximum container quantity). Proper representation of Returnable Container Count. (Type listed once for multiple part numbers within a container). Due to changes in Honda software known as Delivery Batch, a supplier may receive multiple requirements (JIT quantities) where all detail is identical except the sequence number.
5 - 12
April 2008
5. Understanding the Bar Code Requirements: [Delta/GPCS& STAR] Delta/GPCS - Container, Master, Mixed, Quick Receive and Delivery Batch Labels. STAR - Container, Master, Mixed Smart label/License Plate concept Logical linking of master/mixed label to container labels. Container is the pallet. Honda allows a supplier to ship without a Master label on a pallet, when that pallet has one part and serves the purpose of a container. The ASN will use the container serial identification number at the tare and item level. (See Ch. 9). Under Special Circumstances, Honda may allow a supplier to ship with one Master/Mixed and Quick Receive Label where the entire trailer is the pallet which contains single racks or large containers. (See Ch. 9) 6. Understanding Pick and Load Sheet: [Delta/GPCS] Review these requirements as applicable for sequencing and batch container building.
7. Understanding the Master Packing List requirements: [Delta/ GPCS, STAR, AHM] Different specification for STAR vs. Delta/GPCS vs. AHM. Understanding when to create a new ASN [Delta/GPCS] Any changes to the top 15 items on a MPL should result in a new ASN. Insure Proper Returnable Container Counts on bottom of MPL.
8. For Understanding Returnable Container count requirements: [Delta/GPCS] A container with multiple parts would count as one type. 9. Fifteen minute System reminder/call back for ASN Validation [Delta/GPCS] System generated reminder/call-back for the 824 (after ASN generation)
10. For shipments crossing borders (US / Canada / Mexico) the relationship between the ASN# and the BOL# must be one to one. Supplier software must have the capability to create one ASN for each BOL#, regardless of how many ASNs are on a truck.
Ordering Documents(850, 862)

11. Understanding Hondas PO and Ship Schedule number: [Delta/GPCS] The Ship Schedule numbers are sent in different elements, GPCS vs. Delta. That the ship schedule number changes daily for Delta Only. What ship schedule number to use when shipping. GPCS Ship Schedule Numbers are Fixed Orders across Multiple Part Numbers and will remain until order is fulfilled or until cancelled. Delta Ship Schedule Numbers are Ship Authorization Numbers assigned to each part number and will change on each subsequent schedule. What 862 should be used when a new one arrives prior to shipment. Suppliers are authorized to stick with current staged requirements, but should review new schedule for immediate demands. Any new demands should be handled as additional requirements Multiple 850s or 862s may be sent under the same interchange envelope.
April 2008
5 - 13

12. Understanding how the Design Change (DC) Level works: [Delta/GPCS] BE vs. EC. BE Must ship this level. EC Latest revision on our books, ship this or newer. Space sensitive 6-digit field. The current DC level is not necessarily imbedded in the part number do NOT try to use this for any programming logic. A D/C level segment is used for running level design tracking and must be present. Suppliers must ship to the most current D/C level. Most current level may not be sent on an 862. Supplier will receive via fax/email/mail the latest D/C level and will send this change in the ASN when applicable. The 862 will be updated at that time (Delta). This may be done manually with GPCS. Supplier must have the ability to change the D/C level manually if the current level is not available on ordering documents.
13. Understanding Hondas replacement logic: [Delta/GPCS] Hondas use of the Transaction Set Purpose Code Review the difference between 830, 850 and 862 Replacement parameters. Understand that for 850s, the line item level PO1 01 is used for replacement. Replacement will be based on match of all digits within PO1 01.
14. Understanding Hondas order types: [Delta/GPCS] Daily Summary Bulk Ship Requirements. May have requirements multiple times per day. Sequence in order based on Honda lot requirements. Many variations represented on 862 based on following items: Sequence Number, Honda Lot Number, and Batch Number. (REF*LT,BT and JS) Honda Lot Number will be returned on ASN if provided on 862.
15. Delivery Batch/Small lot orders: [Delta/GPCS] Batch number is used to identify items that need to be packaged together. Identified by a REF*BT (batch number) within the JIT loop. Batch number is not returned on the ASN, MPL. Batch number should be on Delivery Batch Label. See Pick and Load Sheet Requirements for proper display to shipping associates.
16. Sequence orders: [Delta/GPCS & STAR] Identifies the vehicles by lot that Honda will produce on the production line. Honda Lot Number will be returned on the ASN, MPL, and Quick Receive Label. Sequence Number indicates how a part will be loaded in a container and/or trailer. Sequence number is not returned on the ASN, MPL or any bar code label Identified by a REF*JS (sequence number) within the 862 JIT segment. See Pick and Load Sheet Requirements for proper display to shipping associates. Do not use the sequence number as a control number, as it may not be unique between different parts and may repeat in subsequent 862s.
5 - 14
April 2008
17. Immediate demand: [Delta and GPCS] Immediate Demand requirements are transmitted on an 862/850. Ship the requirement on the next available truck or as required by Honda Planner. Should not change current staged material to include on current truck. Separate ASN may be desired. Identified by a Time of 0001 in Delta. Time assigned to desired trailer window in GPCS with new but separate Ship Schedule Number.
18. Exception Orders: [Delta/GPCS] Exception orders in GPCS will be on an independent 850 PO. Exception orders for Delta will be in the form of a phone call with the Honda Planner requesting a delivery of additional quantity of a particular part, or the Honda Planner may reissue the order with adjusted quantities. Systems must be able to generate an ASN from a Ship Schedule Number linked to this particular part. This number can be from any schedule within 30 days. Do not subtract quantity against future orders in shipping history. Note - all AHM orders are transmitted via the 850.
19. Backorder demand: [GPCS] Honda plants may or may not send backorders on 862s Suppliers must maintain their own backorder Used on daily summary and multi-summary Time of 0001 Ship the requirement on the next available truck or as required by Honda Planner. Should not change current staged material to include on current truck. Separate ASN may be desired. Suppliers should review their open backorders with their planner before shipping. Take care not to drop demand from requirements between a previous 862 and its replacement. Use the DTM of the document if necessary.
20. Independent demand: [Delta/GPCS] Sequence orders only. Lot numbers are indicated by 9s. Used for parts that are not linked to vehicle production (i.e. spare parts).
21. Frozen Periods: [Delta/GPCS] Frozen Periods are assigned by the Honda Planner for a specific length of time and is determined by the suppliers transit time and staging requirements. Frozen Periods are not indicated on any EDI document Although Frozen Periods are assigned the Honda Planner can override these requirements at any time. The Frozen Period includes the current date in its overall application (i.e. a 2 day frozen would apply to requirements for today and tomorrow).
April 2008
5 - 15
Text Message (864)

22. Text Message: [Delta/GPCS] Hybrid At a minimum the supplier must: Indicate there is a text message on the Honda outbound document (830, 846, 850, and 862). Print the 864-text message with the control number tying the 864 to the Honda outbound document. Software Provider At a minimum the software provider must: Print the 864 text message on the Honda outbound hard copy report OR print the 864 text message on the pick list (Whatever is most logical for their system /users.). Ideally both hybrids and software providers would provide the message: Printing on screen (electronically) of the corresponding Honda outbound document. Printing on the hard copy of the corresponding Honda outbound document. Printing on the pick list (where applicable).
Inventory Advice (846)

23. 24. Understanding the 846 (CC, RA, IA). [Delta/GPCS] Data turn-around: [Delta/GPCS] Minimize hand keying. Logic to meet Hondas edits.
Transaction/Standards Information [Delta/GPCS, AHM, STAR]

25. Must do both STAR 4010 and Delta/GPCS 4010: Must have the capability to distinguish between STAR and Delta/GPCS/AHM orders and return the corresponding STAR/Delta/GPCS/AHM documents (846, 856, and 997). 26. Differences between Star and Delta/GPCS 830s and 850s: [Delta/GPCS and Star] The Star 830 is an Ordering Document (Material Release) while Delta/GPCS 830 is a Forecast The Star 850 is used primarily as a Forecast while Delta/GPCS is used as a Special Order. Star 850 can also be used as a Special Order for DSPS or New Model Orders
5 - 16
April 2008

27. Out of compliance specifications STAR 830: STAR 850: NTE segment included but not in ANSI DTM & SCH segments out of position NTE segment included but not in ANSI DTM & TD5 segments out of position
Miscellaneous
28. HL structure logic in the ASN: [Delta/GPCS & STAR] Honda ASNs require both a Tare and an Item level. Must use an item level LIN segment for each part number/container in the ASN summarize). (cannot
29. Transaction Set Control Number (ST02) across all Honda bound documents must be unique for 18 months. [Delta/GPCS]
30.
Zero quantities: [Delta/GPCS & STAR] (Delta) When a change is made to zero a requirement inside the Frozen Period, the zero will be sent with a time of 0001 for the applicable Delivery Date. The requirement will not coincide with the proper dates and times. (GPCS) When a change is made to zero requirements for either inside or outside the Frozen Period, the zero will be sent at the appropriate date, time and order number.
31.
Size of the Documents: [Delta/GPCS & STAR] Some documents like the 820, 830 and 862 can be very large. There should be no size constraints placed on pulling or printing the documents.
April 2008
5 - 17
Delivery History [Delta/GPCS]

32. Shipping History should not interfere with Honda Requirements: Honda does not use Cums or ASNs to relieve delivery requirements. Shipping History should not prevent GPCS Backorders or Delta Immediate Demand from being displayed. For Delta, Suppliers should be able to use past, present or future 862 requirements to create an ASN and post additional quantities for delivery based on phone calls from Honda Planners. These Additional Quantities should not subtract from future requirements. For GPCS, multiple parts are tied to a single Ship Schedule Number (Order Number) with a specific Delivery Time. Each Order number will repeat on subsequent schedules until the order is zeroed, replaced, or removed after the quantity is received. GPCS Order Replacement:
Suppliers should not keep more than 18 months of ship history active, as Honda cannot guarantee that a control number will not repeat after 18 months from initial issue. When Orders are fulfilled, subsequent resends of the same order number and requirements should not cause the supplier to post that requirement as unfulfilled. Creation of a Net Change report is usually best (not required) for handling the above situations. Before posting 862 requirements for shipping the following parameters should be considered: Delta: Part Number, Delivery Date/Time, Quantity, Honda Lot and Batch Number. GPCS: Part Number, Delivery Date/Time, Ship Schedule Number, Honda Lot and Batch Number. Do not use these to determine Replacement Logic for the 862 document itself.
Lot Traceability [Delta/GPCS]

33. The supplier will be required to maintain their own control of production through lot/date of manufacture control. Suppliers must review the Supplier Quality Manual for proper application of Lot Control Procedures. At a minimum the supplier must provide their lot control/date of manufacture number in the proper field of the ASN (Chapter 19) and on the Container Label (Chapter 9). The supplier must be able to link each Honda Container Label Serial Number to a supplier manufacture lot number/date of manufacture. This must be accomplished either manually or systematically. The supplier must be able to demonstrate the ability to provide to Honda the serial numbers to all containers tied to a given supplier lot number if Honda provides either a supplier lot number or a single container serial number.
5 - 18
April 2008
VC2 Packaging Clarification

Background: Numerous questions have arisen from both software providers and suppliers with regard to Hondas VC2 Delivery Batch Requirements. Purpose: To clarify Delivery Batch container and sequence issues related to VC2, thus insuring all designers/developers have a clear understanding of Hondas requirements. Issue/Discussion: 1. Changes in Batch Requirements Issue: Suppliers must have some method of identifying and correcting changes in Delivery Batch requirements. Batches will be fixed for approximately 2 weeks for Delta and GPCS. However, it should be noted that the Honda planner might change these requirements manually at any time. This will be on an exception basis only and will not be considered normal business practice. Suppliers should have some way of identifying changes within a Delivery Batch requirement. Example: use direct comparison or a net change report. 2. Lot Number Duplication Issue: Lot Numbers may appear multiple times. A Batch can have the same Lot Number for a particular part or multiple parts. Example: Part X could apply to Lot 1234 with two or more requirements (quantities of 10, 15, etc.) or Part X and Y could both be for Lot 1234. 3. Sequence Number Duplication Issue: Sequence Numbers within a date can duplicate. Sequence Numbers could duplicate within a given date range. This would normally happen to a supplier that was trailer-sequenced dependant with left and right variation. Example: Part X and Y belong to Lot 1234 which both have Sequence Number of 1 for a quantity of 60. 4. Trailer Sequence versus Container Sequence Issue: The Sequence Number used at time of container build should not be reconciled against the Sequence Number used at time of trailer build if different 862 schedules are utilized. When Sequence Numbers are used for creating Delivery Batch containers or Trailer Sequence it is the load order that is important, as the Sequence Number may change daily. Because the Delivery Batch Container may be created in advance of delivery, caution should be used during trailer verification not to reconcile the Delivery Batch Container against the Sequence Numbers (REF*JS) from which it was created.
April 2008
5 - 19

5. Order Batch Variation Issue: A Batch may consist of parts with various standard pack types and/or quantities. Honda may send the same Batch number covering not only one Part Family, but also multiple Part Families. (A Part Family is one where the base five digits of the part number are identical. Normally the part families would be packaged in the same container). The result is that a supplier may receive variations in requirements that have different package types, sizes or both. Example: A supplier receives Batch 1234 with Part X1, X2, Y1 and Y2, where only the X parts can be packaged in a C type container, while the Y parts can be packaged in a D type container. Due to these variations, software providers may want to have some kind of data identifier within their parts table database to allow the supplier to identify those parts that can be packed together as a group.
6. Part Requirement Quantities may be Distributed over Multiple Containers
Issue: The Software Developer needs to insure they break up part quantities issued on an 862 to correctly load a Delivery Batch Container. Parts that can be packaged together will have the same Batch Number and usually come from the same part family. The Part Quantities issued on the 862 may not distribute these quantities evenly to match the desired container package size, thus the software developer will need to consider the package type and size to provide the suppliers shipping associates accurate packing information. This will need to be done to accurately print container labels. Remember the parts will be packed according to sequence number. 7. Supplier Container Variation Issue: Software must provide flexibility for suppliers who have abnormal packaging requirements. The Developer should allow for unusual container variation where parts from different part families may be mixed in a common container. This is rare, but can happen for items like combining Left/Right Parts or Kit Packs (multiple parts that apply to one process). Example: The 862 may indicate a requirement of X1, X2 and Y1, Y2 (based on sequence sort), however the supplier is required to pack X1, Y1 and X2, Y2. The potential problem here is how to handle the Batch Label since it is tied directly to a specific lot of the first part in the sequence of that container. To handle this the Software Developer has two options (or combination thereof): 1. If the Software Provider intends to pre-print all labels (Container and Batch) according to requirements and issue them with the Pick and Load Sheet, the software will need to provide an option for the supplier to designate what parts can be combined into a container before the label printing. This will allow the proper match of the Lot Number to items within a container.
5 - 20
April 2008

2. If the above option is not feasible, then the Software Provider can issue the container labels along with the Pick and Load Sheet according to requirements. The supplier would apply the labels according to their required package configuration, and then scan the Container Labels for each container to create the Batch Label. This is similar to a pallet build process.
8.
Sequence Verification Issue: Scanning to verify sequencing is not mandatory. The requirements indicate that software should be able to verify the correct order and requirements within a container. This does not mean that software has to scan from part to part. The software should provide the supplier the best information possible to correctly load the container. Note: Reconciliation to requirements is still required.
9.
Tracking Information Issue: Software must provide a method to maintain quality tracking information. The requirements indicate that if a supplier is re-packing from one or more container to create a Delivery Batch, then the new Container Serial Number must provide a link to the original Container Serial Number. The intent here is to provide the supplier the method of tracking the new Container Serial Numbers to the original date or supplier lot of manufacturing. This does not need to happen through scanning. Remember that the new Delivery Batch Container may have parts that originate from multiple containers. In addition, you must pass any IPP Tag information from one container to the next. This requirement is a lead-in to future requirements.
10.
Multiple Batches on a Container Issue: Container Sizes Greater than 60 may be packed with parts from multiple Batch Numbers. For container sizes greater than 60, there may be two or more Batch Number Requirements packed on the same container. For Delivery Batch combinations there would be more than one Delivery Batch Label required. Correct container count is expected when using this method.
April 2008
5 - 21

11. Missing Parts Issue: How do suppliers proceed when they are not able to provide parts? Honda expects that all containers that are created with the mixed Delivery Batch process have priority with regards to part order fulfillment. If circumstances arise, where parts cannot be filled within a Delivery Batch then the spaces within that container will be left blank. Do not print a label for zero quantities or provide a zero quantity in an ASN.
12.
Requirements Sorting Issue: Ability to perform multiple sorting/grouping Honda requires that you sort based on Sequence Number for the Pick, Load sheet, and use the Batch Number as the secondary sort. Additionally, it would be highly helpful to the suppliers shipping associates to group the items within the same Batch Number by Part Family. Indeed, for all suppliers the sort should use the Sequence Number, as this will apply to trailer sequence/container sequencing. It should be noted that providing this data for the suppliers shipping associates to correctly pack a Delivery Batch and Sequence a Trailer (if necessary) depends on the suppliers specific requirements for pack. Software developers are encouraged to offer additional sorting or grouping routines to accurately align this data particularly if they are planning to offer label pre-printing capability.
13.
Family Batch Issue: Family Batch ordering impact Honda has installed software called Family Batch to help eliminate unnecessary small lots. However, a supplier may receive valid requirements where the part, design change, quantity, delivery date and time ship schedule number, batch number, and lot number are identical in an 862. The supplier needs to be able to respond to each requirement as if it is unique.
Previous Chapter
Cover Page
General Information
Next Chapter
5 - 22
April 2008
Chapter 6 Testing Procedure

Testing Procedure
February 2007
6-1
Chapter Contents
This chapter contains information about the criteria and processing involved in the Honda supplier testing process. Hondas EC (Electronic Commerce) Group resources are listed in case help is needed.
Table of Contents
Overview ................................................................................................................................................ 3 Testing Criteria.................................................................................................................................... 3 Setting up a Test Plan......................................................................................................................... 3 Standards Supplier Testing Procedure .............................................................................................. 4 Standard Testing Process................................................................................................................... 4 Honda Supplier Testing Process Flow................................................................................................ 6 Hybrid Supplier Testing Process ........................................................................................................ 8 Hybrid Testing Process....................................................................................................................... 8
6-2
February 2007
Overview
In this chapter, you will find the following: General information on criteria to meet prior to beginning the testing process. Types of paths suppliers may choose to become EDI and Barcode enabled. Testing processes for the different paths: 1. 2. Standard Testing Process Hybrid Testing Process
Testing Criteria
In order to meet Hondas EDI & Barcode requirements, a supplier must purchase and install the appropriate hardware and software, complete training, gain HSThub connectivity, and complete the testing process. There are different testing requirements depending on the path a supplier has chosen to become EDI and Barcode enabled. These paths are as follows: 1. Standard
Used by Honda suppliers who have purchased one of the Honda approved software provider packages.
2. Hybrid
Used by Honda suppliers who will be responsible for developing their own EDI and Bar Code systems.
Setting up a Test Plan

To set up your testing plan, please contact the Honda North American Logistics systems group: HondaEDI@ham.honda.com The following pages describe the testing processes for each path.
February 2007
6-3
Standards Supplier Testing Procedure

Standard Testing Process
Complete testing documentation will be provided by Honda at the beginning of the testing process. Below is an outline of the steps to follow during supplier testing for standards. 1. 2. Honda will confirm that the supplier has met the necessary criteria to move into the testing phase. Honda will confirm suppliers account/user ID (mailbox) for the ISA segment and DUNS number for the GS segment. Honda will also confirm that the supplier is aware of Hondas account/user ID (mailbox) information that they will communicate with during testing. Honda will confirm whether the supplier is a DSPS recipient and what its ordering style is (Summary, Sequence, or both). Honda will then transmit all the outbound EDI test documents to the suppliers mailbox. The supplier will be required to establish a connection to the HSThub, receive all the test files, and end the connection with the network. The supplier must then generate 997s for each test file and transmit all the 997s to the Honda testing mailbox. Honda will pull the 997s down from the mailbox, checking to make sure that the correct number are present and contain accurate information according to the Honda specifications. Supplier will need to create barcode labels to generate the 856s for the specific shipments as directed in the test packet. The following documents will be used: 862 (DELTA/GPCS version 4010), 830 (STAR version 4010) 9. Supplier needs to transmit the 856 documents. This can be done all at once or individually, as needed. The documents will again be sent to the HSThub Honda testing mailbox. Honda will receive the 856 documents and run them through translation to verify accuracy. Suppliers will be required to generate the Master Packing List (MPL) associated with the 856s (generated in #10.) These will need to be faxed to Honda. Honda will verify that the MPL meets specifications. If all above steps have been completed successfully, the supplier will begin final barcode label testing (if applicable), then move into production as appropriate.
3. 4. 5. 6. 7.
8.
10. 11. 12. 13.
6-4
February 2007

Note - If at any time during the testing a supplier is not able to successfully complete the test, NAL Systems group will assist with the problem determination and re-test. Depending on the nature of the problem(s), it may be necessary to refer the supplier back to their software provider for support.
February 2007
6-5
Honda Supplier Testing Process Flow
Honda contacts Supplier Honda contacts Supplier
Honda and supplier confirm suppliers test account Honda supplier confirm suppliers #/user and mailbox ID and (mailbox) Duns # and along Duns with # the alongtest withaccount the #/user ID (mailbox) Duns # along with the mailbox qualifier/receiver and qualifier/receiver ID and to be used ID to be used mailbox and qualifier/receiver ID to be used Supplier prepares Supplier prepares for testing. for testing.
Honda confirms suppliers ordering Honda suppliers ordering style asconfirms sequence, summary, or style as sequence, both. summary, or both.
Honda sends test files to supplier. Honda sends test files to supplier.
Supplier receives test files and generates 997s. Supplier receives test files and generates 997s.
Honda receives 997s and reviews for quantity and Honda receives 997s and reviews for quantity and accuracy. accuracy.
Honda works with Hondato works with supplier identify supplier to identify problems. problems.
Yes
Are 997s Are 997s okay? okay?
No
Supplier answers checkSupplier answers sheets provided in testcheck packet sheets provided in test packet & faxes to Honda & faxes to Honda Answers Answers Accurate? Accurate? Yes No Honda follows Honda up. follows up.
Supplier generates barcode labels. Supplier generates barcode labels.
Supplier generates test 856s. Supplier generates test 856s.
Supplier sends test 856s to Honda. Supplier sends test 856s to Honda.
Honda receives and validates test 856s. Honda receives and validates test 856s.
6-6
February 2007
Honda Supplier Testing Process Flow (continued)

B A
Honda works with Supplier to identify problem.
No
Are 856s Are 856s Accurate? accurate?
Yes
Supplier faxes Master Supplier faxes Master Packing List and bar Packing and bar code labelsList to Honda. code labels to Honda.
to identify
Honda Honda reviews reviews Honda reviews cy. for foraccura Accuracy for accuracy. Honda follows Honda up. follows up. No
Master Master Packing Packin List OK? g List OK?
Yes
Honda does barcode testing. See Chapter 8 for BCQA.
Testing is complete.
February 2007
6-7
Hybrid Supplier Testing Process

Hybrid Testing Process
Below are the steps to be followed during supplier testing for hybrid: Phase 1 Submission of project plan and approval by Honda Provide to Honda your mailbox name and DUNS Number Phase 2 Hard copy reports rip and reads of the Outbound transactions (Honda to Supplier) Phase 3 Completed Check Sheets Inbound (Supplier to Honda) EDI transactions 846, 856, 997 Bar code labels and Master Packing List Phase 4 Site visit demonstrating items in phases 2 and 3. Note - This is only a basic outline of the process. Actual testing requirements will be established at the time of testing. Honda suppliers implementing a hybrid solution historically have taken 190 days to complete the Honda testing process. This does not include training time and upgrades required due to Honda specification changes.
6-8
February 2007
Chapter 7 Troubleshooting

Troubleshooting
September 2007
7-1
Chapter Contents
This chapter contains the guidelines to help you when you experience problems sending ASN transmissions and receiving Functional Acknowledgments.
Table of Contents
Potential Problems and Recommended Countermeasures ............................................................. 3 824 Error Messages and Recommended CounterMeasures............................................................ 6 Reporting a Problem .......................................................................................................................... 20 Required Information ........................................................................................................................ 20 Network Address............................................................................................................................... 20
7-2
September 2007
Potential EDI Connectivity and Bar Code Problems with Countermeasures

If you experience problems with a transmission, use the following guidelines to determine the possible solution. POTENTIAL PROBLEMS
1 EDI Not Sent By Honda
FAILURE POINTS
Honda internal issues Did not receive the Weekly Release, Ship Schedule or Purchase Order
RECOMMENDED COUNTERMEASURES
Honda to resolve. Contact your Honda buyer and verify that the document was sent. If no document was sent, then no action is necessary. If a document was sent, contact the Honda EC Group (2) to verify that the EDI document has actually been transmitted. 1. Honda uses ZZ qualifier in ISA 05. 2. Honda uses Account ID and User ID separated by three spaces in ISA06. 3. Honda uses a Company Specific Duns Number in the GS02. Note: Refer to Chapter 4: Implementation Steps for Account/User IDs and Duns Numbers 1. If using GXS VAN (aka IBM) contact them to insure 50/50 Co-Pay with Honda and all mailbox definitions for each Honda Ordering plants are defined including alias accounts. See Chapter 4: Implementation Steps for Honda Company Account/User IDs and Duns 2. If using Hondas HST Hub insure your FTP or ANX software is set-up to retrieve Production Data as defined in Chapter 4: Implementation Steps 3. If using another Value Added Network (VAN) as an interchange to Honda, please insure that all mailbox definitions for each Honda Ordering plants are defined including alias accounts. Note: Honda will route all interchange data using an 01 qualifier in the ISA07 followed by the suppliers Duns or an agreed upon value in the ISA08 If the action above has been completed, then the supplier should contact the Honda EC Group (See Reporting a Problem later in this chapter).
EDI Sent by Honda but not Received by supplier
Suppliers EDI Software doesnt have correct Trading Partner Information
Suppliers communication tools are set-up incorrectly
Honda Has incorrect Trading Partner Definition
997 Not Received by Honda
Supplier Mailbox setup issue
The supplier should set up their 997s to be sent to the same Interchange as they received their Inbound documents. 1. Honda expects a ZZ qualifier in ISA 07. 2. Honda expects a Honda Account ID and User ID separated by three spaces in ISA08. 3. Honda expects a Company Specific Duns Number in the GS03. Note: Refer to Chapter 4: Implementation Steps for Account/User IDs and Duns Numbers.
September 2007
7-3
POTENTIAL PROBLEMS
4 Supplier Could not Deliver 856
FAILURE POINTS
Supplier could not generate 856
Supplier/Software Provider investigates and corrects. Supplier requests re-send of Ordering Documents if required. Supplier sends 856. The supplier should set up their 856s to be sent to the same Interchange as they received their Inbound Orders. 1. Honda expects a ZZ qualifier in ISA 07. 2. Honda expects a Honda Account ID and User ID separated by three spaces in ISA08. 3. Honda expects a Company Specific Duns Number in the GS03. Note: Refer to Chapter 4: Implementation Steps for Account/User IDs and Duns Numbers. 1. If using Hondas HST Hub insure your FTP or ANX software is set-up to send Production Data as defined in Chapter 4: Implementation Steps 2. If using another Value Added Network (VAN) as an interchange to Honda, please insure that you will route all interchange data using an 01 qualifier in the ISA05 followed by the suppliers Duns or an agreed upon value in the ISA06 NOTE: Remember to inform your Honda buyer if the ASN transmission is not possible.
Supplier mailbox setup issue
Supplier communication problems (modem, network, communication script, HSThub unavailability, translation issues,)
997 Not Received by supplier
Note: All suppliers are required to retrieve these EDI documents from their mailbox within 15 minutes of transmitting an 856 to Honda.
Trading Partner Information
If the 997 is not present within 15 minutes, the supplier should contact the Honda EC Group (See Reporting a Problem later in this chapter) The supplier needs to insure the following: 1. ISA05 ZZ (GSX or HST Hub), Use 01 for Interconnects. 2. ISA06 Suppliers Account/User ID. Use Supplier Duns or Honda Assigned identifier for Interconnects. 3. ISA07 Must be ZZ 4. ISA08 Must be Honda Account and User ID with three spaces between them. 5. ISA15 Must be P for Production 5. GS02 Supplier Duns Number 6. GS03 Honda Ordering Company Duns Number. 7. GS08 must be 004010 Honda identifies discrepancy to supplier. Supplier/Software Provider corrects setup/ configuration based on feedback from Honda. Supplier request re-send of EDI if required. Supplier sends 856. (2)
EDI Structural errors (ISA/IEA,GE/SE. ST/SE). Delimiters invalid. Stream data issues (CR/LF (carriage return/line feed) embedded) 997 Not Sent by Honda
Honda transaction not set to ACK. Contact Honda EC Group (See Reporting a Problem later in this chapter) to resolve. Honda sends 997.
7-4
September 2007
POTENTIAL PROBLEMS
6 824 Not Sent by Honda NOTE: All suppliers are required to retrieve these EDI documents from their mailbox within 15 minutes of transmitting an 856 to Honda.
FAILURE POINTS
Electronic Commerce relationship not valid (unknown supplier number in relation to sender ID)
If the 824 is not present within 15 minutes, the supplier should contact the Honda EC Group (See Reporting A Problem later in this chapter) Supplier/Software Provider corrects based on feedback from Honda. Supplier requests re-send of EDI if required. Supplier sends 856. (2)
824 TR (Transaction Rejection) or TE (Transaction Accepted with Error)
Supplier Receives 824 with a TR or TE
Supplier should review the 824 EDIT List on the following pages in this chapter to resolve their issue. If possible the supplier will correct and resend the ASN if the shipment has not been received by Honda. For further assistance, contact your Honda Buyer or NAL Systems (1). Honda associate to follow up with supplier. Supplier/Software Provider to correct the issue. Supplier sends Bar Code and Master Packing List. Questions/problems regarding bar code labels, contact Honda EDI Help (1).
Bar Code Label/ Master Packing List Not Received by Honda
Supplier did not send. Supplier could not create
Bar Code Labels/Master Packing List Not Valid
Labels / Master Packing List Not valid. Missing Data Invalid data Invalid format Bar Code Not Valid Human Readable missing data Human Readable invalid data Bar code missing data Bar code invalid data Bar code fails scan
Supplier to correct based on feedback from Honda Associate and Delivery Trouble Report (DTR). Prior to next shipment, supplier completes DTR and returns copy.
Supplier to correct based on feedback from Honda Associate and Delivery Trouble Report (DTR). Prior to next shipment, supplier completes DTR and returns copy. Questions/problems regarding bar code labels, contact Honda EDI Help (1)
SUPPORT 1) Honda NAL Systems: HondaEDI@ham.honda.com (937) 642-5000 x62884 2) Honda EC Group: HAM_ISG_EC_Support@ham.honda.com (937) 578-0447
September 2007
7-5
824 Error Messages and Recommended Countermeasures

The following guideline provides the cause and countermeasure for 824 (Application Advice) error messages. 824 Message Description
Trailer number contains invalid characters Bill of Lading not specified.
Cause
Trailer Number contains "special" characters. Bill of Lading Number was omitted in the ASN.
Countermeasure
Correct the trailer number. Verify that the trailer number contains characters from the range 0-9, A-Z, or a-z inclusive. Supplier should resend the ASN if shipment has not already been received. Bill of Lading (BOL) number should be populated in the ASN. BOL Number must be specified, may not be blank or zeroes. Supplier needs to verify software set-up. Supplier may correct and resend the ASN if it has not already been received. Verify the correct Ship To Location from the original ordering document (850/862). Ship to (Warehouse) must be specified, may not be blank. Supplier must indicate Ship To in ASN and should resend the ASN if shipment has not already been received. Verify the correct Ship To location from the original order (850/862). Supplier must indicate correct Ship To in ASN and should resend the ASN if shipment has not already been received.
856 Result
TR
TE
Ship To (Warehouse) not specified.
The Ship To Warehouse code was omitted in the ASN. Supplier specified a Ship To which does not match the referenced ordering document (850/862). Supplier omitted the Ship To location on the ASN (DSPS only). Supplier specified a Ship To location which does not match the referenced Ordering Document (DSPS only). Plant ID was omitted from the ASN. An invalid Plant ID was transmitted in the ASN. Shipment Date omitted from the ASN.
TR
Ship To is invalid.
TR
Ship To Location not specified. Ship To Location is invalid.
Ship to Location must be specified, may not be blank. Supplier must add the Ship To Location and should resend the ASN if shipment has not already been received. Input the correct Ship To Location found on the ordering document (850/862) and resend the ASN if shipment has not already been received.
TR
TR
Plant ID not specified.
Plant ID must be specified, may not be blank. Supplier must input the Plant ID transmitted from the ordering document (850/862) and should resend the ASN if shipment has not already been received. Supplier must input the Plant ID transmitted from the ordering document (850/862) and should resend the ASN if shipment has not already been received. Shipment Date must be specified, my not be blank. Input the correct date and resend the ASN if shipment has not already been received.
TR
Plant ID is invalid. Shipment Date not specified.
TR
TR
7-6
September 2007
824 Message Description

Shipment Date is invalid.
Cause
Incorrect shipment date format was sent in the ASN. Time of shipment was omitted from the ASN. Incorrect ship time format was sent in the ASN (HHMM). Standard Carrier Alpha Code (SCAC) was left blank in ASN. Supplier used a Standard Carrier Alpha Code (SCAC) not defined in the system.
Countermeasure
Shipment Date must be valid CCYYMMDD format. Date must be greater than 2001/06/01. Input the valid date in the correct format and resend the ASN if shipment has not already been received. Shipment Time must be specified, may not be blank. Input the valid time in the correct format (HHMM) and should resend the ASN if shipment has not already been received. Input the accurate time in the correct format (HHMM) and resend the ASN if shipment has not already been received. Standard Carrier Alpha Code (SCAC) must be specified, may not be blank or zeroes. Input the SCAC of the trucking company picking up the freight, this will usually match the ordering document (850/862). Standard Carrier Alpha Code (SCAC) does not exist in Honda's data base. This will be sent if the SCAC in the ASN does not match the SCAC on the ordering document (850/862). This may occur if Honda assigns a carrier that is different than the ordering document. The supplier does not need to take any action in this case. The Standard Carrier Alpha Code (SCAC) is not assigned to the Supplier/Location in Honda's data base. This will be sent if the SCAC in the ASN does not match the SCAC on the ordering document (850/862). This may occur if Honda assigns a carrier that is different than the ordering document. The supplier does not need to take any action in this case. Trailer Number must be specified, may not be blank. The supplier must input the valid trailer number and resend the ASN if shipment has not already been received. Supplier Number must be specified, may not be blank. The supplier must input the Supplier number and resend the ASN if shipment has not already been received. Supplier Number must be valid for the specified plant in Honda's data base. The supplier must input the valid supplier number found on the ordering document (850/862) and resend the ASN if shipment has not already been received. The location code is the last two digits of a supplier's 8 digit supplier number. The supplier must input the correct supplier location code found on the ordering document (850/862) and resend the ASN if the shipment has not already been received.
856 Result
TR
Shipment Time not specified. Shipment Time is invalid. SCAC Code not specified.
TR
TR
TR
SCAC Code not known to Honda
TE
SCAC Code not assigned to supplier.
Supplier used a Standard Carrier Alpha Code (SCAC) that was not assigned to the supplier.
TE
Trailer Number not specified Supplier Number not specified. Supplier Number not valid for specified plant. Supplier Location Code not specified.
Supplier omitted the trailer number from the ASN. Supplier number was not included in the ASN. Valid Supplier Number must be specified.
TR
TR
TR
A Valid Supplier Location Code must be specified.
TR
September 2007
7-7

Supplier Location Code does not match with ship schedule. Supplier Location Code not known to Honda. ASN Create Date not specified. ASN Create Date is invalid.
Cause
Supplier Location Code must match with the 862 ordering document. Supplier location code does not exist in Honda's Database. Supplier did not specify a valid Create Date when creating the ASN. Supplier entered a Create Date with an improper format when creating the ASN. Supplier did not enter a Create Time when creating the ASN. Supplier entered a Create Time with an improper format when creating the ASN. The ASN contains characters that are not acceptable by Honda's Ordering Systems. The supplier referenced an invalid ship schedule number that was not on active 862 (LIN 09 or REF 02).
Countermeasure
The supplier must input the correct supplier location code found on the ordering document and resend the ASN if the shipment has not already been received. The supplier must input the correct supplier location code found on the ordering document (850/862) and resend the ASN if shipment has not already been received. ASN Create Date must be specified, may not be blank. Date must be greater than 2001/06/01. Supplier should correct and resend the ASN if shipment has not already been received. ASN Create Date must be in valid CCYYMMDD format. Supplier should correct and resend the ASN if shipment has not already been received.
856 Result
TR
TR
TR
TR
ASN Create Time not specified. ASN Create Time is invalid.
ASN Create Time must be in valid HHMM format. ASN Create Time must be specified, may not be blank. Supplier should correct and resend the ASN if shipment has not already been received. Create time format must be HHMM. Supplier should correct and resend the ASN if it has not already been received.
TR
TR
ASN Number contains invalid characters No Current Ship Schedule for supplier and item.
Contract associated with current ship schedule not active.
Honda must have a live contract in the System.
ASN Number contains "special" characters. Verify that the ASN number contains characters from the range 0-9, A-Z, a-z inclusive. The supplier should correct the ASN and resend if the shipment has not been received. Supplier should correct the ship schedule number specified in the ASN. This Number must be from the original 862 from which the supplier created the ASN. Sometimes this error occurs with numerous other 824 failures involving supplier number, ship to locations and item/supplier combinations. The supplier should check to see that the part number, ship to, and supplier codes are also correct. Supplier should resend the ASN if shipment has not already been received. Supplier should inform Honda Buyer to correct contract discrepancy. Supplier should resend the ASN if shipment has not already been received.
TR
TR
TR
7-8
September 2007

Label serial ID is not unique within the last 12 months.
Cause
Two causes of this error: A) Suppler has used a duplicate container or pallet label serial number already used within 365 days. Error Data will show previous ASN Number. B) Supplier scanned same container twice when creating ASN. Error Data will indicate the same ASN Number. The Pallet Returnable Container Type is incorrect on the ASN.
Countermeasure
A & B) Supplier must create a process to prevent using same label serial number. Software packages should be modified to prevent duplicate serial numbers from being used within the development of a single ASN or for all ASNs during 365 day period. Supplier should resend the ASN if shipment has not already been received.
856 Result
TR
Pallet Returnable Container Type not known.
Box label serial identifier not specified.
Supplier omitted Container Label Serial Number (1S) detail from the ASN
Box label serial ID is not unique within last 12 months.
A) Suppler has used a duplicate container label serial number used within 365 days. Error Data will show previous ASN Number. B) Supplier scanned same containers twice when creating ASN. Error Data will indicate same ASN Number.
Supplier needs to contact their Honda Buyer for the correct Pallet Returnable Type to be input in the ASN. The use of XX for expendable/other is acceptable. The use of XX or an invalid Returnable ID in the ASN may result in the supplier getting insufficient number of containers returned from Honda. Supplier should correct and resend the ASN if the shipment has not been received. The Container Label Serial Number must be present for each item in the ASN. The supplier needs to correct software or scanning procedures to insure that the serial number appears. Supplier should resend the ASN if shipment has not already been received. A & B) Supplier must create a process to prevent using same label serial number. Software packages should be modified to prevent duplicate serial numbers from being used within the development of a single ASN or for all ASNs during 365 day period. Supplier should resend the ASN if shipment has not already been received.
TE
TR
TR
September 2007
7-9

Manufacturing Base Part Number not specified. Invalid Label Serial.
Cause
Supplier omitted the part number on the ASN. The Label Serial Number must have 16 characters.
Countermeasure
Manufacturing Base Part Number must be specified, may not be blank. Supplier must correct and resend the ASN if the shipment has not already been received. The first 8 characters are the Supplier Number and the second 8 characters are assigned by the supplier's software. Supplier must correct software template for label printing to ensure Supplier Number is correct. Supplier should resend the ASN if shipment has not already been received. Supplier must specify Part Quantity in the ASN and resend the ASN if the shipment has not already been received. An IPP Tag requires a valid IPP Reason Code in the ASN. See the EDI and Bar Code Implementation Manual or Supplier Quality Manual for proper reason codes. The Supplier should correct and resend the ASN if shipment has not already been received. An IPP Tag requires a valid IPP ID Number in the ASN. The Supplier should correct and resend the ASN if shipment has not already been received.
856 Result
TR
TR
Box Part Quantity not specified. IPP Tag reason code not specified.
The Item Level part quantity was missing on the ASN. IPP Tag Reason Code is missing for a valid IPP Tag.
TR
TE
IPP Tag reason code specified, IPP Tag ID not specified. IPP Tag reason code not known.
IPP Tag Reason Code is present, but the IPP Tag Number is missing. IPP Tag Reason Code is invalid format or type.
TE
An IPP Tag requires a valid IPP Reason Code in the ASN. See the EDI and Bar Code Implementation Manual or Supplier Quality Manual for proper reason codes. The Supplier may correct and resend the ASN if shipment has not already been received. Supplier must use the container type specified in the ordering document (862) or "XX" for expendable/other. The use of XX or an invalid Returnable ID in the ASN may result in the supplier getting insufficient number of containers returned from Honda. Supplier should correct and resend the ASN if shipment has not already been received. Supplier must use the container type specified in the Ordering Document (862) or "XX" for expendable/other. The use of XX or an invalid Returnable ID in the ASN may result in the supplier getting insufficient number of containers returned from Honda. Supplier may correct and resend the ASN if shipment has not already been received.
TE
Box Returnable type not specified.
The ASN was missing the Item Level Returnable Container Type.
TE
Box Returnable type is invalid.
The ASN contained an invalid Item Level Returnable Container Type.
TE
7 - 10
September 2007

Part Number not associated with specified production lot.
Cause
There are four reasons why this could happen: A) Part Number and Lot Number combination does not match with the ordering document. B) Lot number is missing from the 856. C) Verbal request from Honda Buyer to ship parts for a lot number that is not on the ordering document. D) Honda put a lot number on HOLD and supplier shipped parts against the hold lot. Supplier did not indicate a box unit of measure in the Item Level of the ASN. Supplier used a unit of measure in the ASN that is inconsistent with the original ordering document. Supplier specified invalid Purpose code in the ASN.
Countermeasure
Check ASN Part, Lot, and Ship Schedule number to see if matched on corresponding 862. If no match follow A through D. A) The supplier should correct the Part Number/lot number and resend the ASN. B) The supplier should add the lot number and resend the ASN. C) The Honda Buyer should prepare an order document for the lot number requested. D) The Honda Buyer should communicate to the supplier of the lot put on HOLD.
856 Result
TR
Box Unit of Measure not specified.
The supplier can find the unit of measure from the original ordering document (850, 862). Honda normally uses "EA" (each) for the box unit of measure field (SN103). The supplier should correct and resend the ASN if the shipment has not already been received. Refer to the original ordering document (850) for correct unit of measure. Honda normally uses "EA" (each) for the box unit of measure field (SN103). The supplier may correct and resend the ASN if the shipment has not already been received. Supplier must send in a valid EDI Purpose Code: 00 for original, 01 for cancel, or 05 for replacement as indicated in the EDI and Bar Code Implementation Manual. The supplier should correct and resend the ASN if shipment has not already been received. Supplier should not resend an ASN that was already valid with a purpose code of "00". If the supplier is resending because the original ASN received an 824 with a "TE" (Accepted with Error), then the supplier should send a "05" replacement code.
TE
Unit of Measure does not match with PO.
TE
Purpose Code is invalid.
TR
Purpose code 00 already exists, processed as replacement.
A valid ASN with the same ASN number was previously received. This ASN indicates that it is also an original.
TE
September 2007
7 - 11
Chapter 7 Troubleshooting 824 Message Description

Attempt to cancel ASN, no valid ASN exists.
Cause
Received ASN with Purpose code 01 (cancel) and there is no valid ASN with the same ASN Number. If all parts on an ASN have been received against, and the supplier sends a replace/cancel for that ASN number, the replace/cancel will be ignored. (The replace/cancel is too late.) ASN indicated that it was a replacement document (05); however, a valid original ASN does not exist. Therefore the ASN was processed as an original (00). The ASN weight was omitted from the ASN (TD107). The ASN weight unit of Measure was omitted from the ASN (TD108). An invalid ASN weight unit of Measure was transmitted in the ASN (TD108) The Country of Origin was omitted from the ASN
Countermeasure
Supplier should not send an ASN that has not been received with a purpose code of "01" (cancel).
856 Result
TR
ASN receipt done, replace/cancel ignored.
There is no way to correct this issue. Supplier should not repeat this problem.
TR
Valid ASN not found, processed as an original.
None - ASN was processed. The supplier should check their business procedures for future shipments. TE
ASN Weight not specified. ASN Weight Unit of measure not specified. ASN Weight Unit of measure is invalid Country of Origin not specified.
ASN weight should be populated in the ASN. Supplier should resend the ASN if shipment has not already been received. ASN weight unit of measure should be populated in the ASN. The supplier needs to specify if the unit is pounds (01) or Kilograms (50). Supplier should resend the ASN if shipment has not already been received. The supplier needs to specify if the unit is pounds (01) or Kilograms (50). Supplier should resend the ASN if shipment has not already been received.
TE
TE
TE Country of Origin (COO) should be populated in the ASN. Supplier should contact Honda Trade Compliance if unsure of proper COO Code. Supplier should resend the ASN if shipment has not already been received. 856 ASN Segment IDs are defined in the EDI and Bar Code Implementation Manual. A supplier's translator should be translating this information properly. The supplier should correct and resend the ASN if the shipment has not already been received.
TE
Invalid Segment ID encountered
Segment ID is less than two characters or more than three characters.
TR
7 - 12
September 2007

Undefined Logistical Company
Cause
Supplier specified Ordering Plant that is not known to Honda's Ordering System. Incorrect P.O. number (LIN 14) on the ASN.
Countermeasure
The supplier must correct the Ordering Plant in the N1 statement by matching it with the original ordering document (850/862). The supplier should correct and resend the ASN if the shipment has not already been received. The ASN Purchase order number should match the Purchase Order from which the ASN was created. Supplier should correct and resend the ASN if shipment has not already been received. View the original ordering document (850/862) to find the correct unit of measure. The supplier may correct and resend the ASN if shipment has not already been received. Input correct project code found from the original ordering document (850/862) and resend the ASN if the shipment has not already been received. Honda Buyer must verify that the Purchase Schedule (830) for the particular part number and supplier was sent. Supplier should then correct and resend the ASN if shipment has not been received.
856 Result
TR
PO is not assigned to supplier.
TR
Box Unit of Measure does not match with order. Project Code invalid.
Purchase Schedule does not exist for supplier and item. Unit of measure not found.
Late ASN, Receipt Already Made. Invalid item / supplier combination.
Supplier used a box unit of measure (SN103) not consistent with the order. The project number must be valid in Honda's Ordering System. The Purchase Schedule (830) for the particular part number and supplier does not exist. The Unit of measure in the ASN does not match the unit of measure in the order document specified in the ASN. Unit of Measure is not known to the system. Receipt of parts made before the ASN arrived. The item numbers specified on the ASN must be valid for the supplier/location as defined in the Honda Ordering data base
TE
TR
TR
View the original ordering document (850/862) to find the correct unit of measure. The supplier should correct and resend the ASN if the shipment has not been received. TE
ASN must be sent at trailer departure. There is no way to correct this error. Verify that the part number on the ASN matches with the Ordering Document (862/850). Use the Part Number/Lot Number/DC Level Algorithm in Chapter 9 of the EDI and Bar Code Implementation Manual to investigate part number errors. Sometimes this error occurs with numerous other 824 failures involving supplier number, ship to locations and no current ship schedule for supplier and item. The supplier should check to see that the part number, ship to, and supplier codes are also correct. Supplier should correct and resend the ASN if shipment has not already been received.
TR
TR
September 2007
7 - 13

PO is invalid.
Cause
Incorrect P.O. number on the ASN.
Countermeasure
View the Purchase Order (pertaining to the part number on the ASN) and verify that the P.O. number matches with that on the ASN. The supplier should correct and resend the ASN if shipment has not already been received. Note: It is possible that the Purchase Order has been deleted from Honda's System after it was issued. The supplier should contact the buyer for direction. Verify that the part number on the ASN matches with what is on the Purchase Order (850). Use the Part Number/Lot Number/DC Level Algorithm in EDI and Bar Code Implementation Manual to investigate part number errors. The supplier should correct and resend the ASN if shipment has not already been received. The supplier needs to compare the part number on the ASN to the original PO. Verify PO Number, Part Number and Project Number is correct. The supplier should correct and resend the ASN if shipment has not already been received.
856 Result
TR
Item does not match with PO item.
Item is not for specified PO / Project.
Both PO and Schedule Number specified Order type invalid. PO or Schedule Number not specified Order type invalid. Data type mismatch / invalid data.
The part number on the ASN does not match the part number assigned to the PO Number provided on the ASN. An Item number specified in the ASN does not appear on the PO referenced by the ASN for the referenced project. Both Delivery Schedule and Purchase Order numbers were specified for the same item in an ASN. ASN did not include a Ship Schedule number or a Purchase Order number in the ASN. Per the EDI and Bar Code Implementation Manual, numeric data elements must be numeric, Dates must be in valid date format, Times must be in a valid time format, the length of a data element must meet the mini/max number of characters.
TR
TR
The Supplier should clarify what type of order the ASN was responding to, either 862 Ship Schedule or 850 PO. Supplier should remove the incorrect order number from the ASN and resend the ASN if shipment has not already been received. . The Supplier should clarify what type of order the ASN was responding to, either 862 Ship Schedule or 850 PO. The supplier should specify the correct Order Number and resend the ASN if the shipment has not been received. Can be caused by type mismatch of data value versus the EDI data specification, including spaces being included/excluded in the ASN Number or the letter O being substituted for 0 (zero). Check ASN item number against order item number. The supplier should correct and resend the ASN if shipment has not already been received.
TR
TR
TR
7 - 14
September 2007
Chapter 7 Troubleshooting 824 Message Description

Invalid D/C for item.
Cause
D/C associated with part number is missing
Countermeasure
This data element should be present for a Manufacturing Base Number whose first two characters are less than 92. The supplier should correct this ASN and resend if the shipment has not already been received. None - ASN was processed. Supplier should use the 05 code for sending replacement ASNs.
856 Result
TR
Valid ASN found, processed as replacement.
Expendable containers should not have serial ID.
Supplier used the same ASN number as a previous transmission and did not indicate the new ASN was a 05 replacement. ASN specified the Container packaging Type (LIN27) was "XX" (expendable), but a Returnable Container Serial Number was also specified. Supplier sends replacement (05) or cancel (01) ASN and the trailer has already arrived and received, the new ASN will be ignored. The trailer arrives at Honda before the ASN is received, but the receipt of parts has not been completed.
TE
Expendable containers do not have Returnable Container Serial Numbers. The supplier may correct the Returnable Container Serial Number and resend the ASN. Note: Honda does not require returnable serial numbers for any packaging.
TE
Trailer arrived, replace / cancel ignored.
The supplier should insure they get any adjustments to ASNs to Honda before the trailer arrives. TR
Late ASN processed.
The supplier needs to transmit the ASN at trailer departure and insure that a valid 824 message is received within 15 minutes. If a valid 824 is not received the supplier should contact their Honda Buyer.
TE
Supplier's Mfg Lot # Missing
The supplier manufacturing lot information was missing in the ASN (LIN 22 and 23)
The supplier must insure that each container has a supplier's manufacturing lot information on the label and in the ASN. The supplier should refer to the Honda EDI and Bar Code Implementation Manual and the Supplier Quality Manual for guidance. The supplier should correct and resend the ASN if the trailer has not already been received.
TE
September 2007
7 - 15

Pallet label serial ID less then 16 characters
Cause
The Pallet Label Serial Number must have 16 characters. The first 8 characters are the Supplier Number and the second 8 characters are assigned by the supplier's software. Pallet label serial ID must be specified, may not be blank. The Pallet Label Serial Number must have 16 characters. The first 8 characters are the Supplier Number and the second 8 characters are assigned by the supplier's software. Box label serial ID in the Item level of the ASN needs to be 16 characters. The first 8 characters are the Supplier Number and the second 8 characters are assigned by the supplier's software. An ASN Number must contain 8 characters The ASN was received without any information pertaining to parts. Supplier combined requirements from an 862 Ship Schedule and an 850 PO on the same ASN.
Countermeasure
The supplier needs to insure that both their bar codes and ASN contain the full 16 character serial number (1st 8 supplier number and last 8 is unique). The supplier should correct and resend the ASN if shipment has not already been received. Note: Receiving a valid ASN does not insure that the shipment will be received electronically if the bar code labels do not have he full 16-character serial number. The supplier needs to insure that both their bar codes and ASN contain the full 16 character serial number (1st 8 supplier number and last 8 is unique). The supplier should correct and resend the ASN if shipment has not already been received. Note: Receiving a valid ASN does not insure that the shipment will be received electronically if the bar code labels do not have the full 16 character serial number.
856 Result
TR
Pallet label serial ID cannot be blank
TR
Box label serial ID less than 16 characters
The supplier needs to insure that both their bar codes and ASN contain the full 16 character serial number (1st 8 supplier number and last 8 is unique). The supplier should correct and resend the ASN if shipment has not already been received. Note: Receiving a valid ASN does not insure that the shipment will be received electronically if the bar code labels do not have he full 16-character serial number.
TR
ASN Number less than 8 characters ASN with no detail lines
The supplier should correct and resend the ASN if shipment has not already been received. The supplier should correct and resend the ASN if shipment has not already been received. Note: For some supplier's software, a simple reprocessing of the ASN through the EDI Translator will resolve this issue. A supplier cannot combine items from a PO (850) and a Ship Schedule (862) on the same ASN. Request the supplier to resend the ASN if shipment has not already been received.
TR
TR
PO and DLS on the same ASN
TR
7 - 16
September 2007

Manual Receipts already in process for this ASN. DSPS Ship To invalid - Must be 8 characters All outstanding quantities for the P.O. have been fulfilled.
Cause
Manual receipts are in progress at the time ASN Validation is attempted. Domestic Supply Parts Supplier (DSPS) Ship To needs to be a supplier number. There are no outstanding quantities on this 850 Purchase Order.
Countermeasure
No Actions, since receipt is in progress. Resend of the ASN will not be accepted.
856 Result
TR
A DSPS Ship To Supplier/location must be 8 characters. The supplier should correct and resend the ASN if shipment has not already been received.
TR
Invalid D/C for item.
D/C associated with part number is incorrect.
Conditional Element Compliance check error. Duplicate Transaction encountered
Supplier created an ASN that does not conform to Honda's EDI Specifications. Supplier created an ASN that contains a duplicate Transmission Set Control Number (ST02) with a previous transmission. The transmission identifier must be unique within an 18-month period.
The Supplier needs to insure they have not doubled shipped and that the P.O. number is correct on the ASN. The supplier should correct and resend the ASN if shipment has not already been received. In rare occasions, the PO could have been deleted from Honda's ordering system without issuing a cancellation. The supplier should check with their Honda Plant Buyer. This field should be present for a Manufacturing Base Number whose first two digits are less than 92. The supplier must send the D/C level at or above the requested D/C on the ordering document. If a supplier is sending a D/C level which does not match the ordering document the new value must match the expected value in the Honda Database. The supplier should review Honda's EDI and Bar Code Implementation Manual. The supplier may correct and resend the ASN if shipment has not already been received. The supplier should review Honda's EDI and Bar Code Implementation Manual. Supplier should recreate the ASN in the proper format and should resend the ASN if shipment has not already been received. Honda's EDI translator will verify that the Transaction Set Control Number (ST02) is unique. Supplier should recreate the ASN with a unique Transaction Set Control Number (ST02) and should resend the ASN if shipment has not already been received.
TR
TE
TR
TR
September 2007
7 - 17

Invalid Message Version
Cause
Supplier created an ASN with a Version/Release/In dustry Identifier Code (GS08) that does not match Honda's expected value. Supplier created an ASN with a Hash total (CTT02) that does not match Honda's calculated value. The Hash total is the total number of parts being sent in the ASN. Supplier created an ASN with a Line Item count (CTT01) that does not match Honda's calculated value.
Countermeasure
Honda's EDI translator will verify that the Version/Release/Industry Identifier Code (GS08) is the expected value. Supplier should recreate the ASN with a Version/Release/Industry Identifier Code (GS08) and should resend the ASN if shipment has not already been received.
856 Result
TR
Incorrect Hash total
Honda's EDI translator will calculate the Hash total based upon data received and verify against the received Hash total (CTT02). Supplier should recreate the ASN with a corrected Hash total (CTT02) and resend the ASN if shipment has not already been received. Note: For some supplier's software, a simple reprocessing of the ASN through the EDI Translator will resolve this issue.
TR
Incorrect Line Item count
Maximum occurrences for segment exceeded
Compliance Check Error(s)
Supplier created an ASN that contains more occurrences of a segment than are allowed by the ANSI X12 standard. Supplier created an ASN that does not conform to Honda's EDI Specifications. The supplier's EDI Definition in Honda's EDI file does not match the N1 Supplier Code sent in the ASN.
Honda's EDI translator will calculate the Line Item count based upon data received and verify against the received Line Item count (CTT01). The EDI translator will calculate the Line Item count based upon data received and verify against the received Line Item count (CTT01).Supplier should recreate the ASN with a corrected Line Item count (CTT01) and resend the ASN if shipment has not already been received. Note: For some supplier's software, a simple reprocessing of the ASN through the EDI Translator will resolve this issue. Supplier should review the Honda EDI and Bar Code Implementation Manual for proper usage. Supplier should recreate the ASN and resend the ASN if shipment has not already been received.
TR
TR
The line Number and Segment ID of the affected part is transmitted on the 824. The supplier should recreate the ASN in the proper format and should resend the ASN if shipment has not already been received. This may be a supplier problem if the supplier has incorrectly specified their supplier/location code; the supplier should correct and resend the ASN if shipment has not already been received. This may be a Honda error where improper EDI set up has taken place. Honda should correct the problem and have the supplier resend the ASN if shipment has not already been received.
TR
Mismatch on TP Code and N1 data element
TR
7 - 18
September 2007

Duplicate Transaction Set Control Number
Cause
Transaction set control number (ST02 Segment) was not unique within the EDI system. Supplier is not defined for inbound EDI for the specified plant.
Countermeasure
The ST02 Transaction Set Control Number was duplicated within the last 18 months. The supplier should correct and resend the ASN if shipment has not already been received.
856 Result
TR
Supplier Code not known to <plant ID>
The supplier needs to verify that they are using the correct supplier code against a valid ordering document (850/862).
TR
TA = Transaction Accepted TE = Transaction Accepted with Error TR = Transaction Rejected Note: When an 824 is transmitted, the results show all errors detected on the entire ASN. This means that a message could be repeated more than once or multiple messages could relate to the same error.
September 2007
7 - 19
Reporting a Problem
R equire d Info rmat io n To report a problem with the HSThub, call: (937) 578-0447 or email HAM_ISG_EC_Support@ham.honda.com Please be prepared to provide the following information: Name and Company Name Your mailbox ID Your supplier number The impacted Honda plant / company A description of the problem (Ex. ASN transmitted but unable to verify it was received by Honda) When reporting a problem, please indicate one of the following key words:
NAME
INVOICE REMITTANCE ADVICE APPLICATION ADVICE WEEKLY RELEASE PRICE SALE CATALOG INVENTORY ADVICE PURCHASE ORDER ADVANCE SHIP NOTICE RECEIVING ADVICE SHIP SCHEDULE TEXT MESSAGE FUNCTIONAL ACKNOWLEDGEMENT
TRANSACTION SET
810 820 824 830 832 846 850 856 861 862 864 997
Network Add ress Please refer to table in chapter 4 for the Honda mailbox ID with whom you are attempting to communicate. These Honda IDs will be the sender IDs in the EDI transactions you receive from Honda for the related system. If you send/receive EDI to any of the locations listed, you must add these trading partner profiles to your system.
7 - 20
September 2007
Chapter 8 Bar Code/Master Packing List Quality Assurance Program

Bar Code/Master Packing List Quality Assurance Program
April 2008
8-1
Chapter Contents
This chapter contains information about Hondas Bar Code and Master Packing list Quality Assurance Program. It describes the quality requirements, inspection procedures and associated forms used to ensure suppliers are in conformance with Honda specific label requirements.
Table of Contents
Bar Code Quality Assurance Program ............................................................................................... 3 Overview ............................................................................................................................................. 3 Initial Enablement ............................................................................................................................... 3 Production Scannability Failure .......................................................................................................... 4 Figure 8.1 - Bar Code Label & MPL Quality Assurance Trouble Report Flow Chart ...................... 5 Removable Label Specifications......................................................................................................... 6 Item ..................................................................................................................................................... 6 Required Application........................................................................................................................... 6 Product Specification .......................................................................................................................... 6 Printer Specified Source ..................................................................................................................... 7 Non-Removable Label Specifications ................................................................................................ 8 Item ..................................................................................................................................................... 8 Required Application........................................................................................................................... 8 Product Specification .......................................................................................................................... 8 Bar Code Quality Assurance Test Form ............................................................................................ 9 Sample Form....................................................................................................................................... 9 Bar Code Self Test Check List .......................................................................................................... 10 Overview ........................................................................................................................................... 10 Master Packing List Quality Assurance Program ........................................................................... 20 Overview ........................................................................................................................................... 20 Initial Enablement ............................................................................................................................. 20 Production MPL Failure .................................................................................................................... 21
8-2
April 2008
Bar Code Quality Assurance Program

Overview
The objective of Honda's Bar Code Quality Assurance Program is to ensure suppliers are in conformance with Honda specific label requirements and that the labels are of sufficient quality to be read by bar code scanning equipment. The basis for Honda's label requirement is AIAG's B-10 guidelines. High quality bar codes help to assure the success of an automatic identification system. The quality of the printed bar code symbol is a critical factor in the success or failure of the entire EDI and automatic identification system. No reads, low-first-read rates, and substitution errors are the result of poorly produced bar code symbols. Shipping labels often are subjected to harsh environmental conditions that result in degradation in the scannability of the bar code. Your quality control program must include bar codes in addition to physical product. All suppliers to which Honda sends an ordering document (including DSPS) must submit a parts identification label for evaluation and approval prior to the first production shipment of product. Honda will evaluate the quality of labels submitted for testing. Numerous quality checks are involved in the test and the three most critical categories are: Physical label material Technical aspects of printing quality Layout of information.
Initial Enablement
This section details the steps involved in obtaining initial bar code quality assurance approval. 1. The supplier should complete the following tasks for Bar Code Quality Assurance approval: a. Submit one sample of each bar code label to Honda. Each label shall conform to the Honda requirements specified in this supplier manual and be an original (no copies or faxes). DELTA/ GPCS Container Master Mixed Quick Receive Delivery Batch Pack STAR N/A N/A N/A
b. Each label should be submitted on a separate copy of the Bar Code Quality Assurance Test Form. c. For each label, submit to Honda the appropriate completed Bar Code Self-Test Checklist. See the Bar Code Quality Assurance Test Form section for more information
April 2008
8-3

d. Please send the labels attached to the Bar Code Quality Assurance Test Form and the Self Test Check List to: Honda of America Manufacturing Inc. Attn: NAL/Systems 25000 Honda Parkway Marysville, Ohio 43040-9251 2. Honda will complete the following tasks after receiving the barcode label samples: a. An evaluation of the label stock. (See the Removable Label Specification section and the Non Removable Label Specification section for Hondas specification of label stock.) b. A test to confirm that all Bar Codes are ANSI Grade "A" or "B". Honda will use a commercially available Bar Code verification system designed for fast, accurate evaluation of print quality. Each parameter will receive a scan grade ranging from "A" (good) to "F" (bad). c. A verification of label format. (See the Bar Code Quality Assurance Test Form section) 3. Honda will provide each supplier their Honda Bar Code Label test results. a. If a supplier fails any category above, Honda will suggest corrective measures. The supplier shall submit new labels or a schedule for countermeasures within 7 working days. b. Once a supplier successfully completes the above, it will be the suppliers responsibility to keep their Bar Code Label Quality Standards up to that acceptable level throughout Honda's mass production
Production Scannability Failure

Honda scans 100% of all production receipts, so it is imperative that suppliers continue to ship high quality bar code labels. This section describes the steps involved when a bar code is not scannable. 1. If a shipment is received and the bar code label is unscannable, the Honda receiving associate will document the problem on a trouble report, such as a Delivery Trouble Report (DTR), with the failed bar code label attached. (See the flow diagram in Figure 8.1) After internal processing, the trouble report and the label will be sent to the supplier for review. A cause and countermeasure is to be returned to the issuing Honda associate within five working days, along with an example of the amended bar code label. Honda will review the countermeasure and test the improved label to confirm the label meets specifications. If the amended label fails to receive an ANSI symbol grade of "A" or "B", Honda will provide feedback to reach an acceptable solution. 5. Once the amended label meets specifications and the countermeasures are accepted, the supplier shall send the amended bar code labels with every subsequent shipment.
2. 3. 4.
8-4
April 2008

6. The trouble report will be reported on the Monthly Supplier Report and kept in the closed file at Honda.
Figure 8.1 shows the failed label/MPL processing flow.
Supplier Ships Parts
Honda Receives Parts by Scanning
Scannable
Shipment Approval for Payment (affects payment)
Not Scannable or MPL Issue Copy of Trouble Report & Label or MPL
Supplier Reviews and Provides Countermeasure

Countermeasured Labels or MPL
Receiving Completes a Trouble Report (ex. Delivery Trouble Report) with Failed Bar Code Label or MPL Attached
Planning Logs and Reviews the Trouble Report
Fails
Review Countermeasure and Labels or MPL
Passes
Add to Supplier Report and File
Figure 8.1 - Bar Code Label & MPL Quality Assurance Trouble Report Flow Chart
April 2008
8-5
Removable Label Specifications

Item
Removable Label Stock
Required Application
To be utilized on returnable containers at all Honda North American Facilities. These labels are required so associates may easily scan and remove the labels from returnable containers. Honda builds an extra price into the cost of each part to ensure all suppliers are compliant with this requirement.
Product Specification
The labels are typically 4 x 6.0-6.5 and meet the following base criteria: 1. Durability
Do not easily tear or damage Label quality should not deteriorate over a specified timeframe
2.
Residual Adhesion/Peeling
Will remain affixed to containers in various shipping environments, including extreme temperature ranges Can be easily removed without tearing or leaving behind excess residue
3.
Readability
Label should receive a B grade or better when scanned by Honda
8-6
April 2008
Specified Sources
1. Avery Dennison Product (s) Honda Duralabel v2 or v4 Contact Name - Rick Davidson Contact Number 765-641-9950 Contact Email rick.davidson@averydennison.com Electronic Printing Consumables Product(s) TT400650 Honda Thermal Transfer labels DT400650 1Honda Direct Thermal labels DT400650 2Honda Direct Thermal labels Contact Name Patricia Post Contact Number Toll free 1-866-221-3404 Office 313-881-2244 or cell 313-402-4636 Contact Email ppost@epcbarcode.com General Data Product(s) PBH or P-99 label stock Contact Name Kelly OToole Contact Number - 800-733-5252*2234 Contact Email kotoole@general-data.com Grand Rapids Label Product(s) GRL 233110/Honda Returnable Container Label Contact Name Dallas Graffis Contact Number 260-432-4373 Contact Email dgraffis@grlabel.com Standard Register Product(s) Dynalabels Contact Name Jill Messmer or Debbie Noell Contact Number - 614-734-7602 or 513-714-3251 Contact Email jill.messmer@standardregister.com or debbie.noell@standardregister.com Three-Leaf Productions, Inc. Product(s) Honda Thermal Transfer Film Label Contact Name Mark Hall Contact Number - 614-846-8358 Contact Email mhall@three-leaf.com Tri-State Media Product(s) Polymatte Contact Name John Clary (USA) or Dave Roe (Canada) Contact Number 937-743-2001 or 905-760-2662 Contact Email johnclary@tri-statemedia.com or droe@genecomm.com
2.
3.
4.
5.
6.
7.
April 2008
8-7
Non-Removable Label Specifications

Item
Non-Removable Label Stock
Required Application
To be utilized on non-returnable containers at all Honda North American facilities.
Product Specification
Please adhere to the Automotive Industry Action Group (AIAG) B-10 Guidelines. Dimension: 4 x 6.0-6.5 Temperature Range : Minimum Application + 40 degree F Service Range: 30 degree F to 180 degree F
Other Label Considerations

In some cases Honda may approve label variations such as: Colored stripes across the top of the label (i.e. - a 3/8-inch pastel stripe) Different colored label stock Different sized label stock All variations must be approved by: The receiving plant the parts are being shipped to Coordinate with your Purchasing contact NAL Systems Email to HondaEDI@ham.honda.com
8-8
April 2008
Bar Code Quality Assurance Test Form

Sample Form
The Bar Code Quality Assurance Test Form is shown on the following page. Copy this form to use when submitting bar code labels for approval or review.
Supplier Information:
Company Name Company Mailing Address: Street City State Phone Numbers Contact Persons
Zip Code
Supplier Label Information:

Printer Type (circle one) Thermal Transfer Other Direct Transfer Laser Dot Matrix
Honda Visual Test Results:

Material Type Label Layout Symbol Grade
Approval:
Yes No See Attached Comments:
Place Label Here
Evaluator Signature:
April 2008
Date:
8-9
Bar Code Self Test Check List

Overview
The checklists on the following pages are the measuring tools used by Honda when approving visual compliance of Bar Code quality. When submitting labels to Honda for approval, a completed copy of each label checklist should be attached to the appropriate Bar Code Quality Assurance Test Form.
8 - 10
April 2008
April 2008
8 - 11
8 - 12
DELTA/GPCS MASTER LABEL

4 DESCRIPTION
Check List
1. Bar Code Height Minimum of 1.0" 2. The encoded value must equal the human readable less the dash plus the data identifier 3. Quiet Zone minimum of 0.25" 4. Human readable Bold 1 LPB Standard (64 Pts. or .90 in. Min.) (No encroachment into Bar Code, lines, or label edge allowed) 5. Human readable 6 LPB Standard (10 Pts. or .12 in. Min.) (No encroachment into Bar Code, lines, or label edge allowed)
1996 Accord ABS RR Bumper 5 (TI# 2040)

PART NO. 8 QUANTITY 6 6 SUPPLIER PART NO.
71570-SV4 -A000-AA-01 YR169L

PKG. ID. MASTER (4S) 9
1000000
6
10
123456789 123456789
12345678-12345678
*4S1234567812345678*
6. Human readable 3 LPB Standard (20 Pts. or .25 in. Min.) (No encroachment into Bar Code, lines, or label edge allowed) 7. Human readable 7 LPB Standard (8 Pts. or .10 in. Min.) (No encroachment into Bar Code, lines, or label edge allowed) 8. If ninth position not populated leave blank 9. For human readable only, dash must be present between pos's 8 & 9 10. 16 digits, 8 position supplier no. + 8 position serial no. 11. Supplier name and address including street (Abbreviation OK)
XYZ COMPANY, 100 S BLOOM ST. , COLUMBUS, OH 43221
11 General Information: 1. LPB - Lines per block 2. Pts. = Points 3. Quiet Zone = A blank area leading and trailing each bar code with a minimum width of 0.25"
Customer Name:
Honda
Purpose / Use: This form should be used to check the Note: Illustration is NOT actual size. Any dimensions that are not otherwise specified on this page SHALL not be in visual layout of the Honda Master Label prior to compliance with AIAG B-10, Version 3. June 2004. submittal for Honda approval.
April 2008
April 2008
PKG. ID. MASTER (5S) 3 Customer Name:
DELTA/GPCS MIXED LABEL

4
Check List
1. Bar Code Height Minimum of 1.0" 2. The encoded value must equal the human readable less the dash plus the data identifier 3. Quiet Zone minimum of 0.25" 4. Human readable Bold 1 LPB Standard (64 Pts. or .90 in. Min.) (No encroachment into Bar Code, lines, or label edge allowed)
12345678-12345678
5. Human readable 3 LPB Standard (20 Pts. or .25 in. Min.) (No encroachment into Bar Code, lines, or label edge allowed) 2 6. For human readable only, dash must be present between pos's 8 & 9 7. 16 digits, 8 position supplier no. + 8 position serial no. 8. Supplier name and address including street (Abbreviation OK)
*5S1234567812345678*
Purpose / Use:
Honda
This form should be used to check the visual layout of the Honda Mixed Label prior to submittal for Honda approval.
Note: Illustration is NOT actual size. Any dimensions that are not otherwise specified on this page SHALL be in compliance with AIAG B-10, Version 3. June 2004.
8 - 13
8 - 14
April 2008
April 2008
8 - 15
8 - 16
April 2008
April 2008
8 - 17
8 - 18
STAR MASTER LABEL

PART NO. (P) 2
Check List
1. Bar Code Height Minimum of 0.5" 2. Verify data identifiers
71570-SV4-A000-NH178L 7
*P71570SV4A000NH178L*
3 1 4
4 QUANTITY (Q) 2
3. The encoded values must equal the human readable less the dashes plus the data identifier 4. Quiet Zone minimum of 0.25"
60
*Q60*
DESCRIPTION
4 SUPPLIER (V) 2
Bumper
MFG. DATE 9
14032001
AUDITOR
5. 8 digit supplier number Human readable 3 LPB Standard (20 Pts. or .25 in. Min.) (No encroachment into Bar Code, lines, or label edge allowed) 9 6. 9 digit serial number Human readable 3 LPB Standard (20 Pts. or .25 in. Min.) (No encroachment into Bar Code, lines, or label edge allowed) 7. For human readable only, dashes must be present as indicated in the ordering document. (Dashes after the 5th, 8th & 12th digits.) 8. Supplier name and address, street is optional (Abbreviation OK) 9. Special data areas. May be adjusted to accommodate supplier specific information per Honda's approval.
*V14032001*
4 ZONE 9 PLANT 9
SERIAL (4S) 2 4
000760697
*4S00076097*
4
Customer Name:
Purpose / Use:
Honda
This form should be used to check the visual layout of the Honda STAR Master Label prior to submittal for Honda approval.
NOTE: Illustration is NOT actual size. Any dimensions that are not otherwise specified on this page SHALL be in compliance with AIAG B-10, Version 3, June 2004.
April 2008
April 2008
SUPPLIER (V)
STAR MIXED LABEL
Check List
1. Bar Code Height Minimum of 0.5" 2. Verify data identifiers
3. The encoded values must equal the human readable less the dashes plus the data identifier
7
4. Quiet Zone minimum of 0.25" 5. 8 digit supplier number Human readable 3 LPB Standard (20 Pts. or .25 in. Min.) (No encroachment into Bar Code, lines, or label edge allowed)
19163001
*V14032001
5 3
MFG. DATE
AUDITOR
4
2
SERIAL (5S)
001234569
*5S00076097
ZONE
PLANT
6 9 9 3
6. 9 digit serial number Human readable 3 LPB Standard (20 Pts. or .25 in. Min.) (No encroachment into Bar Code, lines, or label edge allowed) 7. For human readable only, dashes must be present as indicated in the ordering document. (Dashes after the 5th, 8th & 12th digits.) 8. Supplier name and address, street is optional (Abbreviation OK) 9. Special data areas. May be adjusted to accommodate supplier specific information per Honda's approval.
4
General Information: 1. LPB - Lines per block 2. Pts. = Points 3. Quiet Zone = A blank area leading and trailing each bar code with a minimum width of 0.25"
Customer Name:
Label Purpose / Use:
Honda
This form should be used to check the visual layout of the Honda NOTE: Illustration is NOT actual size. Any dimensions that are STAR Mixed Label prior to submittal for Honda approval. not otherwise specified on this page SHALL be in compliance with AIAG B-10, Version 3, June 2004.
8 - 19
Master Packing List Quality Assurance Program

Overview
The objective of Hondas Master Packing List Quality Assurance Program is to ensure suppliers are in conformance with Honda requirements. The Master Packing List (MPL) is critical to the receiving function. It is used as: 1. 2. the source of the SCAC code and trailer number when receiving an order, and a tool to confirm parts and parts quantities on the shipment.
Your quality control program must now include the MPL in addition to the physical product and bar code labels. All suppliers to which Honda sends ordering documents (including DSPS) must submit a Master Packing List (MPL) for evaluation and approval prior to the first production shipment of product. The following quality checks will be performed: b. Physical layout c. Completeness of information
Initial Enablement
These section details the steps involved in obtaining initial MPL quality assurance approval. 1. The supplier should complete the following tasks for MPL quality assurance approval. a. Submit one sample of each MPL to Honda. Each MPL shall adhere to the Honda requirements specified in this manual.
DELTA STAR /GPCS MPL required for: 9 9

b. For each MPL, submit to Honda the appropriate completed MPL Self Test Check List. For more information, see the MPL Self Test Checklist section c. Send the MPLs and Self Test Checklist to: Honda of America Manufacturing, Inc. Attn: NAL Systems Group 25000 Honda Parkway Marysville, OH 43040-9251
8 - 20
April 2008

2. Honda will complete the following tasks after receiving the MPL samples: a. An evaluation of the MPL size. b. A verification of MPL format. (See the MPL Self Test Checklist section) 3. Honda will provide each supplier their Honda MPL test results. a. If a supplier fails any category, Honda will suggest corrective measures. The supplier shall submit new MPLs or a schedule for countermeasures within seven working days. b. Once a supplier successfully completes the above, it will be the suppliers responsibility to keep their MPL Quality Standards up to that acceptable level throughout Hondas mass production. c. After initial approval, MPL failures will be dealt with similar to bar code failures. Refer to the Production Scannability Failure section.
Production MPL Failure

This section describes the steps involved when a MPL does not meet Hondas specifications. 1. If a shipment is received and the MPL is missing data or otherwise out of spec, the Honda receiving associate will document the problem on a trouble report, such as a Delivery Trouble Report (DTR) with the failed MPL attached. (See the flow diagram Figure 8.1) After internal processing, the trouble report and the MPL will be sent to the supplier for review. A cause and countermeasure is to be returned to the issuing HAM associate within five working days, along with an example of the amended MPL. Honda will review the countermeasure and verify the MPL meets specifications. If the amended MPL does not meet Honda specifications, Honda will provide feedback to help reach an acceptable solution. Once the amended MPL meets specifications and the countermeasures are accepted, the supplier shall send the amended MPL with every subsequent shipment. The DTR will be reported on the Monthly Supplier Report and kept in the closed file at Honda.
2. 3. 4.
5.
6.
April 2008
8 - 21
8 - 22
DELTA/GPCS MASTER PACKING LIST

MASTER PACKING LIST
PLANT ID.NO. SHIP TO NO./ WH: 200 QPZ
1
Check List
4 5
SHIP TO NAME :
Honda, MAP, MEI C/O NEX
1. Verify 3 digit plant code (Match data against the corresponding ASN for all items on the MPL) 2. Verify 2 to 8 digit ship to code 3. Verify 8 digit supplier code, bold text 4. Verify data is complete, bold text
2
3 4
SUPPLIER #:
123456 01 XYZ COMPANY
ASN/SID (2S) 12345678
SUPPLIER NAME:
PLANNED SHIP DATE:

6
PLANNED DELIVERY DATE : 02/04/96 PLANNED DELIVERY TIME:

7
5. Verify 8 digit ASN number, bold text 6. Verify appropriate ship or deliver date / time
PLANNED SHIP TIME:
10:00
SCAC:
CHAM 245
PROJECT NO.
123456
TRAILER NO.:
9 10 11
7. Verify 4 digit SCAC code. "SCAC" label bold. SCAC data bold is optional 8. Verify project code (if included) 9. Verify data is complete. Labels must be bold. Data being bold is optional.
14
BILL OF LADING NO.: 123456789

12 13
PART NUMBER
COLOR
SHIPMENT DESIGN CHANGE AUTHORIZATION NUMBER LEVEL
DELIVERY QUANTITY
10. Verify dashes 11. Verify data (if included) 12. Verify "P-" for PO's, "S-" for ship schedules 13. Verify quantity is a total
* 53320-SH3-G001 53320-SH3-G100-M1 53320-SH3-A000-M1 53320-SH3-A100- -01 53320-SH3-J000-M1-01
YR169L12345 YR169L12345 YR169L12345 YR169L12345 YR169L12345
01- 00-M100-M100- -01 00-M1-01
S-123456 S-123457 P-123458 S-123459 P-123410
900 900 900 900 900

15
LOT NUMBERS
V19604001001, V19604002001, V19604003001, V29604001001, V29604002001, V29604003001
14. Verify blank lines 15. Verify lot number info (if included)
CONTAINER SUMMARY TYPE B C C2

* IPPTag Enclosed Page 1 of 1
18
QTY
16
16. Verify container info (if included). Type "XX" should not be included 17. Verify IPP tag flag used correctly.
6 3
18. Is page number info used? Recommend it.

10
Customer Name:
Honda
Purpose / Use: This form should be used to check the visual layout of the Honda Master Packing List prior to submittal for Honda approval.
NOTE: Illustration is NOT actual size. See chapter 10 for specifications.
April 2008
April 2008
Customer Name:
STAR MASTER PACKING LIST

1. Plant Destination: ELP 2. SUPPLIER NAME: XYZ COMPANY 3. SUPPLIER NO.: 12345601 4. DELIVERY DATE: 10/15/99 5. HONDA MATERIAL RELEASE NO.: 22014501
9
5 3 7 2 1 6
Check List
1. Verify 3 digit plant code (Match data against the corresponding ASN for all items on the MPL) 2. Verify supplier name
6. ASN NO.: 12345678
7. BILL OF LADING NO.: 987654 8. TRAILER NO.: 245

8
3. Verify 8 digit supplier code 4. Verify deliver date
11
5. Verify Material Release Number 6. Verify ASN number 7. Verify BOL number. 8. Verify trailer number 9. Verify data is complete. 10. Verify dashes
9. P/N COLOR 53320-SH3-G000-M1 75270-SB3-000-B49L 76270-SH4-000 83501-SH4-0000B49L 83551-SH4-A000-B49L 83551-SH4-A000-Y18L
10
10. DESCRIPTION Cover, Strg Joint Esctn, Reg Handle Garn L Door Mirro Pull Pocket R Door Pull Pocket L Door Pull Pocket L Door
11. DELIVERY QUANTITY 360 480 240 120 360 240
12. LOT NUMBERS
12
11. Verify quantity is total 12. Verify lot number info and dahes (if lot numbers included 13. Verify container info (if included). Type "XX" should not be included.
1-9112-001-1, 1-9112-002-1, 1-9112-003-1 2-9112-010-1, 2-9112-011-1, 2-9112-012-1 13. CONTAINER SUMMARY TYPE B C C2 D1 A1 AP QTY 6 3 10 12 3 6
13
Purpose / Use:
Honda of America Mfg., Inc.
This form should be used to check the visual layout of the Honda STAR Master Packing List prior to submittal for Honda approval.
8 - 23
8 - 24
Customer Name:
AHM MASTER PACKING LIST

MASTER PACKING LIST
PLANT ID.NO. SHIP TO NO./ WH: AHM 90
1
Check List
duplex
4
SHIP TO NAME :
American Honda 101 S. Stanfield Rd
1. Verify 3 digit plant code (Match data against the corresponding ASN for all items on the MPL) 2. Verify 2 to 8 digit ship to code 3. Verify 8 digit supplier code, bold text 4. Verify data is complete, bold text for Supplier Name 5. Verify 8 digit ASN number, bold text 6. Verify appropriate ship or deliver date / time 7. Verify 4 digit SCAC code 8. Verify project code (if included) 9. Verify data is complete
2
3 4
SUPPLIER #:
ASN/SID (2S) 12345678
SUPPLIER NAME:
PLANNED SHIP DATE:

6

7
PLANNED SHIP TIME:
10:00
SCAC:
CHAM 245
PROJECT NO.
123456
TRAILER NO.:
9 10

12 11 13
PART NUMBER
COLOR
DELIVERY QUANTITY
14
10. Verify dashes 11. Verify data (if included) 12. Verify "P-" for PO's, "S-" for ship schedules 13. Verify quantity is a total
39127-SM4-960ZE Lighter, Cigarette 39600-SV1-A02 Grille, L. *NH89L*
P-6543210001 P-6543210002
900 900
LOT NUMBERS
15
14. Verify blank lines 15. Verify lot number info (if included)
CONTAINER SUMMARY TYPE B C C2

Page 1 of 1
18
QTY
16
16. Verify container info (if included). Type "XX" should not be included 17. Verify description 18. Is page number info used? Recommend it.
6 3 10
Purpose / Use:
Honda
This form should be used to check the visual layout of the Honda Master Packing List prior to submittal for Honda approval.
April 2008
Chapter 9 Bar Code Labeling

Bar Code Labeling
February 2007
9-1
Chapter Contents
This chapter contains information concerning the DELTA/GPCS bar code labels, their primary function, and an example of each.
Table of Contents
Bar Code Labeling Overview............................................................................................................... 3 Honda Label Specifications................................................................................................................. 4 Who Should Read This ....................................................................................................................... 4 Overview ............................................................................................................................................. 4 Honda Bar Code Label Standards ...................................................................................................... 4 Honda Customizations to the Guidelines............................................................................................ 4 Color Stripes on Labels....................................................................................................................... 4 Testing Requirements......................................................................................................................... 5 Smart Labels ....................................................................................................................................... 5 Honda Bar Code Label Specifications................................................................................................ 6 Who Should Read This ..................................................................................................................... 13 Overview ........................................................................................................................................... 13 Label Application Process................................................................................................................. 16 Who Should Read This ..................................................................................................................... 16 Overview ........................................................................................................................................... 16 Part Number/Lot Number/DC Level Algorithm ................................................................................ 20 Who Should Read This ..................................................................................................................... 20 Overview ........................................................................................................................................... 20 Part Number Algorithm (for AHM)..................................................................................................... 20 Rule #1: Mass Production & Prototype Part Number Algorithm ....................................................... 21 Rule #2: Standard or Bulk Part Number Algorithm ........................................................................... 22 Honda Production Lot Number Algorithm ......................................................................................... 22 Design Change (DC) Part Level Algorithm ....................................................................................... 23 Container is the Pallet ........................................................................................................................ 24 Who Should Read This ..................................................................................................................... 24 Overview ........................................................................................................................................... 24 Bar Code Labeling a Container is the Pallet..................................................................................... 24 System Design .................................................................................................................................. 25 Trailer is the Pallet ............................................................................................................................ 25 Honda Returnable Label Serial Number........................................................................................... 26 Who Should Read This ..................................................................................................................... 26 Overview ........................................................................................................................................... 26 Returnable Container Serial Number Description............................................................................. 26 Returnable Container Serial Number Requirements ........................................................................ 26 Returnable Container Management Examples ................................................................................ 28
9-2
February 2007
Bar Code Labeling Overview

This chapter consists of Hondas Bar Code specifications and many of Hondas business practices relating to Bar Coding. These business practices should assist the supplier in making better design decisions for their own business and computer systems. Please read the Who Should Read This paragraph prior to each section. This identifies to whom the section applies and which areas to concentrate on.
February 2007
9-3
Honda Label Specifications

Who Should Read This
1. 2. All Honda suppliers should read Testing Requirements. System developers must read and understand this complete section prior to developing their Honda-style bar code labels. (See Chapter 25 for STAR Bar Code specifications.)
Overview
This section provides the necessary information to design the DELTA and GPCS Bar Code Labels.
Honda Bar Code Label Standards

All Honda labels must adhere to the Automotive Industry Action Group (AIAG) B-10 Guidelines, except for the customizations listed below. These guidelines may be purchased from the AIAG at: Automotive Industry Action Group Suite 200 26200 Lahser Road Southfield, MI 48034 Phone: 248-358-3570 Email: http://www.aiag.org
Honda Customizations to the Guidelines

The following known customizations were made to the AIAG B-10 Guidelines: The Honda Container Label includes two blocks that are subdivided horizontally, which the B-10 guideline does not recommend. Honda uses a 1S data identifier for the Serial Number on the container label. This data identifier is not included in AIAGs B-10 guidelines. Honda requires the supplier name and address directly below each labels serial number. This was specified in the B-3 guidelines, but is not specified in the B-10 guidelines. Color stripes on labels are not specified in the B-10 guidelines. The Supplier and Honda MUST agree upon any customizations not listed here.
Color Stripes on Labels

Honda permits the use of a 3/8-inch pastel colored stripe across the top of the label if it does not interfere with the bar code segment on the labels and is approved by Honda in advance.
9-4
February 2007
Testing Requirements
Honda must approve all DELTA, GPCS and STAR labels. See Chapter 8, Quality Assurance Program, for the bar code label approval requirements. The information provided in Chapter 8 might also prove useful when evaluating compliance with Honda specifications.
Smart Labels
The Smart Label concept is a term Honda uses for the license plate on each label. The license plate is a serial number for that label. This number uniquely identifies a container for traceability and links it to the other information on the label. This setup allows the scanning of only the serial number when creating a shipment, instead of scanning every field on a label. This is why the field is referred to as a smart label. The AIAG B-10 Guidelines further describe the license plate concept. AIAG calls the license plate a Unique Container Identifier.
Code 39 / 128:
Honda supports the AIAG B-10 specifications concerning the use of two linear hymnologies, code 39 or 128. See the AIAG B-10 specifications for further information. The Honda Inner Pack label may require the use of code 128 due to the length of the part number with color.
DSPS:
DSPS suppliers (tier 2 and higher supplier) are required to use approved Honda labels similar to Tier 1 suppliers
February 2007
9-5
Honda Bar Code Label Specifications

Honda has specific label requirements on layout and data elements for the following labels: 1. 2. 3. 4. 5. 6. Container Master Mixed Quick Receive Batch Delivery Pack
The specifications are shown on the following pages. Note - For information concerning when, how many, and where to apply
labels, see the Label Information section.
9-6
February 2007
February 2007
9-7
9-8
Master Label Block Title = MASTER Data = The word "MASTER" will signify this is a Master Label Text Height = 1 LPB NOTE: NOT TO SCALE For correct measurements see the AIAG B-10 Guidelines Description Block Title = DESCRIPTION Data = Part Description as assigned by Honda (Source = 830 or 850) Text Height = 6 LPB
DELTA / GPCS MASTER LABEL

DESCRIPTION
Note 3: Description may wrap
Part Number Block Title = PART NO Data = Honda part number and extension (if applicable). (Source = 830, 850 or 862) Text Height = 3 LPB Note 1: See the part number algorithm on pages 9-18 20 for use of hyphens and spaces in the human readable part number.
MASTER
PART NO. PKG. ID MASTER (4S)
2002 Accord ABS RR Bumper (TI# 2040)

QUANTITY SUPPLIER PART NO.
Supplier Information Block Title = Supplier Part No.

1234567891 1234567891
71570-SV4 -A000-AA-01 1000000 YR169L 12345678-12345678
Data = Optional area for supplier data such as supplier part number. To be used at the suppliers discretion. (Source = Supplier) Text Height = 7 LPB
Quantity Block Title = QUANTITY Data = Quantity shall match the quantity of parts inside the shipping container(s) (Source = Supplier) Text Height = 3 LPB
Serial Number Block Title = SERIAL (4S) Data = A unique serial number not repeating for 18 months: the first 8 digits is the Honda assigned supplier number, and last 8 digits is a unique alpha-numeric number assigned by the supplier. Text Height: Serial Number = 3 LPB (Source = Supplier) Supplier Name & Address = 7-8 LPB right justified (Source = Supplier) Data Identifier (DI) = 4S Maximum Length: 18 Max Data Chars = 16 (Minimum 16) DI Chars = 2 Note 2: The human readable serial number should contain a hyphen between the 8th & 9th characters. (No hyphens should occur in the bar code.)
February 2007
Customer Name: Honda
Label Purpose / Use: Used to identify a pallet containing only one Mfg. Base Part Number.
NOTE A: Illustration is NOT actual size. Any dimensions that are not otherwise specified on this page SHALL be in compliance with AIAG B-10 Guidelines.
NOTE B: The narrow element of the "X" dimension shall be between .013 and .017 inch.
February 2007 9-9
Mixed Label Block Title = MIXED Data = The word "MIXED" will signify this is a Mixed Label Text Height = 1 LPB NOTE: NOT TO SCALE For correct measurements see the AIAG B-10 Guidelines
DELTA / GPCS MIXED LABEL
MIXED
PKG. ID MASTER (5S)
12345678-12345678
Serial Number Block Title = SERIAL (5S) Data = A unique serial number not repeating for 18 months: the first 8 digits is the Honda assigned supplier number, and last 8 digits is a unique alpha-numeric number assigned by the supplier. Text Height: Serial Number = 3 LPB (Source = Supplier) Supplier Name & Address = 7-8 LPB right justified (Source = Supplier) Data Identifier (DI) = 5S Maximum Length: 18 Max Data Chars = 16 (Minimum 16) DI Chars = 2 Note 1: The human readable serial number should contain a hyphen between the 8th & 9th characters. (No hyphens should occur in the bar code.)
Label Purpose / Use: Used to identify a pallet containing multiple Mfg. Base Part Numbers.
9 - 10
Quick Receive Label Block Title = QUICK RECEIVE Data = The word "QUICK RECEIVE" will signify this is a Quick Receive Label Text Height = 3 LPB NOTE: NOT TO SCALE For correct measurements see the AIAG B-10 Guidelines Ship To Address Block Title = TO: Data = Supplier ship to name, address 1, address 2, city, state, zip code. (Source = 830, 850 or 862) Text Height = 7 LPB Note 3: The Ship To address should appear noticeably larger than the Ship From address. Ship From Address Block Title = FROM:
FROM:
Data = Supplier ship from name, address, city, state, zip code. (Source = 830, 850 or 862) Text Height = 8 LPB
XYZ COMPANY 345 SOUTH STREET COLUMBUS, OH 43221

SHIPMENT ID
DELTA / GPCS QUICK RECEIVE LABEL HONDA MAP (MEI 2A) C/O NEX QUICK 13000 U.S. Route 33 RECEIVE East Liberty, OH 43319
TO:
PROJECT NO. LOT NO.
Lot Number Block Title = LOT NO. Data = The term Honda Lot and a lot number assigned to this container/pallet. If the container/pallet is loaded by sequence order, the lot number associated with the lowest sequence number must be used (source 862) Text Height = 3 LPB minimum
12345678
PKG. ID MASTER (9S)
123456
196081501
Shipment ID (ASN #) Block Title = SHIPMENT ID Data = The Shipment Identification Number (SID). Same as the ASN number. The length must be 8 digits. (Source = Supplier) Text Height = 3 LPB Serial Number
12345678-12345678
Note 2: Print only ONE Lot Number per Quick Receive label. If there are multiple lot numbers on the pallet, any one lot number on that pallet will be sufficient.
Block Title = PKG ID UNIT (9S) Data = Serial number, which should match the serial number on the pallet label (Master/Mixed or Container label when the container is the pallet). Text Height: Serial Number = 3 LPB (Source = Supplier) Supplier Name & Address = 7-8 LPB right justified (Source = Supplier) Data Identifier (DI) = 9S Maximum Length: 18 Max Data Chars = 16 (Minimum 16) DI Chars = 2 Note 1: The human readable serial number should contain a hyphen between the 8th & 9th characters. (Hyphens must not be encoded in the bar code.)
Project Number Block Title = PROJECT NO. Data = Project number. Only used if available. (Source = 850 or 862) Text Height = 4 LPB
February 2007
Label Purpose / Use: Used by HAM Receiving to identify each pallets requirements.
February 2007 9 - 11
Delivery Batch Block Title = Delivery Batch Data = The word "Delivery Batch" will signify this is a Delivery Batch Label Text Height = 2 LPB NOTE: NOT TO SCALE For correct measurements see the AIAG B-10 Guidelines Honda Lot Block Title = Honda Lot Data = The term "Honda Lot" and a lot number assigned to this container/pallet. If the container/ pallet is loaded by sequence order, the lot number associated with the lowest sequence number must be used (Source=862) Text Height = 3 LPB
Delivery Batch Label Delivery Batch Honda Lot:

Batch# (T)
E19802029655
123456 5566
Delivery Batch Number Block Title = Batch # Data = The Delivery Batch number that is associated with this container/pallet. This number may appear on multiple containers/pallets. (Source=862) Text Height = 3 LPB Data Identifie (DI) = T Maximum Length: 7 Max Data Chars = 6 DI Chars = 1
Supplier Group Number Block Title = LOT # SPLR Data = Operational usage. If used, must consist of information that will help the supplier link all parts in the Delivery Batch together. This is a traceability number assigned to a group of items by the supplier. Text Height = 3 LPB Data Identifier: 1T Maximum Length: Supplier assigned
Lot # SPLR (1T)
Label Purpose / Use: Identifies a container/pallet that has part numbers packed together based on a Batch
9 - 12
February 2007
Label Information
This section should be reviewed and understood by users as well as system developers. This information will be critical to suppliers as they establish their business practices to meet Hondas Requirements.
Overview
The following chart describes how Honda uses the six types of DELTA/GPCS labels. Also detailed are when, how many, and where to apply labels.
Note
In the following chart, the word container is used to describe a Honda Returnable (such as B2, B, C2, D1), wire basket, cart, rack, or expendable packaging. In the following chart, the word pallet is used to describe an item that takes up floor space on a truck. A pallet could be a Honda returnable (such as A1, A3, A4), rack, basket, expendable pallet, or big box (when the box is the pallet).
February 2007
9 - 13
9 - 14 February 2007
Label Information Label Questions What is the purpose of each label type and why is each required? Container Labels
To identify parts and quantities in a container.
Master Labels
To identify a pallet containing two or more containers of the same part (which may have different design change levels) All container labels on the pallet will be linked to Manufacturing process or during shipment staging. Two labels per pallet (when meeting the criteria Why are they required, above).
Mixed Labels
Quick Receive Labels

To identify each pallets requirements to Honda Receiving: ASN, Project Number, Honda Production Lot Number and Ship To Address.
Delivery Batch Labels

Based on a common delivery/small lot batch number, this identifies: A container that includes a mix of two or more parts. A less than Standard Pack Quantity that At the completion of the build of each batch container.
Pack Labels
To identify a pallet containing two or more different part numbers. All containers on the pallet will be linked to the corresponding Mixed Label.
Used by Honda to link Pack Label to Container Label for tracking purposes. NOTE: The pack level is not supported by Hondas ASN structure, so this label is not present on the ASN. Manufacturing Process
When in the process should labels be applied? How many labels are required?
Manufacturing process.
Manufacturing process or during shipment staging.
During shipment staging.
Two labels per part per container.
Two labels per pallet (when meeting the criteria, Why are they required, above).
Two labels per pallet.
Two labels per batch per container.
Single Label per bag, or 2 per box if larger than 4 x 6 inch label.
Label Questions
Container Labels
For all container types: -Upper right hand corner on opposing sides. -Load truck so labels are facing both rear and front of truck. Note If stretch wrap is used, the label should be placed under the wrap. Note Bar code surface should be flat. Note AHM may have different requirements, please contact AHM for more information. -
Master Labels
For all pallet types: Upper right hand corner of pallet, below the Container Label. on opposing sides.
Mixed Labels
Pallet of parts: Upper right hand corner of pallet, below the container label. on opposing sides.

Pallet of parts: Upper right hand corner of pallet, below all other labels, on opposing sides. Load truck so labels are facing both the rear and front of the truck. Note If stretch wrap is used, the label should be placed on the outside of the wrap. Note Bar Code surface should be flat. Note If the trailer is the pallet, apply to the last pallet on trailer or 8x11 paper and attach to MPL.
Delivery Batch Labels

For all container types: -Immediately left of all Container Labels on the upper right hand corner of container. -Placed on opposing sides. -Place containers on pallet so that label is easily visible. Note If stretch wrap is used, the label should be placed under the wrap. Note Bar Code surface should be flat.
Pack Labels
-Place label in center of box or package. -Place labels on opposing sides if multiple labels are required
Where should the labels be placed?

Note Label placement may be modified based on NAL, Plant and Supplier agreement. [Also, see Packaging Guidelines.]
Load truck so labels are facing both the rear and front of the truck. Note If stretch wrap is used, the label should be placed on the inside of the wrap. Note Bar Code surface should be flat. Note If the trailer is the pallet, apply to the last pallet on trailer or 8x11 paper and attach to MPL.
Load truck so labels are facing both the rear and front of the truck. Note If stretch wrap is used, the label should be placed on the inside of the wrap.
Note Bar Code surface should be flat.
Note If the trailer is the pallet, apply to the last pallet on trailer or 8x11 paper and attach to MPL.
Label Application Process

This section should be reviewed and understood by users as well as system developers. This section can be used as a model when the supplier develops its business processes for applying and scanning labels.
Overview
The underlying principle of Hondas label application process is to insure the label matches the part. Honda prefers that suppliers apply the Honda Container Label as soon as the container is filled on the manufacturing line (line side labeling). Ideally, the EDI and Bar Coding System would interface with a Production Control System to allow a direct print and application of a single set of labels to the container. While line side labeling with its many variations may not be feasible for all suppliers, each supplier should control their labeling processes to prevent a label mishap to Honda. If you do not apply the Container label on the line, you may be required to submit a letter detailing why this is not feasible and the actions involved in preventing labeling mishaps (See the MPR Section of the Honda Quality Manual). Honda reserves the right to request labeling improvements in processes, manpower, and equipment if mishaps occur which put our plants at risk of line shutdown or part integrity. Suggestions on how to control your labeling processes or questions on line side labeling should be addressed to your Honda Buyer or to the Honda Systems Team at hondaedi@ham.honda.com.
Changes affecting the posting and control of the bar code database table can have a major impact to the validation process and may result in failed ASNs. Any system or label changes to meet line side labeling requirements must be approved by the NAL Systems Team before implementation.
9 - 16
February 2007
Chapter 9 Bar Code Labeling The following is a minimum list of items that should be addressed in the label creation and application process: 1. 2. 3. 4. 5. 6. 7. Security: Limiting access to label creation and the use of control logs. Traceability: Provide supplier lot number information to label. Part Verification: Insuring part matches label. Creating labels in Batches (if used): Limit label quantity and use control logs. Application: Insure labels are applied to the correct location. Rejection Procedures: Controls on eliminating poor labels or those tied to rejected parts. Small Lots: Use a separate small lot creation area, and provide limits on small lot inventory and storage time. 8. Quality: Insure Labels are clean, and meet proper format and scanning requirements. 9. Audits: Verify shipment accuracy and perform periodic checks on personnel and procedures. Note: This is a list of minimum process control points that need to be addressed and is not to be all inclusive. For details, please contact you Honda Buyer or Honda NAL Systems for a complete AYR Guide. The following two charts describe label application and the various steps to follow when preparing a shipment. The terminology may not match your system, but the basic functionality should be equivalent.
February 2007
9 - 17
9 - 18
Picking and Shipping Flow
PICK LIST Planned Load Creation

Created from 850 or 862 The planned load should reconcile to the 850 / 862
xxxxx xxxxxxxxx xxxxx xxxxx
Create Pick List

Based on the Planned Load
Pick & Scan Shipment

Stage order Link pallets to shipment (ASN) via scanning Input package type
QUICK RECEIVE
MASTER PACKING LIST

xxxxxxxxx xxxxx xxxxx
Send ASN
Send ASN after loading the trailer, as truck departs
Planned Load to ASN Reconciliation

Reconcile part number, quantity, Design Change level, order number
Create Quick Receive Label & MPL & BOL

Apply Quick Receive label(s) Done prior to loading the truck The MPL & BOL should be given to the truck driver Quick Receive and Master/Mixed label serial numbers must match
ASN Confirmation
Verify 997 received Verify 824 acknowledgement code Correct errors & re-send ASN if necessary (prior to arrival of truck at Honda receiving)
February 2007
February 2007
Planning and Production Flow

Production
Produce parts Use 830, 850, 862 for planning purposes
Print Container Labels

Data from 830, 850, 862, manufacturers database, etc. Design Change Level must match the actual part being shipped (which may differ from the order) Observe smart label concept (all label info linked to the serial number)
Master Label Delivery Batch Label Container Label
Package Parts & Apply Container & Delivery Batch Labels

Container label application preferred at the manufacturing location. Apply IPP tags if applicable Apply Delivery Batch label when shipping partial quantities or shipping multiple parts within a container.
Create and apply master/mixed label (to palletized product)

Link Container Serial Number to Master/Mixed Serial Number via scanning Could be done at manufacturing point, palletizing, shipping, etc. If applicable (see container is the pallet)
9 - 19
Part Number/Lot Number/DC Level Algorithm

System developers (hybrid and software providers) need to understand this section.
Overview
This section provides information concerning blank spaces, dashes, and formats for various Honda members. Formats for Bar Code Labels, Master Packing List and EDI transmissions are discussed. Special attention should be paid to the differences between AHM and the Honda manufacturing facilities.
Part Number Algorithm (for AHM)

THE FOLLOWING ALGORITHM APPLIES TO AHM ONLY
Note - There are no algorithms for Production Lot Number or DC Level for AHM, as these do not apply.
AHM will NOT follow the same algorithms that the Honda manufacturing facilities use. All Honda part numbers are up to 17 positions; trailing blanks will not be transmitted. Within the 17 positions, if no value exists, a blank space will hold that position. Part numbers will be transmitted from AHM to suppliers with dashes. Part numbers being returned to AHM in an ASN should also include dashes. The human readable portion of the bar code labels and Master Packing List must contain dashes and spaces identical to the EDI data. The bar coded data on the bar code labels must contain dashes and spaces the same as the EDI data. There is no published algorithm for AHM, unlike HAM, HCM and HMA.
9 - 20
February 2007
Rule #1: Mass Production & Prototype Part Number Algorithm

Rule #1 describes part numbers when positions 1 & 2 are less than 92. (See Rule #2 for part numbers with positions 1 & 2 greater than or equal to 92.) Honda Part numbers can be up to 29 positions; trailing blanks will not be transmitted. The color code always starts at position 19. Within the first 18 positions, if no value exists, a blank space will hold that position. Blanks are valid in: Position 9 (will always be blank or alpha character), Positions 14 through 17 (might be blank or contain a character on a case-bycase basis, Position 18 (always blank), Positions 19 through 29 (might be blank or contain a character, on a case-bycase basis.) Part numbers will be transmitted from Honda to suppliers without dashes or hyphens. Part Numbers being returned to Honda in an ASN should also be without dashes or hyphens. Dashes are required on the human readable portion of the Honda bar code labels and Honda Master Packaging List. Dashes or hyphens occur between: Positions 5 & 6, Positions 9 & 10, Positions 13 & 14,and Positions 15 & 16. Dashes should not be included in the scannable bar coded part number. Dashes or hyphens never replace values in specified positions. Position: 1-2 3 4 5-6 7 8 9-10 11 12 13-14 15-16 17 18 19 20 21 22 23 24 25 26 27 28 29
Blank = mass production A-Z = prototype
Always Blank
Color code starts here (if applicable)
May be filled in or blank (Case by case)
February 2007
9 - 21
Rule #2: Standard or Bulk Part Number Algorithm

Rule #2 describes part numbers when positions 1 & 2 are equal to or greater than 92. (See Rule #1 for part numbers with positions 1 & 2 less than 92.) Honda part numbers are up to 29 positions; trailing blanks will not be transmitted Part numbers using Rule #2 are always 12 positions. (Only use the first 12 positions. Position 13 through 29 will always be blank. Part numbers will be transmitted from Honda to suppliers without dashes or hyphens. Part numbers being returned to Honda in an ASN should also be without dashes or hyphens. Dashes are required on the human readable portion of the Honda bar code labels and Honda Master Packing List. Dashes or hyphens occur between: Positions 5 & 6 and Positions 10 & 11 Dashes or hyphens never replace values in specified positions. Position: 1 2 3 4 5-6 7 8 9 10-11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
Always blank use this as ex.
Honda Production Lot Number Algorithm

All positions will always have values. There are no dashes or hyphens in human readable fields. All Honda Productions Lot numbers are 12 positions. Different Honda facilities may use different 12-digit formats For Honda use only, should not be used for anything other than turnaround data
9 - 22
February 2007
Design Change (DC) Part Level Algorithm

The DC Level will be transmitted from Honda to suppliers without dashes and hyphens. DC Levels being returned to Honda in an ASN should also be without dashes and hyphens. Dashes are required, however, on the human readable portion of the Honda bar code labels and Honda Master Packing List. This algorithm describes where to place the dashes. All Honda Design Change levels are alphanumeric and up to 6 positions. Trailing blanks will not be transmitted. A blank is valid in only certain positions: Position 3 through 6 (might be blank or contain a character, on a case-bycase basis). Blanks may occur in positions 3 & 4 but not in 5 & 6. In this case, blank spaces will hold those positions. Dashes or hyphens occur between the following in human readable format only Positions 2 & 3, Positions 4 & 5. Dashes should not be in scan of a bar-coded part number. Dashes or hyphens never replace values in specified positions. Position: 12-34-56 May be filled in or blank (case-by-case)
February 2007
9 - 23
Container is the Pallet

1. 2. Honda suppliers who use the shipping container for both the container and pallet should read the overview. System developers (hybrid and software providers) need to understand this section. System design issues are involved.
Overview
Container is the Pallet is a term used by Honda to describe a single large container that is used as both a container and a pallet. It usually refers to a Honda returnable (such as A1, A3, etc.), but could be an expendable (type XX).
Bar Code Labeling a Container is the Pallet

This section describes how to label a Container is the Pallet and how the subsequent ASNs should be populated. There are two methods to label a container that is a pallet. They are: 1. 2. Use a Container Label, Master/Mixed Label and Quick Receive Label. Use a Container Label and Quick Receive Label.
Note - A container is a pallet including multiple part numbers must have a Container Label, Mixed Label and Quick Receive Label.
It is the suppliers choice which method to use. The following are examples of the logic you may use to decide which method is correct for your business: 1. Supplier A may choose choice 1 because they ship many types of containers, and they do not want to have a circumstance where you do not apply a Master Label, and in all other cases you do. In other words, make the label application process more consistent, with a goal of reducing errors. Supplier B may choose choice 2 because they only ship container is the pallet and they want to avoid the time and cost of applying the Master Label.
2.
9 - 24
February 2007
System Design
After establishing the method of labeling a Container is the Pallet, use the following key points during system design. (Label serial numbers transmitted in the ASN and possibly the scanning routine will be affected.) Using either method, the ASN Pallet Type (Tare Level LIN03) must be the key indicator of the returnable pallet/container code. The supplier must enter the actual returnable code in this field. The supplier has the option to enter this same value in the Container Level (LIN27), or they may enter XX. Examples of this can be found on pages 28-29 at the end of this chapter. If the supplier enters the same returnable code in both the Tare Level (LIN03) and Container Level (LIN27) and uses the Fixed Asset Tag values, the Tare LIN05 must equal the Container Level LIN25
Note - These elements (LIN05 & LIN25) are optional.

Method 1, (Container Label, Mast/Mixed Label and Quick Receive Label), the ASN Container Serial Number should NOT equal the Master/Mixed Label Serial Number. (Tare level REF02 Item Level REF02). [The Master/Mixed Label Serial Number should equal the Quick Receive Label as normal.] Method 2, (container Label and Quick Receive Label only), the ASN Container Serial Number should equal the Quick Receive Serial Number. (Tare level REF02 = Item level REF02.)
Trailer is the Pallet

Suppliers may be asked by the Honda Ordering Plant to designate the trailer as a pallet. This applies when a supplier ships an entire trailer load with a basic part configuration on multiple containers/racks that can be defined as a pallet. This method would require that all containers have appropriate container labels that are linked to a single Master/Mixed Label. A single Quick Receive Label would be generated and applied for the entire trailer. The Honda Ordering Plant will request that the Master/Mixed and Quick Receive be applied to the last pallet on the trailer, or an 8.5 by 11 sheet of paper attached to the Honda Master Packing List. The trailer is the pallet option must be approved by the Honda Ordering Plant.
Pack Label
Use of this label is restricted to those parts that are packaged as a unit and placed in a container which requires a 1S Container Label. Example: Parts placed in a bag then loaded into a container not used as a pallet. The Pack Label will not be represented in the ASN. The Pack Label should be applied when the package is first filled. The supplier is responsible for Supplier Lot Tracking between the Container Labels and the affiliated Pack Labels. Pack Serial Numbers must be unique, help insure FIFO, and not repeat within 18 months.
February 2007
9 - 25
Honda Returnable Label Serial Number

Honda suppliers and system developers need to understand this Overview section. System design issues are involved.
Overview
An accurate returnable container count on the ASN and MPL is critical. This will allow Honda to better manage the returnable container inventory and assure returnable containers are returned to suppliers in a timely and accurate fashion in relation to actual need. The section below describes Hondas requirements concerning the Returnable Container Label Serial Number.
Returnable Container Serial Number Description

Each Honda returnable (container, pallet, rack, etc.) should have a permanent serial number. If the serial number is missing, the supplier must be able to determine the container type using past experience, other containers as a guide, or the Honda Packaging Guidelines. Each serial number consists of a 7 to 16 digit code. The first 6 digits are a unique serial number. Digits 7 through 16 are the container type. The container type on the serial number may only contain the first 1 or 2 digits of the container type.
Returnable Container Serial Number Requirements

1. The container type must be returned to Honda in the ASN and MPL. The Corresponding ASN, the type (returnable or expendable) for each tare (pallet) and item (container) must be returned. For the corresponding MPL, a summary of the types (returnable only) must be included. The container type may be captured automatically during the scanning process when creating the ASN and MPL (See # 3). If multiple parts (container labels are in one returnable container, the returnable container must be counted only once on the ASN and MPL.
9 - 26
February 2007

2. Optionally, the full serial number can be returned on the ASN. This is not recommended unless your system needs the information for container count accuracy. Tips: The use of a bingo card to capture container type during the ASN creation (scanning) process can reduce time and is an alternative when the serial number is missing or damaged. Pulling the container type from a database is another timesaving possibility. If this technique is used, make sure the operator of the scanning device has the opportunity to override the data from the database if necessary (as in the case of a different container type being used).
3.
February 2007
9 - 27
Returnable Container Management Examples

Diagram
Container is the pallet with one part Part A
ASN Detail
Expected Supplier software result: Choice #1 or #2 Tare level A1 A1 LIN level Part A A1 XX #1 Hondas system will calculate one A1 container. This will be calculated based on a match of Tare container type to LIN container type. If match, count Tare level type. #2 Hondas system will calculate one A1 container. Expected Supplier software result: Choice #1 or #2 Tare level A1 A1 LIN level Part A A1 XX LIN level Part B A1 XX #1 Hondas system will calculate one A1 container. This will be calculated based on a match of Tare container type to LIN container type. If match, count Tare level type. #2 Hondas system will calculate a total of one A1 container.
MPL Returnable Container Summary

Supplier software requirement: A1 = 1
A1
Container is the pallet with multiple parts
Supplier software requirement: A1 = 1
Part A Part B
A1
9 - 28
February 2007

Returnable pallet with returnable containers
Part A D1 Part A D1
Expected Supplier software result: Tare level AP LIN level Part A D1 LIN level Part A D1 LIN level Part B D1 LIN level Part B D1 Hondas system will calculate a total of one AP container and four D1 containers.
Supplier software requirement: AP = 1 D1 = 4
Part B D1
Part B D1
AP
Returnable pallet with returnable containers Small Lot

Part A Part B D1 Part A D1 Part A D1 Part A D1
Expected Supplier software result: Tare level AP LIN level Part A D1 LIN level Part B XX LIN level Part A D1 LIN level Part A D1 LIN level Part A D1 Hondas system will calculate a total of one AP container and four D1 containers. The suppliers system must have the capability to list the actual container type only once when multiple parts are in a container. All other parts must use XX. Note: Hondas system cannot use the full returnable container serial number to calculate the number of returnable containers.
Supplier software requirement: AP = 1 D1 = 4
AP
February 2007
9 - 29
Chapter 10 Master Packing List

Master Packing List
February 2007
10 - 1
Chapter Contents
This chapter contains information concerning the Master Packing List (MPL). A detailed overview is given, along with the required data elements for using the MPL. Other pertinent information is given separately.
Table of Contents
Master Packing List .............................................................................................................................. 3 Purpose............................................................................................................................................... 3 Requirements...................................................................................................................................... 3 Ozone Depleting Substance ............................................................................................................... 4 Figure 10.1 Master Packing List for Manufacturing facilities (in response to 862 Ship Schedule) ........................................................................................................................................ 5 Figure 10.2 Master Packing List for Manufacturing facilities (in response to an 850 Purchase Order).............................................................................................................................. 6 Figure 10.3 - Master Packing List for AHM (in response to 862 Ship Schedule)............................ 7 Figure 10.4 Master Packing List for AHM (in response to 850 Purchase Order)......................... 8 Elements of the Master Packing List .................................................................................................. 9
10 - 2
February 2007
Master Packing List

Purpose
The purpose of the Master Packing List (MPL) is to identify the contents of an individual Honda shipment. Honda uses the MPL as: 1. 2. the source of the SCAC code, trailer number, supplier number, and ASN number when receiving a shipment, and a tool to confirm parts, part quantities, and returnable container quantities on the shipment.
Honda views the MPL as a summarized hard copy printout of the Advance Ship Notice (ASN) 856.
Requirements
The MPL format shown on pages 10-5 through 10-8 is mandatory. (There are no Honda specifications for character size.) The MPL format on pages 10-5 and 10-6 are to be used for all manufacturing plants except AHM. The MPL format on pages 10-7 and 10-8 are to be used by only AHM suppliers. The MPL size shall be 8.5 X 11 or 11 X 15 computer paper. The MPL shall be attached to the BOL and given to the driver. A copy of the MPL should also be placed inside the trailer, attached to the last product placed onto the trailer. In the event of any differences in items labeled 1 through 15 on pages 10-5 and 10-8, the supplier must print a new MPL (and create a new ASN.) Do not mix Purchase Order (i.e. 850) and Ship Schedule (i.e. 862) Shipments on the same Master Packing List. The MPL should be created during the ASN generation process: after scanning to create the ASN after entering the trailer and SCAC codes during the same process of Quick Receive label creation before the truck leaves to dock before the ASN is transmitted. The delivery quantity (for each part number) on the MPL should be a total quantity. When a shipment includes multiple containers with the same part number, color, DC level, and shipment authorization, the item should only be listed on the MPL once, with a total quantity. Please review the Quality Assurance Program chapter (Chapter 8) for testing requirements concerning the Master Packing List. DSPS suppliers (Tier 2 and higher suppliers) are required to create an approved Honda Master Packing List February 2007
10 - 3
Ozone Depleting Substance

The Ozone Depleting Substance (ODS) label should be affixed in the most costeffective method possible. Hard coding in your system is not required, if manual means are available. Manual means include: stamping using a pre-printed label pre-printing on paper stock tying the label on after the MPL has been generated.
10 - 4
February 2007
Master Packing List Specifications

The example in Figure 10.1 is a Master Packing list for all manufacturing plants, except AHM, in response to an 862 Ship Schedule. Match the numbers in this MPL example to the numbers starting on page 10-9.
Figure 10.1 Master Packing List for Manufacturing facilities (in response to 862 Ship Schedule)
MASTER PACKING LIST
Plant ID. NO. SHIP TO NO./ WH: 200 750
1
SHIP TO NAME :
3
4 6
HONDA, MAP, MEI 2A C/O NEX
2 5
SUPPLIER #:
ASN/SID (2S) 12345678
SUPPLIER NAME:
PLANNED SHIP DATE: PLANNED SHIP TIME:
8 10
or or
9 11

12
10:00
SCAC:
CHAM 245
PROJECT NO.
123456
13 14
TRAILER NO.:
15 16 17 18

19 20
PART NUMBER
COLOR
DELIVERY QUANTITY
21
YR169L12345 * 53320-SH3- G001 53320-SH3- G100-M1 YR169L12345 YR169L12345 53320-SH3- A000-M1 53320-SH3- A100- -01 YR169L12345 53320-SH3- J000-M1-01 YR169L12345
01- 00-M100-M100- -01 00-M1-01
S-123456 S-123457 P-123458 S S-123459 P-123410 S
900 900 900 900 900

22
LOT NUMBERS
V19604001001,V19604002001,V19604003001 V29604001001,V29604002001,V29604003001
24
CONTAINER SUMMARY TYPE B C C2 QTY

23
6 3 10
Page 1 of 1
25
* IPP Tag Enclosed
February 2007
10 - 5

The example in Figure10.2 is a Master Packing list for all manufacturing plants except for AHM, in response to an 850 Purchase Order. Match the numbers in this MPL example to the numbers starting on page 10-9.
Figure 10.2 Master Packing List for Manufacturing facilities (in response to an 850 Purchase Order)
MASTER PACKING LIST
Plant ID. NO. SHIP TO NO./ WH: 200 750
1
SHIP TO NAME :
HONDA, MAP, MEI 2A C/O NEX
2 5
3
4 6
SUPPLIER #:
ASN/SID (2S) 12345678
SUPPLIER NAME:
8 10
or or
9 11

12
10:00
SCAC:
CHAM 245
PROJECT NO.
123456
13 14
TRAILER NO.:
15
16 17 18

19 20
PART NUMBER
COLOR
DELIVERY QUANTITY
21
* 53320-SH3- G001
YR169L12345 01- -
P-1234560001
60
LOT NUMBERS
22
24
CONTAINER SUMMARY TYPE QTY

23
* IPP Tag Enclosed
Page 1 of 1
25
10 - 6
February 2007

The example in Figure 10.3 is a Master Packing list for AHM in response to an 862 Ship Schedule. Match the numbers in this MPL example to the numbers starting on page 10-9.
Figure 10.3 - Master Packing List for AHM (in response to 862 Ship Schedule).
MASTER PACKING LIST

Plant ID. NO. SHIP TO NO./ WH: AHM 90
1
SHIP TO NAME :
3
4 6
American Honda Receiving Warehouse
2 5
SUPPLIER #:
ASN/SID (2S) 12345678
SUPPLIER NAME:
8 10
or or
9 11
PLANNED DELIVERY DATE :
02/04/96
PLANNED DELIVERY TIME:

12
10:00
SCAC:
CHAM 245
PROJECT NO.
123456
13 14
TRAILER NO.:
15
16 17 18

19 20
PART NUMBER
COLOR
DELIVERY QUANTITY
21
* 53320-SH3- G001 WIRE HARN. L CABIN 53320-SH3- A000-M1 SW ASSY, CRUISE MAIN
S-123456
26
900 900
S-123457
LOT NUMBERS
22
24
CONTAINER SUMMARY TYPE QTY

23
* IPP Tag Enclosed
Page 1 of 1
25
February 2007
10 - 7

The example in Figure 10.4 is a Master Packing list for AHM in response to an 850 Purchase Order. Match the numbers in this MPL example to the numbers starting on page 10-9.
Figure 10.4 Master Packing List for AHM (in response to 850 Purchase Order)
MASTER PACKING LIST
Plant ID. NO. SHIP TO NO./ WH: AHM 90
1
SHIP TO NAME :
3
4
American Honda Receiving Warehouse
2 5
SUPPLIER #:
ASN/SID (2S) 12345678

6
SUPPLIER NAME:
PLANNED SHIP PLANNED SHIP
8 10
or or
9 11 12
PLANNED DELIVERY DATE 02/04/96 PLANNED DELIVERY TIME:

SCAC: : CHAM 245
PROJECT NO.
123456
13 14
TRAILER NO.:
15
16 17 18

20 19
PART NUMBER
COLOR
DELIVERY QUANTITY
21
* 53320-SH3- G001 WIRE HARN. L CABIN 53320-SH3- A000-M1 SW ASSY, CRUISE MAIN
26
P-6543210001 P-6543210002
900 900
LOT NUMBERS
22
24
TYPE
CONTAINER SUMMARY QTY

23
* IPP Tag Enclosed

10 - 8
Page 1 of 1
25
February 2007
Elements of the Master Packing List

No.
1
Details
Name = Plant Identification Number Data = Three digit code Purpose = Identifies the Honda plant for which the parts were ordered ASN (856) data location = N104 (Pos. 220) Note: An additional MPL and ASN must be generated if this number changes. Name = Ship to Name Data = Consists of the Ship to Name above the Ship to Address Information 1 Purpose = Identifies the ship to location ASN (856) data location = N/A Note: An additional MPL and ASN must be generated if this name changes. Name = Ship to Number / Warehouse Data = Two to eight digit character code Purpose = A Honda code that indicates the ship to location ASN (856) data location = N104 (Pos. 285) Note: An additional MPL and ASN must be generated if this number changes. Name = Supplier Number (Text must be bold) Data = Hondas six digit supplier number and 2 digit location code (Text must be bold) Purpose = Identifies the shipper ASN (856) data location = N104 (Pos. 287) Note: An additional MPL and ASN must be generated if this number changes. Name = Advance Ship Notice / Shipment Identification Number (Text must be bold) Data = 8 character value assigned by the supplier (must be unique within a year) (Text must be bold) Purpose = Identifies the shipment ASN (856) data location = BSN02 (Pos. 020) Note: An additional MPL and ASN must be generated if this number changes.
Modifiable by Supplier?
No
Source of Data
850 N104 (Pos. 310) or 862 N104 (Pos. 050)
No
830 N102 (Pos. 320) & 830 N301 (Pos. 340) or 850 N102 (Pos. 350) & 850 N301 (Pos. 370) or 862 N102 (Pos. 130) & 862 N301 (Pos. 140) 850 N104 (Pos. 350) or 862 N104 (Pos. 130)
No
No
850 N104 (Pos. 425) or 862 N104 (Pos. 115)
Yes
Supplier assigned
Name = Supplier Name (Text must be bold) Data = Supplier name as provided by Honda (Text must be bold) Purpose = Identifies the shipper ASN (856) data location = na Note: An additional MPL and ASN must be generated if this number changes.
Name = ASN number, Bar code format Data = 8 character value assigned by the supplier (must be unique within a year) Purpose = Identifies the shipment ASN (856) data location = BSN02 (Pos. 020) Data Identifier = 2S Note #1: This bar code is OPTIONAL Note #2: An additional MPL and ASN must be generated if this number changes.
No
850 N102 (Pos. 425) or 862 N102 (Pos. 115)
Yes
Supplier assigned
Continued on next page
February 2007
10 - 9
Elements of the Master Packing List (contd)

No.
8
Details
Name = Planned Ship Date Data = Planned Shipment date Purpose = Identifies the date Honda requests the shipment to be made ASN (856) data location = na When to use: If in response to an 850, send when SCH05 = 010 (Requested Ship) or if in response to an 862, send when DTM01 (Pos. 090) = 010 (Requested Ship) Note: Items 8 & 9 are mutually exclusive. One or the other must be used, not both. Name = Planned Delivery Date Data = Planned delivery date Purpose = Identifies the date Honda requests the shipment be delivered ASN (856) data location = na When to use: If in response to an 850, send when SCH05 = 002 (Deliver Requested) or if in response to an 862, send when DTM01 (Pos. 090) = 002 (Deliver Requested) Note: Items 8 & 9 are mutually exclusive. One or the other must be used, not both. Name = Planned Ship Time Data = Planned shipment time Purpose = Identifies the time Honda requests the shipment to be made ASN (856) data location = na When to use: If in response to an 850, send when SCH05 = 010 (Requested Ship) or if in response to an 862, send when DTM01 (Pos. 090) = 010 (requested Ship) Note: Items 10 & 11 are mutually exclusive. One or the other must be used, not both. Name = Planned Deliver Time Data = Planned delivery time Purpose = Identifies the time Honda requests the shipment to be delivered ASN (856) data location = na When to Use: If in response to an 850, send when SCH05 = 002 (Deliver Requested) or if in response to an 862, send when DTM01 (Pos. 090) = 002 (Deliver Requested) Note: Items 10 & 11 are mutually exclusive. One or the other must be used, not both. Name = SCAC (Text must be bold) Data = Four digit SCAC code Standard Carrier Alpha Code. (Text must be bold.) Purpose = SCAC of the freight carrier ASN (856) data location = TD503 (Pos. 120) Note #1: For expedite shipments, if a SCAC code is not provided by Honda, use a SCAC of XXXX. Note #2: An additional MPL and ASN must be generated if this number changes.
No
Source of Data
850 SCH06 (Pos. 295) or 862 DTM02 (Pos. 090)
No
850 SCH06 (Pos. 295) or 862 DTM02 (Pos. 090)
10
No
850 SCH07 (Pos. 295) or 862 JIT02 (Pos. 110)
11
Yes
850 SCH07 (Pos. 295) or 862 JIT02 (Pos. 110)
12
No
850 TD503 (Pos. 430) or 862 TD503 (Pos. 130)
10 - 10
February 2007

No.
13
Details
Name = Project No. Data = 1 6 digit alphanumeric Purpose = The business purpose for the project number will be defined at a later date. (Future Honda system enhancement). ASN (856) data location = LIN11 (Pos. 420) Note: An additional MPL and ASN must be generated if this number changes. Name = Trailer No. (Text must be bold) Data = 1 10 character alphanumeric trailer identifier. (Text may be bold.) Purpose = Identifies the actual number of the trailer picking up the parts at the supplier. ASN (856) data location = TD303 (Pos. 130) Note: An additional MPL and ASN must be generated if this number changes. Note: For mass production shipments, the trailer # must always be provided. In the case of an expedite where XXXX has been used as the SCAC then the trailer # or PRO # must be provided in the Trailer No. field. If sufficient space permits, the name of the expediting carrier should be included after the trailer/Pro#. (Data on the MPL should be the same as what is on the ASN.) Name = Bill of Lading (BOL) No. (Text may be bold.) Data = 1 12 character alphanumeric BOL number. (Text may be bold). Purpose = The Supplier and Carrier contract number. ASN (856) data location = REF02 (Pos. 150) Note: An additional MPL and ASN must be generated if this number changes. Name: Part Number Data = Hondas Manufacturing Base Part Number (MBPN) less the color first 17 positions of the MBPN Purpose = To identify part number(s) contained within the shipment covered by this Master Packing List ASN (856) data location = LIN03 (Pos. 420) Sort = Shall be in numerical order, sorting alpha characters before numeric characters Dashes = Dashes and spaces shall be included as stated in chapter 9. Name = Color Data = Hondas color code located in the Manufacturing Base Part Number (MBPN) positions 18 thru 29 of the MBPN. If there is no color-code, leave this area blank. AHM will not transmit a color code. Purpose = To identify the color of the part number(s) contained within the shipment covered by this Master Packing List ASN (856) data location = LIN03 (Pos. 420) Dashes =There are no dashes within the color code.
No
Source of Data
850 PO113 (Pos. 010) or 862 LIN11 (Pos. 010)
14
Yes
Supplier
15
Yes
Supplier
16
No
850 N104 (Pos. 310) or 862 N104 (Pos. 050)
17
No
850 PO107 (Pos. 010) or 862 LIN03 (Pos.010)
February 2007
10 - 11

No.
18
Details
Name = Design Change Level Data = Hondas 1 to 6 character design change level Purpose = To identify the actual design change level of the parts being shipper. If there is no design change level, leave this area blank. ASN (856) data location = LIN05 (Pos. 420) Dashes = Dashes and spaces shall be included as stated in Chapter 9. Note: This field must be present for part numbers with the first two digits less than 92 (HAM, HMA, HCM only). Name = Shipment Authorization Number Data (1) = A single letter shipment type designator (S = Ship Schedule, P = Purchase Order) Data (2) = The Ship Schedule number or Purchase Order Line ID Purpose = The Honda shipping authorization number. For a Purchase Order this is the PO Line ID. For a Ship Schedule, this is the Part Level Ship Schedule Number. ASN (856) data location = LIN09 (Pos. 420) if in response to an 862 (Ship Schedule) ASN (856) data location = LIN13 (Pos. 420) if in response to an 850 (Purchase Order) Dashes = A dash shall be placed between the shipment type and the authorization number. Note: A Ship Schedule and Purchase Order are never shipped on the same MPL. Note: When the same Part number and D/C combinations are shipped against two Purchase Orders/Order Numbers, two line items must be present. Name = Delivery Quantity Data = The total quantity for this combination of part number, color, DC level and shipment authorization on this ASN. Purpose = To identify the quantity shipped. ASN (856) data location = SN102 (Pos. 430) Note: The Delivery Quantity should be a total. When a shipment includes multiple containers with the same part number, color, DC level and shipment authorization, the item should only be listed on the MPL once, with a total quantity. Note: If there are multiple shipment authorization numbers for the same part number/color/DC level, there should be a line item for each different shipment authorization number. Name = Verification Column Data = None. There should be blank lines input here, corresponding to each delivery quantity. Purpose = Used for verification purposes. ASN (856) data location = na
No
Source of Data
850 PO109 (Pos. 010) or 862 LIN05 (Pos. 010)
19
No
850 PO101 (Pos. 010) or 862 LIN09 (Pos. 010) or 862 REF02 (Pos. 137)
20
Yes
Supplier
21
No
N/A
10 - 12
February 2007

No.
22
Details
Name = Lot Numbers Data = The actual Honda Production Lot Number(s) applicable to the part numbers on the MPL. Purpose = To identify the lot numbers shipped. ASN (856) data location = LIN07 (Pos. 420) Sort = To be listed in numerical order left to right, sorting alpha characters before numeric characters. Note #1: The Lot Numbers section only applies if HAM transmits the Lot Numbers on the Ship Schedule (862). Note #2: The Lot Numbers header is not required if there is no Lot Number data. Note #3: Honda provides a Honda Production Lot Number (Lot Number) and Small Lot Batch number for Small Lot orders. Only the Honda Production Lot Number should be returned on the MPL. Note #4: Honda provides a Honda Production Lot Number (Lot Number) and Sequence Number for Sequence orders. Only the Honda Production Lot Number should be returned on the MPL. Note #5: Only list a Lot Number once, even if tied to more than one part number. Note #6: There is no correlation between the order of the Lot numbers and the order of the Part Numbers.
No
Source of Data
862 REF02 (Pos. 120)
23
Name = Returnable Summary Data = For shipments containing returnable container(s) (Honda modular or other), the supplier shall list a summary of container type and quantity for that shipment. (See the Honda Packaging and Transportation Guidelines for information on Hondas Returnable Packaging and Containers.) Purpose = To identify the returnable containers shipped to Honda. This will allow Honda to return the appropriate amount of containers to the supplier. ASN (856) data location = LIN03 (Pos. 395) [Tare level] and /or LIN27 (Pos. 420) [Item level] Sort = No sort requirements. Note #1: The summary shall be either at the bottom of the MPL or on a separate page attached to the MPL. Note #2: Non-returnable (codeXX in the EDI data) should not be listed. Note #3: The RETURNABLE SUMMARY, TYPE and QTY headers are not required if there is no returnable data. Note #4: If multiple parts (container labels) are in one container, the returnable container must be counted only once on the ASN or MPL.
Yes
850 TD105 (Pos. 296) or 862 TD105 (Pos. 160)
February 2007
10 - 13

No.
24
Details
Name = IPP (Initial Production Parts) Tag Data (1) = The text *IPP Tag Enclosed must be listed where indicated if an IPP tag is included in the shipment. Data (2) = The asterisk * beside a part number indicates an IPP tag is attached to that part for this shipment. Purpose = To notify Honda of part or package change(s). ASN (856) data location = LIN14 through 21 (Pos. 420) Note: The text *IPP Tag Enclosed is optional if there is no IPP Tag included in that shipment. Name = Page Number Data = Page number and total pages in this MPL.. Use the format in the diagram on page 10-5. Purpose = To help Receiving verify all pages of the MPL are accounted for. ASN (856) data location = na Note: The page number is optional, but highly recommended. Name = Description Data = The corresponding part numbers description. Purpose = To assist AHM receiving ASN (856) data location = na Note #1: The description should be the only item on the line and should appear under its corresponding part number. Note #2: The description should be indented approximately 5 spaces. Note #3: The description is only included on AHM MPLs.
No
Source of Data
N/A
25
No
N/A
26
No
850 PO111 (Pos. 010) or 862 LIN07 (Pos. 010)
10 - 14
February 2007
Chapter 11 Invoice (810)

Invoice (810)
September 2007
11 - 1
Chapter Contents
This chapter contains information and procedures for using the Honda Invoice transaction. Transactions specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 3 Transactions Covered......................................................................................................................... 3 Application Standards & Conventions ................................................................................................ 3 Mapping .............................................................................................................................................. 3 Exceptions/Clarifications..................................................................................................................... 3 Schedule ............................................................................................................................................. 3 Specifications ...................................................................................................................................... 3 Back-Up Procedure............................................................................................................................. 3 Business Purpose ................................................................................................................................ 4 Transaction Specification Information ............................................................................................... 5 Transaction Specifications.................................................................................................................. 6 Functional Group ID=IN .................................................................................................................. 6 ST Transaction Set Header............................................................................................................. 7 BIG Beginning Segment for Invoice ................................................................................................ 8 CUR Currency ................................................................................................................................. 9 N1 Name ....................................................................................................................................... 10 N3 Address Information................................................................................................................. 11 N4 Geographic Location................................................................................................................ 11 PER Administrative Communications Contact .............................................................................. 12 ITD Terms of Sale/Deferred Terms of Sale................................................................................... 13 IT1 Baseline Item Data (Invoice) ................................................................................................... 13 PID Product/Item Description ........................................................................................................ 14 REF Reference Identification ........................................................................................................ 14 DTM Date/Time Reference ........................................................................................................... 15 TDS Total Monetary Value Summary ........................................................................................... 15 TXI Tax Information....................................................................................................................... 16 CTT Transaction Totals................................................................................................................. 16 SE Transaction Set Trailer ............................................................................................................ 17 Replacement Logic............................................................................................................................. 18 Replacement: .................................................................................................................................... 18 Retransmission: ................................................................................................................................ 18
11-2
September 2007
Transaction Description
Transactions Covered
Invoice (Transaction Set 810), abbreviated "IN".
Application Standards & Conventions

The 810 set is based upon the ANSI ASC X12 Version Release 004010 document.
Mapping
A list of the Invoice business data elements and how they are transmitted via EDI Standards is provided in the Transaction Specifications section.
Exceptions/Clarifications
There are no Exceptions to ANSI Standards in this Transaction Description.
Schedule
The Invoice can be transmitted daily.
Specifications
It is possible for Honda to transmit multiple Invoices within one envelope. This means that there may be multiple transaction sets (STSE header/trailer segments) within one interchange envelope (ISA-IEA header/trailer segments). Honda transmits all EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up Procedure
In the event of a failure of Electronic Data Interchange, it is the responsibility of the sending party to transmit the contents of any pending Transmission to the receiving party using a method of non-EDI transmission, which is timely, reasonable, and appropriate under the circumstances.
September 2007
11 - 3
Business Purpose
The Honda Invoice (ANSI 810) transaction set is used in the following way: DSPS relationship -- Upon receipt of a tier 2 (or higher) ASN, Honda will use the Invoice (810) to charge or provide notification of a future payment adjustment to the lower tier supplier for the parts they have received. Honda uses the Invoice as an outbound document only. The Invoice plays an important role in the Evaluated Receipt Settlements (ERS) process.
FREQUENCY: Upon receipt of an ASN representing a DSPS shipment or as required. TRANSMITTED TO: 1. 2. OEM Suppliers Service Parts Suppliers
TRANSMITTED FROM: Honda
11-4
September 2007
Transaction Specification Information

The following Transaction Specifications consist of two sections: 1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality.
Note - The Req. Des. for the first segment in a loop is also used for that corresponding loop.
2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column:
M = Mandatory X = Conditional O = Optional

The second column:
ID = Identifier (a unique value from a predefined list from ANSI) DT = Date TM = Time AN = Alphanumeric R = Numeric with a variable decimal place Nx = Numeric with x decimal places The third column: x/y, where x = the minimum number of digits for this element and y = the maximum number of digits for this element.
September 2007
11 - 5
Transaction Specifications
Functional Group ID=
IN
Req. Des. M M M Loop Repeat
Heading:
Pos. No. 010 020 040 Seg. ID ST BIG CUR Name Transaction Set Header Beginning Segment for Invoice Currency LOOP ID - N1 Must Use 070 090 100 120 Must Use 130 N1 N3 N4 PER ITD Name Address Information Geographic Location Administrative Communications Contact Terms of Sale/Deferred Terms of Sale M O O O M 1 1 1 3 1 Max.Use 1 1 1 >1
Must Use Must Use Must Use
Detail:
Pos. No. Must Use 010 Seg. ID IT1 Name LOOP ID - IT1 Baseline Item Data (Invoice) LOOP ID - PID Must Use Must Use 060 120 150 PID REF DTM Product/Item Description Reference Identification Date/Time Reference M M O 1 1 1 Req. Des. M Max.Use 1 1 Loop Repeat 200000
Summary:
Pos. No. 010 020 Must Use Must Use 070 080 Seg. ID TDS TXI CTT SE Name Total Monetary Value Summary Tax Information Transaction Totals Transaction Set Trailer Req. Des. M O M M Max.Use 1 1 1 1 Loop Repeat
Must Use
11-6
September 2007
ST Transaction Set Header

Position: Loop: Level: Usage: Max Use:
010 Heading Mandatory 1 Data Element Summary Data Element Name

143 Transaction Set Identifier Code
Ref. Des.
Must Use ST01
Attributes
M ID 3/3
Valid codes are listed below: 810 Invoice

Must Use ST02 329 Transaction Set Control Number M AN 4/9
This number will be unique (within a transaction set) and ascending. It may be sequential.
September 2007
11 - 7
BIG Beginning Segment for Invoice

020 Heading Mandatory 1 Data Element Summary

Data
Ref.
Des.
Must Use Must Use BIG01
Element Name
373 Date
Attributes
M DT 8/8
This is the accounting invoice date.

BIG02 76 Invoice Number M AN 1/22
- For HCM, HMA, HPE, HPG, HSC, and HTM this will be the GPCS transaction number. - For HAM this will be the material release number
Must Use BIG07 640 Transaction Type Code M ID 2/2
Valid codes are listed below: CN Credit Invoice - Indicates a separate payment by Honda CR Credit Memo - Financial adjustment (payment addition) that will be included in a future payment. DI Debit Invoice - Indicates a separate payment by a supplier DR Debit Memo - Financial adjustment (payment deduction) that will be included in a future payment.
Must Use BIG08 353 Transaction Set Purpose Code M ID 2/2
Valid codes are listed below: 05 Replace
11-8
September 2007
CUR Currency
040 Heading Mandatory 1 Data Element Summary Data Element Name

98 Entity Identifier Code
Ref. Des.
Must Use CUR01
Attributes
M ID 2/3
Valid codes are listed below: SE Selling Party

Must Use CUR02 100 Currency Code M ID 3/3
Code (Standard ISO) for country in whose currency the charges are specified. Examples of some of the valid codes are listed below: 'CAD' = CANADIAN DOLLAR 'JPY' = JAPANESE YEN 'USD' = U.S. DOLLAR MXN = MEXICAN PESO
September 2007
11 - 9
N1 Name
Position: Loop: Level: Usage: Max Use: 070 N1 Mandatory Heading Mandatory 1
Data Element Summary

Must Use Ref. Des. N101 Data Element Name 98 Entity Identifier Code Attributes M ID 2/3
N102
93
N103
66
N104
67
Valid codes are listed below: SE Selling Party ST Ship To SU Supplier/Manufacturer Name X AN 1/35 - For SE, this will be the Honda plant name selling the parts - For SU, this will be the suppliers name who shipped the parts - For ST, this will be the suppliers name who received the parts Identification Code Qualifier X ID 1/2 Valid codes are listed below: 91 Assigned by Seller or Seller's Agent Identification Code X AN 3/8 - For SE, this will be the Honda Plant code. This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM = HAM - Marysville Auto Plant (MAP-used for GPCS) HAM - East Liberty Auto Plant (ELP-used for GPCS) HAM - Marysville Motorcycle Plant (MMP-used for GPCS) HAM - International Parts Supply (IPS-used for GPCS) HAM - Service Parts Procurement (IPS-used for GPCS) HAM - International Parts Supply for Honda de Mexico (IPS-for GPCS) HAM - Anna Engine Plant (AEP-used for GPCS) American Honda Motor Co., Inc. Honda of Canada Mfg. Honda de Mexico Honda Manufacturing of Alabama Honda Manufacturing of Indiana Honda Power Equipment Honda Precision Parts Georgia Honda of South Carolina Honda Transmission
- For SU, this will be the Honda supplier code for the supplier who shipped the parts - For ST, this will be the Honda supplier code for the supplier who received the parts
11-10
September 2007
N3 Address Information
Position: Loop: Level: Usage: Max Use: Notes:
090 N1 Mandatory Heading Optional 1 This segment provides a street address. Data Element Summary
Must Use
Ref. Des. N301 N302
Data Element Name 166 Address Information 166 Address Information
Attributes M AN 1/30 O AN 1/30
N4 Geographic Location
100 N1 Mandatory Heading Optional 1
Data Element Summary Ref. Des.

N401 N402 N403 N404
Data Element Name

19 156 116 26 City Name State or Province Code Postal Code Country Code
Attributes
O O O O AN 2/30 ID 2/2 ID 3/10 ID 2/3
September 2007
11 - 11
PER Administrative Communications Contact

Position: Loop: Level: Usage: Max Use: 120 N1 Mandatory Heading Optional 3

Must Use Ref. Des. PER01 Data Element Name 366 Contact Function Code Attributes M ID 2/2
PER02 PER03
93 365
PER04 PER05
364 365
PER06 PER07
364 365
PER08 PER09
364 443
Valid codes are listed below: AD Accounting Department - Honda Accounting Department contact. AE Corporate Purchasing Agent - Honda CPG contact BD Buyer Name or Department - Honda buyer SH Shipper Contact - Ship-from supplier contact. SU Supplier Contact - Ship-to supplier contact. Name O AN 1/35 Telephone Number Qualifier X ID 2/2 Valid codes are listed below: TE Telephone Telephone Number X AN 1/15 Fax Number Qualifier X ID 2/2 Valid codes are listed below: FX Facsimile Fax Number X AN 1/15 E-Mail Qualifier X ID 2/2 Valid codes are listed below: EM Electronic Mail E-Mail Address X AN 1/80 Honda Plant ID O AN 3/8 This is the Honda code number for the logistical company which the stated contact represents. Please refer to N104 (Position 070) for a complete list of codes.
11-12
September 2007
ITD Terms of Sale/Deferred Terms of Sale

Position: Loop: Level: Usage: Max Use: 130 Heading Mandatory 1

Ref. Des. ITD02 Data Element Name Attributes 333 Terms Basis Date Code O ID 1/2 Valid codes are listed below: 3 Invoice Date 338 Terms Discount Percent O R 1/6 Discount percent. (Zero means no discount.) 351 Terms Discount Days Due X N0 1/3 Number of days in the terms discount period by which payment is due if the terms discount is earned. 446 Terms Net Due Date O DT 8/8 386 Terms Net Days O N0 1/3 Number of days until total Invoice amount is due.
ITD03 ITD05
ITD06 ITD07
IT1 Baseline Item Data (Invoice)

Position: Loop: Level: Usage: Max Use: 010 IT1 Mandatory Detail Mandatory 1

Must Use Must Use Must Use Ref. Des. IT101 Data Element Name 350 Assigned Identification Attributes M AN 1/20
IT102 IT103
358 355
This will be the Tier 2 ASN, Packing Slip, Invoice or BOL number. Quantity Invoiced M R 1/10 Unit or Basis for Measurement Code Valid codes are listed below: EA Each Unit Price Basis of Unit Price Code M ID 2/2
Must Use Must Use
IT104 IT105
212 639
M M
R 1/17 ID 2/2
Valid codes are listed below:

CP Current Price (Subject to Change)
September 2007
11 - 13
PID Product/Item Description

060 PID Mandatory Detail Mandatory 1
Ref. Des.
Must Use Must Use PID01
Data Element Summary Data Element Name

349 Item Description Type
Attributes
M ID 1/1
F
PID05 352 Description
Free-form
M AN 1/30
REF Reference Identification

120 IT1 Mandatory Detail Mandatory 1
Ref. Des.
Must Use REF01

128 Reference Identification Qualifier
Attributes
M ID 2/3
Valid codes listed below: PM Part Number

Must Use REF02 127 Part Number M AN 1/30
11-14
September 2007
DTM Date/Time Reference

150 IT1 Mandatory Detail Optional 1 This segment will provide the ship date/time of the parts shipped by the tier 2 suppliers. Data Element Summary
Ref. Des.
Must Use DTM01
Data Element Name

374 Date/Time Qualifier
Attributes
M ID 3/3
Valid codes are listed below: 011 Shipped

DTM02 DTM03 373 337 Date Time X X DT 8/8 TM 4/4
TDS Total Monetary Value Summary

010 Summary Mandatory 1

Must Use TDS01
Data Element Name

610 Amount
Attributes
M N2 1/15
The grand total of the invoice (example: Honda transmits 123456, supplier should translate as $1,234.56).
September 2007
11 - 15
TXI Tax Information

020 Summary Optional 1 This segment will only be used by HCM. Data Element Summary
Ref. Des.
Must Use TXI01
Data Element Name

963 Tax Type Code
Attributes
M ID 2/2
Valid codes are listed below: GS Goods and Services Tax

TXI02 TXI03 TXI09 782 954 325 Monetary Amount Percent Tax Identification Number X X O R 1/18 R 1/10 AN 1/20
CTT Transaction Totals

Ref. Des.
Must Use CTT01

354 Number of Line Items
Attributes
M N0 1/6
The accumulation of the number of IT1 segments.
11-16
September 2007
SE Transaction Set Trailer


Must Use Must Use SE01 SE02
Data Element Name

96 329 Number of Included Segments Transaction Set Control Number
Attributes
M M N0 1/10 AN 4/9
September 2007
11 - 17
Replacement Logic
Replacement:
Honda sends the 810 as a replacement document. The 810 purpose code transmitted in the BIG08 element is always 05, replace. A document may be replaced for various reasons, including replacing an error in a previous document. Supplier systems should have the capability to compare successive incoming Invoices and replace items that are identical for change points listed below. Replacement of items from the new 810 should be based upon a match of: Invoice Number, BIG02 (Position 020)
Retransmission:
Honda can retransmit the 810 document. Retransmission will only occur when the supplier requests that Honda resend the EDI document. This is typically because the supplier had some problem in the translation processing. A retransmitted document can be overlaid based upon the same logic as the replacement logic above.
11-18
September 2007
Chapter 12 Remittance Advice (820)

Remittance Advice (820)
September 2007
12 - 1
Chapter Contents
This chapter contains information and procedures for using the Honda Remittance Advice transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 4 Transaction Covered........................................................................................................................... 4 Application Standards and Conventions............................................................................................. 4 Mapping .............................................................................................................................................. 4 Exceptions/Clarifications..................................................................................................................... 4 Schedule ............................................................................................................................................. 4 Specifications ...................................................................................................................................... 4 Back-Up Procedure............................................................................................................................. 4 Business Purpose ................................................................................................................................ 5 Transaction Specification Information ............................................................................................... 6 Functional Group ID=RA..................................................................................................................... 7 ST Transaction Set Header............................................................................................................. 9 BPR Beginning Segment for Payment Order/Remittance Advice................................................. 10 TRN Trace ..................................................................................................................................... 11 CUR Currency ............................................................................................................................... 11 REF Reference Identification ........................................................................................................ 12 DTM Create Date/Time Reference ............................................................................................... 12 N1 Honda Name............................................................................................................................ 13 N3 Address Information................................................................................................................. 13 N4 Geographic Location................................................................................................................ 14 PER Administrative Communications Contact .............................................................................. 14 N1 Payee Name ............................................................................................................................ 15 N3 Payee Address Information ..................................................................................................... 15 N4 Geographic Location................................................................................................................ 15 ENT Entity ..................................................................................................................................... 16 NM1 Source Supplier Name.......................................................................................................... 16 NM1 Plant Name ........................................................................................................................... 17 ADX Adjustment ............................................................................................................................ 18 REF Reference Identification ........................................................................................................ 19 IT1 Baseline Item Data (Invoice) ................................................................................................... 20 REF Part Number.......................................................................................................................... 20 DTM Date/Time Reference ........................................................................................................... 21 SAC Service, Promotion, Allowance, or Charge Information........................................................ 21 SLN Subline Item Detail ................................................................................................................ 22 RMR Remittance Advice Accounts Receivable Open Item Reference......................................... 23 REF Reference Identification ........................................................................................................ 24 REF Reference Identification ........................................................................................................ 25 DTM Shipped Date/Time Reference ............................................................................................. 25 12 - 2 September 2007

DTM Received Date/Time Reference ........................................................................................... 26 IT1 Baseline Item Data (Invoice)................................................................................................... 26 REF Part Number.......................................................................................................................... 27 TXP Tax Payment ......................................................................................................................... 27 SE Transaction Set Trailer ............................................................................................................ 28 Operating Procedures........................................................................................................................ 29 Overview ........................................................................................................................................... 29 Replacement: ................................................................................................................................ 29 Retransmission:............................................................................................................................. 29
September 2007
12 - 3
Transaction Covered
Remittance Advice (Transaction Set 820), abbreviated "RA".
Application Standards and Conventions

The 820 set is based upon the ANSI ASC X 12 Version Release 004010 documents.
Mapping
A list of the Remittance Advice business data elements and how they are transmitted via EDI Standards is provided in the Transaction Specifications section.
Schedule
The Remittance Advice can be transmitted daily.
Specifications
It is possible for Honda to transmit multiple Remittance Advices within one envelope. This means that there may be multiple transaction sets (ST-SE header/trailer segments) within one interchange envelope (ISA-IEA header/trailer segments). Honda transmits all EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up Procedure
In the event of a failure of Electronic Data Interchange, it is the responsibility of the sending party to transmit the contents of any pending Transmission to the receiving party using a method of non-EDI transmission which is timely, reasonable, and appropriate under the circumstances.
12 - 4
September 2007
Business Purpose
The Honda Remittance Advice (ANSI 820) transaction set is used in the following ways: To notify Honda Suppliers of a planned payment transaction in advance of the actual payment date. This allows the supplier the opportunity to investigate and negotiate any discrepancy situations prior to the actual payment. To provide details of a payment to Honda Domestic Suppliers. Note - The Remittance Advice plays a critical role for those Honda facilities that use the Evaluated Receipt Settlement (ERS) process.
FREQUENCY: All Honda plants/facilities As required
TRANSMITTED TO: OEM Suppliers Service Parts Suppliers
TRANSMITTED FROM: Honda
September 2007
12 - 5

The following Transaction Specifications consist of two sections: 1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality. Note - The Req. Des. for the first segment in a loop is also used for that corresponding loop. 2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column: M = Mandatory X = Conditional O = Optional The second column: ID = Identifier (a unique value from a predefined list from ANSI) DT = Date TM = Time AN = Alphanumeric R = Numeric with a variable decimal place Nx = Numeric with x decimal places The third column: x/y, where x = the minimum number of digits for this element and y = the maximum number of digits for this element.
12 - 6
September 2007
Functional Group ID=RA

Heading:
Must Use Must Use Pos. No. 010 020 035 Must Use Must Use Must Use 040 050 060 Seg. ID ST BPR TRN CUR REF DTM Name Transaction Set Header Beginning Segment for Payment Order/Remittance Advice Trace Currency Reference Identification Create Date/Time Reference LOOP ID - N1 Must Use Must Use Must Use Must Use 070 090 100 120 N1 N3 N4 PER Honda Name Address Information Geographic Location Administrative Communications Contact LOOP ID - N1 Must Use Must Use Must Use 150 160 170 N1 N3 N4 Payee Name Payee Address Information Geographic Location M M M 1 1 1 M M M M 1 1 1 >1 1 Req. Des. M M O M M M Max.Use 1 1 1 1 1 1 1 Loop Repeat
September 2007
12 - 7
Chapter 12 Remittance Advice (820) Detail:

Pos. No. Must Use 010 Seg. ID ENT Name LOOP ID - ENT Entity LOOP ID - NM1 Must Use 020 NM1 Source Supplier Name LOOP ID - NM1 Must Use 077 NM1 Plant Name LOOP ID - ADX 080 ADX Adjustment LOOP ID - REF Must Use 110 REF Reference Identification LOOP ID - IT1 130 IT1 Baseline Item Data (Invoice) LOOP ID - REF 140 141 REF DTM Part Number Date/Time Reference LOOP ID - SAC 142 SAC Service, Promotion, Allowance, or Charge Information LOOP ID - SLN 144 SLN Subline Item Detail LOOP ID - RMR 150 Must Use 170 175 180 185 RMR REF REF DTM DTM Remittance Advice Accounts Receivable Open Item Reference Reference Identification Reference Identification Shipped Date/Time Reference Received Date/Time Reference LOOP ID - IT1 190 IT1 Baseline Item Data (Invoice) LOOP ID - REF 200 REF Part Number LOOP ID - TXP 280 TXP Tax Payment O 1 O 1 1 O 1 1 O M O O O 1 >1 >1 1 1 >1 O 1 >1 O 1 >1 O O 1 1 >1 O 1 1 M 1 >1 O 1 >1 M 1 >1 M 1 1 Req. Des. M Max.Use 1 >1 Loop Repeat >1
Summary:
Must Use Pos. No. 010 Seg. ID SE Name Transaction Set Trailer Req. Des. M Max.Use 1 Loop Repeat
12 - 8
September 2007


Must Use Ref. Des. ST01 Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes are listed below 820 Payment Order/Remittance Advice 329 Transaction Set Control Number M AN 4/9 This number will be unique (within a transaction set) and ascending. It may be sequential.
Must Use
ST02
September 2007
12 - 9
BPR Beginning Segment for Payment Order/Remittance Advice

Position: Loop: Level: Usage: Max Use: Ref. Des. BPR01 020 Heading Mandatory 1 Data Element Summary Data Element Name Attributes 305 Transaction Handling Code M ID 1/2 Valid codes are listed below: I Remittance Information Only 782 Total Payment Amount M R 1/15 The total calculated value of all paid transactions included in the remittance document. 478 Credit/Debit Flag Code M ID 1/1 Code indicating whether amount is a credit or debit C Credit D Debit 591 Payment Method Code M ID 3/3 Valid codes are listed below: ACH Automated Clearing House (ACH) CHK Check DXC ACH Demand Corporate Trade Exchange (CTX) Credit NON Non-Payment Data SXC ACH Savings Corporate Trade Exchange (CTX) Credit X12 X12 812 Payment Format Code O ID 1/3 If BPR04 is ACH then the valid code for BPR05 is: CCD or PPD. If BPR04 is CHK then the valid code for BPR05 is: PBC. If BPR04 is any other value, omit this data element. CCD Cash Concentration/Disbursement (CCD) (ACH) PBC Commercial/Corporate Check PPD Prearranged Payment and Deposit (PPD+) (ACH) 506 Supplier (DFI) ID Number Qualifier X ID 2/2 If BPR04 value is CHK or NON, the BPR12/13 will be omitted. If BPR04 value is not CHK or NON, one of the following values will be used: 01 ABA Transit Routing Number Including Check Digits (9 digits) 02 Swift Identification (8 or 11 characters) 03 CHIPS (3 or 4 digits) 04 Canadian Bank Branch and Institution Number ZZ Mutually Defined 507 Supplier (DFI) Identification Number X AN 3/12 569 Supplier Account Number Qualifier O ID 1/3 If BPR04 value is CHK or NON, the BPR14/15 will be omitted. If BPR04 value is not CHK or NON, one of the following values will be used: DA Demand Deposit SG Savings 508 Supplier Account Number X AN 1/25 373 Remittance Date O DT 8/8 -Expected funds transfer date -Date expressed as CCYYMMDD.
Must Use
Must Use
BPR02
Must Use
BPR03
Must Use
BPR04
BPR05
BPR12
BPR13 BPR14
BPR15 BPR16
12 - 10
September 2007
TRN Trace
Position: Loop: Level: Usage: Max Use: 035 Heading Optional 1

Must Use Ref. Des. TRN01 Data Element Name Attributes 481 Trace Type Code M ID 1/2 Valid codes are listed below 3 Financial Reassociation Trace Number 127 Reference Identification M AN 1/30 This data element contains the reference number that identifies this remittance advice. - For checks, this number will be the check number. - For EFT, this is a unique number generated by Honda.
Must Use
TRN02
CUR Currency

Must Use Ref. Des. CUR01 Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 This code identifies the originating organization. BY Buying Party (Purchaser) 100 Currency Code M ID 3/3 Code specifying the currency of the transaction dollars. The primary codes used in North America are: MXN Mexican Pesos CAD Canadian Dollars USD U.S. Dollars Other Standard ISO-4217 codes will be used as needed.
Must Use
CUR02
September 2007
12 - 11


Must Use Ref. Des. REF01 Data Element Name Attributes 128 Honda Remittance Advice Qualifier M ID 2/3 Valid codes are listed below: 2H Assigned by transaction set sender 127 Honda Remittance Advice Number M AN 1/14 A unique number assigned by the originator to identify the remittance advice.
Must Use
REF02
DTM Create Date/Time Reference


Must Use Ref. Des. DTM01 Data Element Name 374 Create Date/Time Qualifier Valid codes are listed below: 097 Transaction Creation 373 Create Date Date expressed as CCYYMMDD 337 Create Time Time expressed in 24-hour clock time as HHMM Attributes M ID 3/3
Must Use Must Use
DTM02 DTM03
M M
DT 8/8 TM 4/4
12 - 12
September 2007
N1 Honda Name

Must Use Ref. Des. N101 Data Element Name Attributes 98 Payer Entity Identifier Code M ID 2/2 Valid codes are listed below: PR Payer 93 Payer Name M AN 1/35 The corporate name for the Honda facility issuing this document. For example: (May not be an all-inclusive list.) "Honda of America Mfg., Inc." "Honda Manufacturing of Alabama, LLC" "Honda of Canada Mfg." "Honda Canada, Inc." Honda de Mexico, S.A. de C.V. "American Honda Motor Co., Inc." "Honda Power Equipment" "Honda of South Carolina" Honda Power Train Georgia "Honda Transmission" Payer Identification Code Qualifier Valid codes are listed below: 92 Assigned by Buyer or Buyer's Agent Payer Identification Code
Must Use
N102
Must Use
N103
66
ID 1/2
Must Use
N104
67
AN 2/20
N3 Address Information

Must Use Ref. Des. N301 N302 Data Element Name 166 Payer Address Information 1 166 Payer Address Information 2 Attributes M AN 1/30 O AN 1/30
September 2007
12 - 13

Must Use Must Use Must Use Must Use Ref. Des. N401 N402 N403 N404 Data Element 19 156 116 26 Name Payer City Name Payer State or Province Code Payer Postal Code Payer Country Code Attributes M AN 2/30 M ID 2/2 M ID 3/10 M ID 2/3
PER Administrative Communications Contact

Position: Loop: Level: Usage: Max Use: Notes: 120 N1 Mandatory Heading Mandatory >1
Honda's accounting contact will always be transmitted. The other contacts may be transmitted.

Must Use Ref. Des. PER01 Data Element Name Attributes 366 Contact Function Code M ID 2/2 Valid codes are listed below: AE Corporate Purchasing Agent AP Accounts Payable Department BD Buyer Name or Department 93 Name O AN 1/35 365 Telephone Number Qualifier X ID 2/2 Valid codes are listed below: TE Telephone 364 Telephone Number X AN 1/15 365 Fax Number Qualifier X ID 2/2 Valid codes are listed below: FX Facsimile 364 Fax Number X AN 1/15 365 E-Mail Qualifier X ID 2/2 Valid codes are listed below: EM Electronic Mail 364 E-Mail Address X AN 1/80 443 Honda Plant ID O AN 3/8 This is the Honda code number for the logistical company which the stated contact represents. Please refer to NM109 (Position 077) for a complete list of codes.
PER02 PER03
PER04 PER05
PER06 PER07
PER08 PER09
12 - 14
September 2007
N1 Payee Name
Position: Loop: Level: Usage: Max Use: Ref. Des. N101 150 N1 Mandatory Heading Mandatory 1

Must Use Data Element Name Attributes 98 Payee Identifier Code M ID 2/2 Valid codes are listed below: PE Payee 93 Payee Name M AN 1/35 The name of the Honda supplier being paid. 66 Payee Identification Code Qualifier M ID 1/2 Valid codes are listed below: 92 Assigned by Buyer or Buyer's Agent 67 Payee Identification Code M AN 2/20 A unique number assigned by Honda to identify the supplier's remit to location.
Must Use Must Use
N102 N103
Must Use
N104
N3 Payee Address Information

Position: Loop: Level: Usage: Max Use: Ref. Des. N301 N302 160 N1 Mandatory Heading Mandatory 1

Must Use Data Element Name 166 Payee Address Information 1 166 Payee Address Information 2 Attributes M AN 1/30 O AN 1/30
Position: Loop: Level: Usage: Max Use: Ref. Des. N401 N402 N403 N404 170 N1 Mandatory Heading Mandatory 1

Must Use Must Use Must Use Must Use Data Element 19 156 116 26 Name Payee City Name Payee State or Province Code Payee Postal Code Payee Country Code Attributes M AN 2/30 M ID 2/2 M ID 3/10 M ID 2/3
September 2007
12 - 15
ENT Entity
Position: Loop: Level: Usage: Max Use: 010 ENT Mandatory Detail Mandatory 1

Must Use Ref. Des. ENT02 Data Element Name Attributes 98 Source Supplier Identifier Code M ID 2/2 Valid codes are listed below. Typically this indicates the ship from location. SU Supplier/Manufacturer 66 Source Identification Code Qualifier M ID 1/2 Valid codes are listed below: 92 Assigned by Buyer or Buyer's Agent 67 Source Supplier Number and Location Code M AN 8/8 A unique number assigned by Honda to identify the source supplier of a shipment. The name of the source supplier will appear in NM103 (source supplier name). 98 Ship To Identifier Code M ID 2/2 Valid codes are listed below: ST Ship To 66 Ship To Code Qualifier M ID 1/2 Valid codes are listed below: 92 Assigned by Buyer or Buyer's Agent 67 Ship To Number M AN 2/8 A unique number assigned by Honda to identify the ship to destination related to a shipment.
Must Use
ENT03
Must Use
ENT04
Must Use
ENT05
Must Use
ENT06
Must Use
ENT07
NM1 Source Supplier Name

Position: Loop: Level: Usage: Max Use: 020 NM1 Mandatory Detail Mandatory 1

Must Use Ref. Des. NM101 Data Element Name Attributes 98 Source Supplier ID Code M ID 2/2 Valid codes are listed below: SU Supplier/Manufacturer 1065 Entity Type Qualifier M ID 1/1 Valid codes are listed below: 4 Corporation 1035 Source Supplier Name M AN 1/35 The name of the supplier that a shipment was received from. This name corresponds to the Source Supplier Number and Location in ENT04.
Must Use
NM102
Must Use
NM103
12 - 16
September 2007
NM1 Plant Name

Position: Loop: Level: Usage: Max Use: 077 NM1 Mandatory Detail Mandatory 1

Must Use Ref. Des. NM101 Data Element Name 98 Entity Identifier Code Valid codes are listed below: 16 Plant 1065 Entity Type Qualifier Valid codes listed below: 4 Corporation 1035 Plant Name 66 Honda Plant ID Qualifier Valid codes are listed below: 98 Purchasing Office 67 Honda Plant ID This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM = Attributes M ID 2/2
Must Use
NM102
ID 1/1
Must Use Must Use
NM103 NM108
M M
AN 1/35 ID 1/2
Must Use
NM109
AN 3/3
HAM - Marysville Auto Plant (MAP-used for GPCS) HAM - East Liberty Auto Plant (ELP-used for GPCS) HAM - Marysville Motorcycle Plant (MMP-used for GPCS) HAM - International Parts Supply (IPS-used for GPCS) HAM - Service Parts Procurement (IPS-used for GPCS) HAM - International Parts Supply for Honda de Mexico (IPS-for GPCS) HAM - Anna Engine Plant (AEP-used for GPCS) American Honda Motor Co., Inc. Honda of Canada Mfg. Honda de Mexico Honda Manufacturing of Alabama Honda Manufacturing of Indiana Honda Power Equipment Honda Precision Parts Georgia Honda of South Carolina Honda Transmission
September 2007
12 - 17
ADX Adjustment
Position: Loop: Level: Usage: Max Use: Notes: 080 ADX Optional Detail Optional 1 At least one ADX segment or one RMR segment must be used within the ENT loop.

Must Use Must Use Ref. Des. ADX01 ADX02 Data Element Name Attributes 782 Adjustment Monetary Amount M R 1/15 A positive or negative amount of adjustment to a supplier's payment. 426 Adjustment Reason Code M ID 2/2 At times, Honda will find it necessary to adjust a supplier's payment for one of the following reasons. 01 Pricing Error 06 Quantity Contested 46 Transportation Charge Incorrect 72 Authorized Return E2 Covered By Debit Memo Adjustment Identification Qualifier M ID 2/3 Honda will identify the document number being adjusted in ADX04. The valid qualifier codes related to the document number will be: BM Bill of Lading Number CM Buyer's Credit Memo CR Customer Reference Number DL Seller's Debit Memo FR Freight Bill Number IV Seller's Invoice Number OI Original Invoice Number PK Packing List Number RV Receiving Number RZ Returned Goods Authorization Number SI Shipper's Identifying Number for Shipment (SID) TN Transaction Reference Number Adjustment Identification M AN 1/20 This is a reference number.
Must Use
ADX03
128
Must Use
ADX04
127
12 - 18
September 2007

Position: Loop: Level: Usage: Max Use: Notes: 110 REF Mandatory Detail Mandatory 1
If the ADX loop is sent, the first iteration of this segment will always be used to transmit a code identifying whether the adjustment is paid or unpaid. Optionally, a second iteration of this segment can be used to transmit GST tax information for HCM.

Must Use Ref. Des. REF01 Data Element Name Attributes 128 Reference Identification Qualifier M ID 2/3 - When this segment references an Adjustment Payment on Hold Code, this element will contain the same value as ADX03. - When this segment references GST tax, this element will contain a code value of "ZZ", meaning Mutually Defined. 127 Reference Identification X AN 1/20 - When this segment references an Adjustment Payment on Hold Code, this element will contain the same value as ADX04. - When this segment references GST tax, this element will contain the total GST tax for the items in the ADX loop. 352 Description X AN 1/2 - When this segment references an Adjustment Payment on Hold Code, the code values below will apply. - This element will not be transmitted if this segment references GST tax. - Valid codes are listed below: PD Amount of reference document is included - "PD" = If the document identified in ADX04 and REF02 is included in the calculation of the total payment amount, "PD" will appear in this field. UP Amount of reference document is not included - "UP" = If the document identified in ADX04 and REF02 is not included in the calculation of the total payment amount, "UP" will appear in this field.
REF02
REF03
September 2007
12 - 19

Position: Loop: Level: Usage: Max Use: Notes: Ref. Des. IT101 Must Use Must Use IT102 IT103 130 IT1 Optional Detail Optional 1
If used, this loop provides line item pricing information for this Adjustment.

Data Element Name Attributes 350 Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set. 358 Quantity Invoiced M R 1/10 355 Unit or Basis for Measurement Code M ID 2/2 Valid codes are listed below: EA Each 212 Unit Price M R 1/17 For Retro-payments for price changes, this contains the difference between the old and new price. For everything else it is the unit price. 639 Basis of Unit Price Code M ID 2/2 NT will be used when the value in IT104 represents a retro payment. CP will be used for all other circumstances. Valid codes are listed below: CP Current Price (Subject to Change) To be used for all circumstances except retro-payments. NT Net To be used when the value in IT104 represents a retro payment.
Must Use
IT104
Must Use
IT105
REF Part Number

Position: Loop: Level: Usage: Max Use: Notes: 140 REF Optional Detail Optional 1
If transmitted, this segment contains part number information relating to the preceding ADX04. This segment will always be transmitted if the IT1 segment is transmitted. If Hondas back-end systems cannot identify a part number, the word Labor will be inserted into REF02.

Must Use Ref. Des. REF01 Data Element Name 128 Reference Identification Qualifier Valid codes are listed below: PM Part Number 127 Part Number Attributes M ID 2/3
Must Use
REF02
AN 1/30
12 - 20
September 2007
DTM Date/Time Reference

This segment contains date/time information relating to the preceding IT1/REF.

Must Use Ref. Des. DTM01 Data Element Name 374 Date/Time Qualifier Valid codes are listed below: 102 Issue 373 Date Date expressed as CCYYMMDD. 337 Time Time expressed in 24-hour clock time as HHMM Attributes M ID 3/3
Must Use Must Use
DTM02 DTM03
M M
DT 8/8 TM 4/4
SAC Service, Promotion, Allowance, or Charge Information

Position: Loop: Level: Usage: Max Use: Notes: 142 SAC Optional Detail Optional 1
When re-work costs are incurred, this segment will provide information relating to those costs.

Must Use Ref. Des. SAC01 Data Element Name Attributes 248 Allowance or Charge Indicator M ID 1/1 Valid codes are listed below: A Allowance C Charge 1300 Service, Promotion, Allowance, or Charge Code M ID 4/4 Valid codes are listed below: A170 Adjustments E190 Labor Charges 610 Amount O N2 1/15 Dollar amount (example: Honda transmits 123456, supplier should translate as $1,234.56). 118 Rate O R 1/9 Hourly rate 355 Unit or Basis for Measurement Code X ID 2/2 Valid codes are listed below: HR Hours 380 Quantity X R 1/15 Number of hours billed 331 Allowance or Charge Method of Handling Code O ID 2/2 04 Credit Customer Account 06 Charge to be Paid by Customer
Must Use
SAC02
SAC05
SAC08 SAC09
SAC10 SAC12
September 2007
12 - 21
SLN Subline Item Detail

Position: Loop: Level: Usage: Max Use: Notes: 144 SLN Optional Detail Optional 1
Two SLN loops are used to provide the old and new price information defined for retroactive price adjustments. The first loop will contain "D" in SLN03, the old price in SLN06 and "LR" in SLN07. The second loop will contain "A" in SLN03, the new price in SLN06 and "CP" in SLN07.

Must Use Must Use Ref. Des. SLN01 SLN03 Data Element Name 350 Assigned Identification 662 Relationship Code Valid codes are listed below: A Add - Signifies the price is the new price. D Delete - Signifies the price is the old price. 212 Unit Price 639 Basis of Unit Price Code Valid codes are listed below: CP Current Price (Subject to Change) - Signifies the price is the new price. LR Previous Catalog Price - Signifies the price is the old price. Attributes M AN 1/20 M ID 1/1
Must Use Must Use
SLN06 SLN07
M M
R 1/17 ID 2/2
12 - 22
September 2007
RMR Remittance Advice Accounts Receivable Open Item Reference

Position: Loop: Level: Usage: Max Use: Notes: 150 RMR Optional Detail Optional 1
At least one RMR segment or one ADX segment must be used within the ENT loop.

Must Use Ref. Des. RMR01 Data Element Name Attributes 128 Remittance Identification Qualifier M ID 2/3 Honda will identify the document number being paid in RMR02. The valid qualifier codes related to the document number will be: BM Bill of Lading Number CM Buyer's Credit Memo CR Customer Reference Number DL Seller's Debit Memo FR Freight Bill Number IV Seller's Invoice Number OI Original Invoice Number PK Packing List Number RV Receiving Number RZ Returned Goods Authorization Number SI Shipper's Identifying Number for Shipment (SID) TN Transaction Reference Number 127 Remittance Identification M AN 1/20 A reference identifying the document number being paid. This will often be the ASN number, but could be a packing list number, invoice, etc. 482 Remittance Payment Action Code M ID 2/2 The valid codes specifying how the funds were derived: ER Evaluated Receipts Settlement NS Not Specified (Unknown as to Type of Payment) PA Payment in Advance PI Pay Item PO Payment on Account PP Partial Payment 782 Net Amount M R 1/15 782 Gross Amount M R 1/15 782 Discount Amount O R 1/15
Must Use
RMR02
Must Use
RMR03
Must Use Must Use
RMR04 RMR05 RMR06
September 2007
12 - 23

Position: Loop: Level: Usage: Max Use: Notes: 170 RMR Optional Detail Mandatory >1
If the RMR loop is sent, the first iteration of this segment will always be used to transmit a code identifying whether the remittance is paid or unpaid. Optionally, a sceond iteration of this segment can be used to transmit GST tax information for HCM.

Must Use Ref. Des. REF01 Data Element Name Attributes 128 Reference Identification Qualifier M ID 2/3 - When this segment references an Remittance Payment on Hold Code, this element will contain the same value as RMR01. - When this segment references GST tax, this element will contain a code value of "ZZ", meaning Mutually Defined. 127 Reference Identification X AN 1/20 - When this segment references an Remittance Payment on Hold Code, this element will contain the same value as RMR02. - When this segment references GST tax, this element will contain the total GST tax for the items in the RMR loop. 352 Description X AN 1/2 - When this segment references an Remittance Payment on Hold Code, the code values below will apply. - This element will not be transmitted if this segment references GST tax. - Valid codes are listed below: PD Amount of reference document is included - "PD" = If the document identified in RMR02 and REF02 is included in the calculation of the total payment amount, "PD" will appear in this field. UP Amount of reference document is not included - "UP" = If the document identified in RMR02 and REF02 is not included in the calculation of the total payment amount, "UP" will appear in this field.
REF02
REF03
12 - 24
September 2007

Position: Loop: Level: Usage: Max Use: Notes: Ref. Des. REF01 175 RMR Optional Detail Optional >1
This REF loop will be optionally used by AHM when miscellaneous or freight charges apply.

Must Use Data Element Name 128 Reference Identification Qualifier Valid codes are listed below: 22 Special Charge or Allowance Code - Miscellaneous Cost AI Associated Invoices - Freight Cost 127 Reference Identification Attributes M ID 2/3
Must Use
REF02
AN 1/30
Dollar amount corresponding to the qualifier transmitted in the previous element.
DTM Shipped Date/Time Reference

Position: Loop: Level: Usage: Max Use: Ref. Des. DTM01 180 RMR Optional Detail Optional 1

Must Use Data Element Name Attributes 374 Shipped Date/Time Qualifier M ID 3/3 Valid codes are listed below: 011 Shipped 373 Shipped Date M DT 8/8 If the document being paid (as identified in RMR02) is related to a parts shipment, the date of shipment by the supplier will be identified in this element. Date expressed as CCYYMMDD.
Must Use
DTM02
September 2007
12 - 25
DTM Received Date/Time Reference

Position: Loop: Level: Usage: Max Use: Ref. Des. DTM01 185 RMR Optional Detail Optional 1

Must Use Data Element Name Attributes 374 Received Date/Time Qualifier M ID 3/3 Valid codes are listed below: 050 Received 373 Received Date M DT 8/8 If the document being paid (as identified in RMR02) is related to a parts shipment, the date of receipt by Honda will be identified in this element. Date expressed as CCYYMMDD.
Must Use
DTM02

Position: Loop: Level: Usage: Max Use: Notes: 190 IT1 Optional Detail Optional 1
If used, this loop provides line item pricing information for this RMR.

Ref. Des. IT101 Must Use Must Use IT102 IT103 Data Element Name Attributes 350 Assigned Identification O AN 1/20 Alphanumeric characters assigned for differentiation within a transaction set. 358 Quantity Invoiced M R 1/10 355 Unit or Basis for Measurement Code M ID 2/2 Valid codes are listed below: EA Each 212 Unit Price M R 1/17
Must Use
IT104
12 - 26
September 2007
REF Part Number

If transmitted, this segment contains part number information relating to the preceding IT1 and RMR02. This segment will always be transmitted if the IT1 segment is transmitted.

Must Use Ref. Des. REF01 Data Element Name 128 Reference Identification Qualifier Valid codes are listed below: PM Part Number 127 Part Number Attributes M ID 2/3
Must Use
REF02
AN 1/30
TXP Tax Payment

Position: Loop: Level: Usage: Max Use: Notes: 280 TXP Optional Detail Optional 1 This optional segment will only be used by HCM. It provides GST tax information.

Must Use Must Use Must Use Must Use Must Use Ref. Des. TXP01 TXP02 TXP03 TXP04 TXP05 Data Element Name Attributes 325 Tax Identification Number M AN 1/20 1049 Tax Payment Type Code M ID 1/5 From the Federation of Tax Administrators 373 Date M DT 8/8 Same as BPR16 817 Tax Information Identification M AN 1/30 "GST Percent" 1051 Tax Amount M N2 1/10 Percent as a decimal (example: Honda transmits 7, supplier should translate as .07 or 7%)
September 2007
12 - 27

Position: Loop: Level: Usage: Max Use: Ref. Des. SE01 SE02 010 Summary Mandatory 1

Must Use Must Use Data Element Name 96 Number of Included Segments 329 Transaction Set Control Number Attributes M N0 1/10 M AN 4/9
12 - 28
September 2007
Operating Procedures
Overview
1. 2. 3. The 820 Remittance Advice provides payment detail to suppliers. This detail may be categorized as adjustment and remittances. Suppliers should integrate the 820 Remittance Advice to their Accounts Receivable system(s) to confirm Hondas 820 versus their Accounts Receivable data. The information provided in the 820 directly reflects data received from the supplier in the Advanced Ship Notice (856) and data sent to the supplier in the Invoice (810), Receiving Advice (861) and the Price/Sales Catalog (832). Quantity discrepancies must be identified and communicated immediately with Honda Purchasing, preferably within 3 days after receipt of each EDI transaction identifying a discrepancy. Delay in addressing quantity discrepancies increases the difficulty in tracking and resolving any issues. A supplier discovering a pricing discrepancy when reconciling an 820 should notify their Purchasing Contact. Suppliers may request item level detail be included in the 820. Item level detail (item number, quantity and unit price) will be provided if it is available. Suppliers should notify their Accounts Payable contact at Honda to request this information. HCM suppliers may receive GST tax information within the 820. Re-work costs can cause an adjustment to a Honda payment. Re-work charges will be itemized in the SAC segment.
4. 5.
6. 7.
Replacement:
There is no purpose code included in Honda's 820. Therefore, each 820 document stands alone. An 820 document may be replaced for various reasons, including correcting an error in a previous document. Supplier systems should have the capability to compare successive incoming Remittance Advices and replace the document based upon the change point listed below. Replacement of 820 documents should be based upon a match of: Remittance Advice Number, REF02 (position 050)
Retransmission:
Honda can retransmit the 820 document. Retransmission will only occur when the supplier requests that Honda resend the EDI document. This typically occurs after the supplier has experienced errors in translating the original document. A retransmitted document can be overlaid following the same Replacement Logic defined above.
September 2007
12 - 29
Chapter 13 Application Advice (824)

Application Advice (824)
September 2007
13 - 1
Chapter Contents
This chapter contains information and procedure for using Hondas Application Advice. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 3 Transaction Covered........................................................................................................................... 3 Application Standards and Conventions............................................................................................. 3 Mapping .............................................................................................................................................. 3 Exceptions/Clarifications..................................................................................................................... 3 Schedule ............................................................................................................................................. 3 Specifications ...................................................................................................................................... 3 Back-Up Procedure............................................................................................................................. 3 Business Purpose ................................................................................................................................ 4 Transaction Specification Information ............................................................................................... 5 Transaction Specifications.................................................................................................................. 6 Functional Group ID=AG..................................................................................................................... 6 ST Transaction Set Header............................................................................................................. 7 BGN Beginning Segment ................................................................................................................ 7 N1 Honda Ordering Plant Location ................................................................................................. 8 N1 Supplier Name ........................................................................................................................... 9 N3 Supplier Address ....................................................................................................................... 9 N4 Supplier Geographic Location ................................................................................................. 10 PER Supplier Contact ................................................................................................................... 10 N1 Ship To Location...................................................................................................................... 11 OTI Original Transaction Identification.......................................................................................... 12 TED Technical Error Description................................................................................................... 13 NTE Special Instruction................................................................................................................. 13 SE Transaction Set Trailer ............................................................................................................ 14 Operating Procedures ........................................................................................................................ 15 Replacement Logic ........................................................................................................................... 15 Replacement: ................................................................................................................................ 15 Retransmission:............................................................................................................................. 15
13 - 2
September 2007
Transaction Covered
Application Advice (Transaction Set 824), abbreviated AG.

Mapping
A list of the Application Advice business data elements and how they will be transmitted via EDI Standards is provided in the Transaction Specifications section.
There are no exceptions to ANSI Standards in this Transaction Description.
Schedule
The 824 should be transmitted within 15 minutes of ASN receipt into Hondas application system during production/operating hours.
Specifications
It is possible for Honda to transmit multiple Application Advices within one envelope. This means that there may be multiple transaction sets (ST-SE header/trailer segments) within one interchange envelope (ISA-IEA header/trailer segments). Honda transmits all EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up Procedure
September 2007
13 - 3
Business Purpose
The Honda Application Advice (ANSI 824) will be used by Honda to improve the accuracy of incoming transactions by providing immediate feedback to our trading partners regarding the presence or absence of any errors detected by our system. The 824 responds to EDI transactions sent to Honda. Example: Inventory Advice (ANSI 846) or ASN (ANSI 856) An 824 will be transmitted in response to transactions sent to Honda that reach our application system. Each 824 transaction can have one of three possible results: 1. 2. 3. Transaction is accepted with no errors. Transaction is accepted with errors present*. Transaction is rejected due to errors. This result will require repair and retransmission of the original document*.
FREQUENCY: Immediately following and in response to each incoming transaction received. TRANSMITTED FROM: Honda TRANSMITTED TO:
Supplier (originator) Service Parts Supplier
* In both cases 2 and 3, the Application Advice will furnish an error description, the actual data which is in error, along with relevant reference data to assist the supplier in finding and correcting the error.
13 - 4
September 2007

The following Transaction Specifications consist of two sections: 1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality. Note - The Req. Des. for the first segment in a loop is also used for that corresponding loop. 2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column:

The second column:
ID = Identifier (a unique value from a predefined list from ANSI) DT = Date TM = Time AN = Alphanumeric R = Numeric with a variable decimal place Nx = Numeric with x decimal places
The third column: x/y, where
x = the minimum number of digits for this element and y = the maximum number of digits for this element.
September 2007
13 - 5
Functional Group ID= AG
Heading:
Must Use Must Use Pos. No. 010 020 Seg. ID ST BGN Name Transaction Set Header Beginning Segment LOOP ID - N1 Must Use 030 N1 Honda Ordering Plant Location LOOP ID - N1 Must Use Must Use Must Use Must Use 090 100 110 120 N1 N3 N4 PER Supplier Name Supplier Address Supplier Geographic Location Supplier Contact LOOP ID - N1 130 N1 Ship To Location O 1 M M M M 1 1 1 1 1 M 1 1 Req. Des. M M Max.Use 1 1 1 Loop Repeat
Detail:
Pos. No. Must Use 010 Seg. ID OTI Name LOOP ID - OTI Original Transaction Identification LOOP ID - TED Must Use 070 080 Must Use 090 TED NTE SE Technical Error Description Special Instruction Transaction Set Trailer M O M 1 100 1 Req. Des. M Max.Use 1 >1 Loop Repeat 1
13 - 6
September 2007

Must Use
Ref. Des. ST01
Must Use
ST02
Data Element Summary Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes are listed below 824 Application Advice 329 Transaction Set Control Number M AN 4/9 This number will be unique (within a transaction set) and ascending. It may be sequential.
BGN Beginning Segment

Must Use
Ref. Des. BGN01
Must Use
BGN02
Must Use Must Use
BGN03 BGN04
Data Element Summary Data Element Name Attributes 353 Transaction Set Purpose Code M ID 2/2 Valid codes are listed below 00 Original 127 Application Advice Number M AN 1/8 Application Advice Numbers are unique by transaction type code, OTI10. The Application Advice Number will not repeat within a year. 373 Create Date M DT 8/8 Date expressed as CCYYMMDD 337 Create Time M TM 4/4 Time expressed in 24-hour clock time as HHMM
September 2007
13 - 7
N1 Honda Ordering Plant Location

Must Use
Ref. Des. N101
Must Use
N103
Must Use
N104
Data Element Summary Data Element Name 98 Entity Identifier Code Valid codes are listed below 16 Plant 66 Identification Code Qualifier Valid codes are listed below 6 Plant Code 67 Honda Plant ID This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM =
Attributes M ID 2/2
ID 1/2
AN 3/3
13 - 8
September 2007
N1 Supplier Name
Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid codes are listed below SU Supplier/Manufacturer 93 Supplier Name M AN 1/35 66 Supplier Number Qualifier M ID 1/2 Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Supplier Number and Loc Code M AN 8/8 An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code (which may be 00).
N3 Supplier Address
Must Use
Ref. Des. N301 N302
Data Element Summary Data Element Name 166 Address Information - 1 166 Address Information - 2
September 2007
13 - 9
N4 Supplier Geographic Location

Data Element Summary Ref. Des. N401 N402 N403 N404 Data Element 19 156 116 26 Name City Name State or Province Code Postal Code Country Code Attributes M AN 2/30 M ID 2/2 M ID 3/10 M ID 2/3
Must Use Must Use Must Use Must Use
PER Supplier Contact

Must Use
Ref. Des. PER01
Must Use
PER02
Data Element Summary Data Element Name 366 Contact Function Code Valid codes are listed below SU Supplier Contact 93 Supplier Contact Name
Attributes M ID 2/2
AN 1/30
13 - 10
September 2007
N1 Ship To Location
Position: Loop: Level: Usage: Max Use: Notes: 130 N1 Optional Heading Optional 1 This loop/segment will only be sent when the 824 is in response to an 856. (It will not be included when the 824 is in response to an 846.) Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid codes are listed below ST Ship To 93 Ship to Code M AN 2/8 This is the code assigned by Honda for the ship to location from the corresponding 856.
Must Use
Ref. Des. N101
Must Use
N102
September 2007
13 - 11
OTI Original Transaction Identification

Position: Loop: Level: Usage: Max Use: 010 OTI Mandatory Detail Mandatory 1
Must Use
Ref. Des. OTI01
Must Use
OTI02
Must Use
OTI03
Must Use
OTI06
Must Use
OTI07
Must Use
OTI10
Data Element Summary Data Element Name Attributes 110 Application Acknowledgment Code M ID 1/2 Only resend the transaction set when this element (OTI01) indicates a reject (TR). Valid codes are listed below: TA Transaction Set Accept TE Transaction Set Accept with Error TR Transaction Set Reject 128 Original Document Number Qualifier M ID 2/3 Valid codes are listed below: SI Shipper's Identifying Number for Shipment (SID) - "SI" indicates this 824 is in response to an ASN (856) TN Transaction Reference Number - "TN" indicates this 824 is in response to an Inventory Advice (846) 127 Original Document Number M AN 1/8 - For an ASN, this will be the ASN Number (BSN02) from the original document. - For an Inventory Advice, this will be the Inventory Advice Number (BIA03) from the original document. 373 Original Create Date M DT 8/8 - This date applies to the document that is in error. Date expressed as CCYYMMDD. - If a Honda supplier sends an original and replacement ASN (both with the same ASN number), the date (OTI06) and time (OTI07) will allow the supplier to link the appropriate 824 and ASN. 337 Original Create Time M TM 4/4 This time applies to the document that is in error. Time expressed in 24-hour clock time as HHMM. 143 Transaction Set Identifier Code M ID 3/3 846 Inventory Inquiry/Advice 856 Ship Notice/Manifest
13 - 12
September 2007
TED Technical Error Description

Position: Loop: Level: Usage: Max Use: Notes: 070 TED Mandatory Detail Mandatory 1 This segment will be sent even if a error did not occur. General information will be transmitted if a error did not occur. Data Element Summary Data Element Name Attributes 647 Application Error Condition Code M ID 1/3 Valid codes are listed below ZZZ Mutually Defined 3 Error Description M AN 1/60 - If there was an error, there will be an error message. For example, "unit of measure invalid". - If there was no error, a message stating the ASN or Inventory Advice is valid will appear. 724 Error Data O AN 1/80 - If there was an error, this field will contain the actual data that was in error if available. For example: Error Data = BZ - If there was no error, the ASN number or Inventory Advice number will appear.
Must Use
Ref. Des. TED01
Must Use
TED02
TED07
NTE Special Instruction

Position: Loop: Level: Usage: Max Use: Notes: 080 TED Mandatory Detail Optional 100 This segment will be provided only if data is available. Data Element Summary Data Element Name Attributes 363 Note Reference Code M ID 3/3 Valid codes are listed below ADD Additional Information 352 Reference Data Description M AN 1/80 This field may contain additional information to help identify the data in error. Examples: Error Description (TED02) = unit of measure invalid Error Data (TED03) = BZ Reference Data (NTE02) = 123456SM1A000 (Honda part number associated with 'invalid unit of measure')
Must Use
Ref. Des. NTE01
Must Use
NTE02
September 2007
13 - 13

Position: Loop: Level: Usage: Max Use: 090 Detail Mandatory 1
Must Use Must Use
Ref. Des. SE01 SE02
Data Element Summary Data Element Name 96 Number of Included Segments 329 Transaction Set Control Number
Attributes M N0 1/10 M AN 4/9
13 - 14
September 2007
Replacement Logic
Replacement:
Honda will not replace the 824 document. The purpose code is always 00, original.
Retransmission:
Honda can retransmit the 824 document. Retransmission will only occur when the supplier requests that Honda resend the EDI document. This is typically because the supplier had some problem in the translation processing. A retransmitted document can be overlaid based upon a match of Application Advice Number, BGN02.
September 2007
13 - 15
Chapter 14 Weekly Release (830)

Weekly Release (830)
September 2007
14 - 1
Chapter Contents
This chapter contains information and procedures for using the Hondas Weekly Release transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 4 Application Standards and Conventions............................................................................................. 4 Mapping .............................................................................................................................................. 4 Exceptions/Clarifications..................................................................................................................... 4 Schedule ............................................................................................................................................. 4 Specifications ...................................................................................................................................... 4 Back-Up .............................................................................................................................................. 4 Business Purpose ................................................................................................................................ 5 Transaction Specification Information ............................................................................................... 7 Transaction Specifications .................................................................................................................. 8 Functional Group ID=PS ................................................................................................................. 8 ST Transaction Set Header............................................................................................................. 9 BFR Beginning Segment for Planning Schedule ............................................................................ 9 PER Text Message Identifier......................................................................................................... 10 DTM Create Date .......................................................................................................................... 10 TD5 Carrier Details (SCAC) .......................................................................................................... 11 N1 Honda Ordering Plant Location ............................................................................................... 12 N2 Honda Corporate Name........................................................................................................... 13 PER Honda Contact ...................................................................................................................... 13 N1 Supplier Name ......................................................................................................................... 14 N3 Supplier Address ..................................................................................................................... 14 N4 Supplier Geographic Location ................................................................................................. 15 PER Supplier Contact ................................................................................................................... 15 LIN Item Identification.................................................................................................................... 16 UIT Unit Detail ............................................................................................................................... 17 DTM Cum Last Received Date...................................................................................................... 17 QTY Cumulative Quantity.............................................................................................................. 18 TD1 Container Details ................................................................................................................... 18 N1 Ship To Location...................................................................................................................... 19 N3 Ship To Address ...................................................................................................................... 19 N4 Ship To Geographic Location .................................................................................................. 20 FST Forecast Schedule................................................................................................................. 21 CTT Transaction Totals................................................................................................................. 22 SE Transaction Set Trailer ............................................................................................................ 22 Replacement Logic............................................................................................................................. 23 Replacement: .................................................................................................................................... 23
14 - 2
September 2007

Retransmission: ................................................................................................................................ 23 Operating Procedures........................................................................................................................ 24 Flex Forecast .................................................................................................................................... 24 Flex Forecast Examples: ............................................................................................................... 25 Positive Fixed Flex Value .............................................................................................................. 25 Negative Fixed Flex Value ............................................................................................................ 26
September 2007
14 - 3
Transaction Covered
Planning Schedule with Release Capability -- or Weekly Release (Transaction Set 830), abbreviated PS.

Mapping
A list of the Weekly Release business data elements and how they are transmitted via EDI Standards is provided in the transaction Specifications section.
There are no Exceptions to ANSI Standards in this Transaction description.
Schedule
The Weekly Release is usually transmitted by 12:00 noon Eastern Time. The seller should notify the buyer no later than 12:00 noon of the following production day if the seller has not received the Weekly Release. AHM -- The Weekly Release is transmitted on a weekly or monthly basis as negotiated by AHM and the supplier.
Specifications
It is possible for Honda to transmit multiple Weekly Releases within one envelope. This means that there may be multiple transaction sets (ST-SE header/trailer segments) within one interchange envelope (ISAIEA header/trailer segments). Honda transmits all EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up
In the event of a failure of Electronic Data Interchange, it is the responsibility of the sending party to transmit the contents of any pending Transmission to the receiving party using a method of non-EDI Transmission which is timely, reasonable, and appropriate under the circumstances.
14 - 4
September 2007
Business Purpose
The Honda Weekly Release (ANSI 830) transaction set is used as a firm and/or forecast document that provides information by part number. Forecast information and quantities are subject to change or cancellation by Honda. The 830 does not authorize shipment. A Purchase Order (850) or Ship Schedule (862) is used to authorize shipment. Honda may transmit one or both of the following 830 transaction sets: 1. Production Forecast Will be used to provide anticipated production quantities. Suppliers should use this data for Production and Capacity planning. AHM Up to 52 HAM Up to 26 HCM Up to 26 HDM Up to 8 HMA Up to 26 HPE Up to 26 HPG Up to 26 HSC Up to 26 HTM Up to 26
Number of weeks forecasted Transmission Schedule
Any business day of the week
First business day of the week
Second business week of the month
Any business day of the week
Requirements on the Weekly Release (830) are logically tied to a Ship Schedule (862) or Purchase Order (850) transaction for shipment authorization. Although the 830 and 862 (or 850) are "logically" tied to each other, there is no physical link between them. In other words, there is no identifying number that ties an 830 to an 862 (or 850). 2. Flex Forecast Will be used to provide potential fluctuations in sales quantities. Suppliers should use this data to manage their raw material inventories. AHM N/A HAM Up to 14 HCM Up to 14 HDM N/A HMA Up to 14 HPE TBD HPG HSC TBD HTM N/A
Number of weeks forecasted Transmission Schedule
N/A
Midweek
Midweek
N/A
Midweek
TBD
TBD
N/A
September 2007
14 - 5

The time buckets in the Flex Forecast will corresponds to those in the Production Forecast. The Flex Forecast will contain the following: Weeks 1-3 will provide quantities that represent an actual change. Weeks 4-14 will provide quantities reflecting a potential order increase. Not all suppliers will receive a Flex Forecast. FREQUENCY: HAM/HCM/HMA/HPE/HPG/HSC -- Weekly/as applicable AHM/HTM -- Weekly or monthly/as applicable TRANSMITTED FROM: Honda TRANSMITTED TO: Domestic OEM suppliers Service Parts suppliers
14 - 6
September 2007

The following Transaction Specifications consist of two sections: 1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality. Note: The Req. Des. for the first segment in a loop is also used for that corresponding loop. 2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column: M = Mandatory X = Conditional O = Optional The second column: ID = Identifier (a unique value from a predefined list from ANSI) DT = Date TM = Time AN = Alphanumeric R = Numeric with a variable decimal place Nx = Numeric with x decimal places The third column: x/y, where x = the minimum number of digits for this element and y = the maximum number of digits for this element.
September 2007
14 - 7
Functional Group ID=PS
Heading:
Must Use Must Use Pos. No. 010 020 060 Must Use Must Use 130 190 Seg. ID ST BFR PER DTM TD5 Name Transaction Set Header Beginning Segment for Planning Schedule Text Message Identifier Create Date Carrier Details (SCAC) LOOP ID - N1 Must Use Must Use Must Use 230 240 280 N1 N2 PER Honda Ordering Plant Location Honda Corporate Name Honda Contact LOOP ID - N1 Must Use Must Use Must Use Must Use 295 297 298 299 N1 N3 N4 PER Supplier Name Supplier Address Supplier Geographic Location Supplier Contact M M M M 1 1 1 1 M M M 1 1 1 1 Req. Des. M M O M M Max.Use 1 1 1 1 1 1 Loop Repeat
Detail:
Pos. No. Must Use Must Use 010 020 021 220 Must Use 240 Seg. ID LIN UIT DTM QTY TD1 Name LOOP ID - LIN Item Identification Unit Detail Cum Last Received Date Cumulative Quantity Container Details LOOP ID - N1 Must Use Must Use Must Use 320 340 350 N1 N3 N4 Ship To Location Ship To Address Ship To Geographic Location LOOP ID - FST Must Use 410 FST Forecast Schedule M 1 M M M 1 1 1 >1 Req. Des. M M O O M Max.Use 1 1 1 1 1 1 Loop Repeat >1
Summary:
Must Use Must Use Pos. No. 010 020 Seg. ID CTT SE Name Transaction Totals Transaction Set Trailer Req. Des. M M Max.Use 1 1 Loop Repeat
14 - 8
September 2007

Position: Loop: Level: Usage: Max Use: Ref. Des. ST01 010 Heading Mandatory 1 Data Element Summary Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes are listed below 830 Planning Schedule with Release Capability 329 Transaction Set Control Number M AN 4/9 This number will be unique (within a transaction set) and ascending. It may be sequential.
Must Use
Must Use
ST02
BFR Beginning Segment for Planning Schedule

Position: Loop: Level: Usage: Max Use: Ref. Des. BFR01 020 Heading Mandatory 1 Data Element Summary Data Element Name Attributes 353 Transaction Set Purpose Code M ID 2/2 Valid codes listed below 05 Replace 127 Reference Identification M AN 1/14 This number links all line items (LIN loops) on this 830 together. It is also used to link to the 864 text transaction. 675 Schedule Type Qualifier M ID 2/2 Valid codes listed below PR Planned Requirement Based The qualifier will be used for Production 830's. ZZ Mutually Defined This qualifier will be used for Flex Forecast 830's. 676 Schedule Quantity Qualifier M ID 1/1 Valid codes listed below R Replacement Quantities 373 Forecast Start Date M DT 8/8 Date expressed as CCYYMMDD 373 Date Generated M DT 8/8 Date expressed as CCYYMMDD
Must Use
Must Use
BFR02
Must Use
BFR04
Must Use
BFR05
Must Use Must Use
BFR06 BFR08
September 2007
14 - 9
PER Text Message Identifier

Position: Loop: Level: Usage: Max Use: Notes: 060 Heading Optional 1 This segment will only be used if there is a corresponding text message for this document. Data Element Summary Data Element Name Attributes 366 Text Message Code M ID 2/2 Valid codes listed below ZZ Mutually Defined 93 Check for 864 M AN 1/30 "Comments in EDI 864" When this message appears, it indicates that an applicable 864 Text message has also been transmitted.
Must Use
Ref. Des. PER01
Must Use
PER02
DTM Create Date

Must Use
Ref. Des. DTM01
Must Use Must Use
DTM02 DTM03
Data Element Summary Data Element Name Attributes 374 Date/Time Qualifier-Create M ID 3/3 Valid codes listed below 167 Most Recent Revision (or Initial Version) 373 Create Date M DT 8/8 This is the date this document was created. Date expressed as CCYYMMDD. 337 Create Time M TM 4/4 This is the time this document was created. Time expressed in 24-hour clock time as HHMM.
14 - 10
September 2007
TD5 Carrier Details (SCAC)

Position: Loop: Level: Usage: Max Use: Ref. Des. TD502 190 Heading Mandatory 1 Data Element Summary Data Element Name Attributes 66 SCAC Code Qualifier M ID 1/2 Valid codes listed below 2 Standard Carrier Alpha Code (SCAC) 67 SCAC Code M AN 4/4 - The Standard Carrier Alpha Code (SCAC) of the carrier - AHM and HDM will always transmit "XXXX" for this value
Must Use
Must Use
TD503
September 2007
14 - 11

Position: Loop: Level: Usage: Max Use: Ref. Des. N101 230 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name 98 Plant Name Qualifier Valid codes listed below 16 Plant 93 Plant Name 66 Honda Plant ID Qualifier Valid codes listed below 98 Purchasing Office 67 Honda Plant ID This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM =
Must Use
Attributes M ID 2/2
Must Use Must Use
N102 N103
M M
AN 1/35 ID 1/2
Must Use
N104
AN 3/3
14 - 12
September 2007
N2 Honda Corporate Name

Position: Loop: Level: Usage: Max Use: Ref. Des. N201 240 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name Attributes 93 Corporate Name M AN 1/35 The corporate name for the Honda facility issuing this document. For example: (May not be an all-inclusive list.) Honda of America Mfg., Inc." "Honda Manufacturing of Alabama, LLC" "Honda of Canada Mfg." "Honda Canada, Inc." Honda de Mexico, S.A. de C.V. "American Honda Motor Co., Inc." "Honda Power Equipment" "Honda of South Carolina" Honda Power Train Georgia ?? "Honda Transmission"
Must Use
PER Honda Contact

Position: Loop: Level: Usage: Max Use: 280 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name 366 Contact Code Valid codes listed below BD Buyer Name or Department 93 Honda Planner Name
Must Use
Ref. Des. PER01
Attributes M ID 2/2
Must Use
PER02
AN 1/35
September 2007
14 - 13
N1 Supplier Name
Position: Loop: Level: Usage: Max Use: 295 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name Attributes 98 Supplier Identifier Code M ID 2/2 Valid codes listed below SU Supplier/Manufacturer 93 Supplier Name M AN 1/35 66 Supplier Identification Code Qualifier M ID 1/2 Valid codes listed below 92 Assigned by Buyer or Buyer's Agent 67 Supplier Number and Loc Code M AN 8/8 An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code (which may be 00).
Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
N3 Supplier Address
Position: Loop: Level: Usage: Max Use: 297 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name 166 Supplier Address - 1 Supplier street address 1 166 Supplier Address - 2 Supplier street address 2
Must Use
Ref. Des. N301 N302
14 - 14
September 2007

Position: Loop: Level: Usage: Max Use: 298 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name 19 City Name Supplier's city name 156 State or Province Code Supplier state or province name 116 Postal Code Supplier zip or postal code 26 Country Code Supplier Country Code
Ref. Des. N401 N402 N403 N404
Attributes M AN 2/30 M M M ID 2/2 ID 3/10 ID 2/3

Position: Loop: Level: Usage: Max Use: 299 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name 366 Supplier Contact Code Valid codes listed below SU Supplier Contact 93 Supplier Contact Name
Must Use
Ref. Des. PER01
Attributes M ID 2/2
Must Use
PER02
AN 1/30
September 2007
14 - 15
LIN Item Identification

Position: Loop: Level: Usage: Max Use: 010 LIN Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 235 Mfg Base Part Number Qualifier M ID 2/2 Valid codes listed below BP Buyer's Part Number 234 Mfg Base Part Number and Color M AN 1/29 235 DC Part Level Qualifier X ID 2/2 Valid codes listed below: BE Buyer's Engineering Change Level Number - "BE" Qualifier indicates the part must be shipped at this Design change level. EC Engineering Change Level - "EC" Qualifier is for reference only, parts may be shipped at another level. To determine the correct design level to ship, follow the Honda Specification Change "Instruction Sheet" or Instruction Summary from your Honda planner. - KEY POINT: ALWAYS LABEL THE PARTS WITH THE ACTUAL DESIGN LEVEL. 234 DC Part Level X AN 1/6 - For Honda Manufacturing facilities this field (and the corresponding qualifier) will be present for a Manufacturing Base Part Number that begins with a number less than 92. - For AHM, this field (and the corresponding qualifier) will not be present. 235 Part Description Qualifier M ID 2/2 Valid codes listed below PD Part Number Description 234 Part Description M AN 1/30 235 Release Number Qualifier M ID 2/2 Valid codes listed below RN Release Number 234 Release Number M AN 1/10 This number is a Honda application reference number. Suppliers will not return this data to Honda in any EDI document. 235 Project Number Qualifier X ID 2/2 Valid codes listed below: L1 Program Level 234 Project Number X AN 1/6 The business purpose for the project number will be defined at a later date. (Future Honda system enhancement).
Must Use
Ref. Des. LIN02
Must Use
LIN03 LIN04
LIN05
Must Use
LIN06
Must Use Must Use
LIN07 LIN08
Must Use
LIN09
LIN10
LIN11
14 - 16
September 2007
UIT Unit Detail

Position: Loop: Level: Usage: Max Use: 020 LIN Mandatory Detail Mandatory 1 Data Element Summary Data Element Name C001 Composite Unit of Measure 355 Unit or Basis for Measurement Code Refer to ANSI guidelines for a list of valid codes
Must Use Must Use
Ref. Des. UIT01 C00101
Attributes M M ID 2/2
DTM Cum Last Received Date

Position: Loop: Level: Usage: Max Use: Notes: 021 LIN Mandatory Detail Optional 1 - This segment is optional: - AHM, HCM, HDM, HMA, HPE, HPPG, HSC, and HTM will not transmit this data. - HAM will transmit this data except for the first transmission of a new part number (item number) as HAM plants convert to GPCS, they will not transmit this data - The quantity corresponding to this last received date is listed in QTY position 220, (the following segment). - When used, the last received date in conjunction with the quantity (in the QTY segment position 220) represents the quantity received by HAM as of the received date. Data Element Summary Data Element Name 374 Date/Time Qualifier Valid codes are listed below: 311 Latest Receiving Date/Cutoff Date Cum Qty Last Receipt Date Date expressed as CCYYMMDD Cum Qty Last Receipt Time Time expressed in 24-hour clock time as HHMM
Must Use
Ref. Des. DTM01
Attributes M ID 3/3
Must Use Must Use
DTM02 DTM03
373 337
M M
DT 8/8 TM 4/4
September 2007
14 - 17
QTY Cumulative Quantity

Position: Loop: Level: Usage: Max Use: Notes: 220 LIN Mandatory Detail Optional 1 - This segment is optional: - AHM, HCM, HDM, HMA, HPE, HPPG, HSC, and HTM will not transmit this data. - HAM will transmit this data except for the first transmission of a new part number (item number) as HAM plants convert to GPCS, they will not transmit this data - When used, the last received date (in the DTM segment position 021) in conjunction with the quantity represents the quantity received by Honda as of the received date. Data Element Summary Data Element Name 673 Quantity Qualifier Valid codes listed below 02 Cumulative Quantity 380 Cumulative Quantity
Must Use
Ref. Des. QTY01
Attributes M ID 2/2
Must Use
QTY02
R 1/15
TD1 Container Details

Position: Loop: Level: Usage: Max Use: 240 LIN Mandatory Detail Mandatory 1 Data Element Summary Ref. Des. TD102 TD105 Data Element Name 80 Quantity Per Container 79 Container Type - Container type as designated by Honda - "XX" will be used for non-returnable containers
Must Use Must Use
14 - 18
September 2007
N1 Ship To Location
Position: Loop: Level: Usage: Max Use: Notes: 320 N1 Mandatory Detail Mandatory 1 AHM will not provide ship to information in the 830. For AHM, "Ship To Name" will be filled with XX and "Ship To Code" will be filled with "XX" or YY. Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid codes are listed below ST Ship To 93 Ship To Name M AN 1/35 66 Ship To Code Qualifier M ID 1/2 Valid Code Listed Below 92 Assigned by Buyer or Buyer's Agent 67 Ship To Code M AN 2/8 This is the code assigned by Honda for this ship to location - For OEM forecasts, this will be a ship to code - For DSPS forecasts, this will be the supplier number and location code
Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
N3 Ship To Address
Position: Loop: Level: Usage: Max Use: Notes: 340 N1 Mandatory Detail Mandatory 1 AHM will not provide ship to information in the 830. The mandatory field will be filled with "XX". Data Element Summary Data Element Name 166 Ship To Address 1 166 Ship To Address 2
Must Use
Ref. Des. N301 N302
September 2007
14 - 19
N4 Ship To Geographic Location

Position: Loop: Level: Usage: Max Use: Notes: 350 N1 Mandatory Detail Mandatory 1 AHM will not provide ship to information in the 830. The mandatory fields will contain "X"'s. Data Element Summary Ref. Des. N401 N402 N403 N404 Data Element 19 156 116 26 Name Ship To City Ship To State or Province Code Ship To Postal Code Ship To Country Code Attributes M AN 2/30 M ID 2/2 M ID 3/10 M ID 2/3
14 - 20
September 2007
FST Forecast Schedule

Position: Loop: Level: Usage: Max Use: Notes: 410 FST Mandatory Detail Mandatory 1 Shipment information will be included in the 862 Ship Schedule. Data Element Summary Data Element Name Attributes 380 Quantity M R 1/15 680 Forecast Qualifier M ID 1/1 Valid codes are listed below. Only one Forecast Qualifier can be used per time bucket. C Firm - For Production 830's this will be immediate or past due demand. - For Flex Forecast 830's this will not be present. D Planning - For Production 830's this will be a forecast of future demand. - For Flex Forecast 830's this will not be present. F Potential Order Increase - For Production 830's this will not be present. - For Flex Forecast 830's this will represent the potential increase in quantity in addition to the Production 830 quantity. X Modification - For Production 830's this will not be present. - For Flex Forecast 830's this will represent the actual change in production for that period compared to the Production 830. This could be a positive or negative value. 681 Forecast Timing Qualifier M ID 1/1 Valid codes are listed below: C Daily M Monthly Bucket (Calendar Months) - AHM will use "Monthly Bucket" versus "Four Week Bucket" T Four Week Bucket (13 buckets per year) - When used, the manufacturing plants will use "Four Week Bucket" versus "Monthly Bucket" W Weekly Bucket (Monday through Sunday) 373 Date-Period Start M DT 8/8 - This is the forecast start date. - Beginning date of period if weekly, four week or monthly buckets. Actual date of period if daily. - For weekly and four week buckets, the periods are calculated sequentially on a weekly basis, always starting on a Monday. - For daily buckets HAM will always start on a Monday. (As HAM converts to
Must Use Must Use
Ref. Des. FST01 FST02
Must Use
FST03
Must Use
FST04
September 2007
14 - 21

GPCS, the below rule will apply.) - For daily buckets HCM, HMA, HPE, HPPG, HSC, and HTM will start on the first business day of the week. (Example - If there is a holiday on Monday, the first daily bucket will be Tuesday.) - Date expressed as CCYYMMDD.

Position: Loop: Level: Usage: Max Use: 010 Summary Mandatory 1
Must Use Must Use
Ref. Des. CTT01 CTT02
Data Element Summary Data Element Name Attributes 354 Number of Line Items M N0 1/6 The accumulation of the number of LIN segments. 347 Hash Total M R 1/10 Sum of the values of the quantities (FST01) for each segment.

Must Use Must Use
Ref. Des. SE01 SE02
14 - 22
September 2007
Replacement Logic
Replacement:
Honda sends the 830 as a replacement document. The 830 purpose code transmitted in the BFR01 element is always 05, replace. A document may be replaced for various reasons; including replacing an error in a previous document or issuing a new weekly release that replaces the previous weekly release. Supplier systems should have the capability to compare successive incoming Weekly Releases and replace items that are identical for change points listed below. Replacement of items from the new 830 should be based upon a match of: Schedule Type Qualifier, BFR04 (Position 020) Honda Plant ID, N104 (Position 230) Manufacturing Base Part Number and Color, LIN03 (Position 010) Ship To Code, N104 (Position 320) Usually an 830 consists of a full range of supplier's parts, but it could be a sub-set of supplier parts.
Retransmission:
Honda can retransmit the 830 document also. Retransmission will only occur when the supplier requests that Honda resends the EDI document. This is typically because the supplier had some problem in the translation processing. A retransmitted document can be overlaid based upon the same logic as the replacement logic above.
September 2007
14 - 23
Flex Forecast
1. The Flex Forecast will provide potential forecast changes due to adjustments in sales quantities. Should be used for raw material planning purposes. Suppliers are expected to minimize their unused materials at the end of a model year. Honda will use this information to evaluate compensation requests. 2. The Flex Forecast will contain 9-14 weeks of information Weeks 1-3 will reflect the Fixed Flex usage. These values have been incorporated into the first two weeks of the Production Forecast. These values are frozen. The increase/decrease in actual usage should be used to adjust quantities of future materials orders. Weeks 4-14 will reflect the potential quantity increases. These values are not incorporated into the Production Forecast. These values are not frozen. These values represent the maximum increase to production for a given period. Suppliers must plan to accommodate this demand. 3. The Fixed Flex usage may be a positive or negative value. It will represent the actual increase/decrease to the previously transmitted forecast value. Upon receipt of the Flex Forecast the supplier should analyze the Fixed quantities and adjust future orders accordingly. The following page provides examples on: Positive Fixed Flex A positive value that represents an increase in demand. Hondas usage is greater than forecasted on the Production forecast. Will be transmitted when Honda is building more of a certain vehicle than forecasted. Negative Fixed Flex A negative value that represents a decrease in demand. Hondas usage is less than forecasted on the Production forecast. Will be transmitted when Honda is building less of a certain vehicle than forecasted. Please refer to the following for examples on how to interpret the Fixed Flex values described above.
14 - 24
September 2007
Flex Forecast Examples:

The following examples illustrate how the flex forecast can be used to improve decision making and reduce on-hand inventory levels. The examples have the following underlying assumptions: It is the week of September 1st Supplier is ordering for the week of October 13th (six-week lead-time). On-hand inventory/safety stock is zero. Based on previous Flex Forecasts, the supplier ordered 1,400 units for the week of 9/15.
Positive Fixed Flex Value

The Fixed flex value has been received with an actual quantity of 1,200 parts for 9/15. Based on the assumptions above the supplier has over-ordered for 9/15 by 200 units. This information can be used to make a more accurate order for the 10/13 weekly bucket. The calculations for this example are shown below:
Production Forecast 01-SEP 08-SEP 15-SEP 22-SEP 29-SEP 06-OCT 13-OCT 20-OCT 10240 10400 9000 9000 9000 9000 9000 9000
Flex Forecast 01-SEP 08-SEP 15-SEP 22-SEP 29-SEP 06-OCT 13-OCT 20-OCT 1440 1500 1200 600 1200 1500 1300 1000
9/15 Fixed Flex (Negative): + 1,200 units *9/15 Original Flex Forecast: + 1,400 units 9,000 units 10/13 Production Forecast: 10/13 Flex Forecast: + 1,300 units *Original Flex value was sent in a previous week Planner should be prepared to cover 10,300 for 10/13. May need to adjust 10/13 order by 200 units.
September 2007
14 - 25
Negative Fixed Flex Value

This example follows the same assumptions as the Positive Fixed Flex Value, however Fixed flex value is a negative 1,000 units. Based on this, the supplier has over-ordered for 9/15 by 2,400 units. See calculations below:
Production Forecast 01-SEP 10240 08-SEP 10400 Flex Forecast 01-SEP 1440 08-SEP 1500 15-SEP -1000 22-SEP 600 29-SEP 1200 06-OCT 1500 13-OCT 1300 20-OCT 1000 15-SEP 9000 22-SEP 9000 29-SEP 9000 06-OCT 9000 13-OCT 9000 20-OCT 9000
9/15 Fixed Flex (Negative): - 1,000 units *9/15 Original Flex Forecast: + 1,400 units 9,000 units 10/13 Production Forecast: 10/13 Flex Forecast: + 1,300 units *Original Flex value was sent in a previous week Planner should be prepared to cover 10,300 for 10/13. May need to adjust 10/13 order by 2,400 units.
Note The adjustment amount will be a negative or zero value as Honda will not consume more than the total of the Production and Flex quantities.
14 - 26
September 2007
Chapter 15 Price/Sale Catalog (832)

Price/Sale Catalog (832)
September 2007
15 - 1
Chapter Contents
This chapter contains information and procedures for using Hondas Price/Sale Catalog transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 3 Transaction Covered........................................................................................................................... 3 Application Standards and Conventions............................................................................................. 3 Mapping .............................................................................................................................................. 3 Exceptions/ Clarifications.................................................................................................................... 3 Schedule ............................................................................................................................................. 3 Specifications ...................................................................................................................................... 3 Back-Up Procedure............................................................................................................................. 3 Business Purpose ................................................................................................................................ 4 Transaction Specification Information ............................................................................................... 5 Transaction Specifications.................................................................................................................. 6 Functional Group ID=SC ................................................................................................................. 6 ST Transaction Set Header............................................................................................................. 7 BCT Beginning Segment for Price/Sales Catalog........................................................................... 7 DTM Create Date/Time Reference ................................................................................................. 8 N1 Name - Honda ........................................................................................................................... 8 N2 Corporate Name ........................................................................................................................ 9 PER Honda Contact Info ............................................................................................................... 10 N1 Name - Supplier....................................................................................................................... 11 PER Administrative Contact - Supplier ......................................................................................... 11 LIN Item Identification.................................................................................................................... 12 CTP Pricing Information ................................................................................................................ 12 DTM Date/Time Reference - Retro ............................................................................................... 13 DTM Date/Time Reference - Effective .......................................................................................... 13 DTM Date/Time Reference - Expired............................................................................................ 14 CUR Currency ............................................................................................................................... 14 REF Price Reference .................................................................................................................... 15 CTT Transaction Totals................................................................................................................. 16 SE Transaction Set Trailer ............................................................................................................ 16 Overview ........................................................................................................................................... 17 Replacement Logic ........................................................................................................................... 18 Retransmission ................................................................................................................................. 18
15 - 2
September 2007
Transaction Covered
Price/Sales Catalog (Transaction Set 832), abbreviated "SC".

The 832 set is based upon the ANSI ASC X12 Release 004010 document.
Mapping
A list of the Price/Sales Catalog business data elements and how they will be transmitted via EDI Standards is provided in the Transaction Specifications section.
Exceptions/ Clarifications
Schedule
The Price/Sales Catalog will be transmitted monthly.
Specifications
It is possible for Honda to transmit multiple Price/Sale Catalogs within one envelope. This means that there may be multiple transaction sets (ST-SE header/trailer segments) within one interchange envelope (ISAIEA header/trailer segments). Honda transmits all EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up Procedure
In the event of failure of Electronic Data Interchange, it is the responsibility of the sending party to transmit the contents of any pending Transmission to the receiving party using a method of non-EDI transmission which is timely, reasonable, and appropriate under the circumstances.
September 2007
15 - 3
Business Purpose
The Honda Price/Sale Catalog (ANSI 832) transaction set is used to facilitate agreement between Honda and Suppliers regarding the part price on file as of a specified date. The Price/Sale Catalog is used for informational purposes only and does not supersede or replace the existing quotation approval process.
FREQUENCY: Whenever a price change occurs or upon request TRANSMITTED TO: Service Parts Suppliers OEM suppliers TRANSMITTED FROM: Honda
15 - 4
September 2007


The second column:
3. The third column: x/y, where
September 2007
15 - 5
Functional Group ID=SC
Heading:
Must Use Must Use Must Use Pos. No. 010 020 070 Seg. ID ST BCT DTM Name Transaction Set Header Beginning Segment for Price/Sales Catalog Create Date/Time Reference LOOP ID - N1 Must Use Must Use Must Use 150 160 200 N1 N2 PER Name - Honda Corporate Name Honda Contact Info LOOP ID - N1 Must Use Must Use 202 208 N1 PER Name - Supplier Administrative Contact - Supplier M M 1 1 M M M 1 1 >1 1 Req. Des. M M M Max.Use 1 1 1 1 Loop Repeat
Detail:
Pos. No. Must Use 010 Seg. ID LIN Name LOOP ID - LIN Item Identification LOOP ID - CTP Must Use 170 176 Must Use Must Use Must Use Must Use 178 180 200 225 CTP DTM DTM DTM CUR REF Pricing Information Date/Time Reference - Retro Date/Time Reference - Effective Date/Time Reference - Expired Currency Price Reference M O M M M M 1 1 1 1 1 >1 Req. Des. M Max.Use 1 100 Loop Repeat 700000
Summary:
15 - 6
September 2007

Must Use
Ref. Des. ST01
Must Use
ST02
Data Element Summary Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes are listed below: 832 Price/Sales Catalog 329 Transaction Set Control Number M AN 4/9 This number will be unique (within a transaction set) and ascending. It may be sequential.
BCT Beginning Segment for Price/Sales Catalog

Must Use
Ref. Des. BCT01
Must Use
BCT10
Data Element Summary Data Element Name Attributes 683 Catalog Purpose Code M ID 2/2 Valid codes are listed below: PC Price Catalog SC Sales Catalog 353 Transaction Set Purpose Code M ID 2/2 Valid codes are listed below: 04 Change - This code will be used when issuing a price change for a sub-set of parts. 08 Status - This code will be used in response to a request for a catalog of parts. (Supplier requested) 52 Response to Historical Inquiry - This code will be used in response to a request for historical pricing information. (Supplier requested) - AHM does not support this functionality.
September 2007
15 - 7
DTM Create Date/Time Reference

Must Use
Ref. Des. DTM01
Must Use Must Use
DTM02 DTM03
Data Element Summary Data Element Name Attributes 374 Date/Time Qualifier M ID 3/3 Valid Qualifier listed below: 097 Transaction Creation 373 Create Date M DT 8/8 This is the date the document was created. Date expressed as CCYYMMDD. 337 Create Time M TM 4/4 This is the date the document was created. Time expressed in 24-hour clock time as HHMM
N1 Name - Honda
Must Use
Ref. Des. N101
Must Use
N102
Data Element Summary Data Element Name 98 Entity Identifier Code Valid codes are listed below: 16 Plant 93 Plant Name
Attributes M ID 2/2
AN 1/35
Must Use
N103
66
Must Use
N104
67
Honda Plant ID Qualifier M ID 1/2 Valid codes are listed below: 6 Plant Code Honda Plant ID M AN 3/3 Details on what plant ID the pricing information applies to. Examples: - For American Honda Motor, "AHM" will be used. - For Honda of America, 100 will be used - For Honda of Canada, "HCM" will be used. - The above is not an all-inclusive list, please refer to REF segment in position 225 (REF02) for more plant IDs.
As HAM plants convert, could be HAM
15 - 8
September 2007
N2 Corporate Name
Position: Loop: Level: Usage: Max Use: 160 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name Attributes 93 Corporation Name M AN 1/35 The corporate name for the Honda facility issuing this document. For example: (May not be an all-inclusive list.) "Honda of America Mfg., Inc." "Honda Manufacturing of Alabama, LLC" "Honda of Canada Mfg." "Honda Canada, Inc." Honda de Mexico, S.A. de C.V. "American Honda Motor Co., Inc." "Honda Power Equipment" "Honda of South Carolina" Honda Power Train Georgia ?? "Honda Transmission"
Must Use
Ref. Des. N201
September 2007
15 - 9
PER Honda Contact Info

Position: Loop: Level: Usage: Max Use: 200 N1 Mandatory Heading Mandatory >1 Data Element Summary Data Element Name Attributes 366 Contact Function Code M ID 2/2 Valid codes are listed below: AD Accounting Department AE Corporate Purchasing Agent BD Buyer Name or Department 93 Name O AN 1/35 365 Telephone Number Qualifier X ID 2/2 Valid codes are listed below: TE Telephone 364 Telephone Number X AN 1/15 365 Fax Number Qualifier X ID 2/2 Valid codes are listed below: FX Facsimile 364 Fax Number X AN 1/15 365 E-Mail Qualifier X ID 2/2 Valid codes are listed below: EM Electronic Mail 364 E-Mail Address X AN 1/80 443 Honda Plant ID O AN 3/8 This is the Honda code number for the logistical company which the stated contact represents. Please refer to N104 (Position 150) for a complete list of codes.
Must Use
Ref. Des. PER01
PER02 PER03
PER04 PER05
PER06 PER07
PER08 PER09
15 - 10
September 2007
N1 Name - Supplier
Position: Loop: Level: Usage: Max Use: 202 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid codes are listed below: SE Selling Party 93 Supplier Name M AN 1/35 66 Identification Code Qualifier M ID 1/2 Valid codes are listed below: 92 Assigned by Buyer or Buyer's Agent 67 Supplier Number and Location Code M AN 8/8 An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code (which may be "00".)
Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
PER Administrative Contact - Supplier

Position: Loop: Level: Usage: Max Use: 208 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name 366 Contact Function Code Valid codes are listed below: SR Sales Representative or Department 93 Sales Contact Name
Must Use
Ref. Des. PER01
Attributes M ID 2/2
Must Use
PER02
AN 1/35
September 2007
15 - 11

Position: Loop: Level: Usage: Max Use: 010 LIN Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 235 Product ID Qualifier M ID 2/2 Valid codes are listed below: BP Buyer's Part Number 234 Mfg. Base Part Number and Color M AN 1/29 235 DC Part Level Qualifier X ID 2/2 This element must be used if LIN05 is present. Valid codes are listed below: EC Engineering Change Level 234 DC Part level X AN 1/6 This field (and the corresponding qualifier) will be present only if the item is priced by D/C level. 235 Part Description Qualifier M ID 2/2 Valid codes are listed below: PD Part Number Description 234 Part Description M AN 1/30
Must Use
Ref. Des. LIN02
Must Use
LIN03 LIN04
LIN05
Must Use
LIN06
Must Use
LIN07
CTP Pricing Information

Position: Loop: Level: Usage: Max Use: 170 CTP Mandatory Detail Mandatory 1 Data Element Summary Data Element Name 236 Price Identifier Code Valid codes are listed below: CAT Catalog Price - Price in Honda's approved quote file 212 Unit Price 380 Pricing Quantity This is expected to be "1" C001 Composite Unit of Measure 355 Unit or Basis for Measurement Code Refer to ANSI guidelines for a list of valid codes
Must Use
Ref. Des. CTP02
Attributes M ID 3/3
CTP03 CTP04 CTP05 C00101
M M M M
R 1/15 R 1/15
ID 2/2
15 - 12
September 2007
DTM Date/Time Reference - Retro

Position: Loop: Level: Usage: Max Use: Notes: 176 CTP Mandatory Detail Optional 1
When Honda determines a price needs to be adjusted retroactively, this segment will be transmitted. The amount of the adjustment is not communicated in the 832, just the retro date. Any adjustment would appear on the 820s (in addition to receipt information).
Must Use
Ref. Des. DTM01
Must Use
DTM02
Data Element Summary Data Element Name 374 Date/Time Qualifier - Retro. Valid codes are listed below: 232 Claim Statement Period Start 373 Retro Price Start Date Date expressed as CCYYMMDD
Attributes M ID 3/3
DT 8/8
DTM Date/Time Reference - Effective

Position: Loop: Level: Usage: Max Use: Notes: 178 CTP Mandatory Detail Mandatory 1
This segment provides the date the corresponding price becomes active.
Must Use
Ref. Des. DTM01
Must Use Must Use
DTM02 DTM03
Data Element Summary Data Element Name 374 Date/Time Qualifier Valid codes are listed below: 007 Effective 373 Effective Date Date expressed as CCYYMMDD 337 Effective Time Time expressed in 24-hour clock time as HHMM
Attributes M ID 3/3
M M
DT 8/8 TM 4/4
September 2007
15 - 13
DTM Date/Time Reference - Expired

Position: Loop: Level: Usage: Max Use: Notes: 180 CTP Mandatory Detail Mandatory 1
This segment provides the date the corresponding price becomes in-active.
Must Use
Ref. Des. DTM01
Must Use
DTM02
Must Use
DTM03
Data Element Summary Data Element Name Attributes 374 Date/Time Qualifier M ID 3/3 Valid codes are listed below: 036 Expiration 373 Expired Date M DT 8/8 Date expressed as CCYYMMDD. Honda will usually transmit "99991231" in this field, indicating this price will be in effect until a new price change is transmitted. 337 Expired Time M TM 4/4 Time expressed in 24-hour clock time as HHMM
CUR Currency
Position: Loop: Level: Usage: Max Use: 200 CTP Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid codes are listed below: N4 Price Administration 100 Currency Code M ID 3/3 Code (Standard ISO) for country in whose currency the charges are specified. Examples of some of the valid codes are listed below: 'CAD' = CANADIAN DOLLAR 'JPY' = JAPANESE YEN 'USD' = U.S. DOLLAR
Must Use
Ref. Des. CUR01
Must Use
CUR02
15 - 14
September 2007
REF Price Reference

Position: Loop: Level: Usage: Max Use: Notes: 225 CTP Mandatory Detail Mandatory >1
This segment will identify a logistical company and / or a pricing category for a particular part.
Must Use
Ref. Des. REF01
Data Element Summary Data Element Name 128 Qualifier Valid codes are listed below: CA Cost Allocation Reference PE Plant Number
Attributes M ID 2/3
Must Use
REF02
127
Price Reference M AN 2/5 - If the qualifier is "CA", cost allocation reference, the price information in this CTP loop is effective for the pricing category listed in this element. For example: (May not be an all-inclusive list.) PPMP = Part Price for Mass Production PPNM = Part Price for New Model PPTMP = Temporary Service Parts Price - Firm Quote Required PPSP = Part Price for Service Parts PPI1 = Part Price for IPS (1st price) PPI2 = Part Price for IPS (2nd price) PPI3 = Part Price for IPS (3rd price) - If the qualifier is "PE", plant number, the price information in this CTP loop is effective for the logistical company (plant ID) listed in this element. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM = HAM - Marysville Auto Plant (MAP-used for GPCS) HAM - East Liberty Auto Plant (ELP-used for GPCS) HAM - Marysville Motorcycle Plant (MMP-used for GPCS) HAM - International Parts Supply (IPS-used for GPCS) HAM - Service Parts Procurement (IPS-used for GPCS) HAM - International Parts Supply for Honda de Mexico (IPS-for GPCS) HAM - Anna Engine Plant (AEP-used for GPCS) American Honda Motor Co., Inc. Honda of Canada Mfg. Honda de Mexico Honda Manufacturing of Alabama Honda Manufacturing of Indiana Honda Power Equipment Honda Precision Parts Georgia Honda of South Carolina Honda Transmission
September 2007
15 - 15
Must Use
REF03
352
Price Reference Description M AN 1/80 -For Honda manufacturing facilities, this element will describe the price reference listed in the previous element. - For AHM, this element will contain the quote number followed by the description of the price reference listed in the previous element. The first ten characters will contain the quote number followed by a dash ("-"). If there is no quote number, the first ten characters will be blanks.

Must Use
Ref. Des. CTT01
Data Element Summary Data Element Name 354 Number of Line Items The accumulation of the number of LIN segments.
Attributes M N0 1/6

Position: Loop: Level: Usage: Max Use: 020 Summary Mandatory 1 Data Element Summary Data Element Name 96 Number of Included Segments 329 Transaction Set Control Number
Must Use Must Use
Ref. Des. SE01 SE02
15 - 16
September 2007
Overview
1. 2. 3. The 832 Price/Sales Catalog automatically provides the effective date of a price change between Honda and a Supplier. The 832 Price/Sales Catalog is for informational purposes and does not supersede or replace the existing Honda quotation approval process. Suppliers should integrate the 832 Price/Sales Catalog to their Accounts Receivable system(s) to ensure that their Accounts Receivable system is tracking expected payments from Honda at the proper price. Suppliers may monitor the arrival of 832 Price/Sales Catalogs at their system to confirm that approved quotes have been applied at Honda. Suppliers may notify their Purchasing contact of any discrepancy. The 832 Price/Sales Catalog may also be used to respond to a request by a supplier for reconciliation information. Two additional formats are supported: a. The current price in effect for a range of the supplier parts. The range of parts may vary from one part to every part the supplier provides. b. The pricing history for a range of the suppliers parts. The range of parts may vary from one part to every part the supplier provides. Suppliers should notify their Accounts Payable contact at Honda to request either of these formats.
4.
5.
September 2007
15 - 17
Replacement Logic
Replacement logic for 832s sent from Honda to a supplier varies depending on the Transaction Set Purpose Code (BCT10). If the Transaction Set Purpose Code (BCT10) = 04 (change), replacement of one item by another is based upon a match of: Manufacturing Base Part Number (LIN03) and Price Reference (REF02, Position 225). If the Transaction Set Purpose Code (BCT10) = 08 (status), the document stands alone and replacement is at the suppliers discretion. If the Transaction Set Purpose Code (BCT10) = 52 (response to historical inquiry), the document stands alone and should not be replaced.
Retransmission
Honda can retransmit the 832 document. Retransmission will only occur when the supplier requests that Honda resends the EDI document. This is typically because the supplier had some problem in the translation process. A retransmitted document can be overlaid based upon the same logic as the replacement logic above.
15 - 18
September 2007
Chapter 16 Inventory Advice Inbound to Honda (846)
EDI & Barcode Label Implementation Requirements

Inventory Advice Inbound to Honda (846)
April 2008
16 - 1
Chapter Contents
This chapter contains information and procedures for using the Honda Inbound Inventory Advice transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 3 Transaction Covered........................................................................................................................... 3 Application Standards and Conventions............................................................................................. 3 Mapping .............................................................................................................................................. 3 Exceptions/ Clarifications.................................................................................................................... 3 Schedule ............................................................................................................................................. 3 Specifications ...................................................................................................................................... 3 Back-Up Procedure............................................................................................................................. 3 Business Purpose ................................................................................................................................ 4 Transaction Specification Information ............................................................................................... 5 846 Inventory Advice (Honda Inbound).............................................................................................. 6 Functional Group ID=IB................................................................................................................... 6 ST Transaction Set Header............................................................................................................. 7 BIA Beginning Segment for Inventory Advice ................................................................................. 7 N1 Honda Ordering Plant Location ................................................................................................. 8 N1 Supplier Name ........................................................................................................................... 9 LIN Item Identification.................................................................................................................... 10 DTM Cycle Count Date ................................................................................................................. 12 DTM Last Shipment Received Date.............................................................................................. 12 QTY Quantity................................................................................................................................. 13 UIT Unit Detail ............................................................................................................................... 14 LS Loop Header ............................................................................................................................ 14 REF Parent Part Number Identification......................................................................................... 15 DTM Last Shipment Sent Date...................................................................................................... 15 N1 Parent Name............................................................................................................................ 16 LE Loop Trailer.............................................................................................................................. 17 CTT Transaction Totals................................................................................................................. 17 SE Transaction Set Trailer ............................................................................................................ 18
16 - 2
April 2008
Transaction Covered
Inventory Advice/Inquiry (Transaction Set 846), abbreviated "IB.

Mapping
A list of the Inventory Advice/Inquiry business data elements and how they are transmitted via EDI Standards is provided in the Transaction Specifications section.
Schedule
1. 2. The Honda Inbound Inventory Advice for an Inventory Adjustment or a Receipt Adjustment is transmitted as needed by the supplier. The Honda Inbound Inventory Advice for a Cycle Count is transmitted according to the schedule contained in the Cycle Count request (Honda Outbound Inventory Advice).
Specifications
Honda expects all EDI data to be in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up Procedure
In the event of failure of Electronic Data Interchange it is the responsibility of the sending party to transmit the contents of any pending Transmission to the receiving party using a method of non-EDI transmission that is timely, reasonable, and appropriate under the circumstances.
April 2008
16 - 3
Business Purpose
The Honda Inbound Inventory Advice (ANSI 846) transaction set allows the Supplier to communicate inventory information to Honda. The Inbound 846 has three possible uses: 1. 2. 3. To be sent in response to a cycle count request, To inform Honda of an Inventory Adjustment on a DSPS part, To inform Honda of a receiving discrepancy between a DSPS ASN and the actual receipt.
FREQUENCY: Exceptional conditions or on request TRANSMITTED FROM: OEM Suppliers DSPS Suppliers Service Parts Suppliers TRANSMITTED TO: Honda
16 - 4
April 2008

The following Transaction Specifications consist of two sections: 1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality. Note - The Req. Des. for the first segment in a loop is also used for that corresponding loop. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column: M = Mandatory, X = Conditional, O = Optional The second column: ID = Identifier (a unique value from a predefined list from ANSI) DT = Date TM = Time AN = Alphanumeric R = Numeric with a variable decimal place Nx = Numeric with x decimal places The third column: x/y, where x = the minimum number of digits for this element and y = the maximum number of digits for this element.
2.
April 2008
16 - 5
846 Inventory Advice (Honda Inbound)

Functional Group ID=IB
Heading:
Must Use Must Use Pos. No. 010 020 Seg. ID ST BIA Name Transaction Set Header Beginning Segment for Inventory Advice LOOP ID - N1 Must Use 077 N1 Honda Ordering Plant Location LOOP ID - N1 Must Use 136 N1 Supplier Name M 1 M 1 1 Req. Des. M M Max.Use 1 1 1 Loop Repeat
Detail:
Pos. No. Must Use 010 100 105 Seg. ID LIN DTM DTM Name LOOP ID - LIN Item Identification Cycle Count Date Last Shipment Received Date LOOP ID - QTY Must Use Must Use 320 330 380 QTY UIT LS Quantity Unit Detail Loop Header LOOP ID - REF 390 400 410 440 REF DTM N1 LE Parent Part Number Identification Last Shipment Sent Date Parent Name Loop Trailer O O O O 1 1 1 1 M M O 1 1 1 >1 Req. Des. M C C Max.Use 1 1 1 1 Loop Repeat 10000
Summary:
16 - 6
April 2008

Must Use
Ref. Des. ST01
Must Use
ST02
Data Element Summary Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes are listed below 846 Inventory Inquiry/Advice 329 Transaction Set Control Number M AN 4/9 This number must be unique for this transaction set. It may not be repeated within 18 months. A duplicate number will cause the transaction to be rejected.
BIA Beginning Segment for Inventory Advice

Must Use
Ref. Des. BIA01
Must Use
BIA02
BIA03 BIA04 BIA05 BIA06
Data Element Summary Data Element Name Attributes 353 Transaction Set Purpose Code M ID 2/2 Valid Codes Listed Below 00 Original 01 Cancellation 05 Replace 755 Report Type Code M ID 2/2 Valid Code Listed Below MB Manufacturer/Distributor Inventory Report 127 Inventory Advice Number M AN 1/8 This number is assigned by the supplier. It must not repeat for 18 months. 373 Create Date M DT 8/8 Date expressed as CCYYMMDD 337 Create Time M TM 4/4 Time expressed in 24-hour clock time as HHMM 306 Action Code M ID 1/2 Valid codes listed below 5 Send
April 2008
16 - 7

Ref. Des. N101 N103 N104
Data Element Summary Data Element Name 98 Entity Identifier Code 16 Plant 66 Identification Code Qualifier 6 Plant Code 67 Honda Ordering Plant ID This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM =
Attributes M ID 2/2 M M ID 1/2 AN 3/3
16 - 8
April 2008
N1 Supplier Name
Must Use
Ref. Des. N101
Must Use
N103
Must Use
N104
Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid Code Listed Below SU Supplier/Manufacturer 66 Supplier Number Qualifier M ID 1/2 Valid Code Listed Below 92 Assigned by Buyer or Buyer's Agent 67 Supplier Number and Loc Code M AN 8/8 An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code (which may be 00.)
April 2008
16 - 9

Position: Loop: Level: Usage: Max Use: 010 LIN Mandatory Detail Mandatory 1
Ref. Des. LIN01
Must Use
LIN02
Must Use
LIN03 LIN04
LIN05
Must Use
LIN06
Must Use
LIN07
LIN08
LIN09
Data Element Summary Data Element Name Attributes 350 Sequence Number X AN 1/2 - This element is mandatory only in response to a Cycle Count request. - The sequence number comes from the corresponding LIN01 in the Honda outbound 846 requesting the Cycle Count. - This element should not be used in a Receipt Adjustment or an Inventory Adjustment). 235 Mfg Base Part Qualifier M ID 2/2 Valid codes are listed below BP Buyer's Part Number 234 Mfg Base Part Number and Color M AN 1/29 235 D/C Part Level Qualifier X ID 2/2 Valid codes are listed below BE Buyer's Engineering Change Level Number 234 D/C Part Level X AN 1/6 - "BE" Qualifier indicates that the actual D/C level of the part should be put in this element. - For Honda manufacturing facilities this field (and the corresponding qualifier) should only be used for an RA when the Manufacturing Base Part Number begins with a number less than 92. - For Honda manufacturing facilities this field (and the corresponding qualifier) should not be present for a CC or IA. - For AHM, this field (and the corresponding qualifier) should not be present. 235 IA Function Code Qualifier M ID 2/2 Valid codes are listed below A3 Locally Assigned Control Number 234 IA Function Code M AN 2/2 - "CC" = Cycle Count Response (Actual on-hand qty in response to Honda inquiry) - "IA" = Inventory Adjustment (Change to on-hand qty due to a specific reason) - "RA" = Receiving Adjustment (Qty received +/- ASN Qty) 235 Project Number Qualifier X ID 2/2 Valid codes are listed below: L1 Program Level 234 Project Number X AN 1/6 - LIN08 & 09 are only used in an RA when a valid project number is assigned to the corresponding Manufacturing Base Part Number. - LIN08 & 09 should not be present for a CC or IA.
16 - 10
April 2008
LIN10
235
LIN11
234
LIN12
235
LIN13
234
LIN14
235
LIN15
234
LIN16
235
LIN17
234
LIN18
235
DSPS ASN Qualifier X ID 2/2 Valid codes are listed below. LS Load Sequence DSPS ASN Number of Last Shipment Received X AN 8/8 - LIN10 & 11 must be provided for a RA referencing a domestic parts receipt. - LIN10 & 11 should not be present for a CC or IA. - LIN10 & 11 is mutually exclusive of LIN20 & 21. DSPS Supplier Number Qualifier X ID 2/2 Valid codes are listed below MF Manufacturer DSPS Supplier Number and Location Code X AN 8/8 - This is the supplier number of the DSPS shipper, (versus the DSPS receiver who is creating the 846). - LIN12 & 13 must be provided for a RA. - LIN12 & 13 should not be present for a CC or IA. DSPS Purchase Order Qualifier X ID 2/2 Valid codes are listed below PO Purchase Order Number DSPS Purchase Order Number of Last Shipment X AN 1/10 - This field is only mandatory for Honda suppliers completing an RA who receive DSPS supply parts via a Purchase Order. - LIN14 & 15 should not be present for a CC or IA. - LIN14 & 15 are mutually exclusive of LIN16 & 17 for an RA. DSPS Ship Schedule Qualifier X ID 2/2 Valid codes are listed below PR Process Number DSPS Ship Schedule Number of Last Shipment X AN 1/6 - This field is only mandatory for Honda suppliers completing an RA who receive DSPS supply parts via a Ship Schedule. - LIN16 & 17 should not be present for a CC or IA. - LIN16 & 17 are mutually exclusive of LIN14 & 15. Original Document ID Qualifier X ID 2/2 Valid codes are listed below A6 Document Identification Code Original Document ID Number X AN 6/6 - This element is mandatory for a Cycle Count response (LIN07=CC). - The data value can be found in the corresponding Honda outbound 846 BIA03. - This element should not be used for a Receipt Adjustment (RA) or Inventory Adjustment (IA). PC Number Qualifier X ID 2/2 Valid codes are listed below CR Contract Number PC Number (JSP) X AN 12/12 - LIN20 & 21 must be provided for a RA referencing a Japan parts receipt. - LIN20 & 21 should not be present for a CC or IA. - LIN20 & 21 are mutually exclusive of LIN10 & 11.
LIN19
234
LIN20
235
LIN21
234
April 2008
16 - 11
DTM Cycle Count Date

Position: Loop: Level: Usage: Max Use: Notes: 100 LIN Mandatory Detail Conditional 1 - This segment should contain the actual date & time the supplier completed the cycle count. - This segment must be completed for a CC (Cycle Count) response. - This segment should not be completed for a IA or RA. Data Element Summary Data Element Name Attributes 374 Date Qualifier M ID 3/3 Valid codes are listed below. 167 Most Recent Revision (or Initial Version) 373 Actual Count Date M DT 8/8 Date expressed as CCYYMMDD. 337 Actual Count Time M TM 4/4 Time expressed in 24-hour clock time as HHMM
Must Use
Ref. Des. DTM01
Must Use Must Use
DTM02 DTM03
DTM Last Shipment Received Date

Position: Loop: Level: Usage: Max Use: Notes: 105 LIN Mandatory Detail Conditional 1 - This segment should contain the last shipment received date & time of the part being cycle counted. - This segment must be completed for a CC (Cycle Count) response. - This segment should not be completed for a IA or RA. Data Element Summary Data Element Name 374 Date Qualifier Valid codes are listed below. 050 Received 373 Last Shipment Received Date Date expressed as CCYYMMDD 337 Last Shipment Received Time Time expressed in 24-hour clock time as HHMM
Must Use
Ref. Des. DTM01
Attributes M ID 3/3
Must Use Must Use
DTM02 DTM03
M M
DT 8/8 TM 4/4
16 - 12
April 2008
QTY Quantity
Position: Loop: Level: Usage: Max Use: 320 QTY Mandatory Detail Mandatory 1
Must Use
Ref. Des. QTY01
Data Element Summary Data Element Name 673 Quantity Qualifier Honda's intended use of these codes is as follows: LIN07 Value Code Honda Definition "CC" 17 Quantity on Hand "IA" 03 Disposition Debit "IA" 05 Disposition Credit "IA" 06 Disposition No Action "IA" 77 "RA" 04 Shipping Damage "RA" 21 Disposition Pending "RA" 23 Disposition Pending
Attributes M ID 2/2
Discrete Quantity - Rejected Material: Discrete Quantity - Rejected Material: Discrete Quantity - Rejected Material: Stock Transfer In Discrete Quantity - Rejected Material: Cumulative Quantity Shipped Short Cumulative Quantity Shipped Long -
Must Use
QTY02
380
Valid codes are listed below: 03 Discreet Quantity - Rejected Material 04 Discrete Quantity - Rejected Material: Disposition Replacement 05 Discrete Quantity - Rejected Material: Disposition Credit 06 Discrete Quantity - Rejected Material: Disposition Pending 17 Quantity on Hand 21 Cumulative Quantity Shipped Short - Disposition Pending 23 Cumulative Quantity Shipped Long - Disposition Pending 77 Stock Transfers In Quantity M R 1/15
April 2008
16 - 13
UIT Unit Detail

Must Use Must Use
Data Element Summary Data Element Name C001 Composite Unit of Measure 355 Unit or Basis for Measurement Code Refer to ANSI guidelines for a list of valid codes
LS Loop Header
Position: Loop: Level: Usage: Max Use: Notes: 380 QTY Mandatory Detail Optional 1 - This segment, the corresponding LE segment and the corresponding REF loop (including the three segments therein) are only used for a Cycle Count (CC) response for DSPS parts. Note: DSPS (Domestic Supply Parts Supplier) parts: Parts Honda orders from a tier 2 or higher supplier to be delivered to another Honda supplier. - This segment, the corresponding LE segment and the corresponding REF loop (including the three segments therein) should not be present for a Inventory Adjustment (IA) or Receipt Adjustment (RA).
Must Use
Ref. Des. LS01
Data Element Summary Data Element Name Attributes 447 Loop Identifier Code M AN 1/4 When this segment is used, the value of this field should be the corresponding loop ID: "REF". LS01 and LE01 should be identical.
16 - 14
April 2008
REF Parent Part Number Identification

Position: Loop: Level: Usage: Max Use: Notes: 390 REF Optional Detail Optional 1 The purpose of this REF loop is to identify the last shipment date and time for each of the parent parts of the part which was counted. The Parent Part Number(s) and the Parent Ordering Plant Code(s) are provided in the Honda outbound 846 REF loop, position REF02 & N104 respectively. Data Element Summary Data Element Name 128 Parent Part Number Qualifier Valid codes are listed below 89 Assembly Number 127 Parent Part Number
Must Use
Ref. Des. REF01
Attributes M ID 2/3
Must Use
REF02
AN 1/29
DTM Last Shipment Sent Date

Position: Loop: Level: Usage: Max Use: 400 REF Optional Detail Optional 1
Must Use
Ref. Des. DTM01
Must Use Must Use
DTM02 DTM03
Data Element Summary Data Element Name 374 Last Shipment Sent Date/Time Qualifier Valid codes are listed below 011 Shipped 373 Last Shipment Sent Date Date expressed as CCYYMMDD 337 Last Shipment Sent Time Time expressed in 24-hour clock time as HHMM
Attributes M ID 3/3
M M
DT 8/8 TM 4/4
April 2008
16 - 15
N1 Parent Name
Position: Loop: Level: Usage: Max Use: 410 REF Optional Detail Optional 1
Must Use
Ref. Des. N101
Must Use
N103
Must Use
N104
Data Element Summary Data Element Name 98 Parent Ordering Plant ID Valid codes are listed below 16 Plant 66 Parent Ordering Plant Qualifier Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Parent Ordering Plant Code This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = GPCS) 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM =
Attributes M ID 2/2
ID 1/2
AN 3/3
HAM - Marysville Auto Plant (MAP-used for GPCS) HAM - East Liberty Auto Plant (ELP-used for GPCS) HAM - Marysville Motorcycle Plant (MMP-used for GPCS) HAM - International Parts Supply (IPS-used for GPCS) HAM - Service Parts Procurement (IPS-used for GPCS) HAM - International Parts Supply for Honda de Mexico (IPS-for HAM - Anna Engine Plant (AEP-used for GPCS) American Honda Motor Co., Inc. Honda of Canada Mfg. Honda de Mexico Honda Manufacturing of Alabama Honda Manufacturing of Indiana Honda Power Equipment Honda Precision Parts Georgia Honda of South Carolina Honda Transmission
16 - 16
April 2008
LE Loop Trailer
Position: Loop: Level: Usage: Max Use: 440 QTY Mandatory Detail Optional 1
Must Use
Ref. Des. LE01
Data Element Summary Data Element Name Attributes 447 Loop Identifier Code M AN 1/4 When this segment is used, the value of this field should be the corresponding loop ID: "REF". LS01 and LE01 should be identical.

Must Use
Ref. Des. CTT01
Data Element Summary Data Element Name 354 Number of Line Items The accumulation of number of LIN segments.
Attributes M N0 1/6
April 2008
16 - 17

Must Use Must Use
Ref. Des. SE01 SE02
16 - 18
April 2008
Chapter 17 Inventory Advice Outbound from Honda

Inventory Advice Outbound from Honda (846)
April 2008
17 - 1
Chapter 17 Inventory Advice Outbound from Honda (846)
Chapter Contents
This chapter contains information and procedures for using the Honda Outbound Inventory Advice transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 3 Transaction Covered........................................................................................................................... 3 Application Standards and Conventions............................................................................................. 3 Mapping .............................................................................................................................................. 3 Exceptions/ Clarifications.................................................................................................................... 3 Schedule ............................................................................................................................................. 3 Specifications ...................................................................................................................................... 3 Back-Up Procedure............................................................................................................................. 3 Business Purpose ................................................................................................................................ 4 Transaction Specification Information ............................................................................................... 5 846 Inventory Advice (Honda Outbound)........................................................................................... 6 Functional Group ID=IB................................................................................................................... 6 ST Transaction Set Header............................................................................................................. 7 BIA Beginning Segment for Inventory Advice ................................................................................. 7 PER Text Message Identifier........................................................................................................... 8 N1 Honda Plant Location ................................................................................................................ 9 N2 Honda Corporate Name........................................................................................................... 10 N1 Supplier Name ......................................................................................................................... 10 N3 Supplier Address ..................................................................................................................... 11 N4 Supplier Geographic Location ................................................................................................. 11 PER Supplier Contact ................................................................................................................... 12 LIN Item Identification.................................................................................................................... 12 DTM Cycle Count Request Date ................................................................................................... 13 DTM Response Due Date ............................................................................................................. 13 QTY Quantity................................................................................................................................. 14 LS Loop Header ............................................................................................................................ 14 REF Parent Part Number Identification......................................................................................... 15 N1 Parent Name............................................................................................................................ 16 LE Loop Trailer.............................................................................................................................. 17 CTT Transaction Totals................................................................................................................. 17 SE Transaction Set Trailer ............................................................................................................ 18
17 - 2
April 2008
Transaction Covered
Inventory Advice/Inquiry (Transaction Set 846), abbreviated IB.

Mapping
A list of the Inventory Advice/Inquiry business data elements and how they are transmitted via EDI Standards is provided in the Transaction Specifications.
Schedule
The Honda Outbound Inventory Advice is transmitted as needed by Honda.
Specifications
It is possible for Honda to transmit multiple Inventory Advices/Inquiries within one envelope. This means that there may be multiple transaction sets (ST-SE header/trailer segments) within one interchange envelope (ISA-IEA header/trailer segments). Honda transmits all EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up Procedure
In the event of failure of Electronic Data Interchange it is the responsibility of the sending party to transmit the contents of any pending Transmission to the receiving party using a method of non-EDI transmission which is timely, reasonable, and appropriate under the circumstances.
April 2008
17 - 3
Business Purpose
The Honda Outbound Inventory Advice (ANSI 846) transaction set allows Honda to request inventory information (e.g. on hand quantities) from suppliers. The supplier will receive a cycle count request per supplier, location, and specified part number. Suppliers must respond to a cycle count request within the time specified. FREQUENCY: As required TRANSMITTED FROM: Honda TRANSMITTED TO: Domestic OEM Suppliers DSPS Suppliers Service Parts Suppliers
17 - 4
April 2008


The second column:
April 2008
17 - 5
846 Inventory Advice (Honda Outbound)

Functional Group ID=IB
Heading:
Must Use Must Use Must Use Pos. No. 010 020 070 Seg. ID ST BIA PER Name Transaction Set Header Beginning Segment for Inventory Advice Text Message Identifier LOOP ID - N1 Must Use Must Use 077 090 N1 N2 Honda Plant Location Honda Corporate Name LOOP ID - N1 Must Use Must Use Must Use Must Use 136 137 138 139 N1 N3 N4 PER Supplier Name Supplier Address Supplier Geographic Location Supplier Contact M M M M 1 1 1 1 M M 1 1 1 Req. Des. M M M Max.Use 1 1 1 1 Loop Repeat
Detail:
Pos. No. Must Use Must Use Must Use 010 100 105 Seg. ID LIN DTM DTM Name LOOP ID - LIN Item Identification Cycle Count Request Date Response Due Date LOOP ID - QTY Must Use Must Use 320 380 QTY LS Quantity Loop Header LOOP ID - REF Must Use Must Use Must Use 390 410 440 REF N1 LE Parent Part Number Identification Parent Name Loop Trailer M M M 1 1 1 M M 1 1 >1 Req. Des. M M M Max.Use 1 1 1 1 Loop Repeat 10000
Summary:
17 - 6
April 2008

Must Use
Ref. Des. ST01
Must Use
ST02
Data Element Summary Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes are listed below 846 Inventory Inquiry/Advice 329 Transaction Set Control Number M AN 4/9 This number will be unique (within a transaction set) and ascending. It may be sequential.
BIA Beginning Segment for Inventory Advice

Must Use
Ref. Des. BIA01
Must Use
BIA02
Must Use
BIA03
BIA04 BIA05 BIA06
Data Element Summary Data Element Name Attributes 353 Transaction Set Purpose Code M ID 2/2 Valid Codes Listed Below 05 Replace 755 Report Type Code M ID 2/2 Valid Code Listed Below MB Manufacturer/Distributor Inventory Report 127 Inventory Advice Number M AN 6/6 A unique cycle count order number. This number will be returned in LIN19 on the inbound 846 Cycle Count response. 373 Create Date M DT 8/8 Date expressed as CCYYMMDD 337 Create Time M TM 4/4 Time expressed in 24-hour clock time as HHMM 306 Action Code M ID 1/2 Valid codes listed below 7 Request
April 2008
17 - 7

Must Use
Ref. Des. PER01
PER02
Must Use
PER03
Must Use
PER04
Data Element Summary Data Element Name Attributes 366 Text Message Code M ID 2/2 Valid codes are listed below ZZ Mutually Defined 93 Check for 864 O AN 1/30 "Comments in EDI 864" When this message appears, it indicates that an applicable 864 Text message has also been transmitted. 365 Honda Document ID Number Qualifier M ID 2/2 Valid codes are listed below EM Electronic Mail 364 Honda Document ID Number M AN 1/14 This number is assigned by Honda and may be used to link to an 864 Text message relating to this Inventory Advice.
17 - 8
April 2008
N1 Honda Plant Location

Ref. Des. N101 N102 N103 N104
Data Element Summary Data Element Name 98 Entity Identifier Code 16 Plant 93 Plant Name 66 Identification Code Qualifier 6 Plant Code 67 Honda Plant ID This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM =
Attributes M ID 2/2 M M M AN 1/35 ID 1/2 AN 3/3
April 2008
17 - 9

Position: Loop: Level: Usage: Max Use: 090 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name Attributes 93 Corporate Name M AN 1/35 The corporate name for the Honda facility issuing this document. For example: (May not be an all-inclusive list.) "Honda of America Mfg., Inc." "Honda Manufacturing of Alabama, LLC" "Honda of Canada Mfg." Honda de Mexico, S.A. de C.V. "American Honda Motor Co., Inc." Honda Manufacturing of Indiana "Honda Power Equipment" "Honda of South Carolina" Honda Power Train Georgia "Honda Transmission"
Must Use
Ref. Des. N201
N1 Supplier Name
Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid Code Listed Below SU Supplier/Manufacturer 93 Supplier Name M AN 1/35 66 Supplier Number Qualifier M ID 1/2 Valid Code Listed Below 92 Assigned by Buyer or Buyer's Agent 67 Supplier Number and Loc Code M AN 8/8 An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code. (For some Honda facilities the location code may be "00".)
17 - 10
April 2008
N3 Supplier Address
Must Use
Ref. Des. N301 N302
Data Element Summary Data Element Name 166 Address Information - 1 Supplier street address 1 166 Address Information - 2 Supplier street address 2

Ref. Des. N401 N402 N403 N404
Data Element Summary Data Element Name 19 City Name Suppliers city name 156 State or Province Code Suppliers state or province name 116 Postal Code Suppliers zip or postal code 26 Country Code
Attributes M AN 2/30 M M M ID 2/2 ID 3/10 ID 2/3
April 2008
17 - 11

Must Use
Ref. Des. PER01
Must Use
PER02
Attributes M ID 2/2
AN 1/30

Must Use
Ref. Des. LIN01
Must Use
LIN02
Must Use Must Use
LIN03 LIN04
Must Use
LIN05
Data Element Summary Data Element Name Attributes 350 Sequence Number M AN 1/2 Alphanumeric characters assigned for differentiation within a transaction set. This number will be returned in the corresponding Honda inbound 846 LIN01. 235 Mfg Base Part Qualifier M ID 2/2 Valid codes are listed below BP Buyer's Part Number 234 Mfg Base Part Number and Color M AN 1/29 235 Part Description Qualifier M ID 2/2 Valid codes are listed below PD Part Number Description 234 Part Description M AN 1/30
17 - 12
April 2008
DTM Cycle Count Request Date

Position: Loop: Level: Usage: Max Use: Notes: 100 LIN Mandatory Detail Mandatory 1 This segment provides the date that Honda requests the cycle count. Data Element Summary Data Element Name Attributes 374 Date Qualifier M ID 3/3 167 Most Recent Revision (or Initial Version) 373 Cycle Count Request Date M DT 8/8 Date expressed as CCYYMMDD.
Must Use Must Use
Ref. Des. DTM01 DTM02
DTM Response Due Date

Position: Loop: Level: Usage: Max Use: Notes: 105 LIN Mandatory Detail Mandatory 1 This segment provides the date that Honda requests the cycle count to be completed by. Data Element Summary Data Element Name 374 Date Qualifier 248 Finish no later than 373 Date Count Due Date expressed as CCYYMMDD.
Must Use Must Use
Ref. Des. DTM01 DTM02
Attributes M ID 3/3 M DT 8/8
April 2008
17 - 13
QTY Quantity
Must Use
Ref. Des. QTY01
QTY02 QTY03 C00101
Data Element Summary Data Element Name 673 Quantity Qualifier Valid codes are listed below 01 Discrete Quantity 380 Quantity This field will always be set to "1" C001 Composite Unit of Measure 355 Unit or Basis for Measurement Code Valid codes are listed below EA Each
Attributes M ID 2/2
M M M
R 1/15
ID 2/2
LS Loop Header
Position: Loop: Level: Usage: Max Use: Notes: 380 QTY Mandatory Detail Mandatory 1 This segment, the corresponding LE segment and the corresponding REF loop (including the two segments therein) are only used for a Cycle Count (CC) request for DSPS parts. Note: DSPS (Domestic Supply Parts Supplier) parts: Parts Honda orders from a tier 2 or higher supplier to be delivered to another Honda supplier. Data Element Summary Data Element Name Attributes 447 Loop Identifier Code M AN 1/4 The value of this field will be the corresponding loop ID: "REF". LS01 and LE01 will be identical.
Must Use
Ref. Des. LS01
17 - 14
April 2008
REF Parent Part Number Identification

Position: Loop: Level: Usage: Max Use: Notes: 390 REF Mandatory Detail Mandatory 1 The purpose of this REF loop is to provide the Parent Part Number(s) and the Parent Ordering Plant Code(s) for DSPS parts. The Honda supplier will return this information in the 846 inbound with the date and time of the last shipment to Honda. Data Element Summary Data Element Name 128 Parent Part Number Qualifier Valid codes are listed below 89 Assembly Number 127 Parent Part Number
Must Use
Ref. Des. REF01
Attributes M ID 2/3
Must Use
REF02
AN 1/29
April 2008
17 - 15
N1 Parent Name
Position: Loop: Level: Usage: Max Use: 410 REF Mandatory Detail Mandatory 1
Must Use
Ref. Des. N101
Must Use
N103
Must Use
N104
Data Element Summary Data Element Name 98 Parent Ordering Plant ID Valid codes are listed below 16 Plant 66 Parent Ordering Plant Qualifier Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Parent Ordering Plant Code This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM =
Attributes M ID 2/2
ID 1/2
AN 3/3
17 - 16
April 2008
LE Loop Trailer
Must Use
Ref. Des. LE01
Data Element Summary Data Element Name Attributes 447 Loop Identifier Code M AN 1/4 The value of this field will be the corresponding loop ID: "REF". LS01 and LE01 will be identical.

Must Use
Ref. Des. CTT01
Data Element Summary Data Element Name 354 Number of Line Items The accumulation of number of LIN segments.
Attributes M N0 1/6
April 2008
17 - 17

Must Use Must Use
Ref. Des. SE01 SE02
17 - 18
April 2008
Chapter 18 Purchase Order (850)

Purchase Order (850)
This document may not be disclosed, duplicated or used for any purpose, in whole or in part, without the prior written consent of Honda of America Mfg., Inc. Honda of America Mfg., Inc. 2007
September 2007
18 - 1
Chapter 18 Purchase Order
Chapter Contents
This chapter contains Honda Purchase Order transaction information and procedures. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 4 Transaction Covered........................................................................................................................... 4 Application Standards and Conventions............................................................................................. 4 Mapping .............................................................................................................................................. 4 Exceptions/Clarifications..................................................................................................................... 4 Schedule ............................................................................................................................................. 4 Specifications ...................................................................................................................................... 4 Back-Up Procedure............................................................................................................................. 4 Business Purpose ................................................................................................................................ 5 Transaction Specification Information ............................................................................................... 6 Transaction Specifications.................................................................................................................. 7 Functional Group ID=PO................................................................................................................. 7 ST Transaction Set Header............................................................................................................. 8 BEG Beginning Segment for Purchase Order................................................................................. 8 PER Text Message Identifier........................................................................................................... 9 DTM Create Date ............................................................................................................................ 9 N1 Honda Ordering Plant Location ............................................................................................... 10 N2 Honda Corporate Name........................................................................................................... 11 PER Honda Contact ...................................................................................................................... 11 N1 Supplier Name ......................................................................................................................... 12 N3 Supplier Address ..................................................................................................................... 12 N4 Supplier Geographic Location ................................................................................................. 13 PER Supplier Contact ................................................................................................................... 13 PO1 Baseline Item Data................................................................................................................ 14 CTP Pricing Information ................................................................................................................ 15 CUR Currency ............................................................................................................................... 15 SCH Line Item Schedule ............................................................................................................... 16 TD1 Container Details ................................................................................................................... 16 N1 Ship To Location...................................................................................................................... 17 N3 Ship To Address ...................................................................................................................... 17 N4 Ship To Geographic Location .................................................................................................. 18
18 - 2
September 2007

TD5 Carrier Details (SCAC) .......................................................................................................... 18 CTT Transaction Totals................................................................................................................. 19 SE Transaction Set Trailer ............................................................................................................ 19 Operating Procedures........................................................................................................................ 20 Replacement Logic ........................................................................................................................... 20 Retransmission ................................................................................................................................. 20 Operating Procedures........................................................................................................................ 21 Overview ........................................................................................................................................... 21
September 2007
18 - 3
Transaction Covered
Purchase Order (Transaction Set 850), abbreviated "PO"

The 850-transaction set is based upon the ANSI ASC X 12 Version Release 004010 documents.
Mapping
A list of the Purchase Order (PO) business data elements and how they will be transmitted via EDI Standards is provided in the Transaction Specifications.
There are no exceptions to ANSI X12 Standards in this Transaction Description.
Schedule
The Purchase Order will be transmitted on an as-needed basis, by the end of the production day.
Specifications
It is possible for Honda to transmit multiple Purchase Orders within one envelope. This means that there may be multiple transaction sets (ST-SE header/trailer segments) within one interchange envelope (ISAIEA header/trailer segments). Honda transmits all EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up Procedure
In the event of a failure of Electronic Data Interchange it is the responsibility of the sending party to transmit the contents of any pending Transmission to the receiving party using a method of non-EDI transmission which is timely, reasonable, and appropriate under the circumstances.
18 - 4
September 2007
Business Purpose
The Honda Purchase Order (ANSI 850) transaction set is used in addition to the Weekly Release (ANSI 830) and Ship Schedule (ANSI 862) to meet Honda's business needs. The PO will be transmitted by Honda on an as needed basis for the following purposes (this may not be an all-inclusive list): In-Process Part Orders -- in-process parts are used to replace rejected or damaged parts. Repair Part Orders -- repair parts are used to repair supplier assemblies that were damaged during installation. Domestic Trouble Report (DTR) Part Orders -- are used to correct inventories due to a supplier mis-shipment if applicable. Test Part Orders -- test parts are needed by several departments for quality control purposes. Exception Part Orders -- are used to adjust Honda's inventory levels. American Honda Service Part Order -- for distribution of service parts to Honda Dealers. This will be the standard order type for AHM. Value Added Service Parts Orders -- parts that require additional processing at Honda prior to shipment to Honda dealers. New Model Part Orders -- are used to support Honda New Model trial/preproduction events. Honda de Mexico Part Orders -- are used to support HDM production. This will be the standard order type for HDM.
The Purchase Order (ANSI 850) authorizes shipping of all parts on that order. Suppliers shall treat the PO (ANSI 850) the same as a Ship Schedule (ANSI 862) document. For instructions on the use of the Purchase Order (ANSI 850) please follow all references in this manual to the Ship Schedule (ANSI 862). All shipments shall be properly labeled and an ASN shall be created and sent for these parts.
FREQUENCY: As applicable TRANSMITTED FROM: Honda TRANSMITTED TO: 1st tier and/or DSPS suppliers Service parts suppliers
September 2007
18 - 5

The following Transaction Specifications consists of two sections: 1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality. Note - The Req. Des. for the first segment in a loop is also used for that corresponding loop. 2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column:

The second column:
18 - 6
September 2007
Functional Group ID=PO
Heading:
Must Use Must Use Pos. No. 010 020 060 Must Use 150 Seg. ID ST BEG PER DTM Name Transaction Set Header Beginning Segment for Purchase Order Text Message Identifier Create Date LOOP ID - N1 Must Use Must Use Must Use 310 320 360 N1 N2 PER Honda Ordering Plant Location Honda Corporate Name Honda Contact LOOP ID - N1 Must Use Must Use Must Use Must Use 425 427 428 429 N1 N3 N4 PER Supplier Name Supplier Address Supplier Geographic Location Supplier Contact M M M M 1 1 1 1 M M M 1 1 1 1 Req. Des. M M O M Max.Use 1 1 1 1 1 Loop Repeat
Detail:
Pos. No. Must Use 010 Seg. ID PO1 Name LOOP ID - PO1 Baseline Item Data LOOP ID - CTP 040 043 CTP CUR Pricing Information Currency LOOP ID - SCH Must Use Must Use 295 296 SCH TD1 Line Item Schedule Container Details LOOP ID - N1 Must Use Must Use Must Use Must Use 350 370 380 430 N1 N3 N4 TD5 Ship To Location Ship To Address Ship To Geographic Location Carrier Details (SCAC) M M M M 1 1 1 1 M M 1 1 1 O O 1 1 200 Req. Des. M Max.Use 1 1 Loop Repeat 100000
Summary:
Pos. No. Must Use Must Use 010 030 Seg. ID CTT SE Name LOOP ID CTT Transaction Totals Transaction Set Trailer Req. Des. M M Max.Use 1 1 Loop Repeat 1
September 2007
18 - 7

Must use
Ref. Des. ST01
Must Use
ST02
Data Element Summary Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes are listed below 850 Purchase Order 329 Transaction Set Control Number M AN 4/9 This number will be unique (within a transaction set) and ascending. It may be sequential.
BEG Beginning Segment for Purchase Order

Must Use
Ref. Des. BEG01
Must Use
BEG02
Must Use
BEG03
Must Use
BEG05
Data Element Summary Data Element Name Attributes 353 Transaction Set Purpose Code M ID 2/2 Valid codes are listed below 05 Replace 92 Purchase Order Type Code M ID 2/2 Valid codes are listed below SA Stand-alone Order 324 Honda Document ID Number M AN 1/14 This number links all parts on this 850 together. It is also used to link to the 864 text transaction. This number is NOT returned on the ASN. Honda does NOT use this number as the Purchase Order number. (See PO1 segment, element 01) 373 Create Date M DT 8/8 Date expressed as CCYYMMDD
18 - 8
September 2007

Position: Loop: Level: Usage: Max Use: Notes: 060 Heading Optional 1 This segment will only be used if there is a corresponding text message for this document. Data Element Summary Data Element Name Attributes 366 Text Message Code M ID 2/2 Valid codes are listed below ZZ Mutually Defined 93 Check for 864 M AN 1/30 "Comments in EDI 864" When this message appears, it indicates that an applicable 864 Text message has also been transmitted.
Must Use
Ref. Des. PER01
Must Use
PER02
DTM Create Date

Must Use
Ref. Des. DTM01
Must Use Must Use
DTM02 DTM03
Data Element Summary Data Element Name Attributes 374 Create Date/Time Qualifier M ID 3/3 Valid codes are listed below 167 Most Recent Revision (or Initial Version) 373 Create Date M DT 8/8 Date expressed as CCYYMMDD 337 Create Time M TM 4/4 Time expressed in 24-hour clock time as HHMM
September 2007
18 - 9

Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
Data Element Summary Data Element Name 98 Entity Identifier Code Valid codes are listed below 16 Plant 93 Plant Name 66 Identification Code Qualifier Valid codes are listed below 98 Purchasing Office 67 Honda Plant ID This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM =
Attributes M ID 2/2
M M
AN 1/35 ID 1/2
AN 3/3
18 - 10
September 2007

Must Use
Ref. Des. N201
Data Element Summary Data Element Name Attributes 93 Corporation Name M AN 1/35 The corporate name for the Honda facility issuing this document. For example: (May not be an all-inclusive list.) "Honda of America Mfg., Inc." "Honda Manufacturing of Alabama, LLC" "Honda of Canada Mfg." "Honda Canada, Inc." Honda de Mexico, S.A. de C.V. "American Honda Motor Co., Inc." "Honda Power Equipment" "Honda of South Carolina" Honda Power Train Georgia ?? "Honda Transmission"
PER Honda Contact

Must Use
Ref. Des. PER01
Must Use
PER02
Data Element Summary Data Element Name 366 Buyer Contact Code Valid codes are listed below BD Buyer Name or Department 93 Buyer Name
Attributes M ID 2/2
AN 1/35
September 2007
18 - 11
N1 Supplier Name
Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid codes are listed below SU Supplier/Manufacturer 93 Supplier Name M AN 1/35 66 Supplier Number Qualifier M ID 1/2 Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Supplier Number and Loc Code M AN 8/8 An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code (which may be 00).
N3 Supplier Address
Must Use
Ref. Des. N301 N302
Data Element Summary Data Element Name 166 Supplier Address Information 1 166 Supplier Address Information 2
18 - 12
September 2007

Data Element Summary Ref. Des. N401 N402 N403 N404 Data Element 19 156 116 26 Name Supplier City Name Supplier State or Province Code Supplier Postal Code Supplier Country Code Attributes M AN 2/30 M ID 2/2 M ID 3/10 M ID 2/3

Must Use
Ref. Des. PER01
Must Use
PER02
Attributes M ID 2/2
AN 1/30
September 2007
18 - 13
PO1 Baseline Item Data

Position: Loop: Level: Usage: Max Use: 010 PO1 Mandatory Detail Mandatory 1
Must Use
Ref. Des. PO101
PO102 PO103 PO106
Must Use
PO107 PO108
PO109
Data Element Summary Data Element Name Attributes 350 Part Level PO Line ID M AN 5/10 This alphanumeric character must be returned in the corresponding 856's LIN13 (Pos. 420). This data acts as a Purchase Order Number for this line of data. Each iteration of the PO1 will result in a new PO101 value. This value will be unique for each logistical company. - This number may repeat after 12 months for AHM and 18 months for manufacturing plants. 330 Quantity Ordered M R 1/15 Total number ordered 355 Unit or Basis for Measurement Code M ID 2/2 Refer to ANSI guidelines for a list of valid codes 235 Mfg. Base Part Number Qualifier M ID 2/2 Valid codes are listed below BP Buyer's Part Number 234 Mfg.Base Part Number and Color M AN 1/29 235 D/C Part Level Qualifier X ID 2/2 Valid codes are listed below: BE Buyer's Engineering Change Level Number - "BE" Qualifier indicates the part must be shipped at this Design change level. EC Engineering Change Level - "EC" Qualifier is for reference only, parts may be shipped at another level. To determine the correct design level to ship, follow the Honda Specification Change "Instruction Sheet" or Instruction Summary from your Honda planner. - KEY POINT: ALWAYS LABEL THE PARTS WITH THE ACTUAL DESIGN LEVEL. 234 DC Part Level X AN 1/6 - For Honda manufacturing facilities this field (and the corresponding qualifier) will be present for a Manufacturing Base Part Number that begins with a number less than 92. - For AHM, this field (and the corresponding qualifier) will not be present.
18 - 14
September 2007
Must Use
PO110
235
Must Use
PO111 PO112
234 235
PO113
234
Part Description Qualifier M Valid codes are listed below PD Part Number Description Part Description M Project Number Qualifier X Valid codes are listed below: L1 Program Level Project Number X This is a reference number for a particular Honda event or project
ID 2/2
AN 1/30 ID 2/2
AN 1/6
CTP Pricing Information

Position: Loop: Level: Usage: Max Use: Notes: 040 CTP Optional Detail Optional 1 The information in this loop will only be provided to AHM and HDM suppliers. Data Element Summary Data Element Name 236 Price Identifier Code CON Contract Price 212 Unit Price
Must Use Must Use
Ref. Des. CTP02 CTP03
Attributes M ID 3/3 M R 1/17
CUR Currency
Position: Loop: Level: Usage: Max Use: Notes: 043 CTP Optional Detail Optional 1 The information in this segment will only be provided to AHM and HDM suppliers. Data Element Summary Data Element Name 98 Entity Identifier Code BY Buying Party (Purchaser) 100 Currency Code AHM will always use "USD"
Must Use Must Use
Ref. Des. CUR01 CUR02
Attributes M ID 2/3 M ID 3/3
September 2007
18 - 15
SCH Line Item Schedule

Position: Loop: Level: Usage: Max Use: 295 SCH Mandatory Detail Mandatory 1
Ref. Des. SCH01 SCH02 SCH05
Must Use Must Use
SCH06 SCH07
Data Element Summary Data Element Name 380 Part Quantity 355 Unit or Basis for Measurement Code Refer to ANSI guidelines for a list of valid codes 374 Date/Time Qualifier Valid codes are listed below 002 Delivery Requested 010 Requested Ship 373 Planned Ship/Delivery Date Date expressed as CCYYMMDD 337 Planned Ship/Delivery Time Time expressed in 24-hour clock time as HHMM
Attributes M R 1/15 M ID 2/2 M ID 3/3
M M
DT 8/8 TM 4/4

Position: Loop: Level: Usage: Max Use: 296 SCH Mandatory Detail Mandatory 1
Must Use Must Use
Ref. Des. TD102 TD105
Data Element Summary Data Element Name 80 Quantity Per Container 79 Container Type - Container type as designated by Honda - "XX" will be used for non-returnable containers
18 - 16
September 2007
N1 Ship To Location
Position: Loop: Level: Usage: Max Use: 350 N1 Mandatory Detail Mandatory 1
Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid codes are listed below ST Ship To 93 Ship To Name M AN 1/35 66 Ship To Code Qualifier M ID 1/2 Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Ship To Code M AN 2/8 This is the code assigned by Honda for this ship to location - For OEM and AHM orders, this will be a ship to code - For DSPS orders, this will be the supplier number and location code
N3 Ship To Address
Must Use
Ref. Des. N301 N302
Data Element Summary Data Element Name 166 Ship To Address Information 1 166 Ship To Address Information 2
September 2007
18 - 17

Data Element Summary Ref. Des. N401 N402 N403 N404 Data Element 19 156 116 26 Name Ship To City Name Ship To State or Province Code Ship To Postal Code Ship To Country Code Attributes M AN 2/30 M ID 2/2 M ID 3/10 M ID 2/3

Must Use
Ref. Des. TD502
Must Use
TD503
Data Element Summary Data Element Name Attributes 66 SCAC Code Qualifier M ID 1/2 Valid codes are listed below 2 Standard Carrier Alpha Code (SCAC) 67 SCAC Code M AN 4/4 - The Standard Carrier Alpha Code (SCAC) of the planned carrier - AHM & HDM will always transmit "XXXX" for this value - Honda manufacturing suppliers must return the SCAC code of the trucking company picking up the freight on the 856 (Advance Ship Notice), unless otherwise specified by your Purchasing contact. This will usually match the SCAC found in the ordering document.
18 - 18
September 2007

Position: Loop: Level: Usage: Max Use: 010 CTT Mandatory Summary Mandatory 1
Must Use Must Use
Data Element Summary Data Element Name Attributes 354 Number of Line Items M N0 1/6 The accumulation of the number of PO1 segments. 347 Hash Total M R 1/10 The sum of the value of quantities ordered (PO102) for each PO1 segment.

Must Use Must Use
Ref. Des. SE01 SE02
September 2007
18 - 19
Replacement Logic
Honda sends the 850 as a replacement document. The 850 purpose code transmitted in the BEG01 element is always 05, replace. A document may be replaced for various reasons such as replacing an error in a previous document. Supplier systems should have the capability to compare successive incoming Purchase Orders and replace items that are identical for change points listed below. Replacement of items from the new 850 should be based upon a match of: Honda Plant ID, N104 (Position 310) Part Level PO Line ID, PO101 Based upon a match, all segments subordinate to the PO1 segment are to be replaced. An 850 replacement may (1) include all PO line Ids from the original 850, or (2) be a sub-set of PO line Ids.
Retransmission
Honda can transmit the 850 document. Retransmission will only occur when the supplier requests that Honda resends the EDI document. This is typically because the supplier had some problem in the translation process. A retransmitted document can be overlaid based upon the same logic as the replacement logic above.
18 - 20
September 2007
Overview
1. When an additional quantity is required, it may be transmitted as:
An adjustment to a quantity for an existing PO1 number, or Added as a new PO1 number on an existing 850, or A new PO1 number on a new 850
2.
When a replacement 850 is sent, the quantity transmitted will always be the total order quantity for a given date/time. It is the responsibility of the supplier to track quantity changes and make any necessary adjustments for partial or in-transit shipments. Example:
May 1 - Honda orders 100 pieces of Part A for delivery on July 1. June 1 - Supplier ships 50 pieces of Part A to Honda and supplier manages a backorder in their system for 50 pieces. June 15 - Honda reissues the PO and increases the Part A quantity to 150 pieces due on July 1. Expected Result - Supplier must compare the total requirement of 150 pieces against the 50 units that were previously shipped. The proper adjustment in this case is for the supplier to ship the outstanding balance of 100 pieces by July 1.
3. When a replacement 850 is sent:
It may change any or all detail associated with the P0101. It may add a new P0101 requirement.
4. Multiple P0101s may have identical requirements. 5. AHM only - AHM will not accept over-shipments against 850 Purchase Orders. 6. AHM only - AHM may transmit an 850 with a past due date. This will be done on an exception basis only and must be reviewed with AHM.
September 2007
18 - 21
Chapter 19 Advance Shipping Notice (856)

Advance Shipping Notice (856)
September 2007
19 - 1
Chapter Contents
This chapter contains detailed information concerning Hondas Advance Ship Notice (ASN) transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description................................................................................................................... 4 Transaction Covered........................................................................................................................... 4 Application Standards and Conventions............................................................................................. 4 Mapping .............................................................................................................................................. 4 Exceptions/Clarifications..................................................................................................................... 4 Schedule ............................................................................................................................................. 4 Specifications ...................................................................................................................................... 4 Back-Up Procedure............................................................................................................................. 4 Business Purpose............................................................................................................................. 5 Transaction Specification Information ........................................................................................... 6 Transaction Specifications .............................................................................................................. 7 Functional Group ID=SH..................................................................................................................... 7 ST Transaction Set Header ................................................................................................................ 8 BSN Beginning Segment for Ship Notice ........................................................................................... 8 DTM Shipment Date............................................................................................................................ 9 HL Shipment Hierarchical Level.......................................................................................................... 9 TD1 Carrier Details (Quantity and Weight) ....................................................................................... 10 TD5 Carrier Details (SCAC).............................................................................................................. 10 TD3 Carrier Details (Equipment)....................................................................................................... 11 TD4 Carrier Details (Hazardous Materials)....................................................................................... 11 REF BOL Number ............................................................................................................................. 12 N1 Honda Ordering Plant Location ................................................................................................... 13 N1 Ship To Location ......................................................................................................................... 14 N1 Ship From Supplier Location ....................................................................................................... 14 HL Tare/Pallet Hierarchical Level ..................................................................................................... 15 LIN Tare/Pallet Identification............................................................................................................. 15 REF Master/Mixed Label S/N ........................................................................................................... 16 HL Item Hierarchical Level................................................................................................................ 16 LIN Item Identification ....................................................................................................................... 17 SN1 Item Detail (Shipment) .............................................................................................................. 19 REF Container Label S/N ................................................................................................................. 20 CTT Transaction Totals .................................................................................................................... 20 SE Transaction Set Trailer................................................................................................................ 21 Operating Procedures .................................................................................................................... 22 ASN Creation Flow............................................................................................................................ 22 ASN Data Collection ......................................................................................................................... 23
19 - 2
September 2007

Replacement Logic ........................................................................................................................... 24 Reconciliation Requirements ............................................................................................................ 25 Unscheduled Requirements.............................................................................................................. 26 Part Traceability ................................................................................................................................ 26 Initial Production Parts (IPP) and Sort Tags ..................................................................................... 27 IPP Tag description........................................................................................................................... 27 Sorted Parts Tag description ............................................................................................................ 27 IPP/Sort Tag Instructions .................................................................................................................. 27 General IPP/Sort Tag Notes ............................................................................................................. 28 IPP Tag Reason Codes .................................................................................................................... 28 Honda Returnable Label Serial Number........................................................................................... 28 Data Integrity..................................................................................................................................... 29 Honda Lot Number............................................................................................................................ 29 Small Lot/Delivery Batch Number ..................................................................................................... 29 Lot Sequence Number ...................................................................................................................... 30 Country of Origin Code ..................................................................................................................... 30 ASN Transmission Timing ................................................................................................................ 31 Responses to an Advanced Ship Notice (ASN/8560....32 Sample ASN Responding to an 862 .............................................................................................. 33 Sample ASN Responding to an 850 .............................................................................................. 34 ASN/BOL relationship.35
September 2007
19 - 3
Transaction Covered
Advance Ship Notice/Manifest (Transaction Set 856), abbreviated SH.

Mapping
A list of the Advance Ship Notice business data elements and how they are transmitted via EDI Standards is provided in the Transaction Specifications section.
Schedule
The ASN must be sent immediately following the departure of the shipment. Honda will send Functional Acknowledgements for ASNs.
Specifications
Honda expects all EDI data to be in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up Procedure
In the event of a failure of Electronic Data Interchange, it is the responsibility of the sending party to transmit the contents of any pending transmission to the receiving party using a method of non-EDI transmission which is timely, reasonable, and appropriate under the circumstances. If an ASN cannot be sent, you must notify your Honda planner.
19 - 4
September 2007
Business Purpose
The Honda Advance Ship Notice (ANSI 856) transaction set provides detailed information about the contents of a specific shipment. It is usually created with the assistance of automatic identification devices. The Advance Ship Notice (ASN) plays an important role in the receiving and payment process. Inbound to Honda
FREQUENCY: Immediately following the departure of each shipment. TRANSMITTED FROM: Service Parts Suppliers, OEM Suppliers, DSPS Suppliers TRANSMITTED TO: Honda
Note - Valid ASNs may be forwarded on to DSPS Suppliers by Honda.
Outbound from Honda Outbound copies are only sent under the following conditions: 1. 2. DSPS recipient has requested a copy of DSPS senders ASNs Supplier has requested a copy of ASNs to support Honda business requirements.
FREQUENCY: Upon recognition of a valid ASN TRANSMITTED FROM: Honda TRANSMITTED TO: DSPS recipients Service Parts Suppliers OEM Suppliers
September 2007
19 - 5

The following Transaction Specifications consist of two sections: 1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality. Note - The Req. Des. for the first segment in a loop is also used for that corresponding loop. 2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column: M = Mandatory X = Conditional O = Optional The second column: ID = Identifier (a unique value from a predefined list from ANSI) DT = Date TM = Time AN = Alphanumeric R = Numeric with a variable decimal place Nx = Numeric with x decimal places The third column: x/y, where
19 - 6
September 2007
Functional Group ID=SH
Heading:
Must Use Must Use Must Use Pos. No. 010 020 040 Seg. ID ST BSN DTM Name Transaction Set Header Beginning Segment for Ship Notice Shipment Date Req. Des. M M M Max.Use 1 1 1 Loop Repeat
Detail:
Pos. No. Must Use Must Use Must Use Must Use 010 110 120 130 140 Must Use 150 Seg. ID HL TD1 TD5 TD3 TD4 REF Name LOOP ID - HL Shipment Hierarchical Level Carrier Details (Quantity and Weight) Carrier Details (SCAC) Carrier Details (Equipment) Carrier Details (Hazardous Materials) BOL Number LOOP ID - N1 Must Use 220 N1 Honda Ordering Plant Location LOOP ID - N1 Must Use 285 N1 Ship To Location LOOP ID - N1 Must Use 287 N1 Ship From Supplier Location LOOP ID - HL Must Use Must Use Must Use 390 395 400 HL LIN REF Tare/Pallet Hierarchical Level Tare/Pallet Identification Master/Mixed Label S/N LOOP ID - HL Must Use Must Use Must Use Must Use 410 420 430 440 HL LIN SN1 REF Item Hierarchical Level Item Identification Item Detail (Shipment) Container Label S/N M M M M 1 1 1 1 M M M 1 1 1 >1 M 1 >1 M 1 1 M 1 1 Req. Des. M M M M O M Max.Use 1 1 1 1 1 1 1 Loop Repeat 1
Summary:
September 2007
19 - 7

Position: Loop: Level: Usage: Max Use: 010 Heading Mandatory 1 Data Element Summary Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 856 Ship Notice/Manifest 329 Transaction Set Control Number M AN 4/9 This number must be unique for this transaction set. It may not be repeated within an 18 month period. A duplicate number will cause the transaction to be rejected.
Must Use Must Use
Ref. Des. ST01 ST02
BSN Beginning Segment for Ship Notice

Must Use
Ref. Des. BSN01
Must Use
BSN02
Must Use Must Use
BSN03 BSN04
Data Element Summary Data Element Name Attributes 353 Transaction Set Purpose Code M ID 2/2 Valid codes listed below 00 Original 01 Cancellation 05 Replace 396 ASN Number M AN 8/8 - The Honda supplier creates this number. For an original ASN (BSN01=00), the ASN Number cannot be repeated within 18 months. - This number must consist of characters from the ranges 0 thru 9, A thru Z, or a thru z. -For shipments crossing borders (US / Canada / Mexico) the relationship between the ASN# and the BOL# must be one to one. (See ASN and BOL Relationship at the end of the chapter for further clarification.) 373 Create Date M DT 8/8 This is the date the ASN was created. Date expressed as CCYYMMDD. 337 Create Time M TM 4/4 This is the time the ASN was created. Time expressed in 24-hour clock time as HHMM.
19 - 8
September 2007
DTM Shipment Date

Must Use
Ref. Des. DTM01
Must Use Must Use
DTM02 DTM03
Data Element Summary Data Element Name Attributes 374 Date/Time Qualifier M ID 3/3 Valid codes are listed below 011 Shipped 373 Ship Date M DT 8/8 This is the actual ship date. Date expressed as CCYYMMDD. 337 Ship Time M TM 4/4 This is the actual ship time. Time expressed in 24-hour clock time as HHMM.
HL Shipment Hierarchical Level

Position: Loop: Level: Usage: Max Use: 010 HL Mandatory Detail Mandatory 1
Must Use Must Use
Ref. Des. HL01 HL03
Data Element Summary Data Element Name 628 Hierarchical ID Number - Shipment Level "1" Shipment Level 735 Hierarchical Level Code - Shipment level Valid codes listed below S Shipment
Attributes M AN 1/12 M ID 1/2
September 2007
19 - 9
TD1 Carrier Details (Quantity and Weight)

Position: Loop: Level: Usage: Max Use: Ref. Des. TD106 TD107 110 HL Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 187 Weight Qualifier M ID 1/2 N Actual Net Weight 81 Weight M R 1/10 This represents the total net weight for this ASN and should be rounded to the nearest whole unit. This value should include the product weight only. Any weight associated with packaging should not be included in this value. 355 Unit or Basis for Measurement Code M ID 2/2 Valid codes are listed below: 01 50 Actual Pounds Actual Kilograms
Must Use Must Use
Must Use
TD108

Position: Loop: Level: Usage: Max Use: Ref. Des. TD502 120 HL Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 66 SCAC Code Qualifier M ID 1/2 Valid Code listed Below 2 Standard Carrier Alpha Code (SCAC) 67 Identification Code - SCAC Code M AN 4/4 - Standard Carrier Alpha Code (SCAC) of carrier. - For Honda Manufacturing facilities suppliers must return the SCAC code of the trucking company picking up the freight, unless otherwise specified by your Purchasing contact. This will usually match the SCAC code found in the ordering document (850 or 862). - For Honda Manufacturing facilities, "XXXX" may be used if the SCAC code is unknown. - For AHM, suppliers must return (1) the SCAC code of the carrier or (2) "XXXX" on the 856 (Advanced Ship Notice). 387 Shipment Tracking Number X AN1/35 - Return the Shipment Tracker Number when directed by Honda.
Must Use
Must Use
TD503
TD505
19 - 10
September 2007
TD3 Carrier Details (Equipment)

Must Use
Ref. Des. TD301
Must Use
TD303
Data Element Summary Data Element Name Attributes 40 Equipment Description Code M ID 2/2 Valid codes listed below TL Trailer (not otherwise specified) 207 Trailer Number M AN 1/10 - The number on the side of the trailer. This number must consist of characters from the ranges 0 thru 9, A thru Z, or a thru z. - This data element is mandatory; therefore it must be completed for air shipments also. - This number must match the trailer number on the Master Packing List. - If the trailer number used is greater than 10 characters, enter only the last 10 characters. (i.e. UPS/FED EX tracking numbers) - In the case of an expedite where XXXX has been used as the SCAC then the trailer # or PRO # must be provided in the Trailer No. field. If sufficient space permits, the name of the expediting carrier should be included after the trailer/Pro#. (Data on the MPL should be the same as what is on the ASN.)
TD4 Carrier Details (Hazardous Materials)

Position: Loop: Level: Usage: Max Use: Notes: 140 HL Mandatory Detail Optional 1 Optional segment to be used by all suppliers shipping hazardous material. Data Element Summary Data Element Name Attributes 152 Special Handling Code X ID 2/3 - To be completed for any shipments that contain hazardous materials - This segment must be sent if any part(s) on the ASN contains hazardous materials - All other ASN's should not contain this element/segment - Contact the appropriate Honda Parts Regulatory department if you have questions on your hazardous materials shipments. Valid code listed below: HM Endorsed as Hazardous Material
Ref. Des. TD401
September 2007
19 - 11
REF BOL Number

Position: Loop: Level: Usage: Max Use: Notes: 150 HL Mandatory Detail Mandatory 1 For shipments crossing borders (US / Canada / Mexico) the relationship between the ASN# and the BOL# must be one to one. (See ASN and BOL Relationship at the end of the chapter for further clarification.)
Must Use
Ref. Des. REF01
Must Use
REF02
Data Element Summary Data Element Name 128 Bill of Lading Qualifier Valid codes are listed below BM Bill of Lading Number 127 Bill of Lading Number
Attributes M ID 2/3
AN 1/12
19 - 12
September 2007

Must Use
Ref. Des. N101
Must Use
N103
Must Use
N104
Data Element Summary Data Element Name 98 Entity Identifier Code Valid codes are listed below 16 Plant 66 Identification Code Qualifier Valid codes are listed below 98 Purchasing Office 67 Honda Plant ID This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM =
Attributes M ID 2/2
ID 1/2
AN 3/3
September 2007
19 - 13
N1 Ship To Location
Position: Loop: Level: Usage: Max Use: 285 N1 Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid codes are listed below ST Ship To 66 Identification Code Qualifier M ID 1/2 Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Ship-To Code M AN 2/8 This is the code assigned by Honda for this ship to location. - For OEM orders, this will be a ship to code - For DSPS orders, this will be the supplier number and location code - Honda ship-to codes may have spaces within the code. - The ship-to code on the ASN must be the same as the corresponding ordering document.
Must Use
Ref. Des. N101
Must Use
N103
Must Use
N104
N1 Ship From Supplier Location

Position: Loop: Level: Usage: Max Use: 287 N1 Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid codes are listed below SU Supplier/Manufacturer 66 Identification Code Qualifier M ID 1/2 Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Ship From Supplier Number M AN 8/8 An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code, (which may be 00).
Must Use
Ref. Des. N101
Must Use
N103
Must Use
N104
19 - 14
September 2007
HL Tare/Pallet Hierarchical Level

Position: Loop: Level: Usage: Max Use: 390 HL Mandatory Detail Mandatory 1 Data Element Summary Ref. Des. HL01 HL02 HL03 Data Element 628 734 735 Name Hierarchical ID Number Hierarchical Parent ID Number Hierarchical Level Code Valid codes are listed below T Shipping Tare Attributes M AN 1/12 M AN 1/12 M ID 1/2
LIN Tare/Pallet Identification

Position: Loop: Level: Usage: Max Use: Notes: 395 HL Mandatory Detail Mandatory 1 Honda defines a pallet as anything that takes up floor space on a truck. Data Element Summary Data Element Name Attributes 235 Tare/Pallet Packaging ID Qualifier M ID 2/2 Valid codes are listed below: PG Packaging Specification Number 234 Tare/Pallet Packaging Type M AN 1/10 - This will be a 1 to 10 digit code corresponding to the Honda returnable type. - If the packaging type is not a Honda returnable, input "XX". - Suppliers are encouraged to use Bingo cards for valid packaging types. 235 Returnable Pallet Serial ID Qualifier X ID 2/2 Valid codes are listed below: RC Returnable Container Number 234 Returnable Pallet Serial Number X AN 1/16 - LIN04 & 05 should not be sent if the packaging type is a non-returnable. - LIN04 & 05 are optional for a returnable packaging type. - This value is the scanned returnable ID tag (also called a fixed asset tag).
Must Use
Ref. Des. LIN02
Must Use
LIN03
LIN04
LIN05
September 2007
19 - 15
REF Master/Mixed Label S/N

Position: Loop: Level: Usage: Max Use: 400 HL Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 128 Master/Mixed Label Qualifier M ID 2/3 Valid codes are listed below LS Bar-Coded Serial Number 127 Master/Mixed Label Serial Number M AN 16/16 - Scanned serial number from the Master or Mixed load label. - This number is created by the Honda supplier. - Format: first eight digits should be the supplier and location code, the second eight digits should be assigned such that the number is unique within an 18 month period.
Must Use
Ref. Des. REF01
Must Use
REF02
HL Item Hierarchical Level

Position: Loop: Level: Usage: Max Use: 410 HL Mandatory Detail Mandatory 1 Data Element Summary Ref. Des. HL01 HL02 HL03 Data Element 628 734 735 Name Hierarchical ID Number Hierarchical Parent ID Number Hierarchical Level Code Valid codes are listed below I Item Attributes M AN 1/12 M AN 1/12 M ID 1/2
19 - 16
September 2007

Position: Loop: Level: Usage: Max Use: 420 HL Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 235 Mfg Base Part Number Qualifier M ID 2/2 Valid codes are listed below BP Buyer's Part Number 234 Mfg Base Part Number and Color M AN 1/29 235 D/C Part Level Qualifier X ID 2/2 Valid codes are listed below: BE Buyer's Engineering Change Level Number - "BE" qualifier indicates the part being shipped is at the design level listed in LIN05. 234 D/C Part Level X AN 1/6 - For Honda manufacturing facilities this field (and the corresponding qualifier) must be present for a Manufacturing Base Part Number that begins with a number less than 92. - This must be the actual D/C Level of the part being shipped, even if the D/C Level is different than what was ordered. - For AHM, this field (and the corresponding qualifier) will not be present. 235 Honda Lot Number Qualifier X ID 2/2 Valid codes are listed below: LT Lot Number Honda Lot Number X AN 1/12 - LIN06/07 must be returned if present on the corresponding ordering document. - The data comes from the corresponding Honda outbound 862 (REF02 Pos. 120). - See Honda Lot Number in the Operating Procedures portion of this chapter for further details. Ship Schedule Qualifier X ID 2/2 Valid codes are listed below: ON Customer Order Number Ship Schedule Number X AN 1/6 - This field and the corresponding qualifier are only used for ship schedules. - LIN08 & LIN09 are mutually exclusive of LIN12 & LIN13. - If used, the data comes from the corresponding Honda outbound 862: LIN09 for DELTA REF02 (pos 137) for GPCS
Must Use
Ref. Des. LIN02
Must Use
LIN03 LIN04
LIN05
LIN06
LIN07
234
LIN08
235
LIN09
234
September 2007
19 - 17
LIN10
235
LIN11 LIN12
234 235
LIN13
234
LIN14
235
LIN15
234
LIN16
235
LIN17 LIN18
234 235
LIN19
234
LIN20
235
LIN21 LIN22
234 235
LIN23
234
Project Number Qualifier X ID 2/2 Valid codes are listed below: L1 Program Level Project Number X AN 1/6 This is a reference number for a particular Honda event or project. Purchase Order Qualifier X ID 2/2 Valid codes are listed below: PO Purchase Order Number Purchase Order Number X AN 5/10 - This field and the corresponding qualifier are only used for purchase orders. - LIN12 & LIN13 are mutually exclusive of LIN08 & LIN09. - If used, the data comes from the corresponding Honda outbound 850 PO101. IPP Tag 1 Qualifier X ID 2/2 If IPP Tag 1 is used, LIN 14, 15, 16 & 17 must all be completed. Valid codes are listed below. A6 Document Identification Code IPP Tag Number 1 X AN 10/10 - See Initial Production Parts (IPP) in the Operating Procedures portion of this chapter for further details. -An HTR number may be used in place of an actual IPP Tag Number for certain reason codes. Please review current quality manual or contact your Honda Quality Representative for guidance. -Format must be 10 characters, use leading zeroes if necessary. IPP Tag 1 Reason Code Qualifier X ID 2/2 Valid codes are listed below PQ Product ID Attribute Code IPP Tag 1 Reason Code X AN 2/2 IPP Tag 2 Number Qualifier X ID 2/2 If IPP Tag 2 is used, LIN 18, 19, 20 & 21 must all be completed. Valid codes are listed below. A6 Document Identification Code IPP Tag Number 2 X AN 10/10 - See Initial Production Parts (IPP) in the Operating Procedures portion of this chapter for further details. -An HTR number may be used in place of an actual IPP Tag Number for certain reason codes. Please review current quality manual or contact your Honda Quality Representative for guidance. -Format must be 10 characters, use leading zeroes if necessary. IPP Tag 2 Reason Code Qualifier X ID 2/2 Valid codes are listed below PQ Product ID Attribute Code IPP Tag 2 Reason Code X AN 2/2 Suppliers Mfg Lot Qualifier M ID 2/2 Valid codes are listed below SL Seller's Lot Number Suppliers Mfg Lot Number M AN 1/20 Honda quality departments use this field for tracking purposes. This number should be a suppliers reference in identifying production of the parts. See Honda Quality Manual for further information.
19 - 18
September 2007

LIN24 235 Returnable Container Serial ID Qualifier X ID 2/2 Valid codes are listed below: RC Returnable Container Number Returnable Container Serial Number X AN 1/16 - LIN24 & 25 should not be sent if the packaging type is a non-returnable. - LIN24 & 25 are optional for a returnable packaging type. - Scanned returnable ID tag (also called a fixed asset tag). Container Packaging ID Qualifier M ID 2/2 Valid codes are listed below PG Packaging Specification Number Container Packaging Type M AN 1/10 - The packaging type should match the corresponding Honda outbound 862 TD105 or 850 TD105. - This will be a 1 to 10 digit code corresponding to the Honda returnable type. - If the packaging type is not a Honda returnable, input "XX". - Suppliers are encouraged to use Bingo cards for valid packaging types. Country of Origin Qualifier M ID 2/2 Valid codes are listed below CH Country of Origin Code Country of Origin M AN 1/10 For valid codes and formatting information see details for "Country of Origin Code" in the Operating Procedures at the end of this chapter.
LIN25
234
Must Use
LIN26
235
Must Use
LIN27
234
Must Use
LIN28
235
Must Use
LIN29
234
SN1 Item Detail (Shipment)

Position: Loop: Level: Usage: Max Use: 430 HL Mandatory Detail Mandatory 1 Data Element Summary Data Element Name 382 Quantity The quantity in the container listed in the previous LIN. 355 Unit or Basis for Measurement Code Refer to ANSI guidelines for a list of valid codes
Must Use Must Use
Ref. Des. SN102 SN103
Attributes M R 1/7 M ID 2/2
September 2007
19 - 19
REF Container Label S/N

Must Use
Ref. Des. REF01
Must Use
REF02
Data Element Summary Data Element Name Attributes 128 Container (Part ID) Label Qualifier M ID 2/3 Valid codes are listed below LS Bar-Coded Serial Number 127 Container (Part ID) Label Serial Number M AN 16/16 - Scanned serial number from parts identification label on each container. - This number is created by the Honda supplier. - Format: first eight digits should be the supplier and location code, the second eight digits should be assigned such that the number is unique within an 18 month period.

Position: Loop: Level: Usage: Max Use: 010 Summary Mandatory 1 Data Element Summary Data Element Name Attributes 354 Number of HL Segments M N0 1/6 The accumulation of the number of HL segments. 347 Hash Total M R 1/10 The sum of the value of units shipped (SN102) for each SN1 segment.
Must Use Must Use
19 - 20
September 2007

Must Use Must Use
Ref. Des. SE01 SE02
September 2007
19 - 21
19 - 22
Picking and Shipping Flow
PICK LIST Planned Load Creation

Created from 850 or 862 The planned load should reconcile to the 850 / 862
xxxxx xxxxxxxxx xxxxx xxxxx
ASN Creation Flow
Create Pick List

Based on the Planned Load
Pick & Scan Shipment

Stage order Link pallets to shipment (ASN) via scanning Input package type
QUICK RECEIVE
MASTER PACKING LIST

xxxxxxxxx xxxxx xxxxx
Send ASN
Send ASN after loading the trailer, as truck departs
Planned Load to ASN Reconciliation

Reconcile part number, quantity, Design Change level, order number
Create Quick Receive Label & MPL & BOL

Apply Quick Receive label(s) Done prior to loading the truck The MPL & BOL should be given to the truck driver Quick Receive and Master/Mixed label serial numbers must match
ASN Confirmation
Verify 997 received Verify 824 acknowledgement code Correct errors & re-send ASN if necessary (prior to arrival of truck at Honda receiving)
September 2007
ASN Data Collection

Data used to create an ASN comes from various sources. Hondas goal is to minimize the amount of hand keying, thus reducing errors. The chart below lists many of the items required in an ASN, where the data is located in the ASN, and how the data should be collected. The method of collecting the data is often system-dependent. Data ASN Number ASN Create Date & Time Ship Date & Time SCAC Code Trailer Number Bill of Lading Number Honda Plant ID Ship-To-Code Supplier Number Tare / Pallet Type Returnable Pallet Serial Number AIAG Master / Mixed S/N Part Number D/C Level Honda Lot Number Ship Schedule Number Project Number Purchase Order Number IPP Tag Number IPP Tag Code Suppliers Mfg. Lot Number Returnable Container Serial No. Container Packaging Type Quantity AIAG Container S/N EDI Location BSN02 BSN03 & 04 DTM02 & 03 (Pos. 040) TD503 TD303 REF02 (Pos. 150) N104 (Pos. 220) N104 (Pos. 285) N104 (Pos. 287) LIN03 (Pos. 395) LIN05 (Pos. 395) REF02 (Pos. 400) LIN03 (Pos. 420) LIN05 (Pos. 420) LIN07 (Pos. 420) LIN09 (Pos. 420) for DELTA REF02 (Pos. 137) for GPCS LIN11 (Pos. 420) LIN13 (Pos.420) LIN15, 19 (Pos. 420) LIN17, 21 (Pos. 420) LIN23 (Pos. 420) LIN25 (Pos. 420) LIN27 (Pos. 420) SN103 REF02 (Pos. 440) Standard Input Method Supplier system generated Supplier system generated Manual entry *Data turnaround or hand key for expedite order Hand key Supplier system generated *Data turnaround *Data turnaround *Data turnaround or system file Scan bingo card, system file, (hand key if issues with the other choices) Scan bingo card, system file, (hand key if issues with the other choices) Scan Supplier system generated via link to Smart Label Supplier system generated via link to Smart Label *Data turnaround * Data turnaround *Data turnaround *Data turnaround Scanning or manual entry Supplier system menu option or manual entry Scan, system, manual entry Scan bingo card, system file, (hand key if issues with the other choices) Scan bingo card, system file, (hand key if issues with the other choices) Supplier system generated via link to Smart Label Scan
See the specifications for Mandatory, Optional, and Conditional attributes. * Data turnaround signifies the data from the ordering document should automatically populate these fields.
September 2007
19 - 23
Replacement Logic
Inbound to Honda Replacement logic for ASNs sent from a supplier to Honda is based on the Transaction Set Purpose Code and the ASN number. To cancel or replace an ASN, the supplier must re-send the ASN in question with the following adjustments. 1. 2. The purpose code should be: 01 Cancellation or 05 Replace, (located in BSN01 in the ASN) Any changes identified (for a replacement) Note - The ASN number in the replacement or cancellation must match the original document. (The ASN number is located in BSN02.) Honda will cancel or replace the ASN based upon the purpose code and a match to an existing supplier number and ASN. Note - The ASN to be canceled or replaced must be received prior to shipment arrival. (It will not be processed if it arrives after trailer arrival.) Note - The Transaction Set Control Number (ST02) must be unique within a calendar year, even for a replacement or cancellation. Outbound from Honda Honda will send an outbound ASN in response to a supplier request. This request would usually result from a delivery service or DSPS relationship where Honda has received an ASN, and the shipping supplier wants the ASN forwarded to a third party. Replacement logic for ASNs sent from Honda to a supplier is based on the Ship From supplier and location code, and the ASN number. Honda will pass on the same purpose code from the original ASN sent to Honda. Cancel or replace the ASN based upon the purpose code and a match to an existing supplier number and ASN.
19 - 24
September 2007
Reconciliation Requirements
Honda requires reconciliation (a systematic comparison) of the ordering document (850 or 862) to the Advanced Ship Notice (ASN 856). The purpose is to ensure that suppliers are shipping what Honda has ordered. By capturing discrepancies prior to truck departure and ASN generation, potential mis-shipments can be corrected, avoiding costly corrective countermeasures. There are two distinct steps to the reconciliation process. 1. Reconciling the ordering document (850 or 862) to the planned load(s). Planned load is a Honda term describing a Honda order within the suppliers system. It is a group or subgroup of parts and quantities from a Honda ordering document which share a common Honda ordering plant ID, ship to code and ship (or deliver) date/time. A planned load may take the form of a pick list. A planned load will relate one to one to the ASN and Master Packing List. The suppliers software must have the capability to create multiple planned loads when a Honda ordering document spans multiple trailers. For orders which span multiple trailers, the multiple planned loads should reconcile to the single ordering document. 2. Reconciling the planned load to the ASN.
For both steps, discrepancies can be identified on-line or hard copy. Following are the items to be reconciled and the action requested:
Item to reconcile Design Change (DC) Level Description The system must alert the user of a DC level mismatch between the ordering document and ASN (for a particular part number). Action to be taken The user must verify that the scanned information is correct. If it is correct, the system must allow the different DC level to be processed. If there is an error, a correction must be made. NOTE: The system should NOT force the user to change the design change level to match the ordering document. Verify and correct the information as required.
Invalid Part Number (Manufacturing Base Part Number MBPN) Invalid Ship-to-Code
The system must alert the user of a part number mismatch between the ordering document and ASN. The system must not allow a ship-to-code mismatch between the ordering document and ASN. The system must alert the user of an over or under shipment of parts on the ASN (versus the ordering document).
Correct the discrepancy. Honda will not accept an ASN with a shipto-code that does not match the ordering document. This will result in a fatal error. The shipper should confirm the quantity scanned versus the quantity required. The system must allow the user to take either of the following steps: 1) over or under ship* or 2) re-scan to ship the required amount. The shipper should confirm the quantity scanned versus the order quantity. The system must allow the user to take either of the following steps: 1) over or under ship* or 2) re-scan to ship the required amount.
Over / Under Shipment
Order Quantity linked to an Order Number
The system must alert the user of an over or under shipment of a particular order when creating an ASN (versus the ordering document).
* Mis-shipments may result in a Delivery Trouble Report (DTR)
September 2007
19 - 25
Unscheduled Requirements
Honda may occasionally place an order by phone, instead of using the normal 850 or 862 transactions. An ASN must be used in response to these orders. Approved software must have this capability. There are various methods to create an ASN in this circumstance, including: 1. Using a future or past ordering document (with the correct ordering plant, ship to code, and part number) to ship the requirements against. This will result in a valid Ship Schedule Number or Purchase Order Number being used. Note - The ordering document must be less than 30 days old. 2. Adding the item to an existing planned order (with the correct ordering plant and ship to code), verifying that the part number/ship schedule number relationship existed within the prior 30 days. Creating a planned order, using a valid Ship Schedule Number or Purchase Order Number. Creating a planned order using a valid Ship Schedule Number or Purchase Order Number given to the supplier from Honda. This is the required method for HCM, HDM, HMA, HPE, HSC and HTM.
3. 4.
Part Traceability
Honda requires that all suppliers provide manufacturing traceability. This means that a supplier must logically link the Honda container label serial number to their internal manufacturing lot/quality tracking mechanism. This linkage must be established using the Supplier Manufacturing Lot Number data element (LIN23) of each LIN segment in the ASN. The Supplier Manufacturing Lot Number must also be present in the Supplier Information block of the Container Label (see Chapter 9). The methods for controlling traceability can take many forms and are dependent on many factors. The Supplier Quality Manual and your Honda Plant Quality Representative are the best sources of guidance on how to control these processes.
19 - 26
September 2007
Initial Production Parts (IPP) and Sort Tags

IPP and Sort Tags are used to notify Honda Quality and Production associates of a part change by a supplier. Depending upon part and supplier, tags may be required many times during a model year. The Supplier IPP and Sorted Parts Procedures can be found in the Honda Supplier Quality Manual.
IPP Tag description: Indicates when a supplier has made a change to a part, see
valid Reason Codes below. When an IPP Tag is used, the supplier will enter two items to describe each change: 1. IPP Reason Code (LIN17/21) 2-digit code indicating what has changed for a part (must be selected from the list of valid codes below). 2. IPP Tag Number (LIN15/19) 10-digit number from the IPP Tag. Note There must be 10 characters in this field, if necessary use leading zeroes.
Sorted Parts description: Indicates when a supplier is sending the first guaranteed lot of parts after a quality concern is detected, whether at Honda or the supplier. When the #11 Sort code is used, the supplier will enter two items:
1. Sort Reason Code (LIN17/21) Must always use Reason Code 11 to indicate a sort. 2. Trouble Report Number (LIN15/19) Must enter the Honda Plant Code Letter where the quality/delivery concern was originally detected. Then enter the Honda Trouble Report Number (HTR#/DTR#). Refer to the Honda Supplier Quality Manual, the Supplier Orientation Manual, or your Honda Quality/Delivery contact for more information. Note There must be 10 characters in this field, if necessary use leading zeroes.
IPP/Sort Tag Instructions

Who applies the IPP/Sort Tag: The supplier that makes the change completes the IPP/Sort tag. The tag must be attached to the first shipment of changed parts. Where does the IPP/Sort Tag come from: See the Change-Point Control Procedure in the Honda Supplier Quality Manual. How is the IPP/Sort Tag information entered: This is accomplished during the ASN creation process. The supplier enters the IPP Tag/Trouble Report Number(s) and Reason Code(s) in relation to the impacted container serial number(s). This entry can be accomplished by scanning or manually entering the information.
September 2007
19 - 27
General IPP/Sort Tag Notes

The Master Packing List (MPL) must identify the part numbers in that shipment that have an IPP/Sort tag. The ASN creation process will automatically do this. See the MPL chapter for details. IPP/Sort tags are not applicable for AHM. Hondas EDI specifications allow a maximum of two IPP/Sort Tag Numbers, with one Reason Code each, per container of parts. If there are multiple reason codes for one IPP tag, enter the most important code and omit the others. If there are more than two IPP/Sort tags attached to one container, enter the information for two of the tags and omit the others. Do not duplicate the same IPP/Sort tag information in both available IPP LIN positions. The IPP/Sort information should only be listed in one LIN that contains the affected part, not for each LIN loop containing that part.
IPP Tag Reason Codes

01 02 03 04 05 06 07 08 09 10 11 Design Change New Supplier Material Change Mfg. Method Change Mfg. Process Order Change Machine Change Jig/Tool Change Die/Mold Change Inspection Method Change Transport/Packing Change Sort

See the Bar Code Labeling Chapter 9 for a description of the Returnable Label Serial Number.
19 - 28
September 2007
Data Integrity
The software must maintain the linkage of the following fields from 862 receipt, through shipment/ASN creation: Part Number Ship Schedule/Order Number Honda Lot/Small Lot/Delivery Batch/Lot Sequence Numbers
Honda Lot Number

The Honda Lot Number (Production Lot Number) is an identifier assigned to a Honda Production Lot. A production lot is a grouping of units (usually 30) used for planning purposes. If the Honda Lot Number is transmitted on an 862 (REF02, Position 120), it must be returned in: ASN (856), LIN07 Master Packing List (MPL) Quick Receive Label (one Lot Number per label, see chapter 9) Note - Honda Lot Numbers may not be in sequential order.
For Honda use only, should not be used for anything other than turnaround data. AHM and HDM will not use Honda Lot Numbers.
Small Lot/Delivery Batch Number

The Small Lot/Delivery Batch Number is an identifier used for packaging purposes. A Small Lot/Delivery Batch may need to be packed in one or multiple containers. Please refer to Hondas packaging guidelines for more detailed information. If the Small Lot/Delivery Batch Number is transmitted on an 862 (REF02, Position 130), it must be returned on: Batch Label (see Chapter 9) Note - Must be presented on Pick & Load Sheet Note AHM and HDM will not use Small Lot/Delivery Batch Numbers.
September 2007
19 - 29
Lot Sequence Number

The Lot Sequence Number is an identifier used for loading/packaging purposes. Trailers/containers should be loaded in sequence using this number. Contact Hondas Packaging group for additional information on sequencing. If the Lot Sequence Number is transmitted on an 862, it does not need to be returned to Honda. It is for packaging purposes only. Note - Must be presented on Pick & Load Sheet Note AHM and HDM will not use Lot Sequence Numbers.
Country of Origin Code

The information below describes the values and formats required for LIN29. For Honda Manufacturing Facilities: LIN29 represents the country of origin as defined by the NAFTA Country of Origin Marking Regulations. Parts made outside the USA should use the 2-digit NAFTA Country of Origin code. Examples are as follows:
CA - Made in Canada JP - Made in Japan MX - Made in Mexico CN Made in China TH Made in Thailand PH Made in Philippines EU Made in European Economic Community GB Made in United Kingdom
Parts made in the USA must use UXX as the format, where:
U = United States XX = 2 digit state postal code

Examples are as follows:
UOH = Made in Ohio, USA UMI = Made in Michigan, USA

The above lists are not all-inclusive. For additional codes contact the Trade Compliance Group at the Honda company which ordered the parts. Note - This is for the ASN only, not the Container Label. The Container label should always use the 2-digit NAFTA Country of Origin code. Parts made in the USA should use US on the Container Label.
19 - 30
September 2007

For AHM: LIN29 represents multiple countries of origin. The following codes must be included:
T - Federal Trade Commission Type Code XX - Federal Trade Commission Country of Origin YY - NAFTA Country of Origin ZZ - Substantial Transformation Country of Origin
The data should be sent in the following format: TXXYYZZ. For a list of valid codes, refer to www.customs.ustreas.gov (search for "ISO Country Code"), contact your companys Trade Compliance Group, or contact AHMs Trade Compliance Group. Note - When the Country Code is the same for each of the categories above, the supplier should use the same value for each category. Note The container label should contain the same values as sent in the ASN with slashes separating the characters. Ex. ASN TXXYYZZ Label T/XX/YY/ZZ
Helpful Information:
Rules of Origin for NAFTA
http://www.customs.ustreas.gov/nafta/docs/us/102-1.html#102.11
Enforcement Policy statement on US origin claims
http://www.ftc.gov/os/1997/12/epsmadeusa.htm http://www.ftc.gov/bcp/conline/pubs/buspubs/madeusa.htm
Substantial Transformation country of origin determination
http://www.customs.ustreas.gov/nafta/docs/us/134.html#134.35
ASN Transmission Timing

The ASN must be sent immediately following the departure of the shipment. Honda compares actual shipment time vs. planned shipment time to assist with material planning.
September 2007
19 - 31
Responses to an Advanced Ship Notice (ASN/856)
Honda Supplier
1) 856 Advanced Ship Notice
2) 997 Functional Acknowledgment
3) 824 Application Advice
4) 861 Receiving Advice
Honda
1) The supplier sends Honda an Advanced Ship Notice (ASN or 856). 2) Honda sends a Functional Acknowledgment (997) in response to ASN's that are recevied into our translator. The 997 is a standard communications "handshake" verification. It confirms successful communication has occurred between the EDI translators of each pair of trading partners. Receiving a 997 does not imply acceptance or suitability of data from Honda's application systems. FREQUENCY: A 997 will be sent immediately upon the inbound documents receipt at Honda. 3) Honda will also send a Application Advice (824) in response to ASN's that are received into our application system. The 824 provides feedback to the Honda supplier regarding the presence or absence of any errors detected by Honda's application system. FREQUENCY: For NAP: The 824 will be transmitted approximately fifteen (15) minutes after receipt of the inbound document. For AHM: The 824 will be transmitted after receipt of the inbound and processing of the inbound document. 4) Honda may send a Receiving Advice (861) in response to the 856. The 861 is used as a discrepancy notification indicating the exception situations between a supplier's ASN data and the actual receiving data as recorded by Honda. The 861 is for discrepancy notice purposes only and does not signify acceptance of any goods. FREQUENCY: Following a discrepancy between an ASN and its' physical receipt verification.
19 - 32
September 2007
Sample ASN Responding to an 862

To be used as reference only to outline basic ASN structure it does not detail all potential ASN variables.
HEADER DETAIL
ISA*00* *00* *ZZ*HONDAMAILBOX*ZZ*SUPPLIERMAILBOX*040511*1334*U*00400*00000002 GS*SH*HONDADUNS*SUPPLIERDUNS*20040511*1334*19*X*004010 ST*856*10046 BSN*00*10000481*20040511*1330 DTM*011*20040511*1430 HL*1**S TD1******N*35*01 TD5**2*CUOT TD3*TL**893 REF*BM*23456 N1*16**98*HMA N1*ST**92*HMA1 01 N1*SU**92*12345601 HL*2*1*T LIN**PG*AP REF*LS*1234560100005096 2*0*T*^
1st Pallet Level
1st Item Level (on 1st pallet)

HL*3*2*I LIN**BP*71800S84 A100BB *BE*00BB* **ON*79*************SL*12345 ***PG*D10001*CH*MX SN1**60*EA REF*LS* 12345601 00005090 HL*4*2*I LIN**BP*71800S8 4 A100BB *BE*00BB***ON*79************ *SL*12345* **PG*D10001*CH*MX SN1**60*EA REF*LS* 12345601 00005091
2nd Item Level (on 1st pallet)
2nd Pallet Level
3rd Item Level (on 2nd pallet)

HL*6 *5*I LIN**BP*35250S87JA100M1*BE*10MA01***ON*79************* SL*54321***PG*C10001*CH*UCA SN1**60*EA REF*LS* 12345601 00005100
HL* 5*1*T LIN**PG* EP REF*LS* 12345601 00005098
FOOTER DETAIL
CTT*6 *180 SE*31 *10046 GE*1*19 IEA*1*000000022
September 2007
19 - 33
Sample ASN Responding to an 850

To be used as reference only to outline basic ASN structure it does not detail all potential ASN variables.
HEADER DETAIL
ISA*00* *00* *ZZ*HONDAMAILBOX*ZZ*SUPPLIERMAILBOX*040511*1334*U*00400*000000023*0*T*^ GS*SH*HONDAD UNS*SUPPLIERDUNS*20040511*1334*20 *X*004010 ST*856*10047 BSN*00*1000048 2*20040511*1330 DTM*011*20040511*1430 HL*1 **S TD1******N*35*01 TD5**2*CUOT TD3*TL**893 REF*BM*23456 N1*16**98*HMA N1*ST**92*HMA1 01 N1*SU**92*12345601
1st Pallet Level

HL*2*1*T LIN**PG*AP REF*LS*1234560100005122
1st Item Level (on 1st pallet)

HL*3*2*I LIN**BP* 35244S84 A001 *BE*01******* PO *12345600 01*********SL* 52415***PG*D10001*CH*MX SN1**60*EA REF*LS*12345601 00005128
2nd Item Level (on 1st pallet)

HL*4*2*I LIN**BP* 47546S84 A010 *BE*00 BB*******PO*1234560002 *********SL*52446 ***PG*C100021*CH* UOH SN1**60*EA REF*LS*12345601 00005127
FOOTER DETAIL
CTT*4 *12 0 SE* 24 *1004 7 GE*1*20 IEA*1*00000002 3
19 - 34
September 2007
Chapter 19 Advance Shipping Notice (856) ASN and BOL Relationship: For shipments crossing borders (US / Canada / Mexico) the relationship between the ASN# and the BOL# must be one to one. Examples: Each ASN number should reference only one BOL number. Each BOL number should reference only one ASN number. Multiple ASN numbers on one BOL will not be allowed. Notes: The ASN number and BOL number may or may not be the same. There may be multiple ASN/BOL combinations on a truck. The BOL# on the BOL must exactly match the BOL# entered into the ASN (including leading zeros, etc.)
September 2007
19 - 35
Chapter 20 Receiving Advice (861)

Receiving Advice (861)
April 2008
20-1
Chapter Contents
This chapter contains info and procedures for Hondas Receiving Advice transaction. Transaction specs are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 3 Transaction Covered........................................................................................................................... 3 Application Standards and Conventions............................................................................................. 3 Mapping .............................................................................................................................................. 3 Exceptions/ Clarifications.................................................................................................................... 3 Schedule ............................................................................................................................................. 3 Specifications ...................................................................................................................................... 3 Business Purpose ................................................................................................................................ 4 Transaction Specification Information ............................................................................................... 5 Transaction Specifications.................................................................................................................. 6 Functional Group ID=RC................................................................................................................. 6 ST Transaction Set Header............................................................................................................. 7 BRA Beginning Segment for Receiving Advice............................................................................... 7 REF BOS Information...................................................................................................................... 8 DTM Receipt Date........................................................................................................................... 8 N1 Honda Ordering Plant Location ................................................................................................. 9 N1 Supplier Name ......................................................................................................................... 10 N3 Supplier Address ..................................................................................................................... 10 N4 Supplier Geographic Location ................................................................................................. 11 PER Supplier Contact ................................................................................................................... 11 N1 Ship to Location ....................................................................................................................... 12 RCD Receiving Conditions............................................................................................................ 13 LIN Item Identification.................................................................................................................... 14 REF ASN/Packing List Number..................................................................................................... 15 REF BOL Number ......................................................................................................................... 15 CTT Transaction Totals................................................................................................................. 16 SE Transaction Set Trailer ............................................................................................................ 16 Operating Procedures ........................................................................................................................ 17 Replacement Logic ........................................................................................................................... 17 Replacement: ................................................................................................................................ 17 Retransmission:............................................................................................................................. 17 Overview ........................................................................................................................................... 17
20 - 2
April 2008
Transaction Covered
Receiving Advice (Transaction Set 861), abbreviated "RC".

Mapping
A list of the Receiving Advice business data elements and how they are transmitted via EDI Standards is provided in the Transaction Specifications section.
Schedule
The Receiving Advice will be transmitted within 24 hours of the discrepancies recognized between the sellers Advance Ship Notice (ANSI 856) and parts quantities actually received by Honda.
Specifications
It is possible for Honda to transmit multiple Receiving Advices within one envelope. This means that there may be multiple transaction sets (ST-SE header/trailer segments) within one interchange envelope (ISAIEA header/trailer segments). Honda transmits all EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
April 2008
20-3
Business Purpose
The Honda Receiving Advice (ANSI 861) transaction set is used as a discrepancy notification tool. It may indicate either of the following conditions: 1. 2. An exception situation between a suppliers ASN data and the actual receiving data (as recorded by Honda), or An ASN was not received by the time Honda verified the shipment.
FREQUENCY: Within 24 hours of recognizing a shipment discrepancy TRANSMITTED FROM: Honda TRANSMITTED TO: OEM suppliers Service Parts Suppliers
20 - 4
April 2008


The second column:
April 2008
20-5
Functional Group ID=RC
Heading:
Must Use Must Use Pos. No. 010 020 050 Must Use 070 Seg. ID ST BRA REF DTM Name Transaction Set Header Beginning Segment for Receiving Advice BOS Information Receipt Date LOOP ID - N1 Must Use 130 N1 Honda Ordering Plant Location LOOP ID - N1 Must Use Must Use Must Use Must Use 190 192 193 194 N1 N3 N4 PER Supplier Name Supplier Address Supplier Geographic Location Supplier Contact LOOP ID - N1 195 N1 Ship to Location O 1 M M M M 1 1 1 1 1 M 1 1 Req. Des. M M O M Max.Use 1 1 >1 1 1 Loop Repeat
Detail:
Pos. No. Must Use Must Use 010 040 070 075 Seg. ID RCD LIN REF REF Name LOOP ID - RCD Receiving Conditions Item Identification ASN/Packing List Number BOL Number Req. Des. M M O O Max.Use 1 1 1 1 Loop Repeat 200000
Summary:
20 - 6
April 2008

Must Use Must Use
Ref. Des. ST01 ST02
Data Element Summary Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 861 Receiving Advice/Acceptance Certificate 329 Transaction Set Control Number M AN 4/9 This number will be unique (within a transaction set) and ascending. It may be sequential.
BRA Beginning Segment for Receiving Advice

Ref. Des. BRA01 BRA02 BRA03
Must Use
BRA04
Must Use
BRA05
Data Element Summary Data Element Name 127 Receiving Advice Number 373 Create Date Date expressed as CCYYMMDD 353 Transaction Set Purpose Code Valid codes are listed below 05 Replace 962 Receiving Advice Type Code Valid codes are listed below 1 Receiving Dock Advice 337 Create Time Time expressed in 24-hour clock time as HHMM
Attributes M AN 1/10 M DT 8/8 M ID 2/2
ID 1/1
TM 4/4
April 2008
20-7
REF BOS Information

Position: Loop: Level: Usage: Max Use: Notes: 050 Heading Optional >1 BOS (Body on sequence) suppliers will only use this segment. When used, this segment will be used in multiples of three. Each set of three REF segments will include an 01 element of P7, one of BG and one of EG. Each set of three will be linked by a control number (Model Type Identifier) in REF04 (C04002). Data Element Summary Data Element Name 128 Reference Identification Qualifier Valid codes are listed below BG Beginning Sequence Number EG Ending Sequence Number P7 Product Line Number Reference Identification Reference Identifier Reference Identification Qualifier Valid code is listed below SJ Set Number Model Type Identifier
Must Use
Ref. Des. REF01
Attributes M ID 2/3
REF02 REF04 C04001
127 C040 128
M M M
AN 1/30 ID 2/3
Must Use
C04002
127
AN 1/30
DTM Receipt Date

Position: Loop: Level: Usage: Max Use: Notes: 070 Heading Mandatory 1 The date and time of the receiving transaction. Data Element Summary Data Element Name 374 Date/Time Qualifier Valid codes are listed below 050 Received 373 Receipt Date Date expressed as CCYYMMDD 337 Receipt Time Time expressed in 24-hour clock time as HHMM
Must Use
Ref. Des. DTM01
Attributes M ID 3/3
Must Use Must Use
DTM02 DTM03
M M
DT 8/8 TM 4/4
20 - 8
April 2008

Must Use
Ref. Des. N101
Must Use
N103
Must Use
N104
Data Element Summary Data Element Name 98 Plant Identifier Code Valid codes are listed below 16 Plant 66 Identification Code Qualifier Valid codes are listed below 98 Purchasing Office 67 Honda Plant ID This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM =
Attributes M ID 2/2
ID 1/2
AN 3/3
April 2008
20-9
N1 Supplier Name
Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
Data Element Summary Data Element Name Attributes 98 Supplier Identifier Code M ID 2/2 Valid codes are listed below SU Supplier/Manufacturer 93 Supplier Name M AN 1/35 66 Identification Code Qualifier M ID 1/2 Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Supplier Number and Location Code M AN 8/8 An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code (which may be 00).
N3 Supplier Address
Must Use
Ref. Des. N301 N302
Data Element Summary Data Element Name 166 Supplier Address (1) 166 Supplier Address (2)
20 - 10
April 2008

Data Element Summary Ref. Des. N401 N402 N403 N404 Data Element 19 156 116 26 Name Supplier City Name Supplier State or Province Code Supplier Postal Code Supplier Country Code Attributes M AN 2/30 M ID 2/2 M ID 3/10 M ID 2/3

Must Use
Ref. Des. PER01
Must Use
PER02
Data Element Summary Data Element Name 366 Supplier Contact Code Valid codes are listed below SU Supplier Contact 93 Supplier Contact Name
Attributes M ID 2/2
AN 1/30
April 2008
20-11
N1 Ship to Location
Position: Loop: Level: Usage: Max Use: Notes: 195 N1 Optional Heading Optional 1 This segment will only be included if the data is available. Data Element Summary Data Element Name Attributes 98 Ship to Identifier Code M ID 2/2 Valid codes are listed below ST Ship To 66 Ship to Code Qualifier M ID 1/2 Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Ship To Code M AN 2/8 This is the code assigned by Honda for the ship to location from the corresponding 856.
Must Use
Ref. Des. N101
Must Use
N103
Must Use
N104
20 - 12
April 2008
RCD Receiving Conditions

Position: Loop: Level: Usage: Max Use: 010 RCD Mandatory Detail Mandatory 1
Must Use
Ref. Des. RCD06
Must Use Must Use
RCD07 C00101 RCD08
Data Element Summary Data Element Name Attributes 667 Received Quantity M R 1/9 The actual quantity received. If the actual quantity received was zero, "0" will be entered here. C001 Composite Unit of Measure X 355 Unit or Basis for Measurement Code M ID 2/2 Refer to ANSI guidelines for a list of valid codes 412 Receiving Condition Code M ID 2/2 Valid codes are listed below 01 Damaged Product or Container 02 Quantity Short 03 Quantity Over 04 Quality Problem 05 Incorrect Product 06 Non-standard Container 07 Good Condition 08 Rejected 09 Hold 10 Material Scrapped 11 Adjust Supplier Shipped Cumulative Quantity 12 Quantity Over - Returned to Supplier 13 Quantity Received, But Cannot Process Because No Matching Ship Notice 14 Quantity Received and Processed with No Matching Ship Notice/Manifest 16 Not Received - Ship Notice Required
April 2008
20-13

Position: Loop: Level: Usage: Max Use: 040 RCD Mandatory Detail Mandatory 1
Must Use
Ref. Des. LIN02
Must Use
LIN03 LIN04
LIN05
LIN06
LIN07
LIN08
LIN09
LIN10
LIN11
LIN12
LIN13
Data Element Summary Data Element Name Attributes 235 Product ID Qualifier M ID 2/2 Valid codes are listed below BP Buyer's Part Number 234 Mfg. Base Part Number and Color M AN 1/29 235 Product ID Qualifier X ID 2/2 Valid codes are listed below BE Buyer's Engineering Change Level Number 234 DC Part Level X AN 1/6 - For Honda manufacturing facilities this field (and the corresponding qualifier) will be present for a Manufacturing Base Part Number that begins with a number less than 92. - For AHM, this field (and the corresponding qualifier) will not be present. 235 Ship Schedule ID Qualifier X ID 2/2 Valid codes are listed below ON Customer Order Number 234 Ship Schedule Number X AN 1/6 This field (and the corresponding qualifier) applies only to parts ordered by a ship schedule (862). 235 Project Number Qualifier X ID 2/2 Valid codes are listed below: L1 Program Level 234 Project Number X AN 1/6 The business purpose for the project number will be defined at a later date. (Future Honda system enhancement). 235 Purchase Order Qualifier X ID 2/2 Valid codes are listed below PO Purchase Order Number 234 Purchase Order Number X AN 5/10 This field (and the corresponding qualifier) applies only to parts ordered by a purchase order (850). 235 Container Label Serial Qualifier X ID 2/2 Valid codes are listed below BN Bar-Coded Serial Number 234 Container Label Serial Number X AN 16/16 This field (and the corresponding qualifier) is conditional on the availability of the data.
20 - 14
April 2008
LIN14
235
LIN15
234
Master/Mixed Label Serial Qualifier X ID 2/2 Valid codes are listed below BN Bar-Coded Serial Number Master/Mixed Label Serial Number X AN 16/16 This field (and the corresponding qualifier) is conditional on the availability of the data.
REF ASN/Packing List Number

Position: Loop: Level: Usage: Max Use: Notes: 070 RCD Mandatory Detail Optional 1 This segment will only be included if the data is available. Data Element Summary Data Element Name Attributes 128 ASN or Packing List Number Qualifier M ID 2/3 Valid codes are listed below MK Manifest Key Number 127 ASN or Packing List Number M AN 1/8 If an ASN or Packing list number is not available, Honda receiving may assign a reference number for tracking. This number will also be present on the detailed 820 Remittance Advice..
Must Use
Ref. Des. REF01
Must Use
REF02
REF BOL Number

Position: Loop: Level: Usage: Max Use: Notes: 075 RCD Mandatory Detail Optional 1 This segment will only be included if the data is available. Data Element Summary Data Element Name 128 Bill of Lading Qualifier Valid codes are listed below BM Bill of Lading Number 127 Bill of Lading Number
Must Use
Ref. Des. REF01
Attributes M ID 2/3
Must Use
REF02
AN 1/12
April 2008
20-15

Position: Loop: Level: Usage: Max Use: 010 Summary Mandatory 1 Data Element Summary Data Element Name 354 Number of Line Items The accumulation of the number of RCD segments.
Must Use
Ref. Des. CTT01
Attributes M N0 1/6

Must Use Must Use
Ref. Des. SE01 SE02
20 - 16
April 2008
Replacement Logic
Replacement:
Honda sends the 861 as a replacement document. The 861 purpose code transmitted in the BRA03 element is always 05, replace. A document may be replaced for various reasons such as replacing an error in a previous document. Suppliers should use the most recently received 861 based on the replacement logic criteria. Replacement of items from a new 861 should be based upon a match of: Honda Plant ID, N104 (Position 130) Mfg. Base Part number and Color, LIN03 DC Part Level, LIN05, if specified ASN or Packing List Number, REF02 (Position 070), if specified Bill of Lading Number, REF02 (Position 075), if specified
Based upon a match, the prior information for a part number is replaced by the new information for that part number. An 861 replacement may 1) include all items from the original 861 or 2) be a sub-set of items from the original 861.
Retransmission:
Honda can retransmit the 861 document. Retransmission will only occur when the supplier requests that Honda resends the EDI document. This is typically because the supplier had some problem in the translation processing. A retransmitted document can be overlaid based upon a match of Receiving Advice Number, BRA01.
Overview
1. As a default, the 861 will be sent to the same EDI mailbox as the ordering documents. If a supplier wants the 861 sent to a different mailbox (such as an accounting mailbox) contact HondaEDI@ham.honda.com with the request.
April 2008
20-17
Chapter 21 Ship Schedule (862)

Ship Schedule (862)
September 2007
21 - 1
Chapter Contents
This chapter contains information and procedures for using Hondas Ship Schedule transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 4 Transaction Covered........................................................................................................................... 4 Application Standards and Conventions............................................................................................. 4 Mapping .............................................................................................................................................. 4 Exceptions/ Clarifications.................................................................................................................... 4 Schedule ............................................................................................................................................. 4 Specifications ...................................................................................................................................... 4 Back-Up Procedure............................................................................................................................. 4 Business Purpose ................................................................................................................................ 5 Transaction Specification Information ............................................................................................... 6 Transaction Specifications.................................................................................................................. 7 Functional Group ID=SS ................................................................................................................. 7 ST Transaction Set Header............................................................................................................. 8 BSS Beginning Segment for Shipping Schedule/Production Sequence......................................... 9 DTM Create Date .......................................................................................................................... 10 N1 Honda Ordering Plant Location ............................................................................................... 11 N2 Honda Corporate Name........................................................................................................... 12 PER Text Message Identifier......................................................................................................... 12 PER Honda Contact ...................................................................................................................... 13 N1 Supplier Name ......................................................................................................................... 13 N3 Supplier Address ..................................................................................................................... 14 N4 Supplier Geographic Location ................................................................................................. 14 PER Supplier Contact ................................................................................................................... 14 N1 Ship To Location...................................................................................................................... 15 N3 Ship To Address ...................................................................................................................... 15 N4 Ship To Geographic Location .................................................................................................. 16 LIN Item Identification.................................................................................................................... 16 UIT Unit Detail ............................................................................................................................... 17 FST Forecast Schedule Shipment Info ......................................................................................... 18 DTM Delivery/Shipment Date........................................................................................................ 18 JIT Just-In-Time Schedule ............................................................................................................ 19 REF Honda Lot Number................................................................................................................ 19 REF Small Lot/Delivery Batch Number ......................................................................................... 20 REF Lot Sequence Number .......................................................................................................... 20 REF Ship Schedule Order Number............................................................................................... 21 TD1 Container Details ................................................................................................................... 21 TD5 Carrier Details (SCAC) .......................................................................................................... 22
21- 2
September 2007

CTT Transaction Totals................................................................................................................. 22 SE Transaction Set Trailer ............................................................................................................ 23 Operating Procedures........................................................................................................................ 24 Overview ........................................................................................................................................... 24 Replacement Logic ........................................................................................................................... 25 Replacement: ................................................................................................................................ 25 Retransmission:............................................................................................................................. 25 Data Integrity..................................................................................................................................... 26 Honda Lot Number............................................................................................................................ 26 Small Lot/Delivery Batch Number ..................................................................................................... 26 Lot Sequence Number ...................................................................................................................... 27 Pick & Load Sheet Requirements..................................................................................................... 27 Lot Sequence Number Rules............................................................................................................ 27 Small Lot/Delivery Batch Number Rules........................................................................................... 28 Picking, Packing and Loading Examples.......................................................................................... 28 Trailer Loading .................................................................................................................................. 28 Delivery Batch Sequencing............................................................................................................... 29 Example 1 ..................................................................................................................................... 29 Example 2 ..................................................................................................................................... 29 Delivery Batch Labeling .................................................................................................................... 30 Example 1 ..................................................................................................................................... 30 Example 2 ..................................................................................................................................... 30 862 Delivery Schedule Style Variations............................................................................................ 31 Delivery Batch Control ...................................................................................................................... 38 Flow Charts ....................................................................................................................................... 38 Proposed Labeling Flow (Figure 1)................................................................................................... 39 Batch Control Process (Concept) Figure 2 ....................................................................................... 40 Past Due Demand............................................................................................................................. 41 Past Due Demand............................................................................................................................. 42 Past Due Demand............................................................................................................................. 43 Ship Schedule Number Style ............................................................................................................ 45
September 2007
21 - 3
Transaction Covered
Ship Schedule (Transaction Set 862), abbreviated "SS".

Mapping
A list of the Shipping Schedule business data elements and how they will be transmitted via EDI Standards is provided in the Transaction Specifications section.
Honda may need to transmit more information than can be accommodated in the 96 iterations of the JIT loop permitted by ANSI specifications. When this case occurs, another iteration of the FST loop will occur. Such an iteration of the FST loop will have the same delivery/shipment date as the previous FST loop(s). Therefore multiple iterations of the FST loop (for the item specified in the LIN segment) may occur for a particular shipment/delivery date.
Schedule
For all Honda manufacturing facilities: The Shipping Schedule generally will be transmitted on every Production Day by 12:00 noon Eastern Time. The seller will notify the buyer no later than 1:00 pm Eastern Time if the seller has not received the daily Shipping Schedule. AHM: The Shipping Schedule will be transmitted as needed.
Specifications
It is possible for Honda to transmit multiple Ship Schedules within one envelope. This means that there may be multiple transaction sets (STSE header/trailer segments) within one interchange envelope (ISA-IEA header/trailer segments). Honda transmits all EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up Procedure
In the event of a failure of Electronic Data Interchange, it is the responsibility of the sending party to transmit the contents of any pending transmission to the receiving party using a method of non-EDI transmission which is timely, reasonable, and appropriate under the circumstances.
21- 4
September 2007
Business Purpose
The Honda Ship Schedule (ANSI 862) is used to authorize shipment of specific parts and quantities to specific destinations on specific dates and times. It is loosely linked by part number and quantity to a previously transmitted Weekly Release (830). The Ship Schedule (ANSI 862) is not to be used as a stand alone order for labor or materials. Honda Manufacturing facilities (except HDM) use the Ship Schedule (862) transaction, in conjunction with the Weekly Release (830) transaction, as the normal method of placing OEM orders. AHM will use the Ship Schedule (862) on an as-needed basis based on agreement between AHM and the supplier.
FREQUENCY: Daily/as applicable TRANSMITTED FROM: Honda TRANSMITTED TO: OEM suppliers, DSPS Suppliers, Service Parts Suppliers
September 2007
21 - 5

The following Transaction Specifications consist of two sections: 1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality. Note - The Req. Des. for the first segment in a loop is also used for that corresponding loop.
2.
The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column:

The second column:
21- 6
September 2007
Functional Group ID=SS
Heading:
Pos. No. 010 020 030 Seg. ID ST BSS DTM Req. Des. M M M Loop Repeat
Name Transaction Set Header Beginning Segment for Shipping Schedule/Production Sequence Create Date LOOP ID - N1
Max.Use 1 1 1
1 M M O M 1 1 1 1 1 M M M M 1 1 1 1 1 M M M 1 1 1
Must Use Must Use
050 060 095
N1 N2 PER PER
Honda Ordering Plant Location Honda Corporate Name Text Message Identifier Honda Contact LOOP ID - N1
Must Use
100
115 121 122 123
N1 N3 N4 PER
Supplier Name Supplier Address Supplier Geographic Location Supplier Contact LOOP ID - N1
130 140 150
N1 N3 N4
Ship To Location Ship To Address Ship To Geographic Location
Detail:
Pos. No. Must Use Must Use 010 020 Seg. ID LIN UIT Name LOOP ID - LIN Item Identification Unit Detail LOOP ID - FST Must Use Must Use 080 090 FST DTM Forecast Schedule Shipment Info Delivery/Shipment Date LOOP ID - JIT Must Use 110 120 130 135 137 Must Use Must Use 160 180 JIT REF REF REF REF TD1 TD5 Just-In-Time Schedule Honda Lot Number Small Lot/Delivery Batch Number Lot Sequence Number Ship Schedule Order Number Container Details Carrier Details (SCAC) M O O O O M M 1 1 1 1 1 1 1 M M 1 1 96 Req. Des. M M Max.Use 1 1 100 Loop Repeat 10000
September 2007
21 - 7
Summary:

Must Use
Ref. Des. ST01
Must Use
ST02
Data Element Summary Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes listed below 862 Shipping Schedule 329 Transaction Set Control Number M AN 4/9 This number will be unique (within a transaction set) and ascending. It may be sequential.
21- 8
September 2007
BSS Beginning Segment for Shipping Schedule/Production Sequence

Must Use
Ref. Des. BSS01
Must Use
BSS02
Must Use Must Use
BSS03 BSS04
BSS05 BSS06 BSS08
Must Use
BSS11
Data Element Summary Data Element Name Attributes 353 Transaction Set Purpose Code M ID 2/2 Valid codes listed below 05 Replace 127 Reference Num. - Ship Schedule M AN 1/14 This number links all parts on this 862 together. It is also used to link to the 864 text transaction. 373 Create Date M DT 8/8 This is the creation date of this document. Date expressed as CCYYMMDD 675 Schedule Type Qualifier M ID 2/2 Valid codes listed below DL Delivery Based 373 Horizon Start Date M DT 8/8 Date expressed as CCYYMMDD 373 Horizon End Date M DT 8/8 Date expressed as CCYYMMDD 127 Reference Num. - Ship Schedule M AN 1/14 This number links all parts on this 862 together. The data value of this field is identical to BSS02. Honda uses this field merely to fulfill requirements of the standards. 676 Schedule Quantity Qualifier M ID 1/1 Valid codes are listed below R Replacement Quantities
September 2007
21 - 9
DTM Create Date

Position: Loop: Level: Usage: Max Use: Notes: 030 Heading Mandatory 1 This segment identifies the creation date and time of this document. DTM02 and BSS03 are identical. Data Element Summary Data Element Name Attributes 374 Date/Time Qualifier M ID 3/3 Valid codes listed below 167 Most Recent Revision (or Initial Version) 373 Create Date M DT 8/8 Date expressed as CCYYMMDD. 337 Create Time M TM 4/4 Time expressed in 24-hour clock time as HHMM
Must Use
Ref. Des. DTM01
Must Use Must Use
DTM02 DTM03
21- 10
September 2007

Position: Loop: Level: Usage: Max Use: Notes: 050 N1 Mandatory Heading Mandatory 1 This segment identifies the Honda ordering plant. Data Element Summary Data Element Name 98 Entity Identifier Code Valid codes listed below 16 Plant 93 Plant Name 66 Identification Code Qualifier Valid codes are listed below 98 Purchasing Office 67 Honda Plant ID This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM =
Must Use
Ref. Des. N101
Attributes M ID 2/2
Must Use Must Use
N102 N103
M M
AN 1/35 ID 1/2
Must Use
N104
AN 3/3
September 2007
21 - 11

Must Use
Ref. Des. N201
Data Element Summary Data Element Name Attributes 93 Corporation Name M AN 1/35 The corporate name for the Honda facility issuing this document. For example: (May not be an all-inclusive list.) "Honda of America Mfg., Inc." "Honda Manufacturing of Alabama, LLC" "Honda of Canada Mfg." Honda de Mexico, S.A. de C.V. "American Honda Motor Co., Inc." "Honda Power Equipment" "Honda of South Carolina" Honda Power Train Georgia "Honda Transmission"

Position: Loop: Level: Usage: Max Use: Notes: 095 N1 Mandatory Heading Optional 1 This segment will only be used if there is a corresponding text message for this document. Data Element Summary Data Element Name Attributes 366 Text Message Code M ID 2/2 Valid codes listed below ZZ Mutually Defined 93 Check for 864 M AN 1/30 "Comments in EDI 864 " When this message appears, it indicates that an applicable 864 Text message has also been transmitted.
Must Use
Ref. Des. PER01
Must Use
PER02
21- 12
September 2007
PER Honda Contact

Must Use
Ref. Des. PER01
Must Use
PER02
Data Element Summary Data Element Name 366 Buyer Contact Code Valid codes listed below BD Buyer Name or Department 93 Honda Buyer Name
Attributes M ID 2/2
AN 1/35
N1 Supplier Name
Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/2 Valid codes listed below SU Supplier/Manufacturer 93 Supplier Name M AN 1/35 66 Supplier Number Qualifier M ID 1/2 Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Supplier Number and Loc Code M AN 8/8 An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code (which may be 00).
September 2007
21 - 13
N3 Supplier Address
Position: Loop: Level: Usage: Max Use: 121 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name 166 Supplier Address Information (1) 166 Supplier Address Information (2)
Must Use
Ref. Des. N301 N302

Position: Loop: Level: Usage: Max Use: 122 N1 Mandatory Heading Mandatory 1 Data Element Summary Ref. Des. N401 N402 N403 N404 Data Element 19 156 116 26 Name Supplier City Name Supplier State or Province Code Supplier Postal Code Supplier Country Code Attributes M AN 2/30 M ID 2/2 M ID 3/10 M ID 2/3

Position: Loop: Level: Usage: Max Use: 123 N1 Mandatory Heading Mandatory 1 Data Element Summary Data Element Name 366 Contact Function Code Valid codes listed below SU Supplier Contact 93 Supplier Contact Name
Must Use
Ref. Des. PER01
Attributes M ID 2/2
Must Use
PER02
AN 1/30
21- 14
September 2007
N1 Ship To Location
Must Use
Ref. Des. N101
Must Use Must Use
N102 N103
Must Use
N104
Data Element Summary Data Element Name Attributes 98 Ship To Name Qualifier M ID 2/2 Valid codes are listed below ST Ship To 93 Ship To Name M AN 1/35 66 Ship To Code Qualifier M ID 1/2 Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Ship To Code M AN 2/8 This is the code assigned by Honda for this ship to location - For OEM and AHM orders, this will be a ship to code - For DSPS orders, this will be the supplier number and location code
N3 Ship To Address
Must Use
Ref. Des. N301 N302
Data Element Summary Data Element Name 166 Ship To Address Information 1 166 Ship To Address Information 2
September 2007
21 - 15

Data Element Summary Ref. Des. N401 N402 N403 N404 Data Element 19 156 116 26 Name Ship To City Name Ship To State or Province Code Ship To Postal Code Ship To Country Code Attributes M AN 2/30 M ID 2/2 M ID 3/10 M ID 2/3

Position: Loop: Level: Usage: Max Use: 010 LIN Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 235 Mfg. Base Part Number Qualifier M ID 2/2 Valid codes listed below BP Buyer's Part Number 234 Mfg. Base Part Number and Color M AN 1/29 235 D/C Part Level Qualifier X ID 2/2 Valid codes listed below BE Buyer's Engineering Change Level Number - "BE" Qualifier indicates the part must be shipped at this Design change level. EC Engineering Change Level - "EC" Qualifier is for reference only, parts may be shipped at another level. To determine the correct design level to ship, follow the Honda Specification Change "Instruction Sheet" or Instruction Summary from your Honda planner. - KEY POINT: ALWAYS LABEL THE PARTS WITH
Must Use
Ref. Des. LIN02
Must Use
LIN03 LIN04
21- 16
September 2007

THE ACTUAL DESIGN LEVEL. DC Part Level X AN 1/6 - For Honda manufacturing facilities this field (and the corresponding qualifier) will be present for a Manufacturing Base Part Number that begins with a number less than 92. - For AHM, this field (and the corresponding qualifier) will not be present. Part Number Description Qualifier M ID 2/2 Valid codes listed below PD Part Number Description Part Number Description M AN 1/30 Part Level Ship Schedule Number Qualifier X ID 2/2 Valid codes listed below ON Customer Order Number Part Level Ship Schedule Number X AN 1/6 - For HAM: (Note: As HAM plants convert to GPCS, see the below rule.) - The ship schedule order number will always be transmitted in this element. - This number will be unique for a given logistical company. - This number should be returned in the 856, item level LIN09. - This number may change every time an 862 is received by the supplier. - For AHM, HCM, HMA, HMIN, HPE, HPPG, HSC, HTM - LIN 08 & 09 will not be transmitted. (The ship schedule order number will be transmitted in a REF segment - position 137- within the JIT loop.) Project Number Qualifier X ID 2/2 Valid codes listed below: L1 Program Level Project Number X AN 1/6 This is a reference number for a particular honda event or project.
LIN05
234
Must Use
LIN06
235
Must Use
LIN07 LIN08
234 235
LIN09
234
LIN10
235
LIN11
234
UIT Unit Detail

Must Use Must Use
Data Element Summary Data Element Name C001 Composite Unit of Measure 355 Unit or Basis for Measurement Code Refer to ANSI guidelines for a list of valid codes
September 2007
21 - 17
FST Forecast Schedule Shipment Info

Position: Loop: Level: Usage: Max Use: Notes: 080 FST Mandatory Detail Mandatory 1 When the number of iterations of the JIT loop for a specific Delivery/Shipment date/time exceeds the 96 iteration ANSI limit, Honda will create a new iteration of the FST loop with the same Delivery/Shipment date. Honda will create as many iterations of the FST loop (with the same Delivery/Shipment date) as required to completely define a Delivery/Shipment of the item specified in the LIN segment. Data Element Summary Data Element Name Attributes 380 Total Daily Quantity M R 1/15 This will be a total of the JIT01's within this iteration of the FST loop. 680 Quantity Qualifier M ID 1/1 Valid codes listed below C Firm 681 Delivery/Shipment Qualifier M ID 1/1 Valid codes listed below C Daily 373 Delivery/Shipment Date M DT 8/8 - Date expressed as CCYYMMDD. - When the number of JIT iterations exceeds 96 within an FST loop, a new FST loop will result (see Notes above). When the JIT loop exceeds 96 iterations, the resulting FST04 will duplicate the previous FST04.
Must Use Must Use
Ref. Des. FST01 FST02
Must Use
FST03
Must Use
FST04
DTM Delivery/Shipment Date

Position: Loop: Level: Usage: Max Use: 090 FST Mandatory Detail Mandatory 1
Must Use
Ref. Des. DTM01
Must Use
DTM02
Data Element Summary Data Element Name 374 Date/Time Qualifier Valid codes are listed below 002 Delivery Requested 010 Requested Ship 373 Delivery/Ship Date Date expressed as CCYYMMDD
Attributes M ID 3/3
DT 8/8
21- 18
September 2007
JIT Just-In-Time Schedule

Position: Loop: Level: Usage: Max Use: Notes: 110 JIT Mandatory Detail Mandatory 1 If an order exceeds 96 JIT iterations, the 97th JIT loop will result in a new FST loop. A new FST loop will begin each time the JIT iterations exceed 96. Data Element Summary Data Element Name 380 Quantity The quantity to be delivered/shipped at the time in JIT02. 337 Delivery/Ship Time Time expressed in 24-hour clock time as HHMM
Must Use Must Use
Ref. Des. JIT01 JIT02
Attributes M R 1/15 M TM 4/4
REF Honda Lot Number

Position: Loop: Level: Usage: Max Use: 120 JIT Mandatory Detail Optional 1 Data Element Summary Data Element Name Attributes 128 Honda Lot Number Qualifier M ID 2/3 Valid codes are listed below LT Lot Number 127 Honda Lot Number M AN 1/12 - If this number is transmitted in an ordering document, it must be returned in the corresponding 856, item level LIN07.
Must Use
Ref. Des. REF01
Must Use
REF02
September 2007
21 - 19
REF Small Lot/Delivery Batch Number

Position: Loop: Level: Usage: Max Use: 130 JIT Mandatory Detail Optional 1 Data Element Summary Data Element Name Attributes 128 Small Lot/Delivery Batch Number Qualifier M ID 2/3 Valid codes are listed below BT Batch Number 127 Small Lot/Delivery Batch Number M AN 1/6 - Identifier used for packaging purposes. Refer to Honda's Packaging Guidelines for more detailed information. - This number must be included on the shipping Pick & Load Sheet.
Must Use
Ref. Des. REF01
Must Use
REF02
REF Lot Sequence Number

Position: Loop: Level: Usage: Max Use: 135 JIT Mandatory Detail Optional 1 Data Element Summary Data Element Name Attributes 128 Lot Sequence Number Qualifier M ID 2/3 Valid codes are listed below JS Job Sequence Number 127 Lot Sequence Number M AN 1/6 - This data indicates one of the following: - The order to load containers on a trailer - The order to pack parts in a container - This number must be included on the shipping Pick & Load Sheet.
Must Use
Ref. Des. REF01
Must Use
REF02
21- 20
September 2007
REF Ship Schedule Order Number

Position: Loop: Level: Usage: Max Use: Notes: 137 JIT Mandatory Detail Optional 1 This segment will always be provided for AHM, HCM, HMA, HMIN, HPE, HPPG, HSC, HTM orders. Data Element Summary Data Element Name 128 Ship Schedule Order Number Qualifier Valid codes are listed below
Must Use
Ref. Des. REF01
Attributes M ID 2/3
Must Use
REF02
127
ON Order Number Ship Schedule Order Number M AN 1/6 This number may repeat after 18 months. For AHM, HCM, HMA, HMIN, HPE, HPPG, HSC, HTM -The ship schedule order number will always be transmitted in this location. -This number should be returned in the 856, item level LIN09. -This number is a discrete number that will not change for a given date/time, from one 862 to another. - Multiple order numbers per part with the same date/time are possible. -This number will be unique for a given logistical company For HAM: -This segment will not be transmitted until the HAM plant converts to GPCS. At that time see the above rule. (The ship schedule order number will be transmitted in LIN 08 & 09 until the HAM plant converts to GPCS.)

Position: Loop: Level: Usage: Max Use: Notes: 160 LIN Mandatory Detail Mandatory 1 This segment concerns the Container Type that should be used to ship the product in. This Container Type is returned in the ASN. Honda also requires the Pallet Type be returned in the ASN. The Pallet Type is NOT sent on the 862. Please contact you buyer to obtain the correct Pallet Type. Data Element Summary Data Element Name 80 Quantity Per Container 79 Container Type - Container type as designated by Honda - "XX" will be used for non-returnable containers
Must Use Must Use
Ref. Des. TD102 TD105
September 2007
21 - 21

Position: Loop: Level: Usage: Max Use: 180 LIN Mandatory Detail Mandatory 1 Data Element Summary Data Element Name Attributes 66 SCAC Code Qualifier M ID 1/2 Valid codes listed below 2 Standard Carrier Alpha Code (SCAC) 67 SCAC Code M AN 4/4 - The Standard Carrier Alpha Code (SCAC) of the planned carrier - AHM & HDM will always transmit "XXXX" for this value - Honda manufacturing suppliers must return the SCAC code of the trucking company picking up the freight on the 856 (Advance Ship Notice), unless otherwise specified by your Purchasing contact. This will usually match the SCAC found in the ordering document.
Must Use
Ref. Des. TD502
Must Use
TD503

Position: Loop: Level: Usage: Max Use: 010 Summary Mandatory 1 Data Element Summary Data Element Name Attributes 354 Number of Line Items M N0 1/6 The accumulation of number of LIN segments. 347 Hash Total M R 1/10 Sum of the value of the quantities (FST01) for each FST segment.
Must Use Must Use
21- 22
September 2007

Must Use Must Use
Ref. Des. SE01 SE02
September 2007
21 - 23
Overview
1. The Ship Schedule (862), also referred to as the "Delivery Schedule", is used to authorize actual shipment of specific parts and quantities to specific destinations on specific dates and times. The 862 generally supports forecast information contained in the Weekly Release (830). Suppliers receive a Ship Schedule for a defined "frozen" period including the current day. Quantities in the frozen period are relatively stable; however they may be subject to change. Depending on the part(s) involved, the frozen period typically reflects transportation lead-time. The frozen period may be negotiated between the supplier and Honda's buyer. Replacement logic is critical for proper system-to-system communication. Please review the Replacement Logic section. Suppliers should ship parts according to the most recently received Ship Schedule (862). If an 862 arrives, and there is a discrepancy with the former 862, please contact your Honda Buyer. Each Ship Schedule will include either a ship date/time or a delivery date/time. This information will be consistent within each ship schedule and from ship schedule to ship schedule for a given supplier. A Text Message (864) can be attached with special instructions or other pertinent information. See the Text Message (864) Transaction Specifications for details. Zero quantities may be transmitted for parts that have no requirements for designated ship dates/times. AHM use of the 862 will be determined at a later time. The DC level on Honda ordering documents will be updated after receiving a new DC level from the suppliers ASN (HAM, HPPG, HTM). The Supplier is responsible for all backorders. A Backorder is any order that is short of the Requested Quantity. HDM does not use the 862 at this time.
2.
3. 4. 5. 6.
7.
8. 9. 10. 11. 12.
21- 24
September 2007
Replacement Logic
Replacement:
Honda sends the 862 as a replacement document. The 862 purpose code transmitted in the BSS01 element is always 05, replace. A document may be replaced for various reasons such as replacing an error in a previous document. Supplier systems should have the capability to compare successive incoming Ship Schedules and replace items that are identical for the change points listed below. Replacement of items from the new 862 should be based upon a match of: Honda Plant ID, N104 (Position 050) Ship To Code, N104 (Position 130) Mfg. Base Part Number and Color, LIN03 Honda uses direct replacement methodology. When a match of Mfg. Plant ID/Ship To Code/Base Part Number and Color occurs, all subordinate details should be replaced with the new information. NOTE Date/time buckets may be used for reporting purposes but should not be a data replacement key. When requirements are reduced to zero or moved to another date/time a zero may or may not be transmitted to cancel the previous quantity. When a zero is not sent the original quantity must still be cancelled.
Retransmission:
Honda can retransmit the 862 document. Retransmission will only occur when the supplier requests that Honda resend the EDI document. This is typically because the supplier had some problem in the translation processing. A retransmitted document can be overlaid based upon the same logic as the replacement logic above.
September 2007
21 - 25
Data Integrity
The software must maintain the linkage of the following fields from 862 receipt, through shipment/ASN creation, although not all this information will be returned on the ASN: Part Number Ship Schedule/Order Number Honda Lot /Small Lot/Delivery Batch/Lot Sequence Numbers
Honda Lot Number

The Honda Lot Number (Production Lot Number) is an identifier assigned to a Honda Production Lot. A production lot is a grouping of units (usually 30) used for planning purposes. If the Honda Lot Number is transmitted on an 862 (REF02, Position 120), it must be returned in: ASN (856), LIN07 Master Packing List (MPL) Quick Receive Label (one Lot Number per label, see chapter 9) Note Honda Lot Numbers may not be sent in sequential order. For Honda use only, should not be used for anything other than turnaround data The Lot Number may be repeated with same or different parts. AHM will not use Honda Lot Numbers.
Small Lot/Delivery Batch Number

The Small Lot/Delivery Batch Number is an identifier used for packaging purposes. A Small Lot/Delivery Batch may need to be packed in one or multiple containers. Please refer to Hondas packaging guidelines for more detailed information. If the Small Lot/Delivery Batch Number is transmitted on an 862 (REF02, Position 130), it must be returned on: Batch Label (see Chapter 9) Note Must be presented on Pick & Load Sheet AHM will not use Small Lot/Delivery Batch Numbers.
21- 26
September 2007
Lot Sequence Number

The Lot Sequence Number is an identifier used for loading/packaging purposes. Trailers/containers should be loaded in sequence using this number. Contact Hondas Packaging group for additional information on sequencing. If the Lot Sequence Number is transmitted on an 862, it does not need to be returned to Honda. It is for packaging purposes only. Note Must be presented on Pick & Load Sheet The Sequence Number will be unique for a single part number. The Sequence Number may be duplicated across multiple part numbers. AHM will not use Lot Sequence Numbers.
Pick & Load Sheet Requirements

Suppliers are required to systematically generate a Pick & Load Sheet for each shipment. This should provide (at a minimum) the following information:
Part number (w/ color code if applicable) Quantity Lot Sequence Number (if on 862) Small Lot Batch Number (if on 862)
Lot Sequence Number Rules

1. 2. 3. 4. When present, it must be linked to the Part Number and Quantity that was transmitted on the 862. When present, parts must be sorted on this number. May be the first key field on which to sort the Pick & Load Sheet. Suppliers are required to load trailers according to the Lot Sequence Number (descending). For example:
4/5/6
2/1
Front Lot sequence #7
Tail Lot sequence #1
September 2007
21 - 27
Small Lot/Delivery Batch Number Rules

1. 2. 3. When present, it must be linked to the Part Number and Quantity that was transmitted on the 862. When present, Part Numbers and Quantities with common Small Lot/Delivery Batch Numbers must be grouped together. Suppliers are required to use this number for packing purposes.
Picking, Packing and Loading Examples

The following are examples of Honda picking, packing, and loading requirements. They are split into four categories: 1. 2. 3. 4. Trailer Loading Delivery Batch Sequencing Delivery Batch Labeling 862 Delivery Schedule Variations
Trailer Loading
The purpose of the following two examples is to illustrate different methods of trailer loading based on Honda requirements. In all cases where trailer sequencing is involved, the trailer should be loaded in descending sequence number order from the front to the back of the trailer.
Seq #8 Part A Seq #7 Part A Seq #6-4 Parts C,D Batch 1000 Seq. #3-1 Parts E, F Batch 1050
Example 1 Trailer/Container Sequenced Shipment Full containers and small lots in sequence. Example 2 Summary with Delivery Batch Shipment In some cases batches can span across multiple containers and trailers.
Std. Pack Parts A
Std Pack Parts B
Seq # 4-3 Batch 1000
Seq # 2-1 Batch 1010
21- 28
September 2007
Delivery Batch Sequencing

The next two examples illustrate sequencing within a container based on 862 requirements. Example 1 shows a typical Delivery Batch situation with a 15 unit container quantity. The second example is similar to the first but shows that Honda could have a lot split across containers (30 unit containers). In this case, suppliers system should split requirements to even container quantity based on sequence number.
Example 1
Sequence # 231 232 233 234 1st container:
1pc. - AAAA 14pcs. - BBBB
Honda Lot # Batch # E303100060 E303100070 E303100080 E303100090 322048 322048 322048 322048
Item AAAA BBBB BBBB AAAA
Quantity 1 14 14 1
2nd container:
14pcs. - BBBB 1pc. - AAAA
Delivery Batch Label
Delivery batch label
Example 2
Sequence # Honda Lot # Batch # 451 452 453 454 455 456 457 E303100051 E303100051 E303100051 E303100052 E303100052 E303100052 E303100052 322051 322051 322051 322051 322051 322051 322051 Item CCCC DDDD DDDD DDDD DDDD DDDD CCCC Quantity 1 18 7 10 22 1 1
1st container:
1pc. - CCCC 29pcs. - DDDD
2nd container:
29pcs. - DDDD 1pc. - CCCC
September 2007
21 - 29
Delivery Batch Labeling

Some delivery batches require a supplier to split quantities over multiple containers. Because delivery batches and partial lots require a Delivery Batch Label, there are some cases where a Delivery Batch Label does not apply. Example 1 shows the label requirements for containers with multiple part numbers. In this case, only the first container has mixed part numbers and requires the Delivery Batch Label. Example 2 shows a partial lot of 13 parts and requires a Delivery Batch Label (container 4). Containers 1and 2 are full packs of multiple parts numbers and also requires a Delivery Batch Label. Container 3 does not require a Delivery Batch Label because the container is a full pack with one part number. Both examples assumes a container quantity of 15.
Example 1
Sequence # Honda Lot # Batch # 654 655 656 657 E303100020 E303100030 E303100040 E303100050 1st container:
Item AAAA BBBB AAAA AAAA
Quantity 6 4 5 15
322051 322051 322051 322051
2nd container:
15 pcs. - AAAA
6 pcs. - AAAA 4 pcs. BBBB 5 pcs. - AAAA
Example 2
Sequence # Honda Lot # Batch # 785 786 787 788 789 E303100097 E303100097 E303100097 E303100097 E303100098 322051 322051 322051 322051 322051 Item AAAA BBBB BBBB CCCC AAAA Quantity 8 7 5 8 30 3rd container:
15 pcs. - AAAA
1st container:
8pcs - AAAA 7 pcs - BBBB
Delivery Batch Label Delivery Batch Label
2nd container:
5pcs -BBBB 8pcs - CCCC 2pcs -AAAA
4th container:
13pcs - AAAA
21- 30
September 2007
862 Delivery Schedule Style Variations

The following 862 Delivery Schedule Styles describe 862 variations that can be sent by Honda. The 862 style received by each supplier will be determined by the Buyer/Planner based on how the part(s) will be consumed on the production line. A supplier could have one or more variations of these schedules depending on their overall relationship with Honda. The three basic categories for delivery to Honda are:
1. Summary Parts that are shipped in bulk and normally delivered to a Honda third party warehouse. Presence of a Batch, Lot and/or Sequence Number in this ordering style refers to individual packaging requirements. 2. Multi-Summary Similar to Summary except there are multiple ship times per day due to the demand and/or characteristics of the individual parts. Presence of a Batch, Lot and/or Sequence Number in this ordering style refers to individual packaging requirements. Presence of only the Sequence Number indicates a priority for trailer loading. 3. Sequence Parts are sent directly to a Honda plant and the demand is determined directly by the Honda Production Lot being produced.
The following pages provide examples of each style type, including a screen print of each 862 style and any of its variations. Also provided is a sample of a Picklist/Shipping Summary with notes as to how Honda would expect this shipment to be packed in containers and loaded on the trailer. Software Developers should note how the pick list is both sorted and grouped on the appropriate fields to allow for the proper staging of these parts by a suppliers shipping associates. In this manner, the examples have built on everything presented in this manual up to this point. Note: Normally, once a delivery style is established for a part, the delivery style will be maintained for the duration of that part. However, the Honda Ordering Plant may change the delivery style if necessary.
September 2007
21 - 31
862 Example 1: Summary Supplier

(Bulk - No Small Lot Requirements)
Due Date 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 Seq. Lot Batch Part 83301SEP A003 NH167L 83301SEP A003 NH528L 83301SEP A003 YR167L 83301SEP A003 YR240L 83302SEP A003 NH167L 83302SEP A003 NH528L 83302SEP A003 YR167L 83302SEP A003 YR240L D/C 03 03 03 03 00 00 00 00 Order 54755 54756 54757 54758 54773 54774 54775 54776 Pack Qty 15 15 15 15 15 15 15 15 Order Qty 30 15 135 135 30 15 120 135
Example of Supplier Pick list/Shipping Summary For Requirements due on 11/30 at 9:00
Seq. Lot Batch Part 83301SEP A003 NH167L 83301SEP A003 NH528L 83301SEP A003 YR167L 83301SEP A003 YR240L 83302SEP A003 NH167L 83302SEP A003 NH528L 83302SEP A003 YR167L 83302SEP A003 YR240L D/C 03 03 03 03 00 00 00 00 Order 54755 54756 54757 54758 54773 54774 54775 54776 Pack Qty 15 15 15 15 15 15 15 15 Order Qty 30 15 135 135 30 15 120 135 Cont. Count 2 1 9 9 2 1 8 9 Remarks Full Containers Full Container Full Containers Full Containers Full Containers Full Container Full Containers Full Containers
Note: 1) This example represents how Honda would want the requirements packed for a Summary Supplier with full lot requirements.
21- 32
September 2007
862 Example 2: Summary Supplier with Small Lots

Due Date 11/29 9:00 11/29 9:00 11/29 9:00 11/29 9:00 11/29 9:00 11/29 9:00 11/29 9:00 11/29 9:00 11/29 9:00 11/29 9:00 11/29 9:00 Seq.
000001 000002
Lot
010411160050 010411160060
Batch
411250 411250
Part
77520SHJ A210M1 YR239L 77610SHJ A010M1 NH167L 77620SHJ A010M1 NH167L 83226SOX A000M1 G64L 83226SOX A000M1 NH220L 83226SOX A000M1 YR239L 83227SOX A000M1 G64L 83227SOX A000M1 NH220L 83227SOX A000M1 YR239L 7490ASHJ A200 NH678M 7490AShJ A200 B530M
D/C
14M101 12M1 12M1 12M102 12M102 12M102 12M1 12M1 12M1 00 11 00 11
Order 702065 702065 702065 702065 702065 702065 702065 702065 702065 702065 702065
Pack Qty 30 15 15 30 30 30 30 30 30 15 15
Order Qty 0 90 90 0 360 0 0 360 0 6 24
Example of Supplier Picklist/Shipping Summary For Requirements due on 11/29 at 9:00

Seq. 000001 Lot 010411160050 Batch 411250 Part 77610SHJ A010M1 NH167L 77620SHJ A010M1 NH167L 83226SOX A000M1 NH220L 83227SOX A000M1 NH220L 7490ASHJ A200 NH678M 7490ASHJ A200 B530M D/C 12M1 12M1 12M1 02 12M1 00 11 Order 702065 702065 702065 702065 702065 Pck Qty 15 15 30 30 15 Rqd. Qty 90 90 360 360 6 Cont. Count 6 6 12 12 0 Remarks Full Containers Full Containers Full Containers Full Containers Combine with Next Container One mixed with above and One full
000002
010411160060
411250
00 11
702065
15
24
Notes: 1. This example represents how Honda would want the requirements packed for a Summary Supplier with Small Lot Requirements. 2. For a Summary supplier, the Small Lots are loaded at the rear of the trailer. 3. A Delivery Batch Label must be used for the small lot container that is mixed. 4. It is possible to receive a batch and lot number without a sequence number. When this occurs sequence within the container is not critical.
September 2007
21 - 33
862 Example 3: Multi-Summary Sequenced Supplier

Due Date 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 Seq. 000005 000005 000006 000006 000007 000007 Lot Batch Part 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P D/C 10M103 13M103 10M103 13M103 10M103 13M103 Order 702842 702842 702842 702842 702842 702842 Pack Qty 30 30 30 30 30 30 Order Qty 30 30 30 30 30 30

Seq. 000005 000005 000006 000006 000007 000007 Notes: 1. This example represents how Honda would want the requirements packed for a Multi-Summary Supplier without small lots. - The supplier needs to sequence the containers on the trailer (Highest Sequence Number on the front of the trailer). 2. A Multi-Summary Supplier ships multiple times per day. 3. It is possible to receive a batch and lot number without a sequence number. When this occurs sequence within the container is not critical. Lot Batch Part 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P D/C 10M103 13M103 10M103 13M103 10M103 13M103 Order 702842 702842 702842 702842 702842 702842 Pack Qty 30 30 30 30 30 30 Rqd. Qty 30 30 30 30 30 30 Cont. Count 1 1 1 1 1 1 Remarks Full Container Full Container Full Container Full Container Full Container Full Container
21- 34
September 2007
862 Example 4: Multi-Summary Sequenced Supplier with Small Lots

Due Date 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 Seq.
000001 000001 000002 000002 000003 000003 000004 000004
Lot
020412020100 020412020100 020412030010 020412030010 -
Batch
411128 411128 411128 411128 -
Part
71120SHJ A010M1 74890SHJ A010M1 71120SHJ A010M1 74890SHJ A010M1 71120SHJ A010M1 74890SHJ A010M1 71120SHJ A010M1 74890SHJ A010M1 NH662P NH662P NH662P NH662P NH662P NH662P NH662P NH662P
D/C
10M103 13M103 10M103 13M103 10M103 13M103 10M103 13M103
Order
702842 702842 702842 702842 702842 702842 702842 702842
Pack Qty
30 30 30 30 30 30 30 30
Order Qty
30 30 10 10 20 20 30 30

Seq. 000001 000001 000002 020412020100 Lot 411128 Batch Part 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P 71120SHJ A010M1 NH662P D/C 10M103 13M103 10M103 Order 702842 702842 702842 Pack Qty 30 30 30 Rqd. Qty 30 30 10 Cont. Count 1 1 Remarks Full Container Full Container Combine with Next Container Combine with Above Container Combine with Next Container Combine with Above Container Full Container Full Container
000003
020412030010
411128
71120SHJ A010M1 NH662P
10M103
702842
30
20
000002
020412020100
411128
74890SHJ A010M1 NH662P
13M103
702842
30
10
000003 000004 000004
020412030010 -
411128 -
74890SHJ A010M1 NH662P 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P
13M103 10M103 13M103
702842 702842 702842
30 30 30
20 30 30
1 1 1
Notes: 1.This example represents how Honda would want the requirements packed for MultiSummary Supplier with Small Lot Requirements. The supplier needs to sequence the containers on the trailer (Highest Sequence Number on the front of the trailer). The small lot containers would intermix in the positions as appropriate. 2.A Multi-Summary Supplier ships multiple times per day. - The supplier will need to coordinate their packing requirements with each individual plant. 3.In the above example, the two small lot containers do not need a Delivery Batch Label because they form a full container of the same part. 4.In this example, the supplier has a small lot order for the same part because this supplier is unaffected by the difference in vehicle type of the entire lot size of 30. 5. It is possible to receive a batch and lot number without a sequence number. When this occurs sequence within the container is not critical.
September 2007
21 - 35
862 Example 5: Sequence Supplier

Due Date 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 Pack Qty 30 30 30 30 30 30 Order Qty 30 30 30 30 30 30 Cont Type EC EC EC EC EC EC
Seq.
000001 000001 000002 000002 000003 000003
Lot
020412040050 020412040050 020412040060 020412040060 020412040070 020412040070
Batch
411145 411145 411146 411146 412005 412005
Part
71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P 71120SHJ A010M1 YR545M 74890SHJ A010M1 YR545M
D/C
10M103 13M103 10M103 13M103 10M103 13M103
Order
705086 705086 705086 705086 705086 705086
Example of Supplier Pick list/Shipping Summary For Requirements due on 11/30 at 9:00
Seq. 000001 000001 000002 000002 000003 000003 Lot 020412040050 020412040050 020412040060 020412040060 020412040070 020412040070 Batch 411145 411145 411146 411146 412005 412005 Part 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P 71120SHJ A010M1 NH662P 74890SHJ A010M1 NH662P 71120SHJ A010M1 YR545M 74890SHJ A010M1 YR545M D/C 10M103 13M103 10M103 13M103 10M103 13M103 Order 705086 705086 705086 705086 705086 705086 Pack Qty 30 30 30 30 30 30 Rqd. Qty 30 30 30 30 30 30 Cont. Count 1 1 1 1 1 1 Remarks Full Container Full Container Full Container Full Container Full Container Full Container
Notes:
ETC.
1. This example represents how Honda would want the requirements packed for a Sequence Supplier with out small lots requirements. The supplier needs to sequence the containers on the trailer. 2. The container size is equal to the ordering lot and batch size of 30; therefore, there is only one container per requirement.
21- 36
September 2007
862 Example 6: Sequence Supplier (Bulk) with Small Lots

Due Date 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 11/30 9:00 Seq.
000001 000002 000003 000004 000005 000006
Lot
010411160200 010411160210 010411160220 010411160230 010411160240 010411160250
Batch
411261 411262 411262 411263 411264 411265
Part
61300SHJ A600 61300SHJ A000 61300SHJ A000 61300SHJ A000 61300SHJ A000 61300SHJ A000
D/C
01 02 01 02 01 02 01 02 01 02 01 02
Order
701615 701615 701615 701615 701615 701615
Pack Qty
10 10 10 10 10 10
Order Qty
30 21 9 30 30 30
Cont Type EC EC EC EC EC EC

Seq. 000001 000002 Lot 010411160200 010411160210 Batch 411261 411262 Part 61300SHJ A600 61300SHJ A000 D/C 01 02 01 02 Order 701615 701615 Pack Qty 10 10 Rqd. Qty 30 21 Cont. Count 3 2 Remarks Full Containers Two Full containers plus combine one with next req. Full Container combined with above Full Containers Full Containers Full Containers
000003 000004 000005 000006
010411160220 010411160230 010411160240 010411160250
411262 411263 411264 411265
61300SHJ A000 61300SHJ A000 61300SHJ A000 61300SHJ A000
01 02 01 02 01 02 01 02
701615 701615 701615 701615
10 10 10 10
9 30 30 30
1 3 3 3
Notes: 1. This example represents how Honda would want the requirements packed for a Sequence Supplier with Small Lot Requirements. The supplier needs to sequence the containers on the trailer. 2. The container size is less than the ordering lot and batch size of 30, therefore, there are more containers per requirement. 3. No Delivery Batch labels would be applied because all small lots round to even full pack quantities of the same part. 4. In this example, the supplier has a small lot order for the same part because this supplier is unaffected by the difference in vehicle type of the entire lot size of 30.
September 2007
21 - 37
Delivery Batch Control

The following section provides guidance and control for Delivery Batch Creation. While not every supplier and/or software provider accomplishes tasks in the same manner, this section is designed to provide a model for this process. The illustrations described herein are not intended to be the end-all for system integration. Software designers are encouraged to develop methods and controls that meet and adhere to the principles of these illustrations, but follow the guidelines in the Delivery Batch Requirements table.
DELIVERY BATCH REQUIREMENTS AREA Mis-Label Potential Batch Control Sequence Control Batch Staging Part Tracking REQUIREMENTS Reduce Mis-label potential by developing internal checks and controls. Scan Verification to Batch Requirement (reconciliation to requirements). Provide Control of Container Build by Line Sequence Number. Insuring correct parts are in the correct containers. Allow for building container batches prior to Staging (inventory area). Provide Tracking by Container Serial Numbers and Batch to tie back to original date/lot of manufacture. One Non-Serialized ID Label Identifying the batch container (see Chapter 10). The following information must be on the label: Delivery Batch 1st Lot Number in Line Sequence Order Batch Number with barcode Accurate Container Count at Item Level
Container Identification Container Type Count
Flow Charts
The following explanations and flowcharts (Figure 1 and 2) are intended to assist in understanding the end-to-end process for delivery batch control. The labeling flowchart illustrates the general order in which the container, delivery batch, pallet, and quick receive labels are generated and attached to the packaging items. The statements below provide some additional commentary to support the business flow presented in each diagram. While much of the process is unchanged from current practices, redundant and additional information should solidify the understanding of this process. Not all details provided are exact methods; individual processes will be determined by each software provider or supplier.
21- 38
September 2007
Proposed Labeling Flow (Figure 1)

1. 2. 3. Parts are manufactured by the supplier and a container label is applied (now or at future time). In this diagram, each container holds single parts of X and Y Containers may be warehoused in preparation for future delivery schedule builds. Upon receipt of the 862 Delivery Schedule, a Batch Pick and Load Sheet is created that identifies the quantities and lots that need to be packed into the same container(s). A batch requirement will typically be frozen for more than one week. This means that the batch number, part number, and quantity will not change. The sequence number from the 862 may changes (REF*JS), but the order in which the parts are packed will not. Caution: when assigning parts to containers within a batch, some order quantities indicated may need to be split between containers to accommodate a standard container quantity. The containers of items that need to be packed/batched are pulled from the warehouse to build the mixed container. It is assumed this is done in a Batch Area to allow suppliers to create batches in advance of delivery. Scanning to verify that the right part, quantity order is required. The scan should also insure that the proper container type is associated only once for each batch container. Generate and apply the Delivery Batch and Container labels to the mixed or partial containers. Note - The Delivery Batch Label will display the Honda Lot Number (REF*LT) of the lowest sequence number (REF*JS) within that container.
4.
5.
At Delivery Time, a Pick and Load sheet will be created to begin building pallets for all requirements for delivery. At a minimum, the list should contain the sequence number, batch number, part number, and quantity. The pallet contains standard packs of part X, Y, and Z (30 units each). The mixed batch container of X/Y/Z, created in step 4 above, should be pulled and placed on the pallet (also in sequence if applicable). Scan the container labels for the full containers and the delivery batch label to generate a mixed or master label. Note - In this example, a mixed label would be generated and applied to the pallet. It also assumes that the Delivery Batch label contains a barcoded unique serial number (optional) that links the container label serial numbers within this container. The item level detail would be passed to the ASN. Additional time is saved since the batch container was previously scanned in item 4 above.
6.
7. 8.
Next, scan the mixed label, then generate and apply a quick receive label. Generate the Master Packing List and load the trailer as required.
September 2007
21 - 39
Batch Control Process (Concept) Figure 2

The table at the bottom of the diagram is an example of the data that a supplier or software provider may maintain within their systems. This process ensures that the supplier can trace mixed container parts back to the original production container through the use of an internal Batch Serial Number and Reference Serial Number. This example is an extension to the previous flowchart by using the same delivery schedule information. 1. As in the previous process, this diagram shows, in summarized fashion, the containerization process. The difference is that this diagram shows the internal supplier delivery batch label and number concept. A bar code and text area will exist on the delivery batch label that is intended for supplier usage. In this concept, each delivery batch is given an internal batch serial number. This number will enable the supplier to trace the batch contents back to the original container serial numbers. This tie is shown in the table where the reference serial number represents the original part container number. The container type is indicated once for each container. For Batch Serial Number 5566, the container type of C1 is listed for the first part only (X), the remaining parts (Y/Z) will use the expendable identifier. Caution should be exercised when storing and comparing the sequence number (REF*JS). Notice that Batch Serial Number 5566 (Batch 12345) has sequence numbers of 1, 2, 3 for parts X, Y, and Z. However, in the Pick and Load sheet, Batch 12345 has sequence numbers of 4, 5, and 6. This is because the trailer would get loaded from the most current delivery schedule with the sequence that applies. Batch 12345 sequence numbers were applied when the batch container was first packed (days earlier). The general order of the contents within the container did not change in either circumstance.
2.
3.
21- 40
September 2007
September 2007 21 - 41
Proposed Labeling Flow

Example Only
Container Labels
1
X Y
Note: May palletize for storage
3 Batch Pick Sheet
Production Line Container Label Applied 5
Storage / Warehousing Store using Containers
Pick List
Batch 123456 X qty 10 lot 55
Mixed or Master Label

X Z
Pallet Staging
Pick & Load Sheet
X qty 30 Y qty 30
Container Labels and Delivery Batch Labels

X Y Z X
Y qty 10 lot 56 Z qty 10 lot 57
123456
Y 123456
X Y Z
Z qty 30
Batch: 123456
X qty 10 Y qty 10
4 Pick List
6 Z qty 10 Pallet Build Scan Container labels for non-Batch Scan Delivery Batch label and apply to small lot container Generate Mixed or Master label Apply Mixed or Master label to pallet
Batch Area 123 qty 60 Re-pack small lots before Load Staging 456 qty 90 Scan Small Lot Parts for Verification to 862 information (e.g. Batch and Sequence) Place Container labels on container as applicable Apply Delivery Batch label to container Store Small Lot batches as needed Provide Container Type to first container only Load Trailer Attach Master Packing list Send ASN when trailer departs

X Z
7
Y 123456 X Y Z
Generate Quick Receive Scan Mixed or Master label Generate Quick Receive label (with first lot number of batch if applicable) 8 Apply Quick Receive label Generate Master Packing List
21- 42 September 2007
Batch Control
Example Only
Supplier Batch Pick Sheet
Batch # 123456 Seq 1 Seq 2 Seq 3 Part X Part Y Part Z Qty 10 Qty 10 Qty 10
Scan Pre-Pkg Container Label for Tracking and Verification
Create Delivery Batch Label X Y

5566
Batch # 567890 Seq 4 Seq 5 Part Z Part Y Qty 15 Qty 15
Z Full Containers
Load Staging
Pick & Load Sheet
Seq 1 Seq 2 Seq 3 Part X Part Y Part Z Batch 123456 Seq 4 Seq 5 Seq 6 Part X Part Y Part Z Qty 10 Qty 10 Qty 10 Qty 30 Qty 30 Qty 30
Scan Requirements Parts scanned in sequence

Input part quantities placed in new container New Cont Labels
Note: By scanning Delivery Batch label supplier can carry data from table to ASN without scanning again each container serial number. LOT Batch # Qty Cont. Type Ref Serial #
Old Cont Labels
Batch Serial Number
Container Serial #
Part LSEQ
5566 5566 5566 6677 6677
1234567801234568 1234567801234569 1234567801234570 1234567801234590 1234567801234591
X Y Z Z Y
1 2 3 4 5
E19802029655 E19802029656 E19802029657 E19802109665 E19802109666
123456 123456 123456 567890 567890
10 10 10 15 15
C1 XX XX C1 XX
1234567800000001 1234567800000002 1234567800000003 1234567800000010 1234567800000011
Note: Sequence Order of Batch Container indicated by label serial number
Past Due Demand

1. Definitions: Honda will treat past due demand using two different methods: Immediate Demand: An item that was not completely shipped on a previous day may be included in the current days requirements using a new order number. Immediate demand may have been caused by an under-shipment the day before, an inventory adjustment, etc. Back-order: An item that was not completely shipped on a previous day may be included in the current days requirements using the same order number as the previous day. A backorder would be caused by an under-shipment.
2.
Usage:
Immediate Demand Back-order HAM AHM HCM HMA HPE HPG HSC HTM
DELTA
GPCS X X X X X X X
3.
How to identify:
Below are the key fields that signify whether an 862 (Ship Schedule) contains Immediate Demand or a Back-order.
Immediate Demand
Back-order
Summary/multi-summary style orders Time = 0001 (DELTA) DTM segment (position 090) Time = Assigned delivery window (GPCS) New order number. -The backorder will have the same order number as in previous transmissions. -The date will be the current date and the time will be 0001. *
Sequence style orders N/A
The backorder will have the same order number as in previous transmissions. The date will be the current date and the time will be 0001. *
* Note - The part number, date and time will be identical for multiple back-orders of the same part. (The order number will be different.)
September 2007
21 - 43

4. Key Concepts:
a) Immediate demand is one of three ways the PPMD / SPPC contact can deal with past due requirements. The other two methods would be to (1) move the requirements outside the frozen window, or (2) roll the requirements into the first bucket of the current days requirements. b) Immediate demand and backorders should be shipped on the next available truck. c) Honda maintains that all suppliers are responsible for shipping their requirements in full. Should a supplier need to short or delay shipment to Honda, they should inform their Honda Buyer of the circumstances. The supplier is then responsible for any parts not shipped. Ordering Systems should have the functionality to maintain these back orders until the supplier takes action to resolve the issue. This may include completing the shipment, or manually deleting if instructed to do so by the Honda Buyer. d) Hybrid Suppliers and Software Providers should take care not to drop requirements when material is not shipped between a previous 862 and its replacement. If a ship schedule is missed because of a plant shutdown, or a supplier does not ship on time for a late evening shipment, the new ship schedule may not show the previous days requirements. Therefore, systems should insure that they compare the DTM of the most recent schedule to that of the currently received schedule to insure requirements were not missed. Comparisons to ship history and the opportunity to manually delete should be among the options for the supplier. e) Contact the Honda Buyer/Planner for further clarification if needed.
21- 44
September 2007
Ship Schedule Number Style

1. Definitions a. Non-discrete ship schedule number: An order number that changes with each MRP regeneration (typically on a daily basis). The order number has no relationship to the previous number. b. Discrete ship schedule number: An order number that remains constant as long as order quantities remain open. 2. Usage:
HAM AHM HCM HMA HPE HPG HSC HTM
Non-Discrete Ship Schedule Number DELTA
Discrete Ship Schedule Number GPCS X X X X X X X
3.
How to Identify:
The mailbox senders address or ordering plant information can be used to distinguish ordering plants, and thus Ship Schedule number styles. For example, to distinguish ship schedule number style by ordering plant: a. If LIN 08/09 is present, a non-discreet ship schedule number will be used. b. If LIN 08/09 is not present, a discreet ship schedule number will be used.
4.
Key concepts:
a. The discrete ordering method supports multiple back-orders. If this occurs, there would be multiple occurrences of the same part number, date and time, with a different order number. b. The order number (discrete or variable) will be transmitted in the FST09 element of the 862. c. The order number (discrete or variable) must be returned in the ASN, position LIN09. d. The order number (discrete or variable) must follow the reconciliation logic listed in the 856 and 862 chapters.
September 2007
21 - 45
Chapter 22 Text Message

Text Message (864)
September 2007
22 - 1
Chapter 22 Text Message (864)
Chapter Contents
This chapter contains information and procedures for using the Honda Text Message transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 3 Transcation Covered........................................................................................................................... 3 Application Standards and Conventions............................................................................................. 3 Mapping .............................................................................................................................................. 3 Exceptions/Clarifications..................................................................................................................... 3 Schedule ............................................................................................................................................. 3 Specifications ...................................................................................................................................... 3 Back-Up Procedure............................................................................................................................. 3 Business Purpose ................................................................................................................................ 4 Transaction Specification Information ............................................................................................... 5 Transaction Specifications.................................................................................................................. 6 Functional Group ID = TX ................................................................................................................... 6 ST Transaction Set Header ................................................................................................................ 7 BMG Beginning Segment For Text Message ..................................................................................... 7 DTM Create Date ................................................................................................................................ 8 N1 Honda Plant Location .................................................................................................................... 9 N2 Honda Corporate Name .............................................................................................................. 10 PER Honda Contact.......................................................................................................................... 10 MIT Message Indentification ............................................................................................................. 11 N1 Supplier Name............................................................................................................................. 11 PER Supplier Contact ....................................................................................................................... 12 MSG Message Text .......................................................................................................................... 12 SE Transaction Set Trailer................................................................................................................ 13
22 - 2
September 2007
Transcation Covered
Text Message (Transaction 864) abbreviated TX.

Mapping
A list of the Text Message business data elements and how they will be transmitted via EDI Standards is provided in the Transaction Specifications section.
Schedule
The Text Message will be transmitted on an as-needed basis, whenever the appropriate Honda Associate needs to add comments or directions to the Weekly Release (ANSI 830), Inventory Advice (ANSI 846), Purchase Order (ANSI 850), or Ship Schedule (ANSI 862).
Specifications
It is possible for Honda to transmit multiple Text Messages within one envelope. This means that there may be multiple transaction sets (STSE header/trailer segments) within one interchange envelope (ISAIEA header/trailer segments).
Honda transmits all EDI data in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
Back-Up Procedure
September 2007
22 - 3
Business Purpose
The Honda Text Message (ANSI 864) is used to electronically move messages, explanations, and one-time communications in support of other defined ANSI transaction sets. Unlike other EDI transactions, the Text Message provides electronic messages for people, not for computer processing. Honda uses the Text Message to support the following EDI documents:
Weekly Release (ANSI 830) Honda Outbound Inventory Advice (ANSI 846) Purchase Order (ANSI 850) Ship Schedule (ANSI 862)
The text message may reference an EDI transaction, a part number, or the given supplier. Honda may also use the Text Message to communicate general, one-time only information, including, but not limited to production plan changes, production calendars, and scheduled overtime. HDM does not use the 864. FREQUENCY: As applicable TRANSMITTED FROM: Honda TRANSMITTED TO: OEM Suppliers
DSPS Suppliers Service Parts Suppliers
22 - 4
September 2007

The following Transaction Specifications consist of two sections:
1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality. Note - The Req. Des. for the first segment in a loop is also used for that corresponding loop. 2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column: M = Mandatory X = Conditional O = Optional The second column: ID = Identifier (a unique value from a predefined list from ANSI) DT = Date TM = Time AN = Alphanumeric R = Numeric with a variable decimal place Nx = Numeric with x decimal places The third column: x/y, where x = the minimum number of digits for this element and y = the maximum number of digits for this element.
September 2007
22 - 5
Functional Group ID =
Heading:
Pos. No. Seg. ID Name Req. Des. Max.Use Loop Repeat
TX
M M M M M M 1 1 1 1 1 1 1
Must Use 010 Must Use 020 Must Use 030 Must Use 040 Must Use 050 Must Use 090
ST BMG DTM N1 N2 PER
Transaction Set Header Beginning Segment For Text Message Create Date LOOP ID - N1 Honda Plant Location Honda Corporate Name Honda Contact
Detail:
Pos. No. Seg. ID MIT Name LOOP ID - MIT Message Identification LOOP ID - N1 Req. Des. M Max.Use 1 1 M M M 1 1 100000 Loop Repeat 1
Must Use
010
Must Use Must Use 070 Must Use 080
020
N1 PER MSG
Supplier Name Supplier Contact Message Text
Summary:
Pos. No. 010 Seg. ID SE Name Transaction Set Trailer Req. Des. M Max.Use 1 Loop Repeat
Must Use
22 - 6
September 2007


Ref. Des. ST01 Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes are listed below 864 Text Message 329 Transaction Set Control Number M AN 4/9 This number will be unique (within a transaction set) and ascending. It will not be sequential.
Must Use
Must Use
ST02
BMG Beginning Segment For Text Message


Must Use Ref. Des. BMG01 Data Element Name 353 Transaction Set Purpose Code Valid codes are listed below: 05 Replace 640 Transaction Type Code Valid codes are listed below: 03 Report Message Attributes M ID 2/2
Must Use
BMG03
ID 2/2
September 2007
22 - 7
DTM Create Date


Must Use Ref. Des. DTM01 Data Element Name 374 Date/Time Qualifier Valid codes are listed below 097 Transaction Creation 373 Create Date Date expressed as CCYYMMDD 337 Create Time Time expressed in 24-hour clock time as HHMM Attributes M ID 3/3
Must Use Must Use
DTM02 DTM03
M M
DT 8/8 TM 4/4
22 - 8
September 2007
N1 Honda Plant Location


Must Use Data Element Name 98 Entity Identifier Code Valid codes are listed below 16 Plant 93 Honda Plant Name 66 Honda Plant ID Qualifier Valid codes are listed below 98 Purchasing Office 67 Honda Plant ID This is the Honda code number for each logistical company. For example: (May not be an all-inclusive list.) 200 = 210 = 220 = 230 = 240 = 260 = 300 = AHM = HCM = HDM = HMA = HMI = HPE = HPG = HSC = HTM = Attributes M ID 2/2
Must Use Must Use
N102 N103
M M
AN 1/35 ID
Must Use
N104
AN 3/3
September 2007
22 - 9


Must Use Data Element Name Attributes 93 Corporation Name M AN 1/35 The corporate name for the Honda facility issuing this document. For example: (May not be an all-inclusive list.) "Honda of America Mfg., Inc." "Honda Manufacturing of Alabama, LLC" "Honda of Canada Mfg." Honda de Mexico, S.A. de C.V. "American Honda Motor Co., Inc." "Honda Power Equipment" "Honda of South Carolina" Honda Power Train Georgia "Honda Transmission"
PER Honda Contact

Position: Loop: Level: Usage: Max Use: Ref. Des. PER01 090 N1 Mandatory Heading Mandatory 1

Must Use Data Element Name 366 Contact Code Valid codes are listed below BD Buyer Name or Department 93 Honda Planner Name 365 Communication Number Qualifier Valid codes are listed below TE Telephone 364 Phone Number 365 Communication Number Qualifier Valid codes are listed below FX Facsimile 364 Fax Number Attributes M ID 2/2
Must Use Must Use
PER02 PER03
M M
AN 1/35 ID 2/2
Must Use Must Use
PER04 PER05
M M
AN 1/15 ID 2/2
Must Use
PER06
AN 1/15
22 - 10
September 2007
MIT Message Indentification

Position: Loop: Level: Usage: Max Use: 010 MIT Mandatory Detail Mandatory 1

Must Use Ref. Des. MIT01 Data Element Name Attributes 127 Honda Document ID Number M AN 1/14 - This number is assigned by Honda and is used to link this text message to another Honda transaction set to which these comments apply. - This value will be unique for a given logistical company. - The potential linked Honda Documents and their related ID Number locations are: 830 - BFR02 846 Outbound from Honda - PER04 850 - BEG03 862 - BSS02 931 Page Width Page width will be set to 80 M N0 1/3
Must Use
MIT03
N1 Supplier Name

Must Use Ref. Des. N101 Data Element Name 98 Entity Identifier Code Valid codes are listed below SU Supplier/Manufacturer 93 Supplier Name 66 Supplier Number Qualifier Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Supplier Number Attributes M ID 2/2
Must Use Must Use
N102 N103
M M
AN 1/35 ID 1/2
Must Use
N104
AN 8/8
September 2007
22 - 11

Position: Loop: Level: Usage: Max Use: Ref. Des. PER01 070 N1 Mandatory Detail Mandatory 1

Must Use Data Element Name 366 Contact Function Code Valid codes are listed below SU Supplier Contact 93 Supplier Contact Name Attributes M ID 2/2
Must Use
PER02
AN 1/30
MSG Message Text

Position: Loop: Level: Usage: Max Use: Ref. Des. Must Use MSG01 Must Use MSG02 080 MIT Mandatory Detail Mandatory 100000

Data Element Name Attributes 933 Free-Form Message Text M AN 1/80 934 Printer Carriage Control Code M ID 2/2 Valid codes are listed below DS Advance two lines before print NP Advance to next page before print SS Advance to new line before print Note: Printer carriage control should be performed BEFORE printing the associated message text.
22 - 12
September 2007


Must Use
Must Use
Ref. Des. SE01 SE02
Data Element Name 96 Number of Included Segments 329 Transaction Set Control Number
September 2007
22 - 13
Chapter 23 Functional Acknowledgement (997)

Functional Acknowledgement (997)
February 2007
23 - 1
Chapter Contents
This chapter contains detailed information concerning the Functional Acknowledgement transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 3 Transaction Covered........................................................................................................................... 3 Application Standards and Conventions............................................................................................. 3 Mapping .............................................................................................................................................. 3 Exceptions/Clarifications..................................................................................................................... 3 Schedule ............................................................................................................................................. 3 Specifications ...................................................................................................................................... 3 Back-Up Procedure............................................................................................................................. 4 Business Purpose ................................................................................................................................ 5 Transaction Specification Information ............................................................................................... 6 Transaction Specifications.................................................................................................................. 7 Functional Group ID = FA ................................................................................................................... 7 ST Transaction Set Header ................................................................................................................ 7 AK1 Functional Group Response Header .......................................................................................... 8 AK2 Transaction Set Response Header............................................................................................. 8 AK3 Data Segment Note..................................................................................................................... 9 AK4 Data Element Note.................................................................................................................... 10 AK5 Transaction Set Responder Trailer ........................................................................................... 10 AK9 Functional Group Response Trailer .......................................................................................... 11 SE Transaction Set Trailer................................................................................................................ 11
23 - 2
February 2007
Transaction Covered
Functional Acknowledgment (Transaction Set 997), abbreviated FA.

Mapping
A list of the Functional Acknowledgment business data elements and how they are transmitted via EDI Standards is provided in the Transaction Specifications.
Schedule
Honda will generate the Functional Acknowledgment in response to incoming transaction sets generally within 5 minutes of the receipt of the respective transmissions. Under normal business conditions, Honda expects all suppliers to respond to incoming documents by submitting a Functional Acknowledgement immediately following and in response to each EDI transmission received.
Specifications
Honda requires a 997 for every outbound transaction (ST-SE header/trailer segments) within one interchange envelope (ISA-IEA header/trailer segments). It is possible for Honda to transmit multiple Functional Acknowledgments within one envelope. This means that there may be multiple transaction sets (ST-SE header/trailer segments) within one interchange envelope (IS-IEA header/trailer segments). Honda expects all EDI data (inbound and outbound) to be in a wrapped format. A wrapped format does not contain a linefeed (new line) at the end of each segment.
February 2007
23 - 3
Back-Up Procedure
In the event of a failure of Electronic Data Interchange it is the responsibility of the sending party to transmit the contents of any pending Transmission to the receiving party using a method of non-EDI Transmission which is timely, reasonable, and appropriate under the circumstances.
23 - 4
February 2007
Business Purpose
The Functional Acknowledgment (ANSI 997) transaction set is a standard communications handshake verification. It confirms successful communication has occurred between the EDI translators of each pair of trading partners. Honda requires a Functional Acknowledgment in response to all outbound transmissions and provides it in response to all incoming transmissions. The specifications in this chapter are for both the outbound and incoming transmissions. FREQUENCY: Immediately following and in response to each EDI transmission received. TRANSMITTED FROM: Each trading partner as mutually defined TRANSMITTED TO: Each trading partner as mutually defined
February 2007
23 - 5

The following Standard Specifications consist of two sections: 1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality. Note - The Req. Des. for the first segment in a loop is also used for that corresponding loop. 2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column: M = Mandatory X = Conditional O = Optional The second column: ID = Identifier (a unique value from a predefined list from ANSI) DT = Date TM = Time AN = Alphanumeric R = Numeric with a variable decimal place Nx = Numeric with x decimal places The third column: x/y, where x = the minimum number of digits for this element and y = the maximum number of digits for this element.
23 - 6
February 2007
Functional Group ID =
FA
Introduction: The following specifications are for Honda Inbound and Honda Outbound Functional Acknowledgments. These specifications also cover STAR transactions.
Pos. No. 010 020 Seg. ID ST AK1 Req. Des. M M Loop Repeat
Must Use Must Use
Name Transaction Set Header Functional Group Response Header LOOP ID - AK2
Max.Use 1 1
999999 M 1 999999 O O M M M 1 99 1 1 1
Must Use
030
AK2
Transaction Set Response Header LOOP ID - AK3
040 050 Must Use Must Use Must Use 060 070 080
AK3 AK4 AK5 AK9 SE
Data Segment Note Data Element Note Transaction Set Response Trailer Functional Group Response Trailer Transaction Set Trailer

Position: Loop: Level: Usage: Max Use: 010 Mandatory 1

Must Use Must Use Ref. Des. ST01 ST02 Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 329 Transaction Set Control Number M AN 4/9 - For inbound to Honda, this number may not be repeated within an 18 month period. - For outbound from Honda, this number will not be repeated within a calendar year.
February 2007
23 - 7
AK1 Functional Group Response Header


Must Use Ref. Des. AK101 Data Element Name 479 Transaction Group Type Being Acknowledged For example: "AG" = Application Advice (824) "IB" = Inventory Advice (846) "PO" = Purchase Order (850) "PS" = Weekly Release (830) "RA" = Remittance Advice (820) "RC" = Receiving Advice (861) "SC" = Price Sales Catalog (832) "SH"= Advance Ship Notice (856) "SS" = Ship Schedule (862) "TX" = Text Message (864) 28 Group Control Number From GS06 from the corresponding transaction. Attributes M ID 2/2
Must Use
AK102
N0 1/9
AK2 Transaction Set Response Header

Position: Loop: Level: Usage: Max Use: 030 AK2 Mandatory Mandatory 1

Must Use Must Use Ref. Des. AK201 AK202 Data Element Name 143 Transaction Set Type Being Acknowledged For example: 830, 850, 862 329 Transaction Set Control Number From ST02 from the corresponding transaction. Attributes M ID 3/3 M AN 4/9
23 - 8
February 2007
AK3 Data Segment Note

Position: Loop: Level: Usage: Max Use: 040 AK3 Optional 1 Optional

Must Use Must Use Ref. Des. AK301 AK302 Data Element Name Attributes 721 Segment ID Code M ID 2/3 Code defining the segment ID of the data segment in error. 719 Segment Position in Transaction Set M N0 1/6 The numerical count position of this data segment from the start of the transaction set: the ST segment is count position 1. 447 Loop Identifier Code O AN 1/6 The loop ID number given on the transaction set diagram is the value for this data element in segments LS and LE. 720 Segment Syntax Error Code O ID 1/3 Valid codes are listed below 1 Unrecognized segment ID 2 Unexpected segment 3 Mandatory segment missing 4 Loop Occurs Over Maximum Times 5 Segment Exceeds Maximum Use 6 Segment Not in Defined Transaction Set 7 Segment Not in Proper Sequence 8 Segment Has Data Element Errors
AK303
AK304
February 2007
23 - 9
AK4 Data Element Note

Position: Loop: Level: Usage: Max Use: 050 AK3 Optional 99 Optional

Must Use Must Use Ref. Des. AK401 C03001 C03002 AK402 AK403 Data Element C030 722 1528 725 723 Name Attributes Position in Segment M Element Position in Segment M N0 1/2 Component Data Element Position in Composite O N0 1/2 Data Element Reference Number O N0 1/4 Data Element Syntax Error Code M ID 1/3 Valid codes are listed below 1 Mandatory data element missing 2 Conditional required data element missing. 3 Too many data elements. 4 Data element too short. 5 Data element too long. 6 Invalid character in data element. 7 Invalid code value. 8 Invalid Date 9 Invalid Time 10 Exclusion Condition Violated Copy of Bad Data Element O AN 1/99 This data element will not be provided if it contains invalid characters, etc.
Must Use
AK404
724
AK5 Transaction Set Responder Trailer

Position: Loop: Level: Usage: Max Use: 060 AK2 Mandatory Mandatory 1

Must Use Ref. Des. AK501 Data Element Name 717 Transaction Set Acknowledgment Code Valid codes are listed below A Accepted E Accepted But Errors Were Noted R Rejected Attributes M ID 1/1
23 - 10
February 2007
AK9 Functional Group Response Trailer


Must Use Ref. Des. AK901 Data Element Name Attributes 715 Functional Group Acknowledge Code M ID 1/1 Valid codes are listed below A Accepted E Accepted, But Errors Were Noted. P Partially Accepted, At Least One Transaction Set Was Rejected R Rejected 97 Number of Transaction Sets Included M N0 1/6 123 Number of Received Transaction Sets M N0 1/6 2 Number of Accepted Transaction Sets M N0 1/6
AK902 AK903 AK904


Must Use Must Use Ref. Des. SE01 SE02 Data Element Name 96 Number of Included Segments, Including ST and SE 329 Transaction Set Control Number Attributes M N0 1/10 M AN 4/9
February 2007
23 - 11
Chapter 24 Interchange Control Structures (ICS)

Interchange Control Structures (ICS)
April 2008
24 - 1
Chapter Contents
This chapter contains detailed information concerning the Interchange Control Structures. Specifications are included for further clarification.
Table of Contents
Standard Description ........................................................................................................................... 3 Standard Covered ............................................................................................................................... 3 Application Standards and Conventions............................................................................................. 3 Mapping .............................................................................................................................................. 3 Exceptions/Clarifications..................................................................................................................... 3 Schedule ............................................................................................................................................. 3 Specifications ...................................................................................................................................... 3 Back-Up Procedure............................................................................................................................. 3 Business Purpose ................................................................................................................................ 4 Standard Specification Information.................................................................................................... 5 Standard Specifications....................................................................................................................... 6 Functional Group ID............................................................................................................................ 6 ISA Interchange Control Header......................................................................................................... 6 GS Functional Group Header ............................................................................................................. 8 GE Functional Group Trailer ............................................................................................................... 9 IEA Interchange Control Trailer .......................................................................................................... 9 Operating Procedures ........................................................................................................................ 10 Introduction ....................................................................................................................................... 10 Outbound to Supplier ........................................................................................................................ 10 Inbound to Honda ............................................................................................................................. 10
24 - 2
April 2008
Standard Description
Standard Covered
Interchange Control Structures, abbreviated ICS.

Interchange Control Structures are based upon the ANSI ASC X12 Interchange Control Version Number 004010.
Mapping
A list of the Interchange Control Structures business data elements and how they are transmitted via EDI Standards is provided in the Standard Specifications.
There are no Exceptions to ANSI Standards in this Standard Description.
Schedule
N/A
Specifications
N/A
Back-Up Procedure
N/A
April 2008
24 - 3
Business Purpose
The Interchange Control Structures are designed to satisfy the basic requirements for enveloping and routing of electronic business data. FREQUENCY: N/A TRANSMITTED TO: N/A TRANSMITTED FROM: N/A
24 - 4
April 2008
Standard Specification Information

The following Standard Specifications consist of two sections: 1. The first section is an overview of the transaction. It includes segment information as well as a visual depiction of the looping functionality. Note - The Req. Des. for the first segment in a loop is also used for that corresponding loop. 2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column:

The second column:
April 2008
24 - 5
Standard Specifications
Functional Group ID
The following ICS specifications are valid for: - 004010 (Inbound & Outbound) Pos. No. Must Use 010 Must Use 020 Must Use 030 Must Use 040 Seg. ID ISA GS GE IEA Req. Des. Max.Use 1 M M M M 1 1 1 Loop Repeat
Name Interchange Control Header Functional Group Header Functional Group Trailer Interchange Control Trailer
ISA Interchange Control Header

Position: Loop: Level: Usage: Max Use: Ref. Des. ISA01 010 Mandatory 1

Must Use Data Element Name Attributes I01 Authorization Information Qualifier M ID 2/2 Valid codes listed below: 00 No Authorization Information Present (No Meaningful Information in I02) I02 Authorization Information M AN 10/10 Honda does not use this field. 10 empty spaces (or zeros) must be entered here as the ISA segment is space sensitive. Security Information Qualifier M ID 2/2 Valid codes listed below: 00 No Security Information Present (No Meaningful Information in I04) Security Information M AN 10/10 Honda does not use this field. 10 empty spaces (or zeros) must be entered here as the ISA segment is space sensitive. Interchange ID Qualifier M ID 2/2 Valid codes listed below: 01 Duns (Dun & Bradstreet) - Was used in conjunction with VAN interconnects and VAN carbon copy set ups. Honda must give approval prior to use of this code. ZZ Mutually Defined - The standard qualifier for Honda.
Must Use
ISA02
Must Use
ISA03
I03
Must Use
ISA04
I04
Must Use
ISA05
I05
24 - 6
April 2008
Must Use
ISA06
I06
Interchange Sender ID M AN 15/15 - This is the senders mailbox ID. The value for this field will be agreed upon by Honda and each supplier. - Refer to the Software Information chapter in the EDI & Bar Code Label Implementation Requirements manual for Honda's mailbox ID's. - Honda must approve all supplier sender IDs prior to exchanging data. Interchange ID Qualifier M ID 2/2 Valid codes listed below: 01 Duns (Dun & Bradstreet) - Was used in conjunction with VAN interconnects and VAN carbon copy set ups. Honda must give approval prior to use of this code. ZZ Mutually Defined - The standard qualifier for Honda. Interchange Receiver ID M AN 15/15 - This is the receivers mailbox ID The value for this field will be agreed upon by Honda and each supplier. - Refer to the Software Information chapter in the EDI & Bar Code Label Implementation Requirements manual for Honda's mailbox ID's. - Honda must approve all supplier receiver IDs prior to exchanging data Interchange Date Date expressed as YYMMDD Interchange Time Time expressed in 24-hour clock time as HHMM M M DT 6/6 TM 4/4
Must Use
ISA07
I05
Must Use
ISA08
I07
ISA09 ISA10 ISA11
I08 I09 I10
Interchange Control Standards Identifier M ID 1/1 Valid codes listed below: U U.S. EDI Community of ASC X12, TDCC, and UCS Interchange Control Version Number Valid codes listed below: 00400 Standard Issued as ANSI X12.5-1997 Interchange Control Number A control number assigned by the interchange sender Acknowledgment Requested Valid codes listed below: 0 No Acknowledgment Requested M ID 5/5
Must Use
ISA12
I11
Must Use Must Use
ISA13 ISA14
I12 I13
M M
N0 9/9 ID 1/1
Must Use
ISA15
I14
Usage Indicator M ID 1/1 Valid codes listed below: P Production Data T Test Data - Test data must be sent to the test mailboxes as listed in Chapter 5. Component Element Separator M AN 1/1 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. Reference Chapter 4 for further delimiter information.
Must Use
ISA16
I15
April 2008
24 - 7
GS Functional Group Header

Position: Loop: Level: Usage: Max Use: Ref. Des. GS01 020 Mandatory 1

Must Use Data Element Name Attributes 479 Functional Identifier Code M ID 2/2 Valid codes listed below: AG Application Advice (824) FA Functional Acknowledgment (997) IB Inventory Inquiry/Advice (846) IN Invoice Information (810,819) - Honda only uses the 810 PO Purchase Order (850) PS Planning Schedule with Release Capability (830) RA Payment Order/Remittance Advice (820) RC Receiving Advice/Acceptance Certificate (861) SC Price/Sales Catalog (832) SH Ship Notice/Manifest (856) SS Shipping Schedule (862) TX Text Message (864) 142 Application Sender's Code M AN 2/15 The senders code should be the DUNS number of the senders company. Honda's DUNS numbers are listed in Chapter 5. If your company does not have a DUNS number, contact Honda. 124 Application Receiver's Code M AN 2/15 The receivers code should be the DUNS number of the receiving company. Honda's DUNS numbers are listed in Chapter 5. If your company does not have a DUNS number, contact Honda. 373 Date M DT 8/8 Date expressed as CCYYMMDD 337 Time M TM 4/4 Time expressed in 24-hour clock time as HHMM 28 Group Control Number M N0 1/9 Assigned number originated and maintained by the sender 455 Responsible Agency Code M ID 1/2 Code used in conjunction with Data Element GS08 to identify the issuer of the standard. Valid codes listed below: X Accredited Standards Committee X12 480 Version / Release / Industry Identifier Code M AN 1/12 This code indicates the version, release and subrelease of the EDI standard being used, including the GS and GE segments. Positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version. Valid codes listed below: 004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Must Use
GS02
Must Use
GS03
GS04 GS05 GS06 GS07
Must Use
GS08
24 - 8
April 2008
GE Functional Group Trailer

Position: Loop: Level: Usage: Max Use: Ref. Des. GE01 030 Mandatory 1

Must Use Data Element Name Attributes 97 Number of Transaction Sets Included M N0 1/6 Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element 28 Group Control Number M N0 1/9 Assigned number originated and maintained by the sender
Must Use
GE02
IEA Interchange Control Trailer

Position: Loop: Level: Usage: Max Use: Ref. Des. IEA01 IEA02 040 Mandatory 1

Must Use Must Use Data Element Name Attributes I16 Number of Included Functional Groups M N0 1/5 A count of the number of functional groups included in an interchange I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender
April 2008
24 - 9
Introduction
In order for Honda to successfully receive data from a supplier the ICS must be correct. The supplier needs to ensure that their ISA and GS information is populated correctly when they are sending data to Honda. The diagram below provides an example of how the Outbound and Inbound data should be configured to ensure successful communication between Honda and the supplier.
Outbound to Supplier
SUPPLIER Receivers EDI Mailbox
ISA*00* *00* *ZZ*HOAM HXMFG*ZZ*ABCD ABCD001*020421*1148*U*00400*106*0*P*^~

Senders EDI Mailbox HONDA
GS*PO*092162643*123456789*20020421*1148*106*X*004010~
Senders DUNS HONDA Receivers DUNS SUPPLIER
Inbound to Honda
HONDA Receivers EDI Mailbox
ISA*00* *00* *ZZ*ABCD ABCD001*ZZ*HOAM HXMFG*020421*1148*U*00400*106*0*P*^~

Senders EDI Mailbox SUPPLIER
GS*PO*123456789*092162643*20020420*1148*1006*X*004010~
Senders DUNS SUPPLIER Receivers DUNS HONDA
NOTE The Honda EDI Mailbox and DUNS values must align with the Honda plant that the supplier is communicating with. Please refer to Chapter 5 for a complete list of Hondas information.
24 - 10
April 2008
Chapter 25 Bar Code Labeling (STAR)

Bar Code Labeling (STAR)
February 2007
25 - 1
Chapter Contents
This chapter contains information concerning specific STAR bar code labels, their primary function, and an example of each.
Table of Contents
Honda Label Specifications................................................................................................................. 3 Overview ............................................................................................................................................. 3 Honda Bar Code Label Standards ...................................................................................................... 3 Honda Customizations to the Guidelines............................................................................................ 3 Color Stripes on Labels....................................................................................................................... 3 Label Stock ......................................................................................................................................... 3 Smart Labels ....................................................................................................................................... 4 Testing Requirements......................................................................................................................... 4 Bar Cod Label Specifications.............................................................................................................. 4 Star Container LabelStar Master LabelStar Mixed Label................................................................ 5 Star Master LabelStar Mixed Label................................................................................................. 6 Star Mixed Label ............................................................................................................................. 7
25 - 2
February 2007
Honda Label Specifications

Overview
This section provides the necessary information to design the Honda STAR Bar Code Labels.
Honda Bar Code Label Standards

All STAR Honda labels must adhere to the Automotive Industry Action Group (AIAG) B10 Guidelines (except for the customizations listed below). These guidelines may be purchased from the AIAG at:
Automotive Industry Action Group Suite 200 26200 Lasher Road Southfield, MI 48034 Phone: 248-358-3570 Email: http://www.aiag.org
Honda Customizations to the Guidelines

The following known customizations were made to the AIAG B-10 Guidelines: Honda requires the supplier name and address directly below the serial number on the container label. This was specified in the B-3 guidelines, but it is not specified in the B-10 guidelines. Color stripes on labels are not specified in the B-10 guidelines.
Color Stripes on Labels

Honda permits the use of a 3/8-inch pastel color stripe across the top of the label if it does not interfere with the bar code segment on the labels and is approved by Honda in advance.
Label Stock
Removable label stock is required for use on Honda modular containers. Refer to the Removable Label Specification section in chapter 8 for details.
February 2007
25 - 3
Smart Labels
The Smart Label concept is a term Honda uses to describe the use of a license plate on each level. The license plate is a serial number for that label. The license plate (serial number) uniquely identifies a label for traceability and links it to the other information on the label. This will allow scanning of only the serial number when creating a shipment, versus having to scan every field on a label. (This is why the label is referred to as a smart label).
Testing Requirements
Honda must approve all DELTA and STAR labels. See Chapter 8, Quality Assurance Program, for the bar code label approval requirements. The information in Chapter 8 might also prove useful when evaluating compliance with Honda specifications.
Bar Cod Label Specifications

Honda has specific label requirements on layout and data elements for the following labels: 1. 2. 3. Container Master Mixed
These specifications are shown on the following pages.
25 - 4
February 2007
Star Container Label
Part Number Block Title = PART NO. (P) Data = HAM part number and color (Source = 830 or 850) Text Height = 3 LPB Data Identifier (DI) = P Maximum Length: 19 Max Data Chars = 18 DI Chars = 1 Note 1: The human readable part number should contain hyphens where appropriate. (No hyphens should occur in the bar code.) Quantity Block Title = QUANTITY (Q) Data = Quantity shall match the quantity of parts inside the shipping container (Source = 830 or 850) Text Height = 3 LPB Data Identifier (DI) = Q Maximum Length: 8 Max Data Chars = 7 DI Chars = 1
SUPPLIER (V) MFG. DATE AUDITOR PART NO. (P)
NOTE: NOT TO SCALE For correct measurements see the AIAG B-10 Guidelines
Description Block Title = DESCRIPTION Data = Part Description as assigned by HAM (Source = 830 or 850) Text Height = 5 LPB Data Identifier (DI) = na Maximum Length: 40 Max Data Chars = 40 DI Chars = 0 Note 2: Description may wrap
STAR CONTAINER LABEL

32100-SM4-A000-Y18L
QUANTITY (Q)
60
DESCRIPTION
Harness Earth Ground
19163001
SERIAL (S)
Supplier Block Title = SUPPLIER (V) Data = Supplier number as assigned by Honda. (Source = 830 or 850) Text Height = 3 LPB Data Identifier (DI) = V Maximum Length: 9 Max Data Chars = 8 DI Chars = 1
001234567
ZONE
PLANT
Special Data Areas

Serial Number Block Title = SERIAL (S) Data = A unique serial number Text Height: Serial Number = 3 LPB (Source = Supplier) Supplier Name & Address = 6-8 LPB right justified (Source = Supplier) Data Identifier (DI) = S Maximum Length: 10 Max Data Chars = 9 DI Chars = 1
Block Title = See respective areas Data = May be adjusted to accommodate supplier specific information per Honda's approval (Source = Supplier) Text Height = 5 LPB Data Identifier (DI) = na
Customer Name: Label Purpose / Use : Identifies a part NOTE 1: Illustration is NOT actual size. Any Honda of America number in the container the label dimensions that are not otherwise specified on this page Mfg., Inc. is attached to. SHALL be in compliance with AIAG B-10, Version 01.00 5/95.
NOTE 2:
The narrow element of the "X" dimension shall be between .013 and .017 inch. The wide to narrow ratio shall be between 2.8 to 1 and 3.2 to 1.
25 - 6
Part Number Block Title = PART NO. (P) Data = HAM part number and color (Source = 830 or 850) Text Height = 3 LPB Data Identifier (DI) = P Maximum Length: 19 Max Data Chars = 18 DI Chars = 1 Note 1: The human readable part number should contain hyphens where appropriate. (No hyphens should occur in the bar code.) Quantity Block Title = QUANTITY (Q) Data = Quantity shall match the sum of the quantities of the containers on that pallet (Source = Supplier) Text Height = 3 LPB Data Identifier (DI) = Q Maximum Length: 8 Max Data Chars = 7 DI Chars = 1
SUPPLIER (V) MFG. DATE AUDITOR PART NO. (P)
Star Master Label
Description Block Title = DESCRIPTION Data = Part Description as assigned by HAM (Source = 830 or 850) Text Height = 5 LPB Data Identifier (DI) = na
STAR MASTER LABEL

32100-SM4-A000-Y18L
Maximum Length: 40 Max Data Chars = 40 DI Chars = 0 Note 2: Description may wrap Plant Block Title = PLANT Data = 3 digit ship to plant code (Source = 830 or 850) Text Height = 3 LPB Data Identifier (DI) = na
QUANTITY (Q)
240
DESCRIPTION
Harness Earth Ground
19163001
Maximum Length: 3 Max Data Chars = 3 DI Chars = 0

ZONE PLANT
SERIAL (4S)
Supplier Block Title = SUPPLIER (V) Data = Supplier number as assigned by Honda. (Source = 830 or 850) Text Height = 3 LPB Data Identifier (DI) = V Maximum Length: 9 Max Data Chars = 8 DI Chars = 1
001234568
ELP
Special Data Areas Block Title = See respective areas Data = May be adjusted to accommodate supplier specific information per Honda's approval (Source = Supplier) Text Height = 5 LPB Data Identifier (DI) = na
Serial Number Block Title = SERIAL (4S) Data = A unique serial number Text Height: Serial Number = 3 LPB (Source = Supplier) Supplier Name & Address = 6-8 LPB right justified (Source = Supplier) Data Identifier (DI) = 4S Maximum Length: 10 Max Data Chars = 9 DI Chars = 1
February 2007
Customer Name: Label Purpose / Use: Used to Honda of America identify a pallet containing only Mfg., Inc. one Part Number.
NOTE 1:
Illustration is NOT actual size. Any dimensions that are not otherwise specified on this page SHALL be in compliance with AIAG B-10, Version 01.00 5/95.
NOTE 2: The narrow element of the "X" dimension shall be between .013 and .017 inch. The wide to narrow ratio shall be between 2.8 to 1 and 3.2 to 1.
February 2007
Mixed Label Block Title = Mixed Load Data = The word "Mixed Load" will signify this is a Mixed Label Text Height = 1 LPB
SUPPLIER (V)
Star Mixed Label
STAR MIXED LABEL

Plant
Mixed Load
MFG. DATE AUDITOR
Block Title = PLANT Data = 3 digit ship to plant code (Source = 830 or 850) Text Height = 3 LPB Data Identifier (DI) = na
19163001
Maximum Length: 3 Max Data Chars = 3 DI Chars = 0
Supplier
SERIAL (5S)
001234569
ZONE
PLANT
Block Title = SUPPLIER (V) Data = Supplier number as assigned by Honda. (Source = 830 or 850) Text Height = 3 LPB Data Identifier (DI) = V Maximum Length: 9 Max Data Chars = 8 DI Chars = 1
ELP
Special Data Areas Block Title = See respective areas Data = May be adjusted to accommodate supplier specific information per Honda's approval (Source = Supplier) Text Height = 5 LPB Data Identifier (DI) = na
Serial Number Block Title = SERIAL (5S) Data = A unique serial number Text Height: Serial Number = 3 LPB (Source = Supplier) Supplier Name & Address = 6-8 LPB right justified (Source = Supplier) Data Identifier (DI) = 5S Maximum Length: 10 Max Data Chars = 9 DI Chars = 1
Customer Name: Label Purpose / Use: Used to Honda of America identify a pallet containing Mfg., Inc. multiple part numbers.
NOTE 1:
Illustration is NOT actual size. Any dimensions that are not otherwise specified on this page SHALL be in compliance with AIAG B-10, Version 01.00 5/95.
NOTE 2: The narrow element of the "X" dimension shall be between .013 and .017 inch. The wide to narrow ratio shall be between 2.8 to 1 and 3.2 to 1.
25 - 7
Chapter 26 Master Packing List (STAR)

Master Packing List (STAR)
February 2007
26 - 1
Chapter Contents
This chapter contains information concerning specific STAR Master Packing List (MPL). A detailed overview is given, along with the required data elements for using the MPL. Other pertinent information is given separately.
Table of Contents
Master Packing List Requirements..................................................................................................... 3 Purpose............................................................................................................................................... 3 Requirements...................................................................................................................................... 3 Optional Bar Code .............................................................................................................................. 4 Ozone-Depleting Substance ............................................................................................................... 4 Other ................................................................................................................................................... 4 Figure 26.1 Master Packing List Example.................................................................................... 5
26 - 2
February 2007
Master Packing List Requirements

Purpose
The purpose of the Master Packing List (MPL) is to identify the contents of a particular shipment to Honda. The primary source of the shipping information should be the ASN. Honda views the MPL as a summarized hard copy printout of the electronic ASN. The MPL will be heavily utilized by Honda and participating consolidation centers during the receipt of shipments. It is very important that all required information be present so the timely receipt of your shipment is not delayed.
Requirements
The Honda MPL requirements are as follows: 1. Plant Destination - The Plant Destination must be three characters. The threecharacter code represents the Honda plant to which the contents will be delivered. This information is provided in the Material Release as plant code. Supplier Name The Supplier Name must appear and match the name on the Material Release. Supplier Number The Supplier Number must appear and match the number on the Material Release. See Optional Bar Codes. Delivery Date The Delivery Date represents the date on which the parts are to arrive, not the date the parts were shipped. Material Release Each material release received from Honda has an eight-digit Material Release number assigned to it. This number is required on the MPL. Advance Ship Notice (ASN) Number The supplier assigns The ASN Number. The ASN number must be eight characters in length and is not to repeat itself for one year. See Optional Bar Codes. Bill of Lading Number The supplier provides the Bill of Lading Number. Trailer Number This is the actual number of the trailer delivering the parts, unless the parts are off-loaded onto a different trailer prior to arriving at Honda. If the parts are off-loaded, use the BOL number. Part Number Part Numbers, including color if applicable, are to be listed only once. Part Numbers must be in numerical order, sorting alpha characters before numeric characters. See Figure 26.1. Part Description The Part Description is to be listed for each part number and taken from the Material Release. Quantity The total delivery quantity is listed for each part number.
2. 3. 4. 5. 6.
7. 8.
9.
10. 11.
February 2007
26 - 3

12. KD Lot Number(s) If Honda transmits KD Lot Numbers on the Material Release, list the lot numbers applicable to the quantities on the MPL in numeric order, left to right. Modular (Returnable) Container Summary For any shipment containing Honda modular containers, the supplier must list a summary of each container type and its quantity for that shipment. This summary can be either at the bottom of the MPL or as separate page attached to the MPL.
13.
Optional Bar Code

Bar code the Supplier and ASN numbers only if: The MPL is printed on a thermal transfer or laser-type printer and the bar codes are printed directly onto the paper. Bar code symbology is to be 3 of 9 (Code 39). Bar code density/dimensions must meet the AIAG B-10 standards. Do not include the data identifiers. Note - Your company is exempt from bar coding the Supplier and ASN numbers on the MPL if your company does not have the capability necessary to meet both of these requests.
Ozone-Depleting Substance
The Ozone Depleting Substances (ODS) label should be affixed in the most costeffective method possible. Hardcoding in your system is not required if manual means are available. Manual means include: stamping using pre-printed label tying the label on after the MPL has been generated
Other
See Chapter 8, Bar Code/Master Packing List Quality Assurance Program, for details on Hondas testing requirements. The format on the following page is mandatory unless Honda gives a written exception allowance in advance. Packing list size shall be 8.5 x 11 or 11 x 15 computer paper unless Honda gives a written exception allowance in advance. Other data is not required but may appear per Hondas advance written approval. If an ASN has multiple material releases (for same ship-to location), separate MPLs are required for each Material Release. The MPL must be attached to the BOL and given to the driver, not put inside the trailer.
26 - 4
February 2007
1. PLANT DESTINATION: ELP 2. SUPPLIER NAME: 3. SUPPLIER NO: XYZ COMPANY 6. ASN NO.: 12345678
12345601
Optional Bar Code Space
Optional Bar Code Space 4. DELIVERY DATE: 10/15/99
7. BILL OF LADING NO.: 987654 8. TRAILER NO.: 245
5. HONDA MATERIAL RELEASE NO.: 22014501
9. P/N COLOR
10. DESCRIPTION
11. DELIVERY QUANTITY
53320-SH3-G000-M1 75270-SB3-000-B49L 76270-SH4-000 83501-SH4-0000-B49L 83551-SH4-A000-B49L 83551-SH4-A000-Y18L
Cover, Strg Joint Esctn, Reg Handle Garn L Door Mirro Pull Pocket R Door Pull Pocket L Door Pull Pocket L Door
360 480 240 120 360 240
12. KD LOT NUMBERS
1-9112-001-1, 1-9112-002-1, 1-9112-003-1 2-9112-010-1, 2-9112-011-1, 2-9112-012-1

13. MODULAR CONTAINER SUMMARY ____________________ TYPE QUANTITY
B C C2 D1 A1 AP
6 3 10 12 3 6
Figure 26.1 Master Packing List Example
February 2007
26 - 5
Chapter 27 Material Release (830) STAR

Material Release (830) STAR
February 2007
27 - 1
Chapter Contents
This chapter contains information and procedures for using the Honda STAR Material Release transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 3 Transaction Covered........................................................................................................................... 3 Application Standards and Conventions............................................................................................. 3 Mapping .............................................................................................................................................. 3 Exceptions/Clarifications..................................................................................................................... 3 Schedule ............................................................................................................................................. 3 Specifications ...................................................................................................................................... 3 Back Up Procedure............................................................................................................................. 4 Business Purpose ................................................................................................................................ 5 Transaction Specification Information................................................................................................. 6 Transaction Specifications.................................................................................................................. 7 Functional Group ID = PS ............................................................................................................... 7 ST Transaction Set Header............................................................................................................. 8 BFR Beginning Segment for Planning Schedule ............................................................................ 9 NTE Note/Special Instruction .......................................................................................................... 9 REF Reference Numbers .............................................................................................................. 10 N1 Supplier Name ......................................................................................................................... 10 N1 Ship To Name.......................................................................................................................... 11 N3 Ship To Address Information ................................................................................................... 11 N4 Ship To Geographic Location .................................................................................................. 11 DTM Requested Ship Date/Time/Period....................................................................................... 12 TD5 Carrier Details (Routing Sequence/Transit Time) ................................................................. 12 LIN Item Identification.................................................................................................................... 13 UIT Unit Detail ............................................................................................................................... 14 PO3 Additional Item Detail ............................................................................................................ 14 PID Product/Item Description ........................................................................................................ 15 PO4 Item Physical Details............................................................................................................. 15 REF Job Sequence Reference Numbers...................................................................................... 16 REF Zone Reference Numbers..................................................................................................... 16 SDP Ship/Delivery Pattern ............................................................................................................ 17 FST Forecast Schedule................................................................................................................. 17 CTT Transaction Totals................................................................................................................. 18 SE Transaction Set Trailer ............................................................................................................ 18
27 - 2
February 2007
Transaction Covered
Planning Schedule with Release Capability or a Material Release (Transaction Set 830), abbreviated PS.

Mapping
A list of the Material Release business data elements and how they are transmitted via EDI Standards is provided in the Transaction Specifications section.
The following items are not within ANSI compliance: Honda has included the NTE segment (special instructions) which is not in ANSI 4010. Two N1 loops were inserted (positions 085 & 087) in the inappropriate position, causing the DTM segment (position 130) to appear to be out of order.
Schedule
The Material Release generally will be transmitted on every Production day, by 12 noon Eastern Time. The seller will notify the buyer no later than 1:00 p.m. Eastern Time if the seller has not received the daily Material Release.
Specifications
In transmitting the Material Release, a User Message Class (MSGUCLS) of 830 must be present to transmit the data to the sellers mailbox. It is possible for Honda to transmit multiple Material Releases within one envelope. This means that there may be multiple transaction sets (ST-SE header/trailer segments) within one interchange envelope (ISA-IEA header/trailer segments). All transmissions from Honda are in a compressed format in order to reduce costs.
February 2007
27 - 3
Back Up Procedure
27 - 4
February 2007
Business Purpose
The STAR Material Release is authorization to ship the quantities specified in the transmission. The advantage of scheduling delivery via the STAR Material Release (versus the STAR Purchase Order) is that Material Releases are based upon actual production needs and allow Honda to more effectively maintain its inventory levels. The Material Release system also avoids sudden shipping schedule adjustments for suppliers (which occur when Honda issues revised Purchase Orders). Suppliers are provided a mutually agreed upon horizon of firm releases at all times. Honda will not change releases within a horizon period unless cases of production urgency arise. If your organization ships parts to other Honda suppliers, these part numbers will not appear on your STAR Material Releases. Shipment quantities to other Honda suppliers will appear on your monthly STAR Purchase Order instead. (The Purchase Order is your shipment authorization for these parts only). Production support requirements (special orders) will also be transmitted in the form of STAR Material Releases.
Frequency: Daily, by 12 noon Eastern Time Transmitted From: Honda Transmitted To: Domestic OEM Suppliers
February 2007
27 - 5

2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column:

The second column:
ID = Identifier (a unique value from a predefined list from ANSI) DT = Date TM = Time AN = Alphanumeric R = Numeric with a variable decimal place Nx = Numeric with a x decimal places
27 - 6
February 2007
Functional Group ID = PS
Heading:
Must Use Must Use Pos. No. 010 020 030 Must Use 050 Seg. ID ST BFR NTE REF Name Transaction Set Header Beginning Segment for Planning Schedule Note/Special Instruction Reference Numbers LOOP ID - N1 Must Use 085 N1 Supplier Name LOOP ID - N1 Must Use 087 088 089 Must Use 130 190 N1 N3 N4 DTM TD5 Ship To Name Ship To Address Information Ship To Geographic Location Requested Ship Date/Time/Period Carrier Details (Routing Sequence/Transit Time) M O O M O 1 1 1 1 1 M 1 1 Req. Des. M M F M Max.Use 1 1 4 1 1 Loop Repeat
Detail:
Pos. No. Must Use Must Use 010 020 060 080 120 140 145 Seg. ID LIN UIT PO3 PID PO4 REF REF Name LOOP ID - LIN Item Identification Unit Detail Additional Item Detail Product/Item Description Item Physical Details Job Sequence Reference Numbers Zone Reference Numbers LOOP ID - SDP Must Use Must Use 450 460 SDP FST Ship/Delivery Pattern Forecast Schedule M M 1 104 Req. Des. M M O O O O O Max.Use 1 1 1 1 1 1 1 104 Loop Repeat 10000
Summary:
February 2007
27 - 7


Must Use Ref. Des. ST01 Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes are listed below: 830 Planning Schedule with Release Capability 329 Transaction Set Control Number M AN 4/9 This number will be unique (within a transaction set) and ascending. It may be sequential.
Must Use
ST02
27 - 8
February 2007
BFR Beginning Segment for Planning Schedule


Must Use Ref. Des. BFR01 Data Element Name Attributes 353 Transaction Set Purpose Code M ID 2/2 00 Original 01 Cancellation 05 Replace 328 Material Release Number M AN 1/8 675 Schedule Type Qualifier M ID 2/2 Valid codes are listed below. SH Shipment Based This means the FST segment contains delivery dates. 676 Schedule Quantity Qualifier M ID 1/1 Valid codes are listed below A Actual Discrete Quantities 373 Horizon Start Date M DT 8/8 Date expressed as CCYYMMDD. 373 Horizon End Date M DT 8/8 Date expressed as CCYYMMDD. 373 Date Generated M DT 8/8 Date expressed as CCYYMMDD. 324 Purchase Order Number M AN 1/12 HAM's field max is 7. HCM's field max is 12.
Must Use Must Use
BFR03 BFR04
Must Use
BFR05
BFR06 BFR07 BFR08 BFR11
NTE Note/Special Instruction

Position: Loop: Level: Usage: Max Use: 030 Heading Floating 4

Must Use Ref. Des. NTE01 Data Element Name 363 Note Reference Code Valid codes are listed below GEN Entire Transaction Set 352 Note/Special Instruction Attributes M ID 3/3
Must Use
NTE02
AN 1/60
February 2007
27 - 9
REF Reference Numbers


Must Use Ref. Des. REF01 Data Element Name 128 Ship To Plant Code Qualifier Valid codes are listed below PE Plant Number 127 Ship To Plant Code Substitute correct plant code from the following: A = MAP Marysville Auto Plant HAM C = HCM Honda of Canada HCM M = MMP Marysville Motorcycle Plant HAM N = AEP Anna Engine Plant HAM P = APS American Parts Supply HAM Q = HDM Honda de Mexico HAM T = ELP East Liberty Auto Plant HAM V = HMA Honda Mfg. of Alabama HMA W = EXA Accord Exports HAM X = EXC Civic Exports HAM Attributes M ID 2/2
Must Use
REF02
AN 1/1
N1 Supplier Name

Must Use Ref. Des. N101 Data Element Name 98 Supplier Name Qualifier Valid codes are listed below VN Vendor 93 Supplier Name 66 Supplier Number Qualifier Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Supplier Number and Loc Code HAM's field min/max is 8/8. HCM's field min/max is 6/6. Attributes M ID 2/2
Must Use Must Use
N102 N103
M M
AN 1/30 ID 1/2
Must Use
N104
AN 6/8
27 - 10
February 2007
N1 Ship To Name

Must Use Ref. Des. N101 Data Element Name 98 Ship To Code Valid codes are listed below ST Ship To 93 Ship To Name 66 Ship To Code Qualifier Valid codes are listed below 92 Assigned by Buyer or Buyer's Agent 67 Ship To Code Attributes M ID 2/2
Must Use Must Use
N102 N103
M M
AN 1/30 ID 1/2
Must Use
N104
AN 2/17
N3 Ship To Address Information

Position: Loop: Level: Usage: Max Use: Ref. Des. N301 N302 088 N1 Mandatory Heading Optional 1

Must Use Data Element Name 166 Ship To Address line 1 166 Ship To Address line 2 This element is not used for HCM. Attributes M AN 1/24 O AN 1/24

Position: Loop: Level: Usage: Max Use: Ref. Des. N401 N402 N403 089 N1 Mandatory Heading Optional 1

Must Use Must Use Data Element 19 156 116 Name Ship To City Name Ship To State or Province Code Ship To Postal Code Attributes M AN 2/15 M ID 2/2 O ID 5/9
February 2007
27 - 11
DTM Requested Ship Date/Time/Period

Position: Loop: Level: Usage: Max Use: Ref. Des. DTM01 130 Heading Mandatory 1

Must Use Data Element Name 374 Requested Ship Date/Time Qualifier Valid codes are listed below 010 Requested Ship 373 Requested Ship Date Date expressed as CCYYMMDD 337 Requested Ship Time Time expressed in 24-hour clock time as HHMM. Attributes M ID 3/3
Must Use
DTM02 DTM03
M O
DT 8/8 TM 4/4
TD5 Carrier Details (Routing Sequence/Transit Time)

Position: Loop: Level: Usage: Max Use: 190 Heading Optional 1

Ref. Des. TD501 Data Element Name Attributes 133 Routing Sequence Code O ID 1/2 Valid codes are listed below B Origin/Delivery Carrier (Any Mode) 66 SCAC Code Qualifier C ID 1/2 Valid codes are listed below. HCM does not use this element. 2 Standard Carrier Alpha Code (SCAC) 67 SCAC Code C AN 2/4 Standard Carrier Alpha Code (SCAC) of carrier. HCM does not use this element. 91 Transportation Method/Type Code C ID 1/2 Valid codes are listed below M Motor (Common Carrier) 387 Honda Routing Code C AN 1/3 This number should be returned in the corresponding 856's TD505.
TD502
TD503
TD504
TD505
27 - 12
February 2007


Ref. Des. LIN01 LIN02 Data Element Name Attributes 350 Line Item O AN 1/6 235 Buyer Part Number Qualifier M ID 2/2 Valid codes are listed below BP Buyer's Part Number 234 Honda Part Number (includes Part Color) M AN 1/27 235 KD Order Number Qualifier M ID 2/2 Valid codes are listed below ON Customer Order Number 234 KD Order Number M AN 1/9 KD Order Number for Sequence deliveries or the word "HONDA" for nonsequence deliveries. 235 Product ID Qualifier O ID 2/2 Present only for sequence deliveries. The code value "MP" will be used by HAM, "MN" will be used by HCM. Valid codes are listed below: MP MN Model Number Product ID Code O Present only for sequence deliveries. Container Type Qualifier O Valid codes are listed below. This field is not used by HCM. RC Returnable Container Number Honda Container Type Code O This field is not used by HCM.
Must Use
Must Use Must Use
LIN03 LIN04
Must Use
LIN05
LIN06
LIN07 LIN08
234 235
AN 1/10 ID 2/2
LIN09
234
AN 1/2
February 2007
27 - 13
UIT Unit Detail


Must Use Must Use Ref. Des. UIT01 C00101 Data Element Name C001 Composite Unit of Measure 355 Unit or Basis for Measurement Code Refer to ANSI guidelines for a list of valid codes Attributes M M ID 2/2
PO3 Additional Item Detail

Position: Loop: Level: Usage: Max Use: 060 LIN Mandatory Detail Optional 1

Must Use Ref. Des. PO301 Data Element Name 371 Change Reason Code Valid codes are listed below AQ Alternate Quantity and Unit of Measure 380 Quantity per container 355 Unit or Basis for Measurement Code Valid codes are listed below CH Container Attributes M ID 2/2
Must Use Must Use
PO306 PO307
M M
R 1/5 ID 2/2
27 - 14
February 2007
PID Product/Item Description


Must Use Ref. Des. PID01 Data Element Name 349 Item Description Type Valid codes are listed below. X Semi-structured (Code and Text) 352 Honda Part Description Attributes M ID 1/1
Must Use
PID05
AN 1/30
PO4 Item Physical Details

Position: Loop: Level: Usage: Max Use: Notes: 120 LIN Mandatory Detail Optional 1 This segment will only be present for sequence deliveries.

Must Use Must Use Ref. Des. PO402 PO403 Data Element Name 357 Lot Size 355 Unit or Basis for Measurement Code Valid codes are listed below LO Lot Attributes M R 1/5 M ID 2/2
February 2007
27 - 15
REF Job Sequence Reference Numbers

Position: Loop: Level: Usage: Max Use: Notes: 140 LIN Mandatory Detail Optional 1 This segment will only be present for sequence deliveries.

Must Use Ref. Des. REF01 Data Element Name 128 Job Sequence Number Qualifier Valid codes are listed below JS Job Sequence Number 127 Job Sequence Number Attributes M ID 2/2
Must Use
REF02
AN 1/3
REF Zone Reference Numbers


Must Use Ref. Des. REF01 Data Element Name 128 Zone Code Qualifier Valid codes are listed below IR Intra Plant Routing 127 Honda Zone Code Attributes M ID 2/2
Must Use
REF02
AN 1/8
27 - 16
February 2007
SDP Ship/Delivery Pattern

Position: Loop: Level: Usage: Max Use: 450 SDP Mandatory Detail Mandatory 1

Must Use Ref. Des. SDP01 Data Element Name 678 Ship/Delivery Code Valid codes are listed below: N As Directed 679 Ship/Delivery Pattern Time Code Valid codes are listed below: F As Directed - F means Firm Quantities in FST. Attributes M ID 1/2
Must Use
SDP02
ID 1/1
FST Forecast Schedule

Position: Loop: Level: Usage: Max Use: 460 SDP Mandatory Detail Mandatory 104

Must Use Must Use Ref. Des. FST01 FST02 Data Element Name 380 Quantity 680 Forecast Qualifier Valid codes are listed below C Firm 681 Forecast Timing Qualifier Valid codes are listed below D Discrete 373 Delivery Date Date expressed as CCYYMMDD Attributes M R 1/7 M ID 1/1
Must Use
FST03
ID 1/1
Must Use
FST04
DT 8/8
February 2007
27 - 17


Must Use Ref. Des. CTT01 CTT02 Data Element Name Attributes 354 Number of Line Items M N0 1/6 The accumulation of the number of LIN segments 347 Hash Total O R 1/10 The sum of the values of the quantities (FST01) for each FST segment.


Must Use Must Use Ref. Des. SE01 SE02 Data Element Name 96 Number of Included Segments 329 Transaction Set Control Number Attributes M N0 1/6 M AN 4/9
27 - 18
February 2007
Chapter 29 Advance Ship Notice (856) STAR

Advance Ship Notice (856) STAR
February 2007
29 - 1
Chapter Contents
This chapter contains information and procedures for using the Honda STAR Advance Ship Notice transaction. Transaction specifications are included for further clarification.
Table of Contents
Transaction Description ...................................................................................................................... 4 Transaction Covered........................................................................................................................... 4 Application Standards and Conventions............................................................................................. 4 Mapping .............................................................................................................................................. 4 Exceptions/Clarifications..................................................................................................................... 4 Schedule ............................................................................................................................................. 4 Specifications ...................................................................................................................................... 4 Back Up Procedure............................................................................................................................. 4 Business Purpose ................................................................................................................................ 5 Transaction Specification Information................................................................................................. 6 Transaction Specifications.................................................................................................................. 7 Functional Group ID = SH ............................................................................................................... 7 ST Transaction Set Header............................................................................................................. 8 BSN Beginning Segment for Ship Notice........................................................................................ 9 DTM Date/Time Reference - Shipped............................................................................................. 9 HL Hierarchical Level - Shipment.................................................................................................. 10 TD1 Carrier Details (Quantity and Weight) ................................................................................... 10 TD5 Carrier Details (Routing Sequence/Transit Time) ................................................................. 11 TD3 Carrier Details (Equipment)................................................................................................... 11 REF Authorization Reference Numbers........................................................................................ 12 REF Bill of Lading Reference Numbers ........................................................................................ 12 REF Material Release Reference Numbers.................................................................................. 13 REF Plant Identifier Reference Numbers...................................................................................... 14 N1 Ship From Name...................................................................................................................... 14 HL Hierarchical Level - Tare Pallet Level...................................................................................... 15 REF Material Release Reference Numbers.................................................................................. 15 REF Master/Mix Label Reference Numbers ................................................................................. 16 REF Pallet Reference Numbers .................................................................................................... 16 HL Hierarchical Level - Item .......................................................................................................... 17 LIN Item Identification.................................................................................................................... 17 SN1 Item Detail (Shipment)........................................................................................................... 18 REF Container Label Reference Numbers ................................................................................... 18 REF Container Serial Reference Numbers ................................................................................... 19 REF Sequential or Non-Sequential Supplier Reference Numbers ............................................... 19 REF Material Release Reference Numbers.................................................................................. 20 REF IPP Tag Reference Numbers Use Only When Needed..................................................... 20
29 - 2
February 2007

HL Hierarchical Level - Pack ......................................................................................................... 21 LIN Item Identification.................................................................................................................... 21 SN1 Item Detail (Shipment)........................................................................................................... 22 REF Container Label Reference Numbers ................................................................................... 22 REF Container Serial Reference Numbers ................................................................................... 23 REF Sequential or Non-Sequential Supplier Reference Numbers ............................................... 23 REF Material Release Reference Numbers.................................................................................. 24 REF IPP Tag Reference Numbers - Use Only When Needed...................................................... 24 REF Non Returnable Container .................................................................................................... 25 CTT Transaction Totals................................................................................................................. 25 SE Transaction Set Trailer ............................................................................................................ 26 Operating Procedures........................................................................................................................ 27 Reconciliation.................................................................................................................................... 27 Initial Production Parts (IPP)............................................................................................................. 28 Honda Returnable Label Serial Number........................................................................................... 28
February 2007
29 - 3
Transaction Covered
Advance Ship Notice/Manifest (Transaction Set 856), abbreviated SH

Mapping
A list of the Advance Ship Notice (ASN) business data elements and how they are transmitted via EDI Standards is provided in the Transaction Specifications section.
Schedule
The ASN shall be transmitted to the buyer within the specified time window. The buyer will send Functional Acknowledgements for ASNs unless the seller specifies otherwise.
Specifications
In transmitting the Advance Ship Notice, a User Message Class (MSGUCLS) of 856 must be present to transmit the data to the buyers mailbox.
Back Up Procedure
29 - 4
February 2007
Business Purpose
The Honda STAR Advance Ship Notice (ASN) is used to anticipate the contents of supplier deliveries during the receiving process. Because Honda does rely heavily on supplier ASNs for internal purposes, it is very important that the supplier ASNs have a high degree of data integrity.
Frequency: Immediately following the departure of each shipment. Transmitted From: Domestic OEM Suppliers Transmitted To: Honda
February 2007
29 - 5

2. The second section is the detailed specifications of the transaction. The attributes columns within this second section are explained as follows: The first column: M = Mandatory X = Conditional O = Optional The second column: ID = Identifier (a unique value from a predefined list from ANSI) DT = Date TM = Time AN = Alphanumeric R = Numeric with a variable decimal place Nx = Numeric with a x decimal places The third column: x/y, where x = the minimum number of digits for this element and y = the maximum number of digits for this element.
29 - 6
February 2007
Functional Group ID = SH
Heading:
Pos. No. 010 020 040 Seg. ID ST BSN DTM Name Transaction Set Header Beginning Segment for Ship Notice Date/Time Reference - Shipped Req. Des. M M M Max.Use 1 1 1 Loop Repeat
Detail:
Pos. No. Must Use 050 150 Must Use Must Use 160 170 200 Must Use 205 210 Must Use 220 Seg. ID HL TD1 TD5 TD3 REF REF REF REF Name LOOP ID - HL Hierarchical Level - Shipment Carrier Details (Quantity and Weight) Carrier Details (Routing Sequence/Transit Time) Carrier Details (Equipment) Authorization Reference Numbers Bill of Lading Reference Numbers Material Release Reference Numbers Plant Identifier Reference Numbers LOOP ID - N1 Must Use 290 N1 Ship From Name LOOP ID - HL 400 401 Must Use Must Use 410 420 HL REF REF REF Hierarchical Level - Tare Pallet Level Material Release Reference Numbers Master/Mix Label Reference Numbers Pallet Reference Numbers LOOP ID - HL 430 Must Use Must Use 440 450 455 460 470 480 490 HL LIN SN1 REF REF REF REF REF Hierarchical Level - Item Item Identification Item Detail (Shipment) Container Label Reference Numbers Container Serial Reference Numbers Sequential or Non-Sequential Supplier Reference Numbers Material Release Reference Numbers IPP Tag Reference Numbers - Use Only When Needed LOOP ID - HL Hierarchical Level - Pack Item Identification Item Detail (Shipment) Container Label Reference Numbers O M M O O O O O 1 1 1 1 1 1 1 1 >1 O O M M 1 1 1 1 O O M M 1 1 1 1 >1 M 1 >1 Req. Des. M O M M O M O M Max.Use 1 20 1 1 1 1 1 1 1 Loop Repeat 200000
495 496 Must Use Must Use 497 498
HL LIN SN1 REF
February 2007
29 - 7

Must Use 499 500 501 502 503 REF REF REF REF REF Container Serial Reference Numbers Sequential or Non-Sequential Supplier Reference Numbers Material Release Reference Numbers IPP Tag Reference Numbers - Use Only When Needed Non Returnable Container M O O O O 1 1 1 1 1
Summary:
Pos. No. 590 600 Seg. ID CTT SE Name Transaction Totals Transaction Set Trailer Req. Des. M M Max.Use 1 1 Loop Repeat
Must Use Must Use


Must Use Ref. Des. ST01 Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Valid codes are listed below: 856 Ship Notice/Manifest 329 Transaction Set Control Number M AN 4/9 This number must be unique (within a transaction set) and ascending.
Must Use
ST02
29 - 8
February 2007
BSN Beginning Segment for Ship Notice


Must Use Ref. Des. BSN01 Data Element Name Attributes 353 Transaction Set Purpose Code M ID 2/2 Valid codes are listed below 00 Original 01 Cancellation 05 Replace 396 Shipment Identification - ASN Number M AN 8/8 ASN number must always be 8 digits-cannot duplicate within 1 year. 373 ASN Create Date M DT 8/8 Date expressed as CCYYMMDD 337 ASN Create Time M TM 4/4 Time expressed in 24-hour clock time (HHMM)
BSN02 BSN03 BSN04
DTM Date/Time Reference - Shipped


Must Use Ref. Des. DTM01 Data Element Name 374 Ship Date/Time Qualifier Valid codes are listed below 011 Shipped 373 Ship Date Date expressed as CCYYMMDD 337 Ship Time Time expressed in 24-hour clock time (HHMM). Attributes M ID 3/3
Must Use Must Use
DTM02 DTM03
M M
DT 8/8 TM 4/4
February 2007
29 - 9
HL Hierarchical Level - Shipment


Must Use Must Use Ref. Des. HL01 HL03 Data Element Name 628 Hierarchical ID Number-Shipment Level "1" - Shipment Level 735 Hierarchical Level Code-Shipment Level Valid codes are listed below S Shipment Attributes M AN 1/12 M ID 1/2
TD1 Carrier Details (Quantity and Weight)

Position: Loop: Level: Usage: Max Use: 150 HL Mandatory Detail Optional 20

Must Use Must Use Ref. Des. TD101 TD102 Data Element Name 103 Pallet Code Example: "PLT71" = Pallet 80 Number of Pallets Number of pallets on the shipment Attributes M AN 5/5 M N0 1/7
29 - 10
February 2007
TD5 Carrier Details (Routing Sequence/Transit Time)


Must Use Ref. Des. TD501 Data Element Name Attributes 133 Routing Sequence Code M ID 1/2 Valid codes are listed below B Origin/Delivery Carrier (Any Mode) 66 SCAC Identification Code Qualifier C ID 1/2 Valid codes are listed below. This field is required for HAM. This field is not used by HCM. 2 Standard Carrier Alpha Code (SCAC) - Honda's application system will accept "2" or "02". 67 SCAC Code C AN 4/4 SCAC is required for HAM. SCAC is not used by HCM. 91 Transportation Method/Type Code O ID 1/2 Valid codes are listed below M Motor (Common Carrier) 387 Honda Routing Code O AN 3/3 Honda routing code for the corresponding Material Release 830. Found in the 830 TD505.
TD502
TD503 TD504
TD505
TD3 Carrier Details (Equipment)


Must Use Ref. Des. TD301 Data Element Name 40 Equipment Description Code Valid codes are listed below TL Trailer (not otherwise specified) 207 Trailer Number Attributes M ID 2/2
Must Use
TD303
AN 1/10
February 2007
29 - 11
REF Authorization Reference Numbers

Position: Loop: Level: Usage: Max Use: Notes: 200 HL Mandatory Detail Optional 1 This segment is optional and rarely used.

Must Use Ref. Des. REF01 Data Element Name Attributes 128 Authorization Number Qualifier M ID 2/2 Valid list of codes are listed below AU Authorization to Meet Competition Number 127 Authorization Number M AN 1/6 The Authorization Number does not come from an outbound Honda transaction.
Must Use
REF02
REF Bill of Lading Reference Numbers


Must Use Ref. Des. REF01 Data Element Name 128 Bill of Lading Number Qualifier Valid codes are listed below BM Bill of Lading Number 127 Bill of Lading Number Attributes M ID 2/2
Must Use
REF02
AN 1/12
29 - 12
February 2007
REF Material Release Reference Numbers

Position: Loop: Level: Usage: Max Use: 210 HL Mandatory Detail Optional 1

Must Use Ref. Des. REF01 Data Element Name Attributes 128 Material Release Number Qualifier M ID 2/2 Valid codes are listed below RE Release Number 127 Material Release Number M AN 8/8 The 8 digit Material Release Number (from the corresponding outbound Star 830 BFR03) can be used at this level only if the entire shipment is for a single release. The Material Release Number must be returned at either the Shipment, Tare, Item or Pack level.
Must Use
REF02
February 2007
29 - 13
REF Plant Identifier Reference Numbers


Must Use Ref. Des. REF01 Data Element Name 128 Plant ID Qualifier Valid codes are listed below PE Plant Number 127 Plant ID Substitute the correct plant code from the below list. A MAP = Marysville Auto Plant C HCM = Honda of Canada M MMP = Marysville Motorcycle Plant N AEP = Anna Engine Plant P IPS = International Parts Supply Q HDM = Honda de Mexico T ELP = East Liberty Auto Plant V HMA = Honda Mfg. of Alabama W EXA = Accord Exports X EXC = Civic Exports Attributes M ID 2/2
Must Use
REF02
AN 1/1 HAM HCM HAM HAM HAM HAM HAM HMA HAM HAM
N1 Ship From Name


Must Use Ref. Des. N101 Data Element Name 98 Ship From Identifier Code Valid codes are listed below SF Ship From VN Vendor 93 Ship From Supplier Name 66 Ship from Identification Code Qualifier 92 Assigned by Buyer or Buyer's Agent 67 Ship From Honda Supplier Code HAM's field min/max is 8/8. HCM's field min/max is 6/6. Attributes M ID 2/2
Must Use Must Use
N102 N103 N104
O M M
AN 1/30 ID 1/2 AN 6/8
29 - 14
February 2007
HL Hierarchical Level - Tare Pallet Level

Position: Loop: Level: Usage: Max Use: 400 HL Optional Detail Optional 1

Must Use Must Use Must Use Ref. Des. HL01 HL02 HL03 Data Element 628 734 735 Name Hierarchical ID Number Hierarchical Parent ID Number Tare Hierarchical Level Code Valid codes are listed below T Shipping Tare Attributes M AN 1/12 M AN 1/12 M ID 1/2


Must Use Ref. Des. REF01 Data Element Name Attributes 128 Material Release Qualifier M ID 2/2 Valid codes are listed below RE Release Number 127 Material Release Number M AN 8/8 The 8 digit Material Release Number (from the corresponding outbound Star 830 BFR03) can be used at this level only if all items on this tare/pallet are for a single release. The Material Release Number must be returned at either the Shipment, Tare, Item or Pack level.
Must Use
REF02
February 2007
29 - 15
REF Master/Mix Label Reference Numbers

Position: Loop: Level: Usage: Max Use: 410 HL Optional Detail Mandatory 1

Must Use Ref. Des. REF01 Data Element Name Attributes 128 Label Serial Number Qualifier M ID 2/2 Valid codes are listed below LS Bar-Coded Serial Number 127 Master/Mix Label Serial Number M AN 9/9 This number must always be 9 digits, is customer assigned, and must not repeat within a year.
Must Use
REF02
REF Pallet Reference Numbers


Must Use Ref. Des. REF01 Data Element Name Attributes 128 Pallet Type/Number Qualifier M ID 2/2 Valid codes are listed below RS Returnable Container Serial Number 127 Pallet Type/Serial Number M AN 2/8 - If pallet type is a Honda modular container this element must contain the permanent Modular Container Serial Number. - If the permanent Modular Container Serial number is missing or is unscanable input the modular container type code. - If the pallet type is not a Honda modular this element must contain "XX".
Must Use
REF02
29 - 16
February 2007
HL Hierarchical Level - Item


Must Use Must Use Must Use Ref. Des. HL01 HL02 HL03 Data Element 628 734 735 Name Hierarchical ID Number Hierarchical Parent ID Number Item Hierarchical Level Code Valid codes are listed below Attributes M AN 1/12 M AN 1/12 M ID 1/2
Item


Ref. Des. LIN01 LIN02 Data Element Name 350 Line Item Number 235 Buyer Part ID Qualifier Valid codes are listed below BP Buyer's Part Number 234 Buyers Part Number and Color Attributes O AN 1/6 M ID 2/2
Must Use
Must Use
LIN03
AN 1/27
February 2007
29 - 17


Must Use Must Use Ref. Des. SN102 SN103 Data Element Name 382 Item Quantity 355 Unit or Basis for Measurement Code Valid codes are listed below EA Each Attributes M R 1/7 M ID 2/2
REF Container Label Reference Numbers


Must Use Ref. Des. REF01 Data Element Name Attributes 128 Container Label Serial Number Qualifier M ID 2/2 Valid codes are listed below LS Bar-Coded Serial Number 127 Container Label Serial Number M AN 9/9 Container Label Serial Number must be 9 digits, is customer assigned, and must not repeat within a year.
Must Use
REF02
29 - 18
February 2007
REF Container Serial Reference Numbers


Must Use Ref. Des. REF01 Data Element Name Attributes 128 Container Type/Serial Number Qualifier M ID 2/2 Valid codes are listed below RS Returnable Container Serial Number 127 Container Type/Serial Number M AN 2/8 - If pallet type is a Honda modular container this element must contain the permanent Modular Container Serial Number. - If the permanent Modular Container Serial number is missing or is unscanable input the modular container type code. - If the pallet type is not a Honda modular this element must contain "XX".
Must Use
REF02
REF Sequential or Non-Sequential Supplier Reference Numbers

Position: Loop: Level: Usage: Max Use: Notes: 470 HL Optional Detail Optional 1 The "CO" qualifier and corresponding information must be used at the item or pack level.

Must Use Ref. Des. REF01 Data Element Name Attributes 128 Sequential or Non-Sequential Supplier Qualifier M ID 2/2 Valid codes are listed below CO Customer Order Number 127 Sequential or Non-Sequential Reference Number M AN 5/9 Example: From 830 - LIN05 = KD Order Number for Sequential Suppliers From 830 - LIN05 = "HONDA" Non-Sequential Suppliers
Must Use
REF02
February 2007
29 - 19


Must Use Ref. Des. REF01 Data Element Name Attributes 128 Material Release Qualifier M ID 2/2 Valid codes are listed below RE Release Number 127 Material Release Number M AN 8/8 The 8 digit Material Release Number (from the corresponding outbound Star 830 BFR03) can be used at this level only if all items under this HL Item level are for a single release. The Material Release Number must be returned at either the Shipment, Tare, Item or Pack level.
Must Use
REF02
REF IPP Tag Reference Numbers Use Only When Needed


Must Use Ref. Des. REF01 Data Element Name 128 IPP Tag Number Qualifier Valid codes are listed below CR Customer Reference Number 127 IPP Tag Number Use as needed per Honda Quality Guidelines. Attributes M ID 2/2
Must Use
REF02
AN 1/15
29 - 20
February 2007
HL Hierarchical Level - Pack


Must Use Must Use Must Use Ref. Des. HL01 HL02 HL03 Data Element 628 734 735 Name Hierarchical ID Number Hierarchical Parent ID Number Hierarchical Level Code Valid codes are listed below P Pack Attributes M AN 1/12 M AN 1/12 M ID 1/2


Ref. Des. LIN01 LIN02 Data Element Name 350 Line Item Number 235 Buyer Part ID Qualifier Valid codes are listed below BP Buyer's Part Number 234 Buyers Part Number and Color Attributes O AN 1/6 M ID 2/2
Must Use
Must Use
LIN03
AN 1/27
February 2007
29 - 21


Must Use Must Use Ref. Des. SN102 SN103 Data Element Name 382 Item Quantity 355 Unit or Basis for Measurement Code Valid codes are listed below EA Each Attributes M R 1/7 M ID 2/2
REF Container Label Reference Numbers


Must Use Ref. Des. REF01 Data Element Name Attributes 128 Container Label Serial Number Qualifier M ID 2/2 Valid codes are listed below LS Bar-Coded Serial Number 127 Container Label Serial Number M AN 9/9 Container Label Serial Number must be 9 digits, is customer assigned, and must not repeat within a year.
Must Use
REF02
29 - 22
February 2007
REF Container Serial Reference Numbers


Must Use Ref. Des. REF01 Data Element Name Attributes 128 Container Type/Serial Number Qualifier M ID 2/2 Valid codes are listed below RS Returnable Container Serial Number 127 Container Type/Serial Number M AN 2/8 - If pallet type is a Honda modular container this element must contain the permanent Modular Container Serial Number. - If the permanent Modular Container Serial number is missing or is unscanable input the modular container type code. - If the pallet type is not a Honda modular this element must contain "XX".
Must Use
REF02
REF Sequential or Non-Sequential Supplier Reference Numbers

Position: Loop: Level: Usage: Max Use: Notes: 500 HL Optional Detail Optional 1 The "CO" qualifier and corresponding information must be used at the item or pack level.

Must Use Ref. Des. REF01 Data Element Name Attributes 128 Sequential or Non-Sequential Supplier Qualifier M ID 2/2 Valid codes are listed below CO Customer Order Number 127 Sequential or Non-Sequential Reference Number M AN 5/9 Example: From 830 - LIN05 = KD Order Number for Sequential Suppliers From 830 - LIN05 = "HONDA" Non-Sequential Suppliers
Must Use
REF02
February 2007
29 - 23


Must Use Ref. Des. REF01 Data Element Name Attributes 128 Material Release Qualifier M ID 2/2 Valid codes are listed below RE Release Number 127 Material Release Number M AN 8/8 The 8 digit Material Release Number (from the corresponding outbound Star 830 BFR03) can be used at this level. If it was included at a higher HL level, it is not necessary to use it here. The Material Release Number must be returned at either the Shipment, Tare, Item or Pack level.
Must Use
REF02
REF IPP Tag Reference Numbers - Use Only When Needed


Must Use Ref. Des. REF01 Data Element Name 128 IPP Tag Number Qualifier Valid codes are listed below CR Customer Reference Number 127 IPP Tag Number Use as needed per Honda Quality Guidelines. Attributes M ID 2/2
Must Use
REF02
AN 1/15
29 - 24
February 2007
REF Non Returnable Container


Must Use Ref. Des. REF01 Data Element Name 128 Non-Returnable Container Qualifier Valid codes are listed below ZZ Mutually Defined 127 Non-Returnable Container Indicator "XX" indicates a non-returnable container Attributes M ID 2/2
Must Use
REF02
AN 2/2


Must Use Ref. Des. CTT01 CTT02 Data Element Name Attributes 354 Number of Line Items M N0 1/6 The accumulation of the number of HL segments. 347 Hash Total O R 1/10 Sum of the item quantities (SN102) for each unique part number. Do not double count a SN1 segment under an item and pack level.
February 2007
29 - 25


Must Use Must Use Ref. Des. SE01 SE02 Data Element Name 96 Number of Included Segments 329 Transaction Set Control Number Attributes M N0 1/6 M AN 4/9
29 - 26
February 2007
Reconciliation
Honda requires reconciliation (a systematic comparison) of the ordering document (830) to the ASN (856). The purpose is to ensure that suppliers are shipping what Honda has ordered. By capturing discrepancies prior to truck departure and ASN generation, potential miss-shipments can be corrected, avoiding costly corrective countermeasures. There are two distinct steps to the reconciliation process. 1. Reconciling the ordering document (830) to the planned load(s).
Note - If a shipment is large and must be split between multiple trucks, reconciliation from the ordering document to the multiple planned loads must occur.
2. Reconciling the planned load to the ASN.
For both steps, discrepancies can be identified on-line or hard copy. Following are the items to be reconciled and the action requested. Item to reconcile Invalid Part Number Description The system must alert the user if a part number mismatch between the ordering document and ASN. Action to be taken The user must verify that the scanned information is correct. If it is correct, there must be a method to ship the part on an ASN. If there is an error, a correction must be made. (Leaving the part number on the ASN often requires the user to adjust the planned load.) Correct the discrepancy. Honda will not accept an invalid material release number. This will result in a rejected ASN. Correct the discrepancy. Honda will not accept an invalid plant identifier. This will result in a rejected ASN. The shipper should confirm the quantity scanned versus the quantity required. The system must allow the user to take either of the following steps: 1) over ship or 2) re-scan to ship the required amount. The shipper should confirm the quantity scanned versus the quantity required. The system must allow the user to take either of the following steps: 1) under ship or 2) re-scan to ship the required amount.
Invalid Material Release Number Invalid Plant Identifier
Over Shipment
The system must not allow a material release number mismatch between the ordering document and ASN. The system must not allow a plant identifier mismatch between the ordering document and ASN. The system must alert the user of an over shipment of parts on the ASN (versus the ordering document).
Under Shipment
The system must alert the user of an under shipment of parts on the ASN (versus the ordering document).
February 2007
29 - 27
Initial Production Parts (IPP)

IPP Tag description: An initial Production Parts (IPP) tag notifies Honda Quality and Production associates of a change. See the list of Reason Codes below for examples of when an IPP tag is required. Depending upon the part and supplier, IPP tags may be required many times during a model year. The Supplier IPP Procedure can be found in the Honda Supplier Quality Manual. Who applies the IPP Tag: The supplier that makes the change completes the IPP tag. The IPP tag is attached to the first shipment of changed parts. Where does the IPP Tag come from: See the Supplier IPP Procedure in the Honda Supplier Quality Manual. STAR IPP Tag requirements: When an IPP tag is applied to a container (inside or attached to the outside) the supplier must link the IPP tag with a specific container. This is accomplished during the ASN creation process. The supplier scans the container label serial number, then enters the IPP Tag Number. This entry can be accomplished by scanning the IPP Tag or manually entering the information. The data element populated in the ASN is REF02 with a CR qualifier. Hondas STAR EDI specifications allow a maximum of one IPP tag number per container of parts.
Note - If there is more than one IPP tag attached to a container, enter the information for one tag and omit the others.
IPP Tag Reason Codes 1 2 3 4 5 6 7 8 9 10 11 12 Design Changes New Supplier Material Change Mfg. Method Change Mfg. Process Order Change Machine Change Jig/Tool Change Die/Mold Change Inspection Method Change Transport/Packing Change Sort Other

See the Bar Code Labeling chapter for a description of the Returnable Label Serial Number. While the rules for STAR are the same as DELTA, the data locations will be different. (See the STAR 856 specifications).
29 - 28
February 2007
Chapter 30 Functional Acknowledgement (997) STAR

Functional Acknowledgement (997) STAR
February 2007
30 - 1
Chapter 30 Functional Acknowledgement (997) STAR
See the Functional Acknowledgement (997) chapter in the DELTA/GPCS section. The DELTA/GPCS and STAR Functional Acknowledgements are identical.
30 - 2
February 2007
Chapter 31 Interchange Control Structures (ICS) STAR

Interchange Control Structure (ICS) STAR
February 2007
31 - 1
Chapter 31 Interchange Control Structures (ICS) STAR
See the Interchange Control Structures (ICS) chapter in the DELTA/GPCS section. The DELTA/GPCS and STAR Interchange Control Structures are identical.
31 - 2
February 2007

View EDI Barcode Specification 2008 04

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

View EDI Barcode Specification 2008 04

Hochgeladen von

Copyright:

Verfügbare Formate

Chapter 1 Introduction

EDI & Bar Code Label Implementation Requirements

Honda of America Mfg., Inc. 2007

Using Electronic Data Interchange (EDI)

Hondas Financial Institution

Suppliers Financial Institution

RECEIVING AND SHIPPING

- Application Advice (824) - Weekly Releases (830) - Text (864)

- Functional Acknowledgment (997)

ASN/ RECEIVING PROCESSING

- Sequencing/Kitting - Returnable Container - Pallet Control

PRINT AIAG BAR CODE LABELS

RECONCILIATION PROCESS ACKNOWLEDGMENT

Suppliers Using a Warehouse for Delivery Services

Chapter 2 General Terms and Conditions

EDI & Bar Code Label Implementation Requirements

Honda of America Mfg., Inc. 2008

Chapter 2 General Terms and Conditions

Chapter 2 General Terms and Conditions

Chapter 2 General Terms and Conditions

Chapter 3 Key Contacts

EDI & Bar Code Label Implementation Requirements

Honda of America Mfg., Inc. 2007

Chapter 3 Key Contacts

Chapter 3 Key Contacts

Table 3.1 EDI Key Contacts

Situation Supplier uses GXS

Chapter 4 Implementation Steps

EDI & Bar Code Label Implementation Requirements

Honda of America Mfg., Inc. 2008

Chapter 4 Implementation Steps

Chapter 4 Implementation Steps

Chapter 4 Implementation Steps

Requirements to Use Honda Approved Software

Trading Partner Set-up

Chapter 4 Implementation Steps

Honda EDI System Availability

Chapter 4 Implementation Steps

Honda Electronic Mailbox IDs

Chapter 4 Implementation Steps

Chapter 4 Implementation Steps

EDI Copy Documents:

Chapter 4 Implementation Steps

Honda Supply Team Hub HSThub

Supplier Communication Overview

Files Types Supported by HSThub

Chapter 4 Implementation Steps

Vendor Ascential Software Cleo

Product Name Datastage TX Lexicom

Version/PTF Level 7.5 3.5 Win 95 2.1.3 *

Website www.ascential.com www.cleo.com

C-Kermit 8.0.211 (Unix) 32 bit V3R1/3100034

QualEDI for Windows ZMOD FTP

Chapter 4 Implementation Steps

Supplier Fire Wall Considerations

HSThub Test System Considerations

HSThub Production System Considerations

Chapter 4 Implementation Steps

Chapter 4 Implementation Steps

Trading Partner Application Design Considerations

FTP/s or FTP Client Design Considerations

Chapter 4 Implementation Steps

Supported FTP commands