My Oracle Support Banner

Incorrect Alignment Of Child Account Cycle In Case Of Quarterly Billing (Doc ID 2536795.1)

Last updated on MAY 06, 2019

Applies to:

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

Symptoms

SCENARIO:

1> Create parent account (ACC_P) using op_cust_commit_customer on Dec 19 with billinfo (BI_P)
2> Create service BS1 (ex : /service/telco/gsm/telephony ) using op_cust_modify_customer for parent account with new billinfo (BI_1), bill_when 3 and effective_t = Oct 1
3> Create service BS2 (ex : /service/telco/gsm/sms ) using op_cust_modify_customer for parent account with new billinfo (BI_2), bill_when 3 and effective_t = Oct 1
4> Create service BS3 (ex : /service/telco/gsm/telephony ) using op_cust_modify_customer for parent account with new billinfo (BI_3), bill_when 1 and effective_t = Dec 1
5> Create service BS4 (ex : /service/telco/gsm/sms) using op_cust_modify_customer for parent account with new billinfo (BI_4), bill_when 1 and effective_t = Dec 1
6> Create service(child) account (ACC_C) on Dec 19 with billinfo (BI_C), parent_billinfo = BI_P and ar_billinfo = BI_P
7> Create service BS5 (ex : /service/telco/gsm/telephony ) using op_cust_modify_customer for child account with new billinfo (BI_5), bill_when 3 and parent_billinfo = BI_1 and ar_billinfo = BI_1 and effective_t is same as the effective_t of BI_1 i.e. Oct 1
8> Create service BS6 (ex : /service/telco/gsm/sms ) using op_cust_modify_customer for child account with new billinfo (BI_6), bill_when 3 and parent_billinfo = BI_2 and ar_billinfo = BI_2 and effective_t is same as the effective_t of BI_2 i.e. Oct 1

ACTUAL BEHAVIOR

Incorrect alignment of child account cycle in case of quarterly billing cycle. See below:

For Parent BI_1 and BI_2

PIN_FLD_LAST_BILL_T -> Oct 1 00:00:00 2018
PIN_FLD_NEXT_BILL_T -> Jan 1 00:00:00 2019
PIN_FLD_FUTURE_BILL_T -> Apr 1 00:00:00 2019

For child BI_5 and BI_6 :

PIN_FLD_LAST_BILL_T -> Oct 1 00:00:00 2018
PIN_FLD_NEXT_BILL_T -> Mar 1 00:00:00 2019 ------> incorrect
PIN_FLD_FUTURE_BILL_T -> Jun 1 00:00:00 2019 ------> incorrect

EXPECTED BEHAVIOR

For child BI_5 and BI_6 :

PIN_FLD_LAST_BILL_T -> Oct 1 00:00:00 2018
PIN_FLD_NEXT_BILL_T -> Mar 1 00:00:00 2019 ------> incorrect, it should be Jan 1 00:00:00 2019
PIN_FLD_FUTURE_BILL_T -> Jun 1 00:00:00 2019 ------> incorrect, it should be Apr 1 00:00:00 2019

That is, it is expected that the BI_5 and BI_6 dates should be same as BI_1 and BI_2, aligned with the parent.

Changes

 

Cause

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
Symptoms
Changes
Cause
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.