Effective_t Set to Future Date for Purchased Discount Is Causing Incorrect Discounting
(Doc ID 2950033.1)
Last updated on AUGUST 20, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.0.0.3.0 version, Pipeline Manager
A tailor made discount is set to start in future for the customer. Billing Day of the Month (BDOM) = 1.
apply_validity_discount_rules is set to 0, i.e. "Parameter values can be 0 (default) indicates discount validity rules will not be applied if the discount purchase/cancel happens exactly on cycle boundaries"
When the discount is purchased, the effective_t of /purchased_discount instance is getting changed to future cycle_start_t as below:
ACTUAL BEHAVIOR
----------------------
When this discount is canceled before future dated cycle_start_t, the effective_t is getting set to current date.
EXPECTED BEHAVIOR
------------------------
The discount validity should not be updated.
This is causing latest record as per effective_t in au_purchased_discount_t to be the one when discount was purchased hence any usage coming after 1st April is getting discounted though it was cancelled.
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 |