Filtering to eliminate processing of duplicate items

A UCCnetMessageReceive collaboration object filters Catalogue Item Notifications with NEW_ITEM, DATA_CHANGE, WITHDRAW, or DE_LIST commands to ensure that they are not duplicate items.

Process flow

During normal item processing, a UCCnetMessageReceive collaboration object enables persistence of the UCCnetGBO_envelope business object to a local identifier store by converting it to a UCCnetGBO_identifier business object and passing it to its ToIdentifier_Store port. This port is connected to an IdentifierStore collaboration object. The IdentifierStore collaboration object performs the actual storage operation. See Persisting or deleting an item to or from a local identifier store.

Before sending the object to this port, the collaboration object checks the value of its FILTER_DUPLICATE configuration property. If the value is true (which is the default value), the collaboration object checks if an item with identical key attribute values exists in the identifier store.

If you are processing DTDs the keys are the gtin, version, and topic attributes.

If you are processing XSDs, the keys are the gtin, topic, dataRecipientGLN, dataSourceGLN, targetMarket and uniqueCreatorID attributes.

If an identical item does exist, the second entry with identical information is logged as a duplicate and further processing of it ends. If an identical item does not exist, the item is added to the local identifier store and processed normally.

Parent topic: Filtering publication requests before business processing