EDI Implementation Guide

PROCUREMENT

Date: May 2, 2005

Table of Contents

EDI Implementation Guide

Contact List

Revision Section

Introduction

Benefits of EDI

EDI Standards

ANSI ASC X12 Compliance

EDI Standards and Transaction Sets

EDI Integration Testing

Purpose

Test and Production Environment Considerations (ANSI X12)

Integrated Functional Test Steps

Communication

Transmission Methods

Transmission Notes

Glossary of Terms

Trading Partner Setup

850 Purchase Order

855 Purchase Order Acknowledgment

860 Purchase Order Change Request - Buyer Initiated

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

810 Invoice

Contact List

Refer all questions regarding this Implementation Guide to:

Integration Center 33A-2Y

Access Business Group

7575 Fulton St. E.

Ada, MI 49301

Business Phone – 616.787.1648

E-mail –

Alticor is the parent company of Amway Corp., Access Business Group Inc., and Access Business Group LLC. Based in Ada, Michigan, USA.

Revision Section

Date / Name / Description of Change
/ /

Introduction

Transmission of EDI

ANSI X12 documents have been used for decades to exchange business information. Though traditionally used with a VAN (Value Added Network), these can be exchanged directly over the internet as well, thus saving VAN charges. We accept transmissions through our VAN (G-Int’l)

or via an HTTP post with AS2 encryption.

Purpose of EDI Implementation Guide

The purpose of this document is to describe the communication and data specifications for posting EDI documents to relay purchase order status and acknowledgement data to and from Access Business Group. Its audience is the technical staff at the supplier site charged with implementing the relationship.

Benefits of EDI

EDI provides many benefits to support your business in achieving its objectives. Keep the following in mind as we begin to work together to implement EDI.

EDI reduces paperwork (forms handling), data entry labor costs, postage costs, and printing costs.
EDI drives out inefficiencies in the business process

Organizations choosing EDI should consider that the full benefits are only received when both parties fully integrate the EDI data into their application systems.

EDI Standards

ANSI ASC X12 Compliance

Access Business Group complies with the Accredited Standards Committee (ASC) X12. The Accredited Standards Committee is a membership based not-for-profit organization chartered in 1979 by the American National Standards Institute (ANSI) to develop uniform data standards and specifications for cross-industry electronic exchange of business transactions. ASC X12 provides a neutral environment and an appropriate structure to foster data standards development and implementation.

EDI Standards and Transaction Sets

The following ANSI ASC X12 Version 4010 transactions are required:

850 - Purchase Order

855 - Purchase Order Acknowledgment

860 - Purchase Order Change

865 - Purchase Order Change Acknowledgment

810 - Invoice

997 - Functional Acknowledgment

824 - Invoice Rejection Notification (via E-mail or EDI Document)

Purchase order and Purchase order Change and Acknowledgments

The ANSI ASC X12 850 transaction set message requires the 855 to be returned within 3 days of issue of the original Purchase Order.
The ANSI ASC X12 860 transaction set message requires the 865 to be returned within 3 days of issue of the Purchase Order Change.
The ANSI ASC X12 997 transaction set message is required to be returned within 24 hours of the 850/860 being sent to the Trading Partner.

Functional Acknowledgments

The 997 Functional Acknowledgment is sent by Access Business Group to acknowledge receipt of documents sent by our trading partners. Access Business Group will acknowledge each document by the group (GS) and transaction set (ST) control numbers sent on the 850 or 860 documents. Acknowledgments are returned within 12 hours after the receipt of your 855, 865 or 810. If you do not receive an acknowledgment within that time frame, please contact the Integration Center (refer to page 3 for contact information) within 24 hours from your transmission date. If you receive a rejected or partial acknowledgment, you need to correct the error and resend only the transactions that were rejected.

It is your responsibility to ensure that your company’s SPAM blocker will permit messages from Access Business Group and that your E-MAIL addresses are valid and current. Please provide an E-MAIL address for a common E-MAIL account rather than an individual person. This will assure that communication between our companies will not go unnoticed for long periods of time in case of an employee absence or termination.

EDI Integration Testing

Purpose

This section defines Access Business Group EDI test requirements for all inbound and outbound EDI transactions.

The purpose of the integration testing is to confirm that the trading partner can successfully:

