Followup To Patch 20638038 - Collection Actions Rescheduling Behaviour (Doc ID 2049976.1)

Last updated on SEPTEMBER 19, 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

Multiple issues open on the collection actions rescheduling behavior, after applying <Patch 20638038>.

1) After cancelling current date action the corresponding actions are not getting rescheduled

Steps to reproduce

i) Create an account with any currency
ii) Make sure account enters collection
iii) Complete the first action "First Past Due Notice-Checkpoint"
iv) Cancel the next automatic action "First Past Due Notice" without clicking “do not reschedule outstanding actions due date” checkbox
v) The PVT date should be same as action date

Expected : Remaining actions which is after the cancellation action should be rescheduled
Actual: Remaining actions due dates remains on the same dates, not getting rescheduled

2) Manual actions getting completed before completion of all the previous action

Steps to reproduce:
i) Create a US cloud customer with platinum profile and AUD currency
ii) Make sure account should enter collections
iii) Complete the manual action "First Past Due Notice-Checkpoint"
iv) Skip all the other actions between till "2nd call" and Complete the manual action "2nd call"

Expected : Manual action 2nd call should get completed only if all the previous actions are completed
Actual: Manual action 2nd call is getting completed without completion of all other previous actions

3) Two collection actions are shown as "Pending" after inserting manual action

Steps to reproduce

i) Create an account with any currency
ii).Process some usage
iii).Run billing
iv).Execute pin_collections and account should enter collections
v).Insert manual action "Dispute"
vi).After inserting manual action, 2 actions task status are shown as "Pending" - Dispute & First Past Due Notice-Checkpoint

Actual Result : Two actions are shown as "Pending" after inserting manual action
Expected Result : Only the manual action which is inserted should be shown as "Pending"

4) When promise to pay is cancelled, the dates are incorrectly calculated

Case 1 :
Issue : When promise to pay is cancelled, the dates are incorrectly calculated

Steps to reproduce

i).Create an account with any currency
ii).Process some usage
iii).Run billing
iv).Execute pin_collections and account should enter collections
v).Inititate p2p for 2 installments
vi).Cancel all p2p actions after intiating
v).Validate the dates of all the first and second collection actions dates after p2p cancellation action. There is 1 day extra between first and second action.

Actual Result : Second Collection action after P2P cancellation is scheduled wrongly (One day extra on gap between first and second action after p2p cancellation)
Expected Result : Dates should be scheduled correctly after P2P Cancellation

Case 2 :
Issue : After cancelling any future date action the corresponding actions dates are incorrectly calculated

Steps to reproduce

i) Create an account with any currency
ii) Make sure account enters collection
iii) Complete the first action "First Past Due Notice-Checkpoint"
iv) Cancel the next automatic action "First Past Due Notice" without clicking “do not reschedule outstanding actions due date” checkbox and pvt should be current date

Expected: Actions scheduled for each actions should maintain the dependency between the dates
Actual: Some of the remaining actions are merged on the same dates

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