PCM_OP_COLLECTIONS_CALC_AGING_BUCKETS Issue Due To SR 3-16323836501
(Doc ID 2384639.1)
Last updated on APRIL 26, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management (BRM) version 22.214.171.124.0, Collections Manager (CM):
PCM_OP_COLLECTIONS_CALC_AGING_BUCKETS is calculating the wrong due amounts in a scenario. When an account has two billinfos (where one is paying and the other is a non-paying billinfo), the aging due is getting calculated wrongly. The aging due is doubled.
For example, Account A1 has two billinfos (B1 and B2) where B1 is paying and B2 is non-paying.
If the usage of $100 is posted on B1 and B2. The bill generated on B1 would be $200 as it is paying for both B1 ($100) and B2 ($100). When aging info is executed for the account, it shows $300 but the expected amount is $200.
OP_COLLECTIONS_CALC_AGING_BUCKETS should return the total due amount of the actual charges of the paying and non-paying billinfos.
The issue can be reproduced at will with the following steps:
1. Create an account A1
2. Create two billinfos (B1 and B2) one paying and another non paying with subordinate paytype 10007. The AR billinfo for the non-paying account should point to billinfo 1 (B1).
3. Create usage on B2 like $100 charge.
4. Bill the account.
5. Move the PVT after due date and run the opcode PCM_OP_COLLECTIONS_CALC_AGING_BUCKETS.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!