Patch 6169162 Has A Problem With Sponsor Item (Doc ID 840297.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.0.0.0.1 to 7.0.0.1.0 [Release 7.0.0]
Oracle Solaris on x86 (32-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Checked for relevance on 20-Mar-2013

Symptoms

After installing <Patch 6169162>, Billing time discount has 0 balance impact for the counter resource after billing.

Extracted from good log, when validity dates of the Grant buckets are aligned on 00:00:00 with cutoff time, the opcode RATE_AND_DISCOUNT works fine:

1 PIN_FLD_BALANCES ARRAY [500003] allocated 20, used 4
2 PIN_FLD_RESERVED_AMOUNT DECIMAL [0] 0
2 PIN_FLD_NEXT_BAL DECIMAL [0] 0
2 PIN_FLD_CREDIT_PROFILE INT [0] 0
2 PIN_FLD_SUB_BALANCES ARRAY [3] allocated 20, used 7
3 PIN_FLD_CONTRIBUTOR_STR STR [0] "0.0.0.1 /service/telephony 2073089373"
3 PIN_FLD_VALID_TO TSTAMP [0] (1241128800) Fri May 01 00:00:00 2009
3 PIN_FLD_VALID_FROM TSTAMP [0] (1238536800) Wed Apr 01 00:00:00 2009
3 PIN_FLD_CURRENT_BAL DECIMAL [0] 1000
3 PIN_FLD_NEXT_BAL DECIMAL [0] 0
3 PIN_FLD_DELAYED_BAL DECIMAL [0] 0
3 PIN_FLD_ROLLOVER_DATA INT [0] 0

Extracted from problematic log, when validity dates of the buckets are not aligned on cut-off time, as i.e. 02:00:00, the opcode RATE_AND_DISCOUNT is called with resource amount to zero, so BT discount is not applied. 

2 PIN_FLD_BALANCES ARRAY [500003] allocated 20, used 4
3 PIN_FLD_RESERVED_AMOUNT DECIMAL [0] 0
3 PIN_FLD_NEXT_BAL DECIMAL [0] 0
3 PIN_FLD_CREDIT_PROFILE INT [0] 0
3 PIN_FLD_SUB_BALANCES ARRAY [3] allocated 20, used 7
4 PIN_FLD_CONTRIBUTOR_STR STR [0] "0.0.0.1 /service/telephony 2073089373"
4 PIN_FLD_VALID_TO TSTAMP [0] (1241136000) Fri May 01 02:00:00 2009
4 PIN_FLD_VALID_FROM TSTAMP [0] (1238544000) Wed Apr 01 02:00:00 2009
4 PIN_FLD_CURRENT_BAL DECIMAL [0] 1000
4 PIN_FLD_NEXT_BAL DECIMAL [0] 0
4 PIN_FLD_DELAYED_BAL DECIMAL [0] 0
4 PIN_FLD_ROLLOVER_DATA INT [0] 0

The issue seems to be coming from granted resources by IFW (discounting time), with wrongly shifted buckets validity dates. It worked before the patch, but it doesn’t work anymore.


How to reproduce the issue:

  1. Configure the IFW with an iscript that shifts EDR.UTC_TIME_OFFSET of an hour or two hours. 
  2. Create an account with BDOM =1, subscribe to the offer with both Usage discount, Billing Time discounts. 
  3. Rate a pipeline ticket, with the usage discount that credits the tracker (Say 5000003). 
  4. Change virtual time to BDOM. 
  5. Run billing (trigs Billing Time discount) 
  6. Checks the call PCM_OP_RATE_AND_DISCOUNT, the amount resource 500003 used (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