Acknowledge and transmit EDI.

Translate between the ANSI ASC X12 format and native application files, i.e. confirm the application data is mapped correctly.

Although not a direct part of the testing process, it is equally important during testing for the trading partner to confirm their internal business process are receiving the data they require, and can interpret the data and understand what data is being sent.

Test and Production Environment Considerations (ANSI X12)

Overview

Testing is required for each trading partner before they can be moved into a production environment.
A step by step process is described to document the test procedure.

ANSI X12 Control Guidelines

ISA

The ISA usage indicator (ISA15) during the test period will reflect “T”.
The ISA usage indicator (ISA15) for production must be revised to “P” when production readiness has been determined and scheduled by the Trading Partner and Integration Coordinator at Access Business Group.

GS Inbound to Access Business Group

The Application Sender’s Code (GS02) will reflect the Trading Partner’s Test Interchange ID during the testing phase and changed if necessary for production.

The Application Receiver’s Code (GS03) will be set to ‘00602679398’ during the testing phase and will be revised to “00602679322” for production (see chart below).

GS Outbound from Access Business Group

The Application Sender’s Code (GS02) will reflect “00602679398” during the testing phase and will be revised to “00602679322” for production (see chart below).
The Application Sender’s Code (GS03) will reflect the Trading Partner’s Test Interchange ID during the testing phase and changed if necessary for production.

Segment Terminators/Element Separators/Sub-Element Separators – preferred

Segment Terminator – “~” (tilde)
Element Separator – “|” (bar)
Sub-Element Separator – “>” (greater than sign)

The use of any other symbols should be coordinated with Access Business Group prior to testing.

VAN and Interchange ID

The VAN we use is G-Int’l. Access Business Group’s Qualifier and ID information is:

VAN
Used / TEST
Environment / PRODUCTION
Environment
G-Int’l (f.k.a. IBM/Advantis) / Qualifier: 14
U.S. Interchange ID: 00602679398 / Qualifier: 14
U.S. Interchange ID: 00602679322

Integrated Functional Test Steps

Step I

Access Business Group will send a test 850 Purchase Order via EDI to Trading Partner.

Step II

Trading Partner verifies data received from Access Business Group by sending a test 855 Purchase Order Acknowledgment.
Trading Partner corrects any deficiencies and repeats Step II if necessary.

Step III

Access Business Group will send a test 860 Purchase Order Change via EDI to Trading Partner.

Step IV

Trading Partner verifies data received from Access Business Group by sending a test 865 Purchase Order Change Acknowledgment.
Trading Partner corrects any deficiencies and Step III will be repeated if necessary.

Step V

Trading Partner will send 810 Invoice via EDI to Access Business Group.

Step VI

Upon successful completion of the integrated functional test, the Trading Partner will be migrated to production where the same transaction process will be followed as above.

997 Functional Acknowledgements will be sent/received back and forth between Access Business Group and Trading Partner with each transmission along the way.

Communication

Transmission Methods

Access Business Group maintains a B2B Gateway open to Internet traffic which will handle sending and receiving the EDI documents for Access Business Group’s Suppliers. There are currently three methods of transmission available to our trading partners: VAN, AS2/EDIINT, or HTTP post.

VAN Communication:

Suppliers may opt to transmit EDI data to a VAN of their choice which will in turn send the data to Access Business Group’s VAN, G-Int’l. The interconnect setup is the responsibility of each party to ensure the communication between VANs is established. We will need to know which VAN you are using.

AS2/EDIINT Communication:

If you opt to deliver EDI documents via EDIINT (AS/2), we will need to exchange certificates and you will post to our EDIINT URL. Note that using EDIINT is via HTTP post. We will need to know your static IP address to establish the firewall rules on our test and production servers. We will also need to know your URL for posting EDIINT documents to you. An MDN message will be returned as acknowledgement that we received your EDIINT document. We will expect MDN message in return for the EDIINT documents sent to your server.

HTTP Communication:

You may opt to deliver EDI documents via HTTP post. We will need to exchange user id and passwords and you will post to our EDI URL. We require that posts be made via SSL. We will need to know your static IP address to establish the firewall rules on our test and production servers. We will also need to know your URL for posting EDI documents to you.

HTTP Specifics:

Http headers need to be set with the following name/value pair:

