|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows:
Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
Vishwas,
The m_loan table already have client id, group id and product id, I think we are duplicating the data by creating one more table m_client_loan_counter to capture the running count, can’t we add the running count to m_loan table.
Most of the MFI's like GK and Adhikar (with huge client base) are using this feature, so it is good to have running counter in m_loan table.
While discussing with Nayan, one more requirement had popped up, it is good to have two counters, one for loan cycle counter (for client or group) and another for loan cycle counter by product.
e.g. of loan cycle counter user (independent of loan product)
MFI’s may want to see the impact (PPI) of a loan given by MFI to their clients by loan cycle irrespective of loan product. Computing this count using SQL queries would be a heavy process.
Please see the attached sample PPI report requirement for Adhikar.
Note: Assuming that only the loan products which are checked with "Include in loan cycle counter" will be consider for loan cycle counter and loan cycle counter by product.