[
http://mifosforge.jira.com/browse/MIFOS-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57922#action_57922
]
johnwoodlock commented on MIFOS-2945:
-------------------------------------
Some notes before coding
------------------------
The batch job that recalculates days in arrears does so for all loans in good
and bad standing. It also hard codes lateness as '1' (effectively ignoring it
as the batch job runs early morning). So it treats 'lateness' and days in
arrears as two different things.
Any active loan (good or bad standing) may have a days in arrears figure so it
records it. The batch job creates an entry for any such loan if there isn't
one there already. This batch job is the only place that creates entries for
the Loan Arrears Table. If there are problems with batch jobs or perhaps
uncatered for paths in the code... loans of other statuses can appear on the
loan arrears table ... not because they are created new but because loan
arrears entries are only deleted when repayments bring the loan back into good
standing and so may just get left there.
Any loan in good standing whose days in arrears reaches 'lateness' days gets
put into bad standing (by another batch job that runs before the recalculate
days in arrears batch job)
The loan details web page calculates days in arrears dynamically (hence it can
easily be different to what's on the loan arrears table especially after
payments)
The mifos branch report is run on data that is generated from the loan arrears
table. So, as the data in it gets messier more errors will creep in (e.g. not
just good and bad standing loans but others as well)e.g secdep has some
cancelled and rescheduled loans on the loan arrears table and the vast bulk are
active in good standing (because lateness is 10 days).
So, there's quite a bit of scope for bugs in the current system if we implement
what Kay says
1/ it will be easy to implement and remove some code complexity
2/ it should be way easier to ensure data is accurate
One question I have is:
if 'lateness' is 5 and I have loans that are 3 days in arrears (not 3 days past
lateness) then do I need to report on them in the branch report (or elsewhere)?
If not fine. If yes then I can sort of see why both good and bad standing
loans are calculated in the batch job (still could simplify tho)
> Fix Loan Arrears Aging Table to have loans in correct states
> ------------------------------------------------------------
>
> Key: MIFOS-2945
> URL: http://mifosforge.jira.com/browse/MIFOS-2945
> Project: mifos
> Issue Type: Bug
> Components: Database, Loan Account, Reports Module
> Affects Versions: Release 1.5, Release 1.5.0.1
> Reporter: Kay Chau
> Assignee: johnwoodlock
> Priority: Major
> Fix For: Shamim D
>
>
> There seem to be a couple of bugs in Loan Arrears Table
> 1) Loans in Active Standing are included in this table. This implies the
> table isn't correctly taking lateness definition into account. Only those
> loans that have exceeded the lateness definition defined in Mifos should be
> included in this table.
> 2) Loans in states other than Active-Bad Standing - Loans in Closed states
> should not be in this table. If they are closed, then they should be
> removed. Clean the logic up so this happens
> When this issue is fixed, only loans in bad standing should be populated in
> the table.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