Content-Type =’application/EDI’ if sending EDI

A response will be returned on all posts which will confirm that a transmission has been successfully received. Partners need to check the Http Response Status Code from our server. If it is not 200, you must resend the document. If a successful response is not received, it will be your responsibility to retransmit the document.

Transmission Notes

What mechanism you use to transmit the document to us is your choice. See the following page for the B2B Partner SETUP document that will enable us to set up communications. It also provides our information so you can set up your communications. We require an E-mail address for our system to return errors to you. If we encounter problems with the format of the data, we will send an E-mail to the specified E-mail address to inform you of the problem. EDI 997 documents will also be sent as validation.

Glossary of Terms

EDI:Electronic Data Interchange

H TTP: Hypertext Transfer Protocol, the Internet’s Web page protocol.

HTTPS: The HTTP protocol layered over the Secure Socket Layer (SSL) protocol to allow secure data transfer using encrypted data streams.

SSL: Abbreviation for "Secure Sockets Layer". SSL is a transaction security standard that provides data encryption, server authentication, and message integrity.

DMZ: demilitarized zone is a computer host or small network inserted as a "neutral zone" between a company's private network and the outside public network. It prevents outside users from getting direct access to a server that has company data.

AS2: Applicability Statement 2 is a specification for Electronic Data Interchange (EDI) between businesses using the Internet's Web page protocol, the Hypertext Transfer Protocol (HTTP). Security, authentication, message integrity, and privacy are assured by the use of encryption and digital signatures. Another important feature, nonrepudiation, makes it impossible for the intended recipient of a message to deny having received it.

Trading Partner Setup

Please provide the following information about your company.

Company Name: ______

Contact Name: ______

Contact Phone: ______

Contact E-mail: ______

Common E-mail Address: ______

(For syntax error notification, for example, )

It is your responsibility to ensure that your company’s SPAM blocker will permit messages from Access Business Group and that your E-mail addresses are valid and current. Please provide an E-mail address for a group rather than individual people.

For AS2/HTTP Partners only:

Your Static IP Address: ______

(address Access Business Group will receive from, for example, 12.345.678.90)

Access Business Group information for sending EDI documents via AS2 or HTTP:

(Does not apply when using a VAN)

Test Server

Host Name: test.e-abg.com

EDI URL:

EDIINT URL:

AS2 – From/To: 00602679398

IP Address From ABG: 167.23.240.24

IP Address To ABG: 167.23.249.122

Production Server

Host Name:

EDI URL:

EDIINT URL:

AS2 – From/To: 00602679322

IP Address From ABG: 167.23.240.24

IP Address To ABG: 167.23.249.54

Test and production certificates will be available upon request.

850 Purchase Order

Functional Group ID=PO

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.

Notes:

Heading:

Pos.Seg.Req.LoopNotes and

No. ID Name Des. Max.Use Repeat Comments

M / 010 / ST / Transaction Set Header / M / 1
M / 020 / BEG / Beginning Segment for Purchase Order / M / 1
040 / CUR / Currency / O / 1
050 / REF / Reference Identification / O / >1
060 / PER / Administrative Communications Contact / O / 3
070 / TAX / Tax Reference / O / >1
080 / FOB / F.O.B. Related Instructions / O / >1
130 / ITD / Terms of Sale/Deferred Terms of Sale / O / >1
240 / TD5 / Carrier Details (Routing Sequence/Transit Time) / O / 12
LOOP ID - N1 / 200
310 / N1 / Name - VENDOR / O / 1
LOOP ID - N1 / 200
310 / N1 / Name - BILL TO / O / 1
330 / N3 / Address Information - BILL TO / O / 2
340 / N4 / Geographic Location - BILL TO / O / >1
LOOP ID - N1 / 200
310 / N1 / Name - SHIP TO / O / 1
330 / N3 / Address Information - SHIP TO / O / 2
340 / N4 / Geographic Location - SHIP TO / O / >1
360 / PER / Administrative Communications Contact - SHIP TO / O / >1
LOOP ID - N1 / 200
310 / N1 / Name - SHIP FROM / O / 1
330 / N3 / Address Information - SHIP FROM / O / 2
340 / N4 / Geographic Location - SHIP FROM / O / >1

Detail:

