Validity Is Not Set Correctly For 3 Month In-Advance Cycle Forward
(Doc ID 2277669.1)
Last updated on FEBRUARY 21, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.15.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Billing and Revenue Management (BRM) a problem exists with 3 Month In-Advance Cycle Forward (CF) products where the validity is not set correctly.
For example:
There is a requirement to capture 3 months rental (CF) in advance. In trying to do so, configure a charge offer with ChargeDetails "In Advance Billing" attribute to "Charge Cycle Fees" 3 months in advance value. In balance impacts, "Amount is Valid" attribute is set with value as "From event Occurrence - 1 Accounting Cycle(s) from Validity Start".
When this product is purchased, there will be one CF event for the current month and one more event to cover the 3 months advance rental. This advance event has a start date equal to next accounting cycle start date and end date set exactly for one accounting cycle only from start. However, this should have validity of this 3 months freeUnit valid for 3 accounting cycles.
It is expected that the resource should be valid for 3 accounting cycles
Cause
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
Symptoms |
Cause |
Solution |
References |