Incorrect Charged_to Set When Product Configured as 1 Month Valid in Deal Customization

(Doc ID 2294092.1)

Last updated on MAY 09, 2018

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.6.0 version, Subscription Management

With charged_to set to 28th Feb, when running daily billing job (pin_cycle_fee), it charged end users from 28th Feb - 2nd March.
i.e It charged twice, 20th Jan - 28th Feb and  28th Feb - 2nd March, which is wrong.


ACTUAL BEHAVIOR  
--------------------
/purchased_product.purchased_end_t=> 2nd March
/purchased_product.cycle_end_t => 2nd March
/purchased_product.usage_end_t => 2nd March
/purchased_product. charged_to_t => 28th Feb
/balance_group.valid_to for non_currency is set to => 2nd March.

EXPECTED BEHAVIOR
-----------------------
/purchased_product.charged_to should be set to the same as /purchased_product.purchase_end_t  =>  2nd March


STEPS
-----------------------
Pricing configuration:
- create a deal with 1 month validity
- create a product with not aligned to bill cycle and no proration settings.

On Jan 30, purchase the above deal/product, and verify the following:
 - /purchased_product.purchase_end_t  =>  2nd March
 - /purchased_product.charged_to   => 28th Feb
 - /balance_group.valid_to for non_currency set to => 2nd March.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms