[ 
http://mifosforge.jira.com/browse/MIFOS-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60052#action_60052
 ] 

Van Mittal-Henkle commented on MIFOS-3712:
------------------------------------------

Looking at the following account (which showed up in the batch job logs):
AccountId: 32628
CustomerId: 10026

There are 5 fees associated with this account:
MMF2 (14), accountFeeId: 16836 *
MMF1 (Cycle 3), accountFeeId: 46317 *
MMF2 (28), accountFeeId: 16594
MMF1 (Cycle 1), accountFeeId: 16593 *
MMF1 (Cycle 2), accountFeeId: 26994 *

The ones with asterisks have been used, the "MMF2 (28)" fee was removed 
immediately after client creation, so there is no schedule entry that uses that 
fee.  The fact that there are no schedule entries using this fee is the direct 
cause of the batch job failure.


> 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
>
>
> 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

Reply via email to