[
http://mifosforge.jira.com/browse/MIFOS-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60073#action_60073
]
Van Mittal-Henkle commented on MIFOS-3712:
------------------------------------------
The batch job will now run with the patch attached to this issue, but some
clients remain that do not show up to date fees.
The query that returns the list of accounts with schedules that need updating
when the batch job runs is:
select a.account_id as accountId from account a join customer_account ca on
ca.account_id = a.account_id join customer c on c.customer_id = a.customer_id
where c.status_id in (3,9,13) and a.account_state_id = 11 and (select
max(cs.installment_id) from customer_schedule cs where cs.account_id =
a.account_id and cs.action_date <= date('2010-09-16')) + 4 > (select
max(cs2.installment_id) from customer_schedule cs2 where cs2.account_id =
a.account_id)
where the date is the date on which the batch job runs.
Our understanding of the query is that it finds customers that are active, with
accounts that are active and then if there are fewer than 4 customer_schedule
entries remaining in the future, it will generate new customer_schedule entries
and associate fees with them.
For certain accounts such as account_id = 62460, there are more than 3
customer_schedule entries in the future, but those entries have no fees
associated with them. So this account will not be updated by the batch job.
We still don't understand how new customer_schedule entries could be created
without there having the active fees attached to the customer_schedule entries.
> 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
