Annual Product Calculated Long Cycles When It Should Not
(Doc ID 1500481.1)
Last updated on JUNE 12, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.5.0.0.0 [Release 7.4.0 to 7.5.0]Information in this document applies to any platform.
Symptoms
Please consider this scenario:
1) Existing account with Billing DOM 3, account creation date can be 05/03/2012 with any annual product.
2) Billing executed on 06/03
3) Order comes in on 06/04 with END_T 06/01 with an annual product,
It is a backdate (06/01) purchase of an annual product before the last bill date (06/03)
4) Tailormade product set dates for the following:
a) 06/01/2012 to 05/03/2013 Proration
b) 05/03/2012 to 06/01/2013 Promotion
Customization code in the policy opcode : Forces short cycle and changes all event_map to 12 months instead of 1 year.
The expected cycle is
06/01/2012 to 05/03/2013 (short cycle)
The actual cycle is
06/01/2012 to 06/03/2012
06/03/2012 to 06/03/2013
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 |