From: Douglas K. <dou...@gm...> - 2010-09-15 07:58:27
|
John and Ryan, Thank you. Both of your solutions worked. Now I have a different issue. We progressed in our implementation plan to step #5. So we were able to enter all the opening balances for our test group for all loans and savings and everything matched with the current system. However, when we tried to enter the first collection sheet, we could not enter many loan payments because clients were "Paid ahead." Let me give an example: Elizabeth Ayuma has loan of for 39 weeks with payments of 713 per week. She has been paying 800 shillings per week. When we tried to enter the first "real" collection sheet where Elizabeth paid 800 shillings, there is no where to put this because the system has paid this loan ahead and does not think anything is due. Because of the way our loan officers manage their groups, most loans are being paid ahead so this problem occurs for more than 80% of the clients. I realize that the system allows us to apply a payment on an individual loan. But I really do not want to do this because: 1. The time it takes to input collection sheets will dramatically increase. 2. The collection sheets will now rarely match the deposit slips eliminating a very good checks-and-balances in the system. Is there a way to get the collection sheet to show a "0" amount due for loans paid ahead so we could input all collections made at the meeting? Thanks for your help, Doug From: John Woodlock [mailto:joh...@gm...] Sent: Friday, September 10, 2010 2:27 AM To: mif...@li... Subject: Re: [Mifos-users] Loan Expectations not showing in Collection Sheet Doug, presumably you have some way of moving the computer date forward to enter in all the data. I wonder if the batch jobs haven't caught up yet. When you create a center and its meeting schedule , mifos creates 10 future meeting schedules ... The collection sheet looks at the most recent meeting schedule for the center. Then there's a nightly batch job called GenerateMeetingsForCustomerAndSavingsTask which puts in 10 more schedules but if the batch jobs don't run the extra schedules don't get created and the most recent meeting date remains the same. So, if you leave mifos running at midnight (default batch kick-off time) the date should start coming forward by about 2 1/2 months each time. You can also kick it off manually but I'll wait to see if you think batch jobs not running really is the problem before going into how to do that. John On Thu, Sep 9, 2010 at 10:21 PM, Douglas Kurz <dou...@gm...> wrote: We are just starting our deployment and are working with a small set of data (one group) to ensure our process works. Here is a brief summary of our approach to converting our data into mifos: 1. Enter clients as of one year ago (our maximum loan duration is one year). 2. Enter / Approve / Disburse the client's active loans with the as of date of the date of disbursement 3. Enter a collection sheet for the first meeting in August that would include all the savings balances and loan payments up to that point in time. 4. Check reports to ensure correct balances and arrears reporting as of first week of August. 5. Simulate each week for the month of August for this pilot group by entering the collection sheet and entering any loans that were disbursed each week as it may have occurred. Run reports each "simulated week" to ensure correct balances and arrears. 6. If the above works, repeat steps #1-4 for an all groups for a loan officer. 7. Run this loan officer in parallel with current system for a one to three weeks. 8. Repeat #1-4 for the remaining groups/clients/loan officers. 9. Run in parallel with the current system. 10. When comfortable - decommission current system. Mifos is live! Sorry for all that long introduction. Now I have a few questions/ issues: 1. Any comments or concerns about this approach for data conversion, parallel and go-live? 2. We completed steps #1 and #2 without issues. But when we go to enter the first collection sheet for these groups with the balances for the first week in August (3 Aug 2010 to be exact) it will not allow us. The collection sheet comes up but the date is 15 Dec 2009. Therefore, only one of the loans we entered in step #2 is there (because it was disbursed before that date). Why is it giving us 15 Dec 2009? How do we get it to allow us to enter 3 Aug 2010 as the first collection sheet? 3. I know one problem we will have with the above deployment is loan cycle. Despite the fact that we have many clients in their 3rd, 4th and even 5th loan cycle, everyone in Mifos will say cycle 1. Is there a way to correct this or do we need to live with it? Thank you for the help. Doug Kurz Missions of Hope, International ---------------------------------------------------------------------------- -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Mifos-users mailing list Mif...@li... https://lists.sourceforge.net/lists/listinfo/mifos-users |