[
http://mifosforge.jira.com/browse/MIFOS-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukasz Chudy reassigned MIFOS-1980:
-----------------------------------
Assignee: Adrian Winkler (was: mifosdeveloperqueue)
> Customer schedule not updated correctly when group membership for a client is
> changed to a group with different meeting frequency
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: MIFOS-1980
> URL: http://mifosforge.jira.com/browse/MIFOS-1980
> Project: mifos
> Issue Type: Bug
> Components: Batch jobs
> Affects Versions: Release 1.1
> Environment: Platform: All, OS: All
> Reporter: aliyaw
> Assignee: Adrian Winkler
> Priority: Major
> Labels: Client, DocumentInFS, grameenkoota
> Fix For: Unscheduled
>
>
> REPRO (Rev 11326 with standard test data set rev 11704)
> ======
> 1. Load data, set your system date to June 5th, 2008 and start the Mifos
> application
> 1. Log in as admin
> 2. Search for a client with weekly meetings but no active loan accounts -
> CLIENT NO_1 in this case.
> 3. View the customer_schedule table for this client in the DB:
>
> select * from customer_schedule where customer_id = 121 - note the weekly
> sequence in 'Action date' column.
> 3. View client details page and select add/edit group membership
> 4. Add group membership for the client and add them to a group with monthly
> meetings - Group 1 in Center_Monthly1 in this case
> 5. Note that the client is added succesfully to the group and meeting dates
> for
> the client show up as "First monday of every month" in the meeting details
> section for the client, as expected.
> 6. Shut down the application and set the system date forward to June 6th and
> run the batch jobs to update the customer schedule table based on the client's
> new meeting schedule
> 7. Again, view the customer_schedule table:
> select * from customer_schedule where customer_id = 121
> This query shows weekly meetings through June followed by monthly meetings
> starting in July.
> 8. Try to open a new 'Declining balance for monthly clients' loan account for
> the client
> 9. Disbursement date is automatically set to the next date in the
> customer_schedule table - in this case June 9th, 2008
> 10. Try to create the loan account - 'invalid disbursement date' error is
> received since June 9th is not on a valid meeting date for the customer.
> OBSERVED
> =========
> As noted above, the customer_schedule table still has weekly records for the
> remaining month of June. The table is not updated to remove the weekly action
> dates that have not yet passed
> EXPECTED
> ========
> The whole customer_schedule table should be updated to account for the new
> meeting schedule and this should happen from the date the meeting is changed.
> NOTES:
> ======
> The customer_schedule table is used to determine which fees are also due in
> addition to the disbursal date for loans so the system may assume that extra
> fees are due for the extra weekly records in the customer_schedule table.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://mifosforge.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
