2016 Jun 07 12:03 PM
Dunning Related Scenario
In Mumbai DL1 is carried out on Due Date + 3 Days
DL2 = DL1 + 23 days. When DL2 is created a disconnection document is generated.
Scenario.
*)DL2 is generated ,disconnection document is created ,dl2 order is created for the same and notice is sent to consumer.
*) Consumer makes payment by cheque.
*) DL2 order is cancelled via a custom program in Batch and the disconnection document status is 99(Complete).
*) After 3-5 days there is a cheque dishonour .
*) There is a deadlock for the current sceanrio as the payment is reversed(dishonour) order is cancelled and disconenction doc status is 99.
Practise followed currently.
*) We reverse DL2 for the respective consumer so that DL2 is triggered again and new disconnection doc is generated and the process follows.
Do we have any std solution as in I dont want to reverse the DL2 of the consumer.?
2016 Jun 07 4:04 PM
Hi Piyush,
Check the Last Dunning Level parameter which can be configured at the Dunning Procedure level.
If you set the value as 2, then if a further dunning run is carried out, then those open receivables to which the highest dunning level already applied before the dunning run was carried out are dunned again at this same level.
The future dunning runs will be executed on the Dunning frequency and the Alawys dunn indicator that is being configured at the disconnection level, i.e. DL2 in your case.
However, setting the value as 2 has other impacts. So I would recommend you to consider all the scenarios before finally changing the parameter to 2 in Prod.
Hope it helps..
Thanks,
Amlan
2016 Jun 07 3:35 PM
No standard solution exists with the dunning procedure approach. You could realize this requirement with collection strategy approach.
2016 Jun 07 4:04 PM
Hi Piyush,
Check the Last Dunning Level parameter which can be configured at the Dunning Procedure level.
If you set the value as 2, then if a further dunning run is carried out, then those open receivables to which the highest dunning level already applied before the dunning run was carried out are dunned again at this same level.
The future dunning runs will be executed on the Dunning frequency and the Alawys dunn indicator that is being configured at the disconnection level, i.e. DL2 in your case.
However, setting the value as 2 has other impacts. So I would recommend you to consider all the scenarios before finally changing the parameter to 2 in Prod.
Hope it helps..
Thanks,
Amlan
2016 Jun 08 5:41 AM
2016 Jun 08 6:33 AM
2016 Jun 08 7:12 AM
Hi Piyush ,
Why not add the logic in custom program to check if payment done through cheque or draft , to wait for 7 days before reversing the disconnection order , I feel this would be enough time for banks to process the cheque /draft to see if dishonored .if dishonored then take further collection steps other wise mark the disconnection document as complete and reverse the disconnection order.
PS: By wait for 7 days , i mean if pay mode = cheque/draft and BUDAT of payment doc <= 7 ,then skip this records , i have assumed your custom program runs every day.