[
http://mifosforge.jira.com/browse/MIFOS-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=69689#comment-69689
]
Rebecca Scott commented on MIFOS-2605:
--------------------------------------
tbd-archive
> Debit actions not picking up right GL codes
> -------------------------------------------
>
> Key: MIFOS-2605
> URL: http://mifosforge.jira.com/browse/MIFOS-2605
> Project: mifos
> Issue Type: Bug
> Components: Fee
> Affects Versions: Release 1.4
> Environment: Platform: All, OS: All
> Reporter: Jeff Brewster
> Assignee: Sam Birney
> Priority: Major
> Labels: almajmoua, patch
> Fix For: Release E - Iteration 5, Release 2.0.0
>
> Attachments: ae.py, fee-financial-action-patch.txt, jv_export,
> patch-accounting-fees.txt, rv_export
>
>
> Issue reported from Sam
> -----------------------
> I updated my mifosChartOfAccounts.custom.xml in the following way:
> <code>
> <GLIncomeAccount code="30000" name="INCOME">
> <GLAccount code="71" name="Operating Income">
> <GLAccount code="7131" name="Loan Interest" />
> <GLAccount code="7132" name="Fees Received">
> <GLAccount code="7132000" name="Insurance Fee 5" />
> <GLAccount code="7132001" name="Insurance Fee 10" />
> <GLAccount code="7132002" name="Minimum Fee 30" />
> <GLAccount code="7132003" name="Maximum Fee 60" />
> <GLAccount code="7132004" name="Maximum Fee 100" />
> <GLAccount code="7132005" name="Overdue Principal Fee" />
> <GLAccount code="7132006" name="Overdue Interest Fee" />
> <GLAccount code="7132007" name="Loan Fee 2" />
> <GLAccount code="7132008" name="Loan Fee 2.5" />
> <GLAccount code="7132009" name="Loan Fee 3.5" />
> </GLAccount>
> <GLAccount code="7133" name="Penalties Received" />
> </GLAccount>
> <GLAccount code="788" name="Rounding" />
> </GLIncomeAccount>
> </code>
> and made sure the value in my mifosBeanConfig.custom.xml under both
> actionToDebitAccount and actionToCreditAccount matched the top-level
> Fees-Received element:
> <code>
> <entry key="FEEPOSTING" value="7132"/> </code>
> Then I changed my selenium script that creates the desired fees, using the
> following data:
> <code>
> fee_codes = {
> "$5 Insurance Fee":"7132000",
> "$10 Insurance Fee":"7132001",
> "$30 Minimum Fee":"7132002",
> "$60 Maximum Fee":"7132003",
> "$100 Maximum Fee":"7132004",
> "Overdue Principal":"7132005",
> "Overdue Interest":"7132006",
> "2% Loan Fee":"7132007",
> "2.5% Loan Fee":"7132008",
> "3.5% Loan Fee":"7132009",
> }
> </code>
> Then I refreshed my database, started my mifos instance again, ran my script
> to
> populate fees, and then disbursed some test loans.
> Amazingly, the FINANCIAL_TRXN.GLCODE_ID column was now being populated with
> the
> correct codes for credit actions. However, for debit actions it was always
> populating the code corresponding to 7132009. This seems like some sort of
> bug.
> The first loan I created had a 3.5% fee and a $5 fee, but for the subsequent
> test loans I used other fees, like 2% and $5, or 2.5% and $5. It was
> consistently using the right codes for credits, but consistently using 7132009
> for debits.
> Proposed Patch from Sam
> -----------------------
> This seems like a bug that perhaps I am the first to stumble into. I delved
> into the code and eventually made a change in FeesAccountingEntry.java.
> Following the example for credits that seemed to be working, I replaced
> <code>
> addAccountEntryDetails(feeTrxn.getFeeAmount(),
> finActionFee, getGLcode(finActionFee
> .getApplicableDebitCharts()), FinancialConstants.DEBIT);
> </code>
> with this
> <code>
> addAccountEntryDetails(feeTrxn.getFeeAmount(),
> finActionFee,
> feeTrxn.getAccountFees().getFees().getGlCode(),
> FinancialConstants.DEBIT);
> </code>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://mifosforge.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
