During Deal Or Plan Transition The Old Non-currency Bucket Validity Date Should Be End Of Cycle (Doc ID 979384.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.0.0.0 to 7.3.0.0.1 - Release: 7.3.0 to 7.3.0
Information in this document applies to any platform.

Symptoms

In a case, where all product fees are configured as prorated with "charge for complete cycle" for cancellation; during plan/deal transition, the non-currency bucket validity date is set as the transition date.

Consider scenario:
  1. Consider a deal-1 that contains a product-1.
  2. Product-1 contains one CF event that grants a NCR 1000095 with amount -1000 and proration setting is "charge for complete cycle" for cancellation. And one Session event which charges amount 1 to that NCR (session event is configured to consume the NCR value). Here "override credit limit" flag is not checked in rateplan.
  3. Product is purchased on 1st Jan10 with a cycle 1st Jan to 1st Feb.
  4. Within 15th Jan, 700 is consumed from the NCR, so remaining balance is -300.
  5. Now deal transition occurred from deal-1 to deal-2 on 15th Jan. (deal-2 does not contain the NCR1000095).

Here during plan/deal transition the non-currency bucket validity date is set as the transition date, but expected is that it should be end of cycle.

Snippet of the bal group obj is pasted below:

Here the bucket end date is set to 15th Jan but expected is 1st Feb.

0 PIN_FLD_BALANCES ARRAY [1000095] allocated 20, used 5
1 PIN_FLD_CONSUMPTION_RULE ENUM [0] 0
1 PIN_FLD_CREDIT_PROFILE INT [0] 2
1 PIN_FLD_NEXT_BAL DECIMAL [0] 0
1 PIN_FLD_RESERVED_AMOUNT DECIMAL [0] 0
1 PIN_FLD_SUB_BALANCES ARRAY [2] allocated 20, used 10
2 PIN_FLD_CONTRIBUTOR_STR STR [0] ""
2 PIN_FLD_CURRENT_BAL DECIMAL [0] 248.4
2 PIN_FLD_DELAYED_BAL DECIMAL [0] 0
2 PIN_FLD_GRANTOR_OBJ POID [0] 0.0.0.1 /purchased_product 1970419 1
2 PIN_FLD_NEXT_BAL DECIMAL [0] 0
2 PIN_FLD_ROLLOVER_DATA INT [0] 0
2 PIN_FLD_VALID_FROM TSTAMP [0] (1262338432) Fri Jan 1 01:33:52 2010
2 PIN_FLD_VALID_FROM_DETAILS INT [0] 1
2 PIN_FLD_VALID_TO TSTAMP [0] (1263542590) Fri Jan 15 00:03:10 2010
2 PIN_FLD_VALID_TO_DETAILS INT [0] 0

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