EDI: Getting Started
Doing Business Electronically with Bell Helicopter
Bell Helicopter requires each supplier and customer to register with Bell's Electronic Commerce Management Center prior to the beginning of testing. This enables Bell Helicopter to collect needed information on the trading partner such as points of contact, EDI qualifiers and IDs, software used, etc. Please complete and submit the on-line form below.
A traditional form is also available, if desired. Please print and complete the traditional form. After completion, of the traditional form, please fax it back to the Electronic Commerce Management Center. Fax numbers are listed on the form and on the Points of Contact page.
+ BHTI eCommerce Trading Partner Registration Form
Bell Helicopter requires each supplier to sign and return the Bell Helicopter EDI Trading Partner Agreement. Until the signed agreement is received by Bell Helicopter, the supplier will not be placed into a production mode for EDI transmissions. This agreement is modeled on the EDI trading partnership agreement developed by the American Bar Association
+ BHTI eCommerce Trading Partnership Agreement
The following are EDI implementation guides for the EDI transactions being used at Bell Helicopter. Each document is in PDF format. Each implementation guide is for ANSI X12 version 4010 unless otherwise noted.
Routine Procurement
X12 Version 4010
+ Routine Purchase Orders (850)
+ Routine Purchase Order Acknowledgements (855)
+ Routine Purchase Order Changes (860)
+ Routine Purchase Order Change Acknowledgments (865)
Just-In-Time /Commodity Procurement
X12 Version 4010
+ Commodity/ Just-In-Time Releases (850)
+ Commodity/ Just-In-Time Release Acknowledgments (855)
Miscellaneous
X12 Version 4010
+ Functional Acknowledgment (997)
Are you EDI capable?
| Yes, I have EDI software and VAN services, and am doing EDI with other companies. |
No, I do not have EDI software and VAN services, and am not doing EDI with other companies. |
- Complete the + EDI Trading Partner Registration Information and return to Bell Helicopter's EDI Coordinator.
- Inform your Value-Added Network (VAN) or service bureau that you will be exchanging transactions with Bell Helicopter. The information your VAN will require is on the Bell Helicopter's EDI Information page.
- Contact Bell Helicopter's EDI Coordinator when you are ready to receive some test documents. We will send sample 850 and 860 transactions.
- If you will be returning formal acknowledgments (855s and 865s), accept one of the test transactions and reject the other. On the transaction you reject, be sure to include some verbiage (wrong price, cannot meet schedule, etc.). This will ensure that you can send text messages back to us for rejected transactions.
- Make sure you have your software set up to return the 997 Functional Acknowledgment. Bell Helicopter requires that the AK2 and AK5 segments be present in the 997. The definition document for the functional acknowledgment is included in the Transactions Definitions (above).
- When we receive your acknowledgments (functional and formal), we will check them and let you know if anything needs to be corrected.
- Once everything is working properly, we will call you to let you know that we are moving you to production mode. At your option, we will run in parallel mode (EDI and paper documents), or in full production mode (EDI only, no paper). The maximum length for parallel mode is 4 weeks.
- Once in production (parallel or full), we will send you a "production test" document. This will be an 850 purchase order with bogus part numbers and a bogus PO number. This will ensure that all the connections with the Bell Helicopter mainframe are in place. There is no need to send a formal acknowledgment (855) to this transaction, but do send the functional acknowledgment (997).
|
- Select the EDI software or service bureau you wish to use. Click here for a partial list of EDI software and service bureaus.
- Unless you use a service bureau, you will need to select the EDI value-added network (VAN) you wish to use.
- Complete the + Trading Partner Registration Information form and return it to Bell Helicopter.
- Inform your Service Bureau or Value-Added Network (VAN) that you will be exchanging transactions with Bell Helicopter. The information your VAN will require is on the Bell Helicopter's EDI Information page.
- Contact Bell Helicopter's EDI Coordinator when you are ready to receive some test documents. We will send sample 850 and 860 transactions.
- If you will be returning formal acknowledgments (855s and 865s), accept one of the test transactions and reject the other. On the transaction you reject, be sure to include some verbiage (wrong price, cannot meet schedule, etc.). This will ensure that you can send text messages back to us for rejected transactions.
- Make sure you have your software set up to return the 997 Functional Acknowledgment. Bell Helicopter requires that the AK2 and AK5 segments be present in the 997. The definition document for the functional acknowledgment is included in the "Transactions in Use at Bell Helicopter" on the EDI home page.
- When we receive your acknowledgments (functional and formal), we will check them and let you know if anything needs to be corrected.
- Once everything is working properly, we will call you to let you know that we are moving you to production mode. At your option, we will run in parallel mode (EDI and paper documents), or in full production mode (EDI only, no paper). The maximum length for parallel mode is 4 weeks.
- Once in production (parallel or full), we will send you a "production test" document. This will be an 850 purchase order with bogus part numbers and a bogus PO number. This will ensure that all the connectivities with the Bell Helicopter mainframe are in place. There is no need to send a formal acknowledgment (855) to this transaction, but do send the functional acknowledgment (997).
|
