[
http://mifosforge.jira.com/browse/MIFOSBI-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67575#comment-67575
]
johnwoodlock commented on MIFOSBI-309:
--------------------------------------
I think Binny ran against the Digamber production reporting database (if not
let me know). The production reporting ETL hasn't run correctly for some time
and I believe the figures seen are due to partial completion of the ETL (it got
part way through the history before failing).
I have attached what the reports look like in V1.2 and I checked some of the
figures and they look good to me. The resolution would be to bring Digamber up
to Mifos BI V1.2 as this includes the necessary ETL fix.
Other notes:
The DW doesn't actually identify the date a loan officer left an MFI although
there is a field for it (agreed with Kay long time ago). It does track leaving
branches though. I can't find any data on the mifos Digamber database that
indicates the loan officer left the branch/MFI. Not that it really matters
because the key point is all the groups have been reassigned (which they have
except for some partial and closed ones)
LO Detailed Report
==================
Group Formation
# of Clients added(To Date): No. of clients formed by the LO up to the "To"
Date that were active at any time up to the "To" Date
# of Groups added(To Date): as for clients
Client Summary
# of Centers: No. of active centers assigned to the LO as of the "To" Date
Account Summary
# of Active Loans: No. of active loans (in good and bad standing) assigned to
the LO as of the "To" Date
> Loan Officer Reports - show incorrect values for Loan Officer who is no
> longer with the MFI
> -------------------------------------------------------------------------------------------
>
> Key: MIFOSBI-309
> URL: http://mifosforge.jira.com/browse/MIFOSBI-309
> Project: mifos business intelligence
> Issue Type: Bug
> Environment: Digamber - Cloud running Mifos 2.1 and BI
> Reporter: Binny Gopinath Sreevas
> Assignee: johnwoodlock
> Priority: Major
> Labels: Digamber
> Fix For: Mifos BI 1.3
>
> Attachments: LoanOfficerDetailed.pdf, LoanOfficerDetailedV12.pdf,
> LoanOfficerPerformanceSummaryCumulative.pdf,
> LoanOfficerPerformanceSummaryCumulativeV12.pdf
>
>
> This is for Digamber MicroFin:
> Under "01_DCL-Jpr 1" Branch - Loan Officer "Tejpal Meghwanshi" has left the
> MFI and all active clients and centers have been transferred to Loan Officer
> "Manoj Premjani".
> The numbers in "Loan Officer Detailed" and "Loan Officer Performance Summary
> (Cumulative)" reports seem incorrect.
> Loan Officer Detailed Report:
> Under Client Summary:
> Number of Centers: 27 --> This number looks incorrect.
> Number of Clients: 0
> Number of Clients with Active Loans: 395 --> This number looks
> incorrect.
> Under Account Summary:
> Number of Active Loans: 410 --> This number looks incorrect.
> Loan Officer Performance Summary (Cumulative) Report:
> Also shows 27 centers under Tejpal and # of Clients as zero and # of
> Loans as 410. Which again does not reflect the current state for Tejpal.
> Branch Progress Report:
> Shows 440 clients formed by Tejpal (under clients formed) and under
> Handled all numbers are zero.
> This seems to be correct as there are
> 415 active borrowers who were formed by Tejpal and have all been
> transferred to Manoj and
> 5 borrowers who have been formed by Tejpal and are currently closed
> 20 borrowers who have been formed by Tejpal and is still with Tejpal
> and are currently in partial state
> Please confirm if these are bugs in the reports.
> If not, please explain how these numbers are computed in the "Loan Officer
> Detailed" and "Loan Officer Performance Summary (Cumulative)" reports.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
