Payment Allocation is Skipping Cycle Forward but Pays the Usages in a Bill After Partitioning
(Doc ID 2275966.1)
Last updated on OCTOBER 10, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
In Oracle Communications Billing and Revenue Management (BRM), a problem exists where the Payment Allocation is skipping cycle forward, but pays the usages in a bill after partitioning.
Accounts have bills that are still unpaid while the system has not yet partitioned. After partitioning payment allocation to items, user sees the issue. Monthly Service Fees(MSF)/Cycle Forward Items are not being allocated, but usages are allocated and move to the next oldest bill.
The user's scenario: Have Bill #1 and a payment is made, which is then passed through a batch process which calls "PCM_OP_PYMT_COLLECT". The payment initially is unallocated at the billing on the next cycle, which creates Bill #2. The behavior observed is that payment is first allocated on usages of Bill #1 and Bill #2, and then the Cycle Forward items of Bill #1. In case payment exceeds the usages of both bill, apparently those Bill #1 is created prior to partitioning. User created partitioning prior, and then upgrade BRM from Patch Set 5 to Patch Set 13 and Patch Set 16 to Bill #2.
Bill #2 MSF 100 Usage 50
Payment received and allocation: (280)
Bill #1 MSF 0 Usage -150
Bill #2 MSF -100 Usage 20 (-30)
Leaving the first bill have cycle forward items unallocated. Usage charges of both current and old bills are settled of payment (which is found to be prioritized) rather than all items including usages and Cycle Forward Items of the oldest bill would be prioritized.
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