[ 
http://mifosforge.jira.com/browse/MIFOS-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

keithwoodlock updated MIFOS-2793:
---------------------------------

    Fix Version/s:     (was: Mifos Backlog)
                   Unscheduled

> Client Fee charges aren't always appearing in table customer_account_activity
> -----------------------------------------------------------------------------
>
>                 Key: MIFOS-2793
>                 URL: http://mifosforge.jira.com/browse/MIFOS-2793
>             Project: mifos
>          Issue Type: Bug
>          Components: Fee
>    Affects Versions: Release 1.3.1
>            Reporter: Ryan Whitney
>            Assignee: mifosdeveloperqueue
>              Labels: secdep
>             Fix For: Unscheduled
>
>         Attachments: 0003-000011819-charge-activity.png, 
> 0003-000011819-charge-activity.txt, 0003-000011819-customer-fee-schedule.txt, 
> All Charges Shown.png, No Charges Shown.png, Some Charges Shown.png
>
>
> I just noticed this on SECDEP data.  For some clients the client fees that 
> the system is charging aren't appearing in the Account activity, but it is in 
> others (See attached screenshots).
> REPRO: SECDEP Database
> * Fee charges appear:  0004-000001102
> * Fee charges appear, but don't appear in the beginning: 0002-000009540
> * Fee charges don't appear: 0003-000011819

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to