My Oracle Support Banner

Pending Receive Amount in Parent Account is not Updated With The Due From Child during Bill_now (Doc ID 3063005.1)

Last updated on DECEMBER 11, 2024

Applies to:

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

Symptoms

After upgrading Billing and Revenue Management (BRM) from 12.0 to 15.0.1, during bill_now, the pending receive amount of parent's billinfo is not updated with the child's due.


1. BRM 12 :

D Tue Sep 24 03:52:46 2024 l cm_billing:11051 fm_bill_make_bill_now.c:689 2::custom_queue_manager:11041:-189797568:20504:1727175166:1:root.0.0.0.1:::
  op_bill_make_bill_now return flist
# number of field entries allocated 20, used 2
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 398675 0
0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 3
1 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 400211 5
1 PIN_FLD_LAST_BILL_OBJ POID [0] 0.0.0.1 /bill 351667799028243858 0
1 PIN_FLD_PENDING_RECV DECIMAL [0] 436.50


2. BRM 15 :

D Tue Sep 24 05:36:22 2024 l cm_billing:1764743 fm_bill_make_bill_now.c:694 3::custom_queue_manager:1764736:-113756416:20504:1727181382611363:1:root.0.0.0.1::::-1
  op_bill_make_bill_now return flist
# number of field entries allocated 20, used 2
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 1841600 8
0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 3
1 PIN_FLD_BILLINFO_OBJ POID [0] 0.0.0.1 /billinfo 1840064 0
1 PIN_FLD_LAST_BILL_OBJ POID [0] 0.0.0.1 /bill 351667799029741688 0
1 PIN_FLD_PENDING_RECV DECIMAL [0] 218.25 --> This amount should have been 436.50.

It is observed that BRM 15 is creating two different bill numbers for the same bill poid in the parent's bill_t list. In these two different bill numbers, one of them has the child's bill_now total while other has the parent's bill_now total. Due for each bill_no is different, the parent has a collective due of 327.38. However, in parent's billinfo_obj the pending_recv is only 109.13 as per the child's bill_now result.


STEPS
--------------------
1. Create a parent account
2. Purchase subscription on this parent account. This will create a record in the bill_now_queue - customization is done for this bill_now_queue
3. Create a child account
4. Purchase a subscription on the child account. This will create a record in the bill_now_queue - customization is done for this bill_now_queue

Customization: each purchase creates a record in a custom class called /queue/bill_now. Then a multi-thread application (MTA) will call PCM_OP_BILL_MAKE_BILL_NOW based on the the status in this queue. In this case, the subscription for parent was purchased before the subscription for child, thus the bill_now was called individually for parent and child in the same sequence, i.e. bill_now for parent and then a bill-now for child.

5. Run bill_now for parent
6. Run bill_now for child.



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
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.