Promise To Pay Arrangement Is Not Consistent (Doc ID 2091969.1)

Last updated on AUGUST 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

On : 7.5 PS11 version, Collections Manager

ACTUAL BEHAVIOR
-----------------------
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).

  op_collections_invoke_promise_to_pay return flist
# number of field entries allocated 20, used 2
0 PIN_FLD_POID POID [0] 0.0.0.1 /event/activity/collections/promise_to_pay 294493194437940940 0
0 PIN_FLD_PROMISE_TO_PAY_INFO SUBSTRUCT [0] allocated 20, used 3
1     PIN_FLD_INVOKE_T TSTAMP [0] (297) Thu Jan 1 12:04:57 1970
1     PIN_FLD_MILESTONE_AMOUNT DECIMAL [0] 195.00
1     PIN_FLD_END_T TSTAMP [0] (154475192) Sun Nov 24 10:46:32 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.

 
EXPECTED BEHAVIOR
---------------------------
P2P arrangement to remain consistent.

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