My Oracle Support Banner

Excess Discount Application After Its Backdated Modification (Doc ID 2330795.1)

Last updated on DECEMBER 19, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 7.5.0.16.0 version, Subscription Management

ACTUAL BEHAVIOR
---------------
Prorating is not working properly after backdated modification of discount end_t (decrease).
There is excess discount application for cycle.

EXPECTED BEHAVIOR
-----------------------
After this action,excess discount (-17.5) is observed on cycle from 1.2.2017 to 1.3.2017 on gl_id 123456789.

Events for cycle 1.2.2017 to 1.3.2017 with gl_id = 123456789
302550415608073819 17,5
302568007794068090 -17,5
302585599980096244 17,5
302585599980096244 -17,5
302585599980096268 -17,5
after sum they give -17.5 but for this cycle there should be 0 for this gl_id.

STEPS
-----------------------
1. (1.1.2017) Create account
2. (1.1.2017) Purchase product1 with cyclic proratable fee = 40,98 (gl_id=500001321) and start_t = 1.1.2017
    (1.1.2017) Purchase product2 with cyclic non proratable (on open and close) cyclic charge fee = 17.5 (gl_id=123456789) with start_t = 1.1.2017 and end_t = 1.3.2017
    (1.1.2017) Purchase discount1 non proratable (on open and close) which discounts -100% product1 start_t = 1.1.2017 and end_t = 1.3.2017
3. (2.2.2017) Perform billing
4. (2.2.2017) Purchase discount2 with -100% on product1 and product2 with start_t = 1.1.2017
5. (3.2.2017) Change end_t of product2 and discount1 to 15.1.2017

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.