Rating Behaviour Due To Wrong Credit Floor
(Doc ID 2721867.1)
Last updated on OCTOBER 26, 2020
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Rating business logic
User are seeing issues in rating when the wrong credit floor is set. There is a fair usage limit for EU roaming which was 20GB and in recent release it is increased to 50GB.
In production, the credit floor was set as 20GB for existing accounts but during this increase in fair usage limit, the credit floor is not increased to 50GB. So customer balance has got 50GB fair usage limit with 20GB as credit floor. With this configuration, user see the reservation behavior is not proper.
Issue 1: when the usage started, there is a new balance impact created.
Issue 2: When the used units is passed and if the USU is less than the GSU then, it completely consumes 50GB. Here USU is like 10KB.
Issue 1: It should consuming from existing bucket.
Issue 2: It should consume USU passed value.
The issue can be reproduced at will with the following steps:
1. Create account having balance 20GB fair usage limit with 20GB as credit floor.
2. Pass the usage of 10 KB
3. Change the balance 50GB fair usage limit and leave the credit floor to 20 GB
Workaround : Data fix to set the credit floor.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document