Electronic Parts Distribution System (EPDS)     ePDS/Web     ePDS/Ship     ePDS/Counter     ePDS/eData     ePDS/Warehouse     ePDS/CC     ePDS/RFQ     ePDS/Tax     ePDS/Connect Custom Solutions Training Support Workflow Analysis

NOBODY SAYS CHANGE IS EASY… EXCEPT AXIOM’S CLIENTS "If we hadn't invested in ePDS, we would not be where we are today as a top distributor of electronic com- ponents and computer products in the worldwide marketplace.”

ePDS/eData

EPDS Portal for Electronic Data Interchange (EDI)

Overview

The ePDS/EData Processor provides a standard interface between EPDS and other computer systems in order to transfer electronic documents back and forth. Typically, the ePDS/eData Processor is used to facilitate EDI transactions between trading partners (customers and vendors), although it may be used to provide connectivity using other document transmission schemes such as RosettaNet.

When you desire to use EDI with your vendors and/or customers, the ePDS/eData Processor is part of the solution. Axiom Software engineers will work with you and your trading partner to create the EDI interface.

Although this document focuses on the deployment of the ePDS/eData processor to be used to facilitate EDI transmissions, it can be used to connect with other computer systems using other document transmissions schemes.

Details – Trading Information

To implement EDI, you first need to identify your trading partners. These are either customers and/or vendors who wish to electronically exchange information with your company. Then, for each trading partner you need to establish the type of information to be exchanged. Examples of types of information are:

• Purchase Orders

• Invoices

• Shipping Notices

In EDI parlance, each type of information is defined by an ANSI X-12 EDI document or form. Here is a list of some of the commonly used EDI forms:

• 810 Invoice

• 820 Payment Remittance Advice

• 850 Purchase Order

• 855 Purchase Order Acknowledgment

• 856 Advance Ship Notice

• 860 Purchase Order Change

• 861 Receiving Advice

• 865 Purchase Order Change Acknowledgment

• 870 Order Status

Finally, for each form, each trading partner will have their own specific information content requirements. For example, one vendor may require you to always specify a packaging size while others may not care about packaging.

Details – Information Flow

Communication between you and your trading partner typically works like this:

Example 1 – Customer sends purchase order to you.

1. Customer creates purchase order in their ERP computer system.
2. PO data is transmitted to EDI processor software.
3. EDI processor software passes information to EDI Value Added Network (VAN).
4. Your EDI processor software receives PO data from EDI VAN.
5. ePDS/eData Processor picks up data from EDI processor and updates EPDS.
6. You see the purchase order in EPDS as a new Sales Order that has been created via EDI.

Example 2 –You send purchase order to your vendor.

1. You create purchase order in EPDS.
2. PO data is transmitted to EDI processor software.
3. EDI processor software passes information to EDI Value Added Network (VAN).
4. Your EDI processor software receives PO data from EDI VAN.
5. ePDS/eData Processor picks up data from EDI processor and updates EPDS.
6. You see the purchase order in EPDS as a new Sales Order that has been created via EDI.

For more information about the ePDS/eData add-on to ePDS, our flagship Electronic Parts Distribution System, contact us.