|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: <Misc> Duplicates Within Envelopes
I have heard of several companies who have dealt with a systems limitation
in this way, constructing a somewhat artificial but unique order identifier,
perhaps PO number + date. This can cause problems for customer service when
the customer calls asking about order status, and also on the invoices/ASNs,
if you forget to perform the inverse function and return only what was sent.
In the particular case Dan was asking about, transaction number + date would
not have been sufficient since the duplicated transactions were received at
the very same time. If a release number were provided, it would indeed be
the ideal solution. Only one of the several trading partners we have who
duplicate PO numbers use release numbers as well, and it helps avoid any
confusion. For the others, we have duplicate checking turned on at the
translator and we visually review them before releasing them, or notifying
the trading partner. As Rita noted in related post, this is only hurting
the trading partner by slowing down the process.
Howard Parks
Master Lock
-----Original Message-----
From: David Frenkel [mailto:
Sent: Tuesday, January 28, 2003 11:43 AM
To: 'EDI-L (E-mail)'
Subject: RE: [EDI-L] <Misc> Duplicates Within Envelopes
Howard,
I realize you can't tell a customer what to do but the ideal way to
handle multiple orders against one PO number is to use release numbers.
Regards,
David Frenkel
Business Development
GEFEG USA
Global Leader in Ecommerce Tools
www.gefeg.com
425-260-5030
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
