05-22-2009 12:30 PM
Dear All,
When Dunning with FPVA with 'Start Act Run' switched on the application log does not show any error message. But the Print Date is not updated in the dunning history (Environment > Dunning History). The next level dunning also cannot happen without this print date. For the next level an error is displayed in the Application log that the dunning notice was not printed for the earlier dunning id and date.
Please suggest what could be the reason for not updating the 'Print Date' in the dunning history.
Thanking you in advance
Venkat
05-25-2009 8:02 AM
Hi,
Please run the Dunning Activity manually, it has not been triggerred automatically.
The print date gets populated with the dunning run.
Please try executing FPVB for the dunning proposal created.
Hope this should solve your problem!!
Regards,
Rajesh Popat
05-22-2009 1:55 PM
Please check if the first dunning run that has no print date is created thru invoicing. if it is, that is the reason why succeeding dunning runs thru FPVA has no print date.
You need to mark that particular invoice as printed via EA60. That will also put a print date in dunning history.
05-23-2009 6:17 AM
True the first dunning does not contain the print date. I tried what you had suggested. It doesn't work. May be what you suggested works for IS Utilities. I am in Telecom application. There is no billing component in telecom application. The document was created manuall using FPE1.
Please let me know if you have any other idea why this print date is not updated.
Regards
05-25-2009 8:02 AM
Hi,
Please run the Dunning Activity manually, it has not been triggerred automatically.
The print date gets populated with the dunning run.
Please try executing FPVB for the dunning proposal created.
Hope this should solve your problem!!
Regards,
Rajesh Popat
05-28-2009 2:50 PM
There's a bug in the dunning proposal run, check note "1002403 - FPVB: Incorrect initial values for copied dunning proposal". If you go to FPVB you can check if the dunning proposal data is correct, if not just execut it again with full aplication log (Aditional information) then you can see what's the error.
Cheers,