Start Billing Cycles After The Event Occurs Does Not Work

(Doc ID 863604.1)

Last updated on JULY 15, 2011

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.0.0.1 to 7.3.0.0.1 - Release: 7.3.0 to 7.3.0
Information in this document applies to any platform.
Checked for relevance on 15-Jul-2011

Symptoms

When configuring pipeline discount balance impact in pricing center. It does not make the granted resource available for consumption in a future billing cycle.

For example:
When enter 2 for the number of billing cycles to wait before the resource is consumable (impacted), it is expected the resource is impacted only after two "Billing Cycles after event occurs", but the actual result is the resource got impacted right after the first billing.

-- Steps To Reproduce:
1. Create a simple GSM TEL with freeSecond (ResourceID = 1000095) = 36
2. Create a billing time discount deal call "PROTO - Dropped Call Transfer -
Portal" with Discount Model = "DrCallBTD"
- Discount Trigger is Alway True (e.g. 1 > 0)
- Discount Rule:
Drum Expression = 1
Rule Type = Tiered
Drum Type = Quantity
- Discount Step:
Threshold From = 0
Threshold To (Expression) = Bal(1000095)
- Impact/Consume:
Impact/Consume = 1000001
Applied To: Event Owner
Percentage = -100%
Impact/Start: Billling Cycles after the event occurs = 2
3. Restart the system
4. Create an account with the GSM TEL on May 10
5. Purchase the disocunt deal for the account
6. Verifiy the balance group:
0 PIN_FLD_POID POID [0] 0.0.0.1 /balance_group 3025789 2
...
0 PIN_FLD_BALANCES ARRAY [978] allocated 20, used 5
1 PIN_FLD_CONSUMPTION_RULE ENUM [0] 0
1 PIN_FLD_CREDIT_PROFILE INT [0] 3
1 PIN_FLD_NEXT_BAL DECIMAL [0] 0
1 PIN_FLD_RESERVED_AMOUNT DECIMAL [0] 0
1 PIN_FLD_SUB_BALANCES ARRAY [0] allocated 20, used 10
2 PIN_FLD_CONTRIBUTOR_STR STR [0] ""
2 PIN_FLD_CURRENT_BAL DECIMAL [0] 10
2 PIN_FLD_DELAYED_BAL DECIMAL [0] 0
2 PIN_FLD_GRANTOR_OBJ POID [0] 0.0.0.1 /purchased_product 3023613 0
2 PIN_FLD_NEXT_BAL DECIMAL [0] 0
2 PIN_FLD_ROLLOVER_DATA INT [0] 0
2 PIN_FLD_VALID_FROM TSTAMP [0] (1241938800) Sun May 10 00:00:00 2009
2 PIN_FLD_VALID_FROM_DETAILS INT [0] 0
2 PIN_FLD_VALID_TO TSTAMP [0] (0) <null>
2 PIN_FLD_VALID_TO_DETAILS INT [0] 0
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] 36
2 PIN_FLD_DELAYED_BAL DECIMAL [0] 0
2 PIN_FLD_GRANTOR_OBJ POID [0] 0.0.0.1 /purchased_product 3023613 0
2 PIN_FLD_NEXT_BAL DECIMAL [0] 0
2 PIN_FLD_ROLLOVER_DATA INT [0] 1073807360
2 PIN_FLD_VALID_FROM TSTAMP [0] (1241938800) Sun May 10 00:00:00 2009
2 PIN_FLD_VALID_FROM_DETAILS INT [0] 0
2 PIN_FLD_VALID_TO TSTAMP [0] (1244617200) Wed Jun 10 00:00:00 2009
2 PIN_FLD_VALID_TO_DETAILS INT [0] 0

7. Set PVT = June 10, and run billing:
nap(14902)> robj - $DB /balance_group 3025503
# number of field entries allocated 20, used 15
0 PIN_FLD_POID POID [0] 0.0.0.1 /balance_group 3025503 8
...
0 PIN_FLD_BALANCES ARRAY [978] allocated 20, used 5
1 PIN_FLD_CONSUMPTION_RULE ENUM [0] 0
1 PIN_FLD_CREDIT_PROFILE INT [0] 3
1 PIN_FLD_NEXT_BAL DECIMAL [0] 0
1 PIN_FLD_RESERVED_AMOUNT DECIMAL [0] 0
1 PIN_FLD_SUB_BALANCES ARRAY [0] allocated 20, used 10
2 PIN_FLD_CONTRIBUTOR_STR STR [0] ""
2 PIN_FLD_CURRENT_BAL DECIMAL [0] 30
2 PIN_FLD_DELAYED_BAL DECIMAL [0] 0
2 PIN_FLD_GRANTOR_OBJ POID [0] 0.0.0.1 /purchased_product 3023711 0
2 PIN_FLD_NEXT_BAL DECIMAL [0] 0
2 PIN_FLD_ROLLOVER_DATA INT [0] 0
2 PIN_FLD_VALID_FROM TSTAMP [0] (1239346800) Fri Apr 10 00:00:00 2009
2 PIN_FLD_VALID_FROM_DETAILS INT [0] 0
2 PIN_FLD_VALID_TO TSTAMP [0] (0) <null>
2 PIN_FLD_VALID_TO_DETAILS INT [0] 0
0 PIN_FLD_BALANCES ARRAY [1000001] allocated 20, used 6
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 [6] allocated 20, used 10
2 PIN_FLD_CONTRIBUTOR_STR STR [0] ""
2 PIN_FLD_CURRENT_BAL DECIMAL [0] -36
2 PIN_FLD_DELAYED_BAL DECIMAL [0] 36
2 PIN_FLD_GRANTOR_OBJ POID [0] 0.0.0.1 /purchased_discount 3046375 0
2 PIN_FLD_NEXT_BAL DECIMAL [0] 0
2 PIN_FLD_ROLLOVER_DATA INT [0] 0
2 PIN_FLD_VALID_FROM TSTAMP [0] (1241938800) Sun May 10 00:00:00 2009

2 PIN_FLD_VALID_FROM_DETAILS INT [0] 0
2 PIN_FLD_VALID_TO TSTAMP [0] (1244617200) Wed Jun 10 00:00:00 2009
2 PIN_FLD_VALID_TO_DETAILS INT [0] 0
...
Expect Result:
ResourceID 1000001 is not impacted

Actual Result:
ResourceID 1000001 is impacted with PIN_FLD_VALID_FROM/TO = May 10/June 10



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