Profile Label Is Not Getting Updated In ECE Cache Which Is Resulting In Failure Of CUG Rule/rating.

(Doc ID 2311607.1)

Last updated on SEPTEMBER 28, 2017

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.3.0.3.0 version, Customer data management

Profile Label is not getting updated in ECE cache which is created during the account creation. This is resulting in wrong charges getting getting applied for the call as in the CUG rule there is a check for the label 'CUG_XXXXX' and normal charges are applied. this has been reported on ECE patch 11.3.0.3.5.

Now the label of the special rating profile is not getting updated in the ECE cache.

Profile:

 0.0.0.1 /account 16193581173 0
 0.0.0.1 /service/telco/gsm/telephony 16193583349 0
 0.0.0.1 /profile/serv_extrating 16195153416 0
 Tue Aug 22 14:00:20 AST 2017
 
  CLOSEDUSERGROUP
  Tue Aug 22 14:00:20 AST 2017
  
  
 
  Thu Jan 01 04:00:00 AST 1970
  Thu Jan 01 04:00:00 AST 1970
  
 
ECE cache:

profiles = [RatingProfileImpl{name='CLOSEDUSERGROUP'label='', effectiveTime=1503399620000, ratingProfileValues=[RatingProfileValueImpl{name=cde, value=cde, validFrom=1970-01-01T00:00Z, validTo='+292278994-08-17T07:12:55.807Z}]}]


If we check this entry, the label is blank (label=''), because of this CUG rule is failing and CUG rating is not happening.

ACTUAL BEHAVIOR
---------------
ECE cache updated with the label=''

EXPECTED BEHAVIOR
-----------------------
ECE cache to be updated with the lable='CUG_XXXXX'


Changes

 

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