|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: EDIINT - duplicate IDs/Digests?
Rich,
This is the way I handle the whole situation.
1. My VAN (IDX2) blocks all duplicates inbound or outbound. That was MY
choice at account setup time. I can override if I deem the "payload" is
something I haven't received.
2. Depending on situation, I either resend an envelope or process the
"payload" to be resent in a different envelope. I do this because some
trading partners are like me in that they don't accept duplicates as the
rule.
3. I can go to my VANs website tracker page and reprocess through the VAN
any envelope I wish to receive or resend to my trading partner.
Dan Mehlhorn
Crescent Electric Supply Co.
-----Original Message-----
Which is the more common practice (and which is the compliant practice) for
EDIINT message failures - resend a message with duplicate Message IDs and
Message Digests, or make them always unique?
We are receiving duplicates, and our WebMethods installation is refusing to
open the payloads because the original message failed (for an unknown
reason) and the re-send from the trading partner is a duplicate as far as WM
is concerned. The trading partner refuses to resend the document using a
different ID and digest, so here we sit; with a payload that is for all
intents and purposes useless.
The trading partner maintains that "it's standard practice to resend the
same message until an MDN is received" and our team is saying of course "we
are not so sure resending message IDs and message digests is standard
practice in AS2."
The finger pointing game begins.
Any opinions? All I want is my lousy data.
Rich Hurd
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
