My Oracle Support Banner

Accounts Inherit Parent's BILL_NO After Consolidation Whereas ITEM_NO is Unchanged (Doc ID 759820.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.
Checked for relevance on 19-Aug-2011.
***Checked for relevance on 29-Apr-2013***


-- Problem Statement:

When an account is moved from an individual hierarchy to a group hierarchy, the bill_no in the bill_t table is also changed to match the parent bill_no. Whereas, the item_no are still based on the original bill_no.

-- Steps To Reproduce:

1.  Create an account (eg, account #10000) on July 20 (DOM=20)
2.  Create another account (eg, account #20000 ) on Aug 1 (DOM=1)
3.  Run pin_bill_day on Aug 20 --
     /account #10000 is billed and bill (B1-17) is generated, and item (B1-17,1) is created.
4.  Move /account 10000 into hierarchy on Aug 25 --
     /account 20000 is parent, and /account 10000 is non-paying child
5.  Run pin_bill_day on Sep 1 --
     A bill (B1-19) is generated for /account 20000.

But when running pin_bill_day on Sep 1, bill B1-19 is generated and is updating the same bill poid to bill_t of /account 10000, i.e. BILL_NO is getting updated from B1-17 to B1-19. Whereas, the ITEM_NO still remains as B1-17,1 in the item_t table for this child /account 10000.


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

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