Modifying Product By Changing Event Type Results in Unexpected Behavior
(Doc ID 2258092.1)
Last updated on SEPTEMBER 24, 2020
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and laterInformation in this document applies to any platform.
Goal
Consider the following scenarios:
Scenario 1
- Purchase a product with a "Purchase Fee" event tier for an account
- Modify the product by eliminating the "Purchase Fee" event tier and adding a "Monthly Cycle Forward" (MCF) tier with pro-ration enabled and set to "days_remaining" for both pro-rate first/last
- Cancel the product for the account
Scenario 1 Result
- Product is cancelled, no change in the resource balance (from the purchase onward)
- No MCF is generated by the cancel opcode
Scenario 1 Expected Result
- Product is canceled, the resource balance is debited in accordance with the pro-ration
- MCF is generated by the cancel opcode
Scenario 2
- Purchase a product with a "Purchase Fee" event tier for an account
- Modify the product by eliminating the "Purchase Fee" event tier and adding a MCF tier with pro-ration enabled and set to "days_remaining" for both pro-rate first/last
- Advance time until the account bill day
- Cancel the product for the account
Scenario 2 Result
- Product is canceled, and the account somehow winds up with more resources than it started with
Scenario 2 Expected Result
- Product is canceled, the resource balance is debited in accordance with the pro-ration
Solution
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
Goal |
Solution |
References |