My Oracle Support Banner

Bill Object Start_t Is Set To Actg_next_t In PS16 (Doc ID 2226986.1)

Last updated on AUGUST 21, 2018

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.15.0 and later
Information in this document applies to any platform.

Goal

Qn1:

Steps to reproduce the issue:
Create an account with any multi month cycle forward plan.
Advance PVT one month and before calling pin_bill_accts, execute the PCM_OP_BILL_MAKE_BILL_NOW.
A bill with $0 total and due is being generated.

In P16:
The bill's START_T is set to whatever ACTG_LAST_T is set to in the billinfo object.

In PS14:
The bill's START_T is set to the date the bill_now opcode was executed.

Please clarify if this is now the expected behavior with PS16?
 
Qn2: 

How does this influence the population for the bill start_t when user created a bill via bill now when regular bill is suppressed?

- Created account on 3/26 with annual cycle product only
- 4/26 ran billing, bill is not suppressed.
- 5/26 executed bill_now opcode for this account which triggered billing.
- Regular bill is suppressed and billinfo object has following values:

..
0 PIN_FLD_ACTG_FUTURE_T TSTAMP [0] (1627272000) Mon Jul 26 00:00:00 2021
0 PIN_FLD_ACTG_LAST_T TSTAMP [0] (1622001600) Wed May 26 00:00:00 2021
0 PIN_FLD_ACTG_NEXT_T TSTAMP [0] (1624680000) Sat Jun 26 00:00:00 2021
...
0 PIN_FLD_ACTUAL_LAST_BILL_T TSTAMP [0] (1622001637) Wed May 26 00:00:37 2021
...
0 PIN_FLD_BILL_ACTGCYCLES_LEFT INT [0] 1
..
0 PIN_FLD_FUTURE_BILL_T TSTAMP [0] (1627272000) Mon Jul 26 00:00:00 2021
0 PIN_FLD_LAST_BILL_OBJ POID [0] 0.0.0.1 /bill 166536 0
0 PIN_FLD_LAST_BILL_T TSTAMP [0] (1619409600) Mon Apr 26 00:00:00 2021
0 PIN_FLD_NEXT_BILL_OBJ POID [0] 0.0.0.0 0 0
0 PIN_FLD_NEXT_BILL_T TSTAMP [0] (1624680000) Sat Jun 26 00:00:00 2021
0 PIN_FLD_NUM_SUPPRESSED_CYCLES INT [0] 1
...


The bill that was generated had


0 PIN_FLD_START_T TSTAMP [0] (1619409764) Mon Apr 26 00:02:44 2021


This matches the last_bill_t


Advance pvt to 6/26 executed bill_now opcode for this account which triggered billing.

Regular bill is suppressed and billinfo object has following values:

...
0 PIN_FLD_ACTG_FUTURE_T TSTAMP [0] (1629950400) Thu Aug 26 00:00:00 2021
0 PIN_FLD_ACTG_LAST_T TSTAMP [0] (1624680000) Sat Jun 26 00:00:00 2021
0 PIN_FLD_ACTG_NEXT_T TSTAMP [0] (1627272000) Mon Jul 26 00:00:00 2021
...
0 PIN_FLD_ACTUAL_LAST_BILL_T TSTAMP [0] (1624680045) Sat Jun 26 00:00:45 2021
...
0 PIN_FLD_BILL_ACTGCYCLES_LEFT INT [0] 1
...
0 PIN_FLD_FUTURE_BILL_T TSTAMP [0] (1629950400) Thu Aug 26 00:00:00 2021
0 PIN_FLD_LAST_BILL_OBJ POID [0] 0.0.0.1 /bill 166536 0
0 PIN_FLD_LAST_BILL_T TSTAMP [0] (1619409600) Mon Apr 26 00:00:00 2021
0 PIN_FLD_NEXT_BILL_OBJ POID [0] 0.0.0.0 0 0
0 PIN_FLD_NEXT_BILL_T TSTAMP [0] (1627272000) Mon Jul 26 00:00:00 2021
0 PIN_FLD_NUM_SUPPRESSED_CYCLES INT [0] 2
...


The bill that was generated by bill_now has the following start_t

0 PIN_FLD_START_T TSTAMP [0] (1622001637) Wed May 26 00:00:37 2021


This no longer matches the last_bill_t on the billinfo profile.

Please explain how this date is calculated based on how the billinfo dates are set?
 

Solution

To view full details, sign in with your My Oracle Support account.

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


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.