[
http://mifosforge.jira.com/browse/MIFOS-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Van Mittal-Henkle resolved MIFOS-2479.
--------------------------------------
Resolution: Fixed
Resolved in r16889.
> Changing Center Meeting date causes multiple issues with savings
> ----------------------------------------------------------------
>
> Key: MIFOS-2479
> URL: http://mifosforge.jira.com/browse/MIFOS-2479
> Project: mifos
> Issue Type: Bug
> Components: Collection Sheet Entry
> Affects Versions: Release 1.2, Release 1.4
> Environment: Platform: All, OS: All
> Reporter: Ryan Whitney
> Assignee: Van Mittal-Henkle
> Priority: Critical
> Fix For: Gazelle C
>
> Attachments: SECDEP Savings Issue - Screenshot 1.png, SECDEP Savings
> Issue - Screenshot 2.png
>
>
> We now have our second support issue with SECDEP and Van, its as you
> suspected,
> its with Savings.
> Here's the issue (or rather, looks like two for one)
> * SECDEP Mis Officer changed the meeting date for 5 centers late last week (it
> was Thurs or Fri)
> * While entering in the collections this week with the Collection Sheet Entry,
> she noticed that all of the savings products weren't appearing on the screen
> (See screenshot 1). For comparison I'm including a screenshot of how it
> should
> normally look (Screenshot 2)
> * Despite this, she entered in the loan transactions anyways and submitted the
> collection sheet
> * She went to the client accounts to enter in the savings transactions and
> noticed that there was a posting made for savings. And not only was the
> posting
> made, it was made for a multiple of the amount (I've seen it post 80, 100 and
> 120 in different instances)
> * When she ran the collection sheet report for the center for the next week,
> she
> noticed that everything was right except that the savings was requesting 100
> pesos instead of 20. *
> This is only happening when they change center's meeting date. For now they
> can
> somewhat mitigate the issue by making adjustments to the account **, entering
> in
> transactions manually and printing their own collection sheet. But they also
> have a few other centers they have to move.
> We can use their testing server as they are not using it at the moment (and I
> will tell them that we are using it to vet the issue). You will need to copy
> the production database over to the testing server though (I would of done
> this
> but having connection issues, more on that later). I sent a login to Kay.
> A few additional notes:
> * They are running v1....@14355 (which I think is 1.2.2? Why aren't we
> showing
> this ver number?!)
> * I was thinking it would be worth trying to upgrade them to 1.3 to see if
> that
> resolves any of the issues
> * Centers with meetings that were changed (all under the Oton Branch)
> ** Pamuringao Proper
> ** Pamuringao Garrido
> ** Abilay Norte
> ** Bangkal
> ** Gines Patag
--
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
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mifos-issues mailing list
Mifos-issues@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-issues
