Extend and tune your flow configuration > Inbound message validation rules > Validation rules: Duplicate messages tab

Validation rules: Duplicate messages tab

Use the Duplicate messages tab of the Configure message validation rules page to control whether a community accepts or rejects duplicate EDI documents .

Select an option:

Reject duplicate EDI document IDs – Select this if you want Activator to check if an inbound message duplicates a previously received message in the following ways:
- Duplicate control number
- Duplicate sender name
- Duplicate sender routing ID
- Duplicate receiver name
- Duplicate receiver routing ID
If all of these values are the same as those in a previously received message, the message is rejected and given a failed status. You can search for failed messages in Message Tracker.
Activator only checks for duplicates of EDI documents. Specifically, this means documents with the following MIME types:
- application/EDI-X12 (X12 document)
- application/EDIFACT (EDIFACT document)
- application/EDI-consent (TRADACOMS document)
When Activator receives a batch parent document and splits it into multiple child documents, all with the same control number as the parent, Activator does not consider siblings of the same parent to be duplicates. This processing exception accommodates custom EDI splitters that are used in place of the system’s standard EDI splitters.
Allow duplicate EDI document IDs (default) – Select this option to let Activator accept duplicate messages.

Whether you choose to reject or allow duplicate EDI messages, the choice applies to all EDI messages received for the community, unless you define exceptions. You can set up the following exceptions to the duplicates rule setting:

Click Add an exception for a partner to create a partner-specific exception.
Click Add an exception for a category to create an exception for a partner collaboration category. A collaboration category is a group of partners who have common collaboration settings.
Click Add an exception for a trading pickup to create an exception for messages received by the community through a specific community trading pickup.

You can add multiple partners, categories or trading pickups to the exceptions lists. Activator applies the opposite of the selected behavior to any partners, collaboration categories, or trading pickups that display in the exceptions lists.