[
http://mifosforge.jira.com/browse/MIFOS-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60085#action_60085
]
Van Mittal-Henkle commented on MIFOS-3712:
------------------------------------------
A new batch job has been added to fix up customer accounts with missing fees.
An updated war file with the fix has been loaded on testing-secdep and the
batch job has run, so the fees should be inspected to see if they look right.
It appears that the root cause was that additional meetings used to be added by
one batch job and fees added by another, separate job. The fees job was
eliminated and the fee update functionality rolled into the job that creates
additional meeting entries. The problem is that when the 1.5 to 1.6 upgrade is
done, there were customer accounts with customer_schedule entries that had not
been updated to include linked customer_fee_schedule entries. The batch job
that was updating fees was removed so these accounts were left hanging with
fees not being updated. The GenerateMeetingsForCustomerAndSavingsHelper will
not update the fees on a customer account until there are < 4 customer_schedule
entries left in the future, so accounts that didn't meet this criteria were not
getting fees updated. The new batch job goes in and updates fees for accounts
with missing fees to "catch them up" so that the current batch job should be
able to keep them in sync from now on.
> Recurring client charges are not being charged to the accounts after the
> initial application
> --------------------------------------------------------------------------------------------
>
> Key: MIFOS-3712
> URL: http://mifosforge.jira.com/browse/MIFOS-3712
> Project: mifos
> Issue Type: Bug
> Reporter: Ryan Whitney
> Assignee: Van Mittal-Henkle
> Priority: Blocker
> Fix For: Release E - Iteration 7, Release 1.6.1, Release E
>
> Attachments:
> 0001-WIP-on-MIFOS-3712-Recurring-client-charges-are-not-b.patch
>
>
> It appears that for SECDEP's current upgrade, the client charges are not
> being applied for next week. This appears to be unrelated to the bug opened
> yesterday where every 11th payment was not getting applied, this appears as
> NO charges are being applied next week.
> you can see this on SECDEP's production server, account: 0003-000014139
> Her next payment is due next Monday, and it says for 9/20/10, there is
> nothing set to be paid.
> I uploaded a production drop of their database (from the upgrade to test) to
> my local virtual server, and tried shifting the date (not using acceptance
> test, but actually shifting the date on the virtual server) to the next
> monday, hoping that it would appear. It did not.
> This is also affecting the collection sheets that are to be printed for next
> week, as now they aren't showing the charges that are due.
> This appears to be affecting all accounts.
--
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
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
