Discount With Cycle Validity Flags 3 Is Triggered on Cyclic Event
(Doc ID 1591494.1)
Last updated on OCTOBER 01, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]Information in this document applies to any platform.
Symptoms
A discount with all cycle validity flags set to 3 ("No discount") is triggered on cyclic event at the moment of purchasing the deal.
Steps to reproduce the problem:
1. Create account with billing day set to 1.
2. Create service S1.
3. Purchase product P1.
4. Purchase discount D1 on product P1. Discount D1 has all cycle validity PIN_FLD_DISCOUNT_FLAGS set to 2 ("prorate"). Discount D1 has mode PIN_DISC_MODE_CASCADING.
5. Perform billing.
6. 1 day before next billing date, purchase discount D2 on product P1. Discount D2 has all cycle validity PIN_FLD_DISCOUNT_FLAGS set to 3 ("No discount"). Discount D2 has lower priority than discount D1. Discount D2 has mode PIN_DISC_MODE_SEQUENTIAL.
7. Perform billing.
From Billing and Revenue Management (BRM) documentation:
enum PIN_FLD_DISCOUNT_FLAGS
Not Applicable - 0, full discount - 1, prorate - 2, No discount - 3.
Undesired behaviour observed:
Purchasing discount D2 triggers undesired event with discount D1 prorated for 1 day.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |