Brochure

Catalog CIC-2003-1/US
Parker — Your Preferred Supplier
Parker Hannifin Corporation
Climate & Industrial Controls Group
Cleveland, OH
13
Parker — Your
Preferred Supplier
connection or through a third-party communications
service. Point-to-point connection is only practical
in businesses that do not deal with multiple trading
partners.
Third-party communication networks or Value-Added
Networks (VANS) eliminate the need for extra hard-
ware, software, telephone connections, or manpower.
Most trading partners find it convenient to use third-
party networks. VANs are service bureau companies
offering mailbox functions to trading partners, allowing
them to receive and transmit their electronic transac-
tions to multiple locations with minimal problems.
For instance, General Electric Information Services
(GEIS) has a VAN called EDI*Express, which has a
local access network to which a person can subscribe
and receive a mailbox. Parker directly subscribes to
several VANs, and all of these third-party service pro-
viders interconnect with virtually all other VANs.
The Role of Database Integration
Now that we have discussed many of the elements in
the structure of EDI, it is important that you have an
understanding of the content found within the EDI
application structure. In other words, the ANSI standards
alone will not fully ensure acceptance of an electronic
document; the data itself must be recognized by the
divisional application system and be
efficiently applied within that system
structure.
What this means is that if the data
transmitted within the ANSI format
does not conform to the divisional
application database, then additional
manual processing would be re-
quired. Since this would defeat the
purpose of EDI, it is mandatory that
trading partners use identical data
(exact part numbers, prices, etc.)
within their EDI processing.
For Original Equipment Manufactur-
ers (OEMs), part numbers and
prices agreed to by trading partner
divisions must be precisely reflected
in the OEM database. In this way,
the customer's database and
Parker's divisional EDI processing
will be tied together with common
data content.
Transactions that have been
implemented within Parker divisions
with various trading partners include
those shown in the table at the right.
EDI (Electronic Data Interchange)Why Parker?
EDI Communication Guidelines
Communication
• Parker uses a dial out capability only. Trading part-
ners do not have the ability to dial into Parker's
mainframe computer.
• Therefore, Parker requires the use of a third-party
network (VAN) service to provide store-and-forward
capability and compliance checking (see page 9for
more information). A listing of Value-Added Net-
works will be provided upon request.
Technical
• A micro, mini, or mainframe computer must be avail-
able to implement EDI.
• The computer must have communication capability;
that is, you must have at least a business telephone
line or the equivalent, as well as a modem.
• Parker communicates in a FTP protocol. The trading
partners may use any protocol compatible with their
selected third-party network.
• Each trading partner must have the ability to com-
municate data in the ANSI X.12 format. Internal use
of the data is user-defined.
• Each trading partner should have sufficient error
detection capability to ensure compliance within
the ANSI X.12 format. Trading partners agree on
specific field requirements within the ANSI format.
NOTE: Not all transactions are applicable to all trading partnerships.
ANSITrans EDIFACT Trans Send Receive
152 * Statistical Government Information GR X
810 INVOIC Invoice IN X X
820 REMADV Remittance Advice RA X
824 APERAK Application Advice AG X X
830 DELFOR Material Release PS X X
832 PRICAT Price/Sales Catalog SC X
836 * Contract Award RQ X
838 PARTIN Trading Partner Profile TD X
840 REQQTE Request For Quote RQ X
841 QLSPEC Tech Specifications SP X X
842 NONCON Non conformance Report NC X
843 QUOTES Response to RFQ RR X
846 INVINQ Inventory Inquiry/Advice IB X X
850 ORDERS Purchase Order PO X X
853 * Carrier Routing RI X
855 ORDRSP PO Acknowledgment PR X X
856 DESADV or PRODEX Advance Shipment Notification SH X X
860 ORDCHG PO Change PC X
861 RECADV Receiving Advice RC X
862 DELJIT Shipping Schedule SS X
863 QALITY Quality Reporting RT X
864 GENRAL Text TX X
865 ORDRSP PO Change Acknowledgment CA X
867 PROTRA Product Transfer and Resale Report PT X
869 OSTENQ Order Status Inquiry RS X
870 OSTRPT Order Status Report RS X
997 CONTRL Functional Acknowledgment FA X X
Name