FCT_Aggregate Generates The Incorrect Aggregation Results. (Doc ID 1415045.1)

Last updated on OCTOBER 03, 2013

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.0.0 [Release 7.4.0]
Information in this document applies to any platform.
***Checked for relevance on 03-Oct-2013***

Symptoms

File with aggregation results contains incorrect data.

Current results:

00001000004568;20111122;20111220;PINUNIT-LOGIN:8832:14438231011133260;1
;20111122;20111220;PINUNIT-LOGIN:8832:14438231011133260;1
;20111122;20111220;PINUNIT-LOGIN:8832:14438231011133260;2


Expected results:

00001000004568;20111122;20111220;PINUNIT-LOGIN:8832:14438231011133260;3


Steps to reproduce:

  1. Create aggregation scenario CDR_003 with following configuration
    a) Grouping fields
         - DETAIL.CUST_A.ACCOUNT_NO
         - DETAIL.CUST_A.BILL_LAST_DATE
         - DETAIL.CUST_A.BILL_NEXT_DATE
         - DETAIL.CUST_A.PRODUCT.SERVICE_LOGIN
    b) Field: DETAIL.RECORD_NUMBER
        Aggregation Function: Count
    c) Condition: none (aggregate all records)
  2. Rate 3 CDRs via Pipeline
  3. Verify aggregation results

Please find the aggregation scenario configuration as attached (CDR_003.xml).

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