[
http://mifosforge.jira.com/browse/MIFOS-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
johnwoodlock resolved MIFOS-3699.
---------------------------------
Resolution: Fixed
Story Points: 0.5
There was a need to break down certain financial actions into which account
actions they were related to in order to identify the right voucher. Below is
a representation of this change.
(CASE fintrxn.fin_action_id
WHEN 1, 2, 4, 6 then /*PRINCIPALPOSTING, INTERESTPOSTING, MISCFEEPOSTING,
MISCPENALTYPOSTING*/
(CASE atrxn.account_action_id
WHEN 1 then 'RECEIPT' /*LoanRepayment*/
WHEN 9 then 'JOURNAL' /*Adjustment (undoes LoanRepayment)*/
WHEN 18 then 'JOURNAL' /*LoanReversal (reverses fees & payments
parts)*/
ELSE concat('Unknown Account Action:', atrxn.account_action_id,
' for Finanical Action ', fintrxn.fin_action_id)
END)
WHEN 3 then /*FEEPOSTING*/
(CASE atrxn.account_action_id
WHEN 4 then 'RECEIPT' /*Fee*/
WHEN 18 then 'JOURNAL' /*LoanReversal (reverses fees & payments
parts)*/
WHEN 12 then 'RECEIPT' /*Customer Fee*/
WHEN 13 THEN 'JOURNAL' /*CustomerAdjustment*/
ELSE concat('Unknown Account Action:', atrxn.account_action_id,
' for Finanical Action ', fintrxn.fin_action_id)
END)
WHEN 7 then /*DISBURSAL*/
(CASE atrxn.account_action_id
WHEN 10 then 'PAYMENT' /*Disbursal*/
WHEN 19 then 'JOURNAL' /*DisrbursalAmountReversal (undoes
Disbursal part)*/
- Hide quoted text -
ELSE concat('Unknown Account Action:', atrxn.account_action_id,
' for Finanical Action ', fintrxn.fin_action_id)
END)
Further testing identified a couple of places where this logic needed to be
extended.
"there were 2 missing mappings (this is where I hadn't anticipated the
relationship between financial and account actions)
1) 'Loan Processing Fee' & 'Early Repayment Penalty Fee'. These are financial
action '3' (fee) and are associated with an account action of 1 (loan
repayment). I didn't have this mapping.
2) 'Miscellaneous Penalty' - this was financial action 6 (miscpenalty) ,
account action 12 (CustomerAccountRepayment)
So I put these in, all as RECEIPT vouchers, is that ok or are there journals
amongst them ? I've update git and tested again on mifos_lightmf and all seems
good now.
The positive thing about this is that if there are any more missing mappings
they do appear as 'unknown' and can be rectified pretty quickly."
> Adjustments are incorrect in Tally GL Interface Report
> ------------------------------------------------------
>
> Key: MIFOS-3699
> URL: http://mifosforge.jira.com/browse/MIFOS-3699
> Project: mifos
> Issue Type: Bug
> Reporter: Kay Chau
> Assignee: johnwoodlock
> Priority: Critical
> Fix For: Release E - Iteration 7, Release E
>
>
> Turns out we need to go back to Plan A.
> Adjustments do need to be the opposite voucher type of the original
> transaction it was adjusting.
> For example, if an adjustment is made on a loan repayment - the original
> transaction is logged as RECEIPT, but the adjustment needs to roll up to
> PAYMENT.
> If an adjustment is made on a disbursal, the original transaction is a
> PAYMENT, but the adjustment needs to roll up to a RECEIPT.
--
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
