|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: EDI Implementations - Live Data vs. Dummy Data
This is a problem in everyday usage and for nearly every trading
relationship. A proper end-to-end testing regime requires the use of live
data to enable the return of comparable data. A purchase order can't be
verified by an 856 or 810 unless the originator has matching data. Product
tables, destinations, etc., that aren't valid create all kinds of
verification problems. When the time comes to test with your trading
partners you can either fly blind and fix the map interactively, a very bad
practice, or work with actual purchase orders, ship notices, invoices, etc.,
canceling the transactions within the application system. From the
standpoint of establishing good EDI operations the effort involved in
cleaning up the application is more than worth it.
Peter Olivola
708 829 3185
-----Original Message-----
From: [mailto:
Sent: Friday, July 25, 2003 5:12 PM
To:
Subject: [EDI-L] EDI Implementations - Live Data vs. Dummy Data
If anyone has already had to face this road block and would like to share
the verbiage used, please send to me direct.
Basically what I am looking for is the pros and cons of using dummy data
instead of company specific data for an implementation.
[Non-text portions of this message have been removed]
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
