[
http://mifosforge.jira.com/browse/MIFOS-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62052#action_62052
]
Udai Gupta edited comment on MIFOS-4148 at 11/17/10 11:51 PM:
--------------------------------------------------------------
This issue is because some deposits where made using M-Pesa plugin where the
customer_id in account_trxn table was left as null.
select * from account_payment accountpay0_ where accountpay0_.account_id=8125
and accountpay0_.PAYMENT_ID=141214
select * from account_trxn a where customer_id is null
Why customer_id was null when making deposit using M-PESA?
A transaction from M-PESA doesn't specify which client has made the
transaction, it just have the account in which the transaction is being made.
Mifos keep tracks of transactions by client, for example in a group loan or
group/centre savings account you can find out which client actually made the
transaction. This information goes into account_trxn.customer_id (from
PaymentData.customer).
So there is a mismatch in org.mifos.accounts.api.AccountPaymentParametersDto
and org.mifos.accounts.util.helpers.PaymentData.
What I can do to fix this issue?
- if there is no customer information(null check) in PaymentData then use
account.getCustomer() (which would be that group/center but not the actual
client who made the transaction).
OR
- We might have to include the information of client account in the M-PESA
format (if it is already not there)
What should we do to fix the database which has been already corrupted?
I think this was the test database, after fixing the code of 1.7.x it should
not happen again, but I want to reduce the effort of fixing the database if
that's acceptable.
There are only two records which I can update manually instead of creating a
query (or upgrade)
was (Author: ugupta):
This issue is because some deposits where made using M-Pesa plugin where
the customer_id in account_trxn table was left as null.
select * from account_payment accountpay0_ where accountpay0_.account_id=8125
and accountpay0_.PAYMENT_ID=141214
select * from account_trxn a where customer_id is null
Why customer_id was null when making deposit using M-PESA?
A transaction from M-PESA doesn't specify to which client has made the
transaction, it just have the account in which the transaction is being made.
Mifos keep tracks of transactions by client, for example in a group loan or
group/centre savings account you can find out which client actually made the
transaction. This information goes into account_trxn.customer_id (from
PaymentData.customer).
So there is a mismatch in org.mifos.accounts.api.AccountPaymentParametersDto
and org.mifos.accounts.util.helpers.PaymentData.
What I can do to fix this issue?
- if there is no customer information(null check) in PaymentData then use
account.getCustomer() (which would be that group/center but not the actual
client who made the transaction).
OR
- We might have to include the information of client account in the M-PESA
format (if it is already not there)
What should we do to fix the database which has been already corrupted?
I think this was the test database, after fixing the code of 1.7.x it should
not happen again, but I want to reduce the effort of fixing the database if
that's acceptable.
There are only two records which I can update manually instead of creating a
query (or upgrade)
> Exception viewing transaction history on savings for KEEF account
> -----------------------------------------------------------------
>
> Key: MIFOS-4148
> URL: http://mifosforge.jira.com/browse/MIFOS-4148
> Project: mifos
> Issue Type: Bug
> Components: Logging
> Affects Versions: Release E
> Reporter: jbrewster
> Assignee: Udai Gupta
> Priority: Major
> Fix For: Release E - Iteration 11, Release E
>
> Attachments: Mifos-keef.log
>
>
> While investigating MPESA issues, encountered an exception when trying to
> view transaction history.
> Repro:
> 1. load KEEF test data (contact Jeff or Jakub)
> 2. search for account 000100000008125
> 3. click on "View transaction history"
> actual: exception (see attachment)
> expected: view transaction log
--
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
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
