Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
***Checked for relevance on 29-Aug-2014***
An account (owning several thousands product with cycle fees) has an unexpected billinfo status,
with respect to the cycle events found on DB.
The /billinfo has the accounting dates updates such as billing has been completed:
0 PIN_FLD_ACTG_FUTURE_T TSTAMP  (1243807200) Mon Jun 01 00:00:00 2009
0 PIN_FLD_ACTG_LAST_T TSTAMP  (1240217522) Mon Apr 20 10:52:02 2009
0 PIN_FLD_ACTG_NEXT_T TSTAMP  (1241128800) Fri May 01 00:00:00 2009
0 PIN_FLD_ACTUAL_LAST_BILL_OBJ POID  0.0.0.1 /bill 5983552805 0
0 PIN_FLD_ACTUAL_LAST_BILL_T TSTAMP  (0) <null>
On the other hand, searching for the account's cycle event records, none have an earning range (earned-start/end dates) corresponding to the one expected for the closed billing period.
For example, products have 2 month advance billing, but with the query in the following (Which
returns no rows) it's been verified that all products purchased BEFORE 01-Apr-09 are missing the
expected June cycle period:
from event_t ee, event_bal_impacts_t ebi
where ebi.ACCOUNT_OBJ_ID0 = 4099777401
and ee.POID_ID0 = ebi.OBJ_ID0
and ee.CREATED_T > 1238536800
and ee.POID_TYPE = '/event/billing/product/fee/cycle/cycle_forward_monthly'
and ebi.IMPACT_TYPE = 1
group by ebi.OFFERING_OBJ_ID0
having count(*) < 2 ;
Note that the account billing was suspended, on Apr 1st, then resumed on Apr 20th. Resuming
billing hasn't created any new event (indeed it was an instant step), but it did update the
In particular, the following are the steps performed on a test environemnt an account to reproduce this problem.
1) account creation (e.g. on pin_virtual_time = 24 Mar 2009), with billing DOM=24, including a 1-month advance Cycle Forward Fee, account-level deal
2) product purchased, before Apr 1st
3) billing suspension (Apr 30th) with PCM_OP_BILL_SUSPEND_BILLING
4) make_bill triggered (May 25th)
5) updating actg_next_t as follows::
actg_next_t = 1262304000 , ' Fri Jan 1 00:00:00 2010
actg_future_t = 1262304000 , ' Fri Jan 1 00:00:00 2010
billing_state = 2 , ' PIN_ACTG_CYCLE_ALL_CHARGES_DONE
billing_status = 1 , ' PIN_BILL_INACTIVE
billing_status_flags = 128 ' PIN_BILL_FLAGS_DUE_TO_CUSTOMER_REQUEST
account_obj_id0 = <account poid>;
(NB - original values were backed-up, first)
6) Other products purchased, during April
7) Reverted step 5, by setting backed-up values
8) resumed billing (PCM_OP_BILL_RESUME_BILLING)
After step 8, no new Cycle Forward event was generated, but actg_next_t was updated to Jun 24th.
This is similar to the status where the account in production is found, at the moment.
In the test environment where the above scenario has been replicated, the following is the list of Cycle Forward events of the account after this stage:
4026914 24-Apr-09 16:23:32 1.00000 9.95 24-Apr-09 01:00:00 24-May-09 01:00:00 Automatic Account Creation
4026914 24-Apr-09 16:23:33 1.00000 9.95 24-May-09 01:00:00 24-Jun-09 01:00:00 Automatic Account Creation
4023651 30-Apr-09 13:00:32 0.80000 7.96 30-Apr-09 01:00:00 24-May-09 01:00:00 Customer Center
4023651 30-Apr-09 13:00:33 1.00000 9.95 24-May-09 01:00:00 24-Jun-09 01:00:00 Customer Center
4030242 30-May-09 13:00:27 0.80645 8.02 30-May-09 01:00:00 24-Jun-09 01:00:00 Customer Center
4030242 30-May-09 13:00:27 1.00000 9.95 24-Jun-09 01:00:00 24-Jul-09 01:00:00 Customer Center
4027040 10-Jun-09 13:13:19 0.45161 4.49 10-Jun-09 01:00:00 24-Jun-09 01:00:00 Customer Center
4027040 10-Jun-09 13:13:19 1.00000 9.95 24-Jun-09 01:00:00 24-Jul-09 01:00:00 Customer Center
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms