Getting Incorrect Validity Time Error When Plan Is About To Expire
(Doc ID 2880924.1)
Last updated on JULY 25, 2022
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Noticed that when user plan is going to expire, that is product and discount validity is going to expire and just before that if any new sessions comes or any update comes of existing session ,then the validity time going in response is crossing the expiration time of product and discount, which is not expected.
Validity time is going such that it is crossing the 12AM.
Here buckets/grants are not getting expired but usage products and discounts are getting expired.
Validity time should go such that usage is allowed till 12AM only.
The issue can be reproduced at will with the following steps:
1. Create a account with a plan which is getting expired at 13th March 2022 at 00:00:00 .
2. Default Validity Time is 3600 sec (1 hour).
3. Initiate a session somewhere between 11PM to 12AM of 12th March ,for example: 12th March 2022 23:30:00 PM.
4. Verify the response.
Query:How to overcome this behaviour?
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