on ‎2014 Jul 22 6:06 PM
Hi B2B'ers,
Is there a standard way to ignore or reject duplicate interchanges received from a trading partner? Which also includes sending back a functional acknowledgement with information of the same?
Or is this something we have to implement by ourselves?
Best regards,
Jacob
Request clarification before answering.
Hello Jacob,
This is exactly what we just implemented for SP04 release. Here's how it will work:
In the EDI separate receiver adapter, you will get new configuration options to decide at what level you want to determine the duplicate: Interchange (ISA or UNB segment level) / Group (GS segment) / Transaction Set or Message (ST or UNH segment). You also get to specify how long do you want the system remember the interchanges (30 days, 1 year....). Also, you get to specify what to reject when there is a duplicate detected (based on duplicate detection level, of course) - complete interchange, individual groups or individual messages.
Once the duplicate is detected, based on the rejection level, the interchange is completely rejected or partially / fully allowed to be split and forwarded. An appropriate acknowledgement is returned (997 or CONTRL).
If you are, however, exchanging only single message (and not batch messages) in an interchange, your configuration becomes simpler.
I hope this fits your requirement.
Disclaimer: The above description is not a commitment yet and might be subject to change.
Best regards,
Prashantha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Harish,
AS2 duplicate check will work in this scenario only if there is a 1:1 relationship between AS2 message ID and the EDI Interchange. AS2 duplicate check works based on AS2 message IDs that are exchanged between two partners and has no direct relatioship to EDI interchange.
Regards,
Prashantha
| User | Count |
|---|---|
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.