Non-paying Child Account When Added In An Existing Hierarchy Doesn't Have Same Billing Cycle
(Doc ID 1908447.1)
Last updated on MARCH 15, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Customer Registration
Non-paying child account when added in a existing hierarchy doesn't have same billing cycle as parent account billing cycle.
Steps to reproduce:
The issue can be reproduced at will with the following steps:
1. Create a parent account on July 20th, its billing cycle is July 20th to Oct 20th [ This account is created via testnap and added PIN_FLD_BILL_WHEN = 3 in input flist.]
2. Create a non-paying child C1 via testnap [ not passed PIN_FLD_BILL_WHEN in input flist]. Its billing cycle July 20th to Oct 20th [ Same has parent]
3. Move pvt 20th Aug. Created another non-paying child C2 via testnap, its billing cycle is Aug 20th to Nov 20th.
C2 account billing cycle end date [ Nov 20th] is not matching with Parent account [ Oct 20th].
C2 account billing cycle end date should match with Parent account.
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