Duplicate Check Rejects Records Incorrectly (Doc ID 1361381.1)

Last updated on APRIL 22, 2013

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 05-Apr-2013***

Symptoms

The FCT_DuplicateCheck module rejects non duplicate records.

The Input file contains three different records. The last one is rejected due to duplicated. (Note: Before test execution, the pipeline was stopped and the duplicate data was cleared)

The duplicate check is configured as follow:

DuplicateCheck
{
   ModuleName = FCT_DuplicateCheck
   Module
   {
      Active = True
      DataConnection = ifw.DataPool.Login
      Path = ./Roaming/data/preprocessGPRS/reject/duplicate
      TableSpaceName = INTEGRATE_TS_1_DAT
      IndexSpaceName = INTEGRATE_TS_1_IDX
      FileName = call.duplicate
      StreamName = DuplicateOutput
      BufferLimit = 20100530 #EDRs dated April 7, 2010 or later are stored in the duplicate check list in memory
      StoreLimit = 20100512 #EDRs dated April 1, 2010 are moved to the IFW_DUPLICATECHECK database table
      SearchKey = DETAIL.A_NUMBER
      Fields
      {
         1 = DETAIL.BASIC_SERVICE
         2 = DETAIL.B_NUMBER
      }
   }
}



The following shows the crucial values for processed records:

A NUMBER       | B NUMBER | BASIC_SERVICE
------------------------------------------------
44000001500898 | 00       | 813
44000001500002 | 00       | 813
44000001500088 | 00       | 813


Expected results:
None of the records should be rejected.

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