Pos.Seg.Req.LoopNotes and

No. ID Name Des. Max.Use Repeat Comments

LOOP ID - PO1 / 100000
M / 010 / PO1 / Baseline Item Data / M / 1 / n1
LOOP ID - PID / 1000
050 / PID / Product/Item Description / O / 1
100 / REF / Reference Identification / O / >1
210 / DTM / Date/Time Reference / O / 10
250 / TD5 / Carrier Details (Routing Sequence/Transit Time) / O / 12
LOOP ID - PKG / 200
305 / PKG / Marking, Packaging, Loading / O / 1
LOOP ID - N1 / 200
350 / N1 / Name - SHIP TO / O / 1
370 / N3 / Address Information - SHIP TO / O / 2
380 / N4 / Geographic Location - SHIP TO / O / 1
400 / PER / Administrative Communications Contact - SHIP TO / O / 3
LOOP ID - N1 / 200
350 / N1 / Name - SHIP FROM / O / 1
370 / N3 / Address Information - SHIP FROM / O / 2
380 / N4 / Geographic Location - SHIP FROM / O / 1

Summary:

Pos.Seg.Req.LoopNotes and

No. ID Name Des. Max.Use Repeat Comments

LOOP ID - CTT / 1
010 / CTT / Transaction Totals / O / 1 / n2
M / 030 / SE / Transaction Set Trailer / M / 1

Transaction Set Notes

1.PO102 is required.

2.The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.

Segment:ST Transaction Set Header

Position:010

Loop:

Level:Heading

Usage:Mandatory

Max Use:1

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

Syntax Notes:

Semantic Notes:1The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Comments:

Data Element Summary

Ref.Data

Des. Element Name Attributes

M / ST01 / 143 / Transaction Set Identifier Code / M / ID 3/3
Code uniquely identifying a Transaction Set
850 / Purchase Order
M / ST02 / 329 / Transaction Set Control Number / M / AN 4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Segment:BEG Beginning Segment for Purchase Order

Position:020

Loop:

Level:Heading

Usage:Mandatory

Max Use:1

Purpose:To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates

Syntax Notes:

Semantic Notes:1BEG05 is the date assigned by the purchaser to purchase order.

Comments:

Data Element Summary

Ref.Data

Des. Element Name Attributes

M / BEG01 / 353 / Transaction Set Purpose Code / M / ID 2/2
Code identifying purpose of transaction set
00 / Original
M / BEG02 / 92 / Purchase Order Type Code / M / ID 2/2
Code specifying the type of Purchase Order
NE / New Order
M / BEG03 / 324 / Purchase Order Number / M / AN 1/22
Identifying number for Purchase Order assigned by the orderer/purchaser
The purchase order number will be 3 to 10 characters long.
M / BEG05 / 373 / Date / M / DT 8/8
Date expressed as CCYYMMDD

Segment:CUR Currency

Position:040

Loop:

Level:Heading

Usage:Optional

Max Use:1

Purpose:To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Syntax Notes:1If CUR08 is present, then CUR07 is required.

2If CUR09 is present, then CUR07 is required.

3If CUR10 is present, then at least one of CUR11 or CUR12 is required.

4If CUR11 is present, then CUR10 is required.

5If CUR12 is present, then CUR10 is required.

6If CUR13 is present, then at least one of CUR14 or CUR15 is required.

7If CUR14 is present, then CUR13 is required.

8If CUR15 is present, then CUR13 is required.

9If CUR16 is present, then at least one of CUR17 or CUR18 is required.

10If CUR17 is present, then CUR16 is required.

11If CUR18 is present, then CUR16 is required.

12If CUR19 is present, then at least one of CUR20 or CUR21 is required.

13If CUR20 is present, then CUR19 is required.

14If CUR21 is present, then CUR19 is required.

Semantic Notes:

Comments:1See Figures Appendix for examples detailing the use of the CUR segment.

Data Element Summary

Ref.Data

Des. Element Name Attributes

M / CUR01 / 98 / Entity Identifier Code / M / ID 2/3
Code identifying an organizational entity, a physical location, property or an individual
VN / Vendor
M / CUR02 / 100 / Currency Code / M / ID 3/3
Code (Standard ISO) for country in whose currency the charges are specified

Segment:REF Reference Identification