[
http://mifosforge.jira.com/browse/MIFOS-3048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58207#action_58207
]
keithwoodlock commented on MIFOS-3048:
--------------------------------------
Jeff,
had a look at this and sure enough it does'n take account of any holiday or
moratoria when generating schedules for savings accounts (mandatory or
voluntary).
its an easy/quick fix but i have a question or two.
1) Is this behaviour in 1.5.x (i.e doesnt take into account holidays when
generating saving account schedule)
NOTE: schedules for a voluntary account doesn't make sense but i think we keep
schedules so they will appear on collection sheet entry screen etc..
regardless of what comes back i'll put in the fix and check into 1.6.x but
would be good to know if this behaviour was on purpose(is in 1.5.x also) or was
mistake?
> Moratorium not pushing out mandatory savings schedule
> -----------------------------------------------------
>
> Key: MIFOS-3048
> URL: http://mifosforge.jira.com/browse/MIFOS-3048
> Project: mifos
> Issue Type: Bug
> Components: Holidays
> Affects Versions: Shamim D
> Reporter: jbrewster
> Assignee: keithwoodlock
> Priority: Major
> Fix For: Shamim D
>
> Attachments: issue3048.zip
>
>
> Moratorium holiday should push out a mandatory savings action date.
> I found when creating a mandatory savings account on a schedule that lands on
> a moratorium holiday, the action_date is not pushed out and results in a
> savings deposit due on that moratorium day.
> Repro steps:
> 1. Have a customer that meets on Mondays
> 2. Create a moratorium holiday for a Monday, e.g. 14 June 2010
> 3. Create a mandatory savings product for weekly savings
> 4. Create a savings account for the new customer
> 5. query saving_schedule meeting for this customer ID
> 6. Move system date forward 2 weeks, run batch jobs, and navigate to
> Collection Sheet Entry for this customer. See mandatory savings payments due
> for both weeks - 6/14 and 6/21.
> Expected result:
> No action_date on 6/14
> Actual result:
> action_date for savings account on 6/14, so customer is required to pay
> savings on 6/14 unlike the customer fee and loan account which get pushed to
> next meeting of 6/21.
> Testing notes:
> Will attached test database used for this test. Testing done with client
> Stu1232993852651 Client1232993852651, system ID: 0002-000000003.
> To Review savings account schedule, queried savings schedule:
> SELECT customer_ID, action_date, deposit FROM saving_schedule s where
> customer_ID = '3';
> and see these meeting dates:
> (note, another moratorium is from 8/15 to 8/21 and 8/16 is also an
> action_date in this list)
> customer_ID, action_date, deposit
> 3, '2010-06-14', 22.0000
> 3, '2010-06-21', 22.0000
> 3, '2010-06-28', 22.0000
> 3, '2010-07-05', 22.0000
> 3, '2010-07-12', 22.0000
> 3, '2010-07-19', 22.0000
> 3, '2010-07-26', 22.0000
> 3, '2010-08-02', 22.0000
> 3, '2010-08-09', 22.0000
> 3, '2010-08-16', 22.0000
--
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
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
