Entry_t Date In /collections_scenario Is Not Updated (Doc ID 1400858.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.4.0.0.0 to 7.4.0.0.0 - Release: 7.4.0 to 7.4.0
Information in this document applies to any platform.

Symptoms

Replication Steps

1. Set parameter in CM pin.conf file "- fm_collections old_overdue_behavior 1"
2. Ensure that parameter in pin_collections_process application pin.conf file "- pin_collections_process use_current_time 1" is comment and default value is used.
3. Create collections scenario with
ENTRY_AMOUNT = 0.01,
EXIT_AMOUNT=0.0,
ENTRY_DAYS= 0.
4. 01.06.2011 - Create account with cycle fee(e.g. 500 Euro).
5. 01.07.2011 - run billing (bill B1-1)
6. 01.08.2011 - run billing (bill B1-2)
7. 01.09.2011 - run billing (bill B1-3)
8. 01.10.2011 - run billing (B1-4)
9. 01.10.2011 - run collections process.
10. Ran the following query:

select utl.date_t(entry_t),utl.date_t(overdue_t) from collections_scenario_t where account_obj_id0=xxxxxxxx;

ENTRY_T                       OVERDUE_T
---------------------         --------------------------
31-JUL-12 12:30:00                               31-JUL-12 12:30:00  

11. This is same as the DUE_T of the first bill:

select bill_no,utl.date_t(due_t) from bill_t where account_obj_id0=xxxxxxx;

BILL_NO                     DUE_T
------------------------    -----------------------------
B1-1                        31-JUL-12 12:30:00  


12. Made exact payment of B1-1 and applied it to the bill.

13. Ran the collections process

14. Ran the following query:

select utl.date_t(entry_t),utl.date_t(overdue_t) from collections_scenario_t where account_obj_id0=xxxxxxx;

ENTRY_T                                 OVERDUE_T
-----------------------------       --------------------------
31-JUL-12 12:30:00                  31-AUG-12 12:30:00  


15. Only OVERDUE_T is getting updated to the DUE_T of B1-2 but ENTRY_T is not getting updated.

Entry date to collection scenario is not updated as it should be according to documentation:

BRM Documentation->Managing Payments and A/R->Managing Payments->Collecting overdue balances->Configuring how Collections Manager determines dates->Case 4: Optional setting for overdue date and default setting for entry date

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms