[
http://mifosforge.jira.com/browse/MIFOSBI-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
johnwoodlock resolved MIFOSBI-313.
----------------------------------
Resolution: Fixed
Scheduled For: Release
Fixed.
As personnel_movement table is no longer maintained in mifos, changes in
office assignment (for loan officers and other personnel entries) weren't being
picked up by ETL from the date mifos was upgraded (2.1.x I think but not
confirmed).
One symptom of this problem occurred in this bug where a loan officer was moved
for the first time to an office whose created date happened to be before the
loan officer's created date (and fell over because of the date problem)
> ETL not picking up Loan Officer leaving one branch and joining another
> ----------------------------------------------------------------------
>
> Key: MIFOSBI-313
> URL: http://mifosforge.jira.com/browse/MIFOSBI-313
> Project: mifos business intelligence
> Issue Type: Bug
> Affects Versions: Mifos BI 1.2
> Reporter: johnwoodlock
> Assignee: johnwoodlock
> Priority: Major
> Fix For: Mifos BI 1.3
>
>
> Mifos no longer creates personnel_movement entries. Don't know when this
> started. Guess is 2.1.x
> The personnel_movement table was used by ETL to pick up loan officers going
> to new branches. ETL fell over for Digamber prod because some loan officers
> had moved branch. The ETL thought this new branch was the 'first' branch and
> fell over because of date created problem. Even if it didn't fall over it
> wouldn't have recorded the loan officer branch movements correctly and LO
> reports would likely be wrong.
> Probably not worth fixing mifos. The same info is recorded on the mifos
> audit table 'change_log/change_log_detail' but that has the problem of
> recording changes by the branch name rather than the branch id so problems
> can occur when branch name is edited.
> So, think this will need an ETL upgrade for full fix. Can get ETL to run
> through with a data fix to allow non LO reports to be viewed.
> So, data fix requiredd? and/or full fix required (Binny/Kay).
> If full fix done think I'd put some better 'lookup logic in' to reduce chance
> of problems and clear message about where problem is before running the main
> ETL code.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
