Promise To Pay Arrangement Is Not Consistent
(Doc ID 2091969.1)
Last updated on MARCH 21, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 7.5 PS11 version, Collections Manager
P2P (promise to pay) arrangement is not consistent and the following issues in P2P arrangement using Collection center 7.5 PS11 are found:-
(1) When number of interval is given as 35 and number of installment as 1 then due_t of the P2P action is incorrect (i.e. year 1974).
However, the issue was not found when it was passed as 34 or 36.
(2) If the number of installment is 1, then irrespective of number of interval value provided, system adds 1 day extra to the invoke_t in the input.
(3) In all the cases, invoke_t in the response is always inconsistent.
(4) If number of installment is 1, then from Collection Center, there is a validation that interval cannot be 0.
P2P arrangement to remain consistent.
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