e*Xchange not catching all duplicates (Doc ID 1029428.1)

Last updated on FEBRUARY 10, 2006

Applies to:

Sun B2B - Version: 4.5.3 and later
Information in this document applies to any platform.

Symptoms

When the user sends the same message again, eX_ePM did not catch the duplicate message. From the log file, you will see for the first time when the message is sent:

transmission_key
051219_test_20051117_0027_004010X098A1
IS_DUP
N
for the second time when the same message is sent:

transmission_key
051219_test_20051117_0027_004010X098A1
IS_DUP
N

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms