Error While Setting Promise to Pay Action
(Doc ID 2361075.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Collection Manager
All promise to pay actions are in closed status in BRM, but still there were below error while setting Promise to pay action:
The issue can be reproduced at will with the following steps:
1. Create an account, generate bill
2. Move the pvt to due date of bill and run pin_collections_process so that the account enters collections
3. Invoke promise to pay on same date
4. Move the pvt due date+few sec/mints of promise to pay and run pin_collections_process
Since account has not made any payment, it will be a promise to pay breach, the status of promise to pay action should set as completed and call PCM_OP_COLLECTIONS_REVOKE_PROMISE_TO_PAY, which cancels all outstanding payment milestones and reschedules collections scenario actions to start from the following day and updates the scenario object.
It gives error when trying to call second promise to pay.
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