Error in create guarantor

[Mexina M Daniel]

Hi!

There is a bug on the message displayed when you create a guarantor and 
put a same client as a guarantor, When a client doesn't have a saving 
account the error says "A customer cannot serve as his own guarantor", 
shouldn't be "A customer can not serve as his own guarantor if he 
doesn't have a saving account"? because with a saving account, it 
works(he can be his own guarantor)


Can be reproduced by creating a loan product with mandatory guarantee(%) 
x, minimum guarantee from own funds(%) x, and 0 in minimum guarantee 
from guarantor fund(%). Then go to client (who has no saving account) 
and create new loan, before activate it go to "more" in a profile of a 
loan, and click "create guarantor". Enter the name of a client as a 
guarantor and submit, it will give an error "A customer cannot serve as 
his own guarantor"


Regards

--
Mexina M Daniel
Lead Software Developer
Research & Development

Tel:+255 222 618 511 | Mob: +255 712 110 791

Singo Africa Limited
Block G,Mbezi Beach B| 7 Nakawale Road| P.O.Box 78908| 14121 Dar es Salaam

singo.co.tz

Lets grow together

Re: Doubt on Center Savings Account

[Rajan Maurya]

Thanks Adi for the explanation :)




On Wed, Dec 7, 2016 at 9:34 AM, Adi Raju 
wrote:

> Centre and groups use same entity with just different groupType value.
>
> Either centre/group are identified with groupId itself.
>
> In other words, either of them are stored as an entry in m_group DB table.
>
>
>
> So creation of center savings account will use the same parameters as that
> of group savings account creation. groupId mentioned in the parameter will
> carry the centerId(virtually it is again a unique groupId)
>
>
>
> *Regards,*
>
> *Adi Raju*
>
>
>
> *Principal Architect, **Conflux Technologies Pvt Ltd
> *
>
> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> Bengaluru, Karnataka, 560043 INDIA
>
>
>
>
>
> Disclaimer: The information contained in this e-mail message and any
> files/attachment transmitted with it is confidential and for the sole use
> of the intended recipient(s) or entity identified. If you are not the
> intended recipient, please email: supp...@confluxtechnologies.com and
> destroy/delete all copies and attachment thereto along with the original
> message. Any unauthorised review, use, disclosure, dissemination,
> forwarding, printing or copying of this email or any action taken in
> reliance on this e-mail is strictly prohibited and is unlawful. The
> recipient acknowledges that Conflux Technologies Private Limited or its
> subsidiaries and associated companies are unable to exercise control or
> ensure or guarantee the integrity of/over the contents of the information
> contained in e-mail transmissions. Before opening any attachments, please
> check.
>
>
>
> [image: Finflux]
>
>
>
> *From:* Rajan Maurya [mailto:rajanmaurya...@gmail.com]
> *Sent:* 07 December 2016 08:26
> *To:* Ed Cable
> *Cc:* dev (dev@fineract.incubator.apache.org); Adi Raju
> *Subject:* Re: Doubt on Center Savings Account
>
>
>
> Hi All,
>
>
>
> I have looked the implementation at https://demo.openmf.org and found
> here we are making a request with the centerId and sending the centerId in
> the parameter "groupId: centerId."
>
>
>
> I am little confused why there is no parameter available for the
> "centerId: centerId."
>
> Thanks
>
>
>
> On Wed, Dec 7, 2016 at 2:04 AM, Ed Cable  wrote:
>
> I think it would just need the centerId. Can you look at what API is being
> called from the Center Savings Application link in the web app at
> https://demo3.openmf.org/#/viewcenter/17
>
>
>
> Adi - could you clarify Rajan's doubts?
>
>
>
> Ed
>
>
>
> On Tue, Dec 6, 2016 at 9:06 AM, Rajan Maurya 
> wrote:
>
> Hi Ed,
>
>
>
> I have some question regarding the https://github.com/openMF/
> android-client/issues/411.
>
> If I am right you want to add feature to create savings account for the
> center.
>
>
>
> I go though the REST API
>  doc
> and did not found any doc for creating the "SavingsAccount" for Center. I
> know these thing, creating SavingsAccount will work because it needs only
> unique id
>
> like *clientId, groupId, centerId. *
>
>
>
>
> *Please clear my doubt then I will finalize the PR.*
>
>
>
> --
>
> *Thanks*
>
> *Namaste*
>
>
>
> Rajan Maurya
>
> Contact Number : +91 8010665248
>
> Github : https://github.com/therajanmaurya
>
> College : Cluster Innovation Centre, University of Delhi
>
> Student : B.Tech. (Information Technology & Mathematical Innovations)
>
>
>
>
>
>
>
>
>
> --
>
> *Ed Cable*
>
> Director of Community Programs, Mifos Initiative
>
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
>
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
>
>
>
>
>
>
> --
>
> *Thanks*
>
> *Namaste*
>
>
>
> Rajan Maurya
>
> Contact Number : +91 8010665248
>
> Github : https://github.com/therajanmaurya
>
> College : Cluster Innovation Centre, University of Delhi
>
> Student : B.Tech. (Information Technology & Mathematical Innovations)
>
>
>



-- 
*Thanks*
*Namaste*

Rajan Maurya
Contact Number : +91 8010665248
Github : https://github.com/therajanmaurya
College : Cluster Innovation Centre, University of Delhi
Student : B.Tech. (Information Technology & Mathematical Innovations)

RE: Business Event Processor

[Adi Raju]

Hi Markus,

This proposal is mainly intended to help any synchronous processing
requirements.
For eg, In case of validation failure the API(command) should fail. 
I do not see ActiveMQ of help here.

Data Driven Authorisation as such is bigger feature umbrella, in that we
want to control data visibility even in the read APIs based on different
business rules.
In the example provided, "Data Driven Authorisation" was a simple validation
feature request, which requires allowing an API based on role and not just
permission assigned to the App User.

Regards,
Adi Raju

Principal Architect, Conflux Technologies Pvt Ltd
Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, Bengaluru,
Karnataka, 560043 INDIA


Disclaimer: The information contained in this e-mail message and any
files/attachment transmitted with it is confidential and for the sole use of
the intended recipient(s) or entity identified. If you are not the intended
recipient, please email: supp...@confluxtechnologies.com and destroy/delete
all copies and attachment thereto along with the original message. Any
unauthorised review, use, disclosure, dissemination, forwarding, printing or
copying of this email or any action taken in reliance on this e-mail is
strictly prohibited and is unlawful. The recipient acknowledges that Conflux
Technologies Private Limited or its subsidiaries and associated companies
are unable to exercise control or ensure or guarantee the integrity of/over
the contents of the information contained in e-mail transmissions. Before
opening any attachments, please check.



-Original Message-
From: Markus Gei? [mailto:markus.ge...@live.de] 
Sent: 05 December 2016 20:51
To: dev@fineract.incubator.apache.org
Subject: RE: Business Event Processor

Hey,

why not utilizing an existing event queue, e.g. ActiveMQ, to get this
feature in. I don't see any real benefit of creating our own mechanism for
this.

And I believe we are mixing requirements/features here, e.g. data driven
auth is not an event feature ... so it should not be modeled to become one.

Cheers

Markus

From: Adi Raju [mailto:adi.r...@confluxtechnologies.com]
Sent: Monday, December 5, 2016 10:14 AM
To: dev@fineract.incubator.apache.org
Subject: Business Event Processor

Hi All,

Of late, community has been building features like 'Workflow using
datatables', 'Triggered SMS', 'Notifications' etc, also we have many more
features in roadmap like 'Flagging of Accounts', 'Data Driven
Authorisation', 'Tasks Framework' etc. In all of these features, there is
one commonality, which is to listen on a business event on an entity and
perform either additional validation or processing. Drawback being that on
each such business event each of these additional processing/validation
results in a Database query to check if any additional processing or
validation is required. The more such features we continue to add, the more
we are slowing down the system by way of adding more and more DB calls
whether required or not. Also we are adding more and more new APIs and
related processing code which in my view is mundane as well as time
consuming. This design proposes to generalize all such features under one
single framework and API modelling, thus reducing the calls to DB and also
improving the turn-around time for feature addition.

https://cwiki.apache.org/confluence/display/FINERACT/Business+Event+Processo
r

Please review and provide your comments.

Regards,
Adi Raju

Principal Architect, Conflux Technologies Pvt
Ltd
Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, Bengaluru,
Karnataka, 560043 INDIA


Disclaimer: The information contained in this e-mail message and any
files/attachment transmitted with it is confidential and for the sole use of
the intended recipient(s) or entity identified. If you are not the intended
recipient, please email:
supp...@confluxtechnologies.com and
destroy/delete all copies and attachment thereto along with the original
message. Any unauthorised review, use, disclosure, dissemination,
forwarding, printing or copying of this email or any action taken in
reliance on this e-mail is strictly prohibited and is unlawful. The
recipient acknowledges that Conflux Technologies Private Limited or its
subsidiaries and associated companies are unable to exercise control or
ensure or guarantee the integrity of/over the contents of the information
contained in e-mail transmissions. Before opening any attachments, please
check.

[Finflux]

RE: Doubt on Center Savings Account

[Adi Raju]

Centre and groups use same entity with just different groupType value.

Either centre/group are identified with groupId itself.

In other words, either of them are stored as an entry in m_group DB table.

 

So creation of center savings account will use the same parameters as that of 
group savings account creation. groupId mentioned in the parameter will carry 
the centerId(virtually it is again a unique groupId)

 

Regards,

Adi Raju

 

Principal Architect,   Conflux 
Technologies Pvt Ltd

Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, Bengaluru, 
Karnataka, 560043 INDIA

 

 

Disclaimer: The information contained in this e-mail message and any 
files/attachment transmitted with it is confidential and for the sole use of 
the intended recipient(s) or entity identified. If you are not the intended 
recipient, please email:   
supp...@confluxtechnologies.com and destroy/delete all copies and attachment 
thereto along with the original message. Any unauthorised review, use, 
disclosure, dissemination, forwarding, printing or copying of this email or any 
action taken in reliance on this e-mail is strictly prohibited and is unlawful. 
The recipient acknowledges that Conflux Technologies Private Limited or its 
subsidiaries and associated companies are unable to exercise control or ensure 
or guarantee the integrity of/over the contents of the information contained in 
e-mail transmissions. Before opening any attachments, please check.

 

Finflux

 

From: Rajan Maurya [mailto:rajanmaurya...@gmail.com] 
Sent: 07 December 2016 08:26
To: Ed Cable
Cc: dev (dev@fineract.incubator.apache.org); Adi Raju
Subject: Re: Doubt on Center Savings Account

 

Hi All,

 

I have looked the implementation at https://demo.openmf.org and found here we 
are making a request with the centerId and sending the centerId in the 
parameter "groupId: centerId."  

 

I am little confused why there is no parameter available for the "centerId: 
centerId."

Thanks

  

 

 

On Wed, Dec 7, 2016 at 2:04 AM, Ed Cable  wrote:

I think it would just need the centerId. Can you look at what API is being 
called from the Center Savings Application link in the web app at 
https://demo3.openmf.org/#/viewcenter/17

 

Adi - could you clarify Rajan's doubts?

 

Ed

 

On Tue, Dec 6, 2016 at 9:06 AM, Rajan Maurya  wrote:

Hi Ed,

 

I have some question regarding the 
https://github.com/openMF/android-client/issues/411.

If I am right you want to add feature to create savings account for the center.

 

I go though the REST API 
  doc and 
did not found any doc for creating the "SavingsAccount" for Center. I know 
these thing, creating SavingsAccount will work because it needs only unique id 

like clientId, groupId, centerId. 

 

Please clear my doubt then I will finalize the PR.
  

 

 

-- 

Thanks

Namaste

 

Rajan Maurya

Contact Number : +91 8010665248  

Github : https://github.com/therajanmaurya

College : Cluster Innovation Centre, University of Delhi

Student : B.Tech. (Information Technology & Mathematical Innovations)

 









 

-- 

Ed Cable

Director of Community Programs, Mifos Initiative

edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

 

Collectively Creating a World of 3 Billion Maries | http://mifos.org  
    

 





 

-- 

Thanks

Namaste

 

Rajan Maurya

Contact Number : +91 8010665248

Github : https://github.com/therajanmaurya

College : Cluster Innovation Centre, University of Delhi

Student : B.Tech. (Information Technology & Mathematical Innovations)

 

Re: Doubt on Center Savings Account

[Rajan Maurya]

Hi All,

I have looked the implementation at https://demo.openmf.org and found here
we are making a request with the centerId and sending the centerId in the
parameter "groupId: centerId."

I am little confused why there is no parameter available for the "centerId:
centerId."

Thanks


On Wed, Dec 7, 2016 at 2:04 AM, Ed Cable  wrote:

> I think it would just need the centerId. Can you look at what API is being
> called from the Center Savings Application link in the web app at
> https://demo3.openmf.org/#/viewcenter/17
>
> Adi - could you clarify Rajan's doubts?
>
> Ed
>
> On Tue, Dec 6, 2016 at 9:06 AM, Rajan Maurya 
> wrote:
>
>> Hi Ed,
>>
>> I have some question regarding the https://github.com/openMF/
>> android-client/issues/411.
>> If I am right you want to add feature to create savings account for the
>> center.
>>
>> I go though the REST API
>> 
>> doc and did not found any doc for creating the "SavingsAccount" for Center.
>> I know these thing, creating SavingsAccount will work because it needs only
>> unique id
>> like *clientId, groupId, centerId. *
>>
>>
>> *Please clear my doubt then I will finalize the PR.*
>>
>> --
>> *Thanks*
>> *Namaste*
>>
>> Rajan Maurya
>> Contact Number : +91 8010665248
>> Github : https://github.com/therajanmaurya
>> College : Cluster Innovation Centre, University of Delhi
>> Student : B.Tech. (Information Technology & Mathematical Innovations)
>>
>>
>>
>>
>>
>
>
> --
> *Ed Cable*
> Director of Community Programs, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>   
>
>


-- 
*Thanks*
*Namaste*

Rajan Maurya
Contact Number : +91 8010665248
Github : https://github.com/therajanmaurya
College : Cluster Innovation Centre, University of Delhi
Student : B.Tech. (Information Technology & Mathematical Innovations)

Re: Doubt on Center Savings Account

[Ed Cable]

I think it would just need the centerId. Can you look at what API is being
called from the Center Savings Application link in the web app at
https://demo3.openmf.org/#/viewcenter/17

Adi - could you clarify Rajan's doubts?

Ed

On Tue, Dec 6, 2016 at 9:06 AM, Rajan Maurya 
wrote:

> Hi Ed,
>
> I have some question regarding the https://github.com/openMF/
> android-client/issues/411.
> If I am right you want to add feature to create savings account for the
> center.
>
> I go though the REST API
>  doc
> and did not found any doc for creating the "SavingsAccount" for Center. I
> know these thing, creating SavingsAccount will work because it needs only
> unique id
> like *clientId, groupId, centerId. *
>
>
> *Please clear my doubt then I will finalize the PR.*
>
> --
> *Thanks*
> *Namaste*
>
> Rajan Maurya
> Contact Number : +91 8010665248
> Github : https://github.com/therajanmaurya
> College : Cluster Innovation Centre, University of Delhi
> Student : B.Tech. (Information Technology & Mathematical Innovations)
>
>
>
>
>


-- 
*Ed Cable*
Director of Community Programs, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
  

[jira] [Updated] (FINERACT-273) "Recurring Deposit Product" should not be allowed to be created if the interest chart is not synched with Deposit Term and Frequency

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-273:
--
Component/s: (was: Loan)
 Savings

>  "Recurring Deposit Product" should not be allowed to be created  if the 
> interest chart is not synched with Deposit Term and Frequency
> --
>
> Key: FINERACT-273
> URL: https://issues.apache.org/jira/browse/FINERACT-273
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>
> Posted by Subramany at https://mifosforge.jira.com/browse/MIFOSX-1167
> Original Description:
>  it is allowing to create "Recurring Deposit Product" if the "Deposit Term" 
> and "Deposit every" are defined in Months and interest chart is defined in 
> weeks, It should be restricted to do so.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-273) "Recurring Deposit Product" should not be allowed to be created if the interest chart is not synched with Deposit Term and Frequency

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-273:
--
Attachment: TC-423 -Sheet001.ON 05.05.2014.png

>  "Recurring Deposit Product" should not be allowed to be created  if the 
> interest chart is not synched with Deposit Term and Frequency
> --
>
> Key: FINERACT-273
> URL: https://issues.apache.org/jira/browse/FINERACT-273
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
> Attachments: TC-423 -Sheet001.ON 05.05.2014.png
>
>
> Posted by Subramany at https://mifosforge.jira.com/browse/MIFOSX-1167
> Original Description:
>  it is allowing to create "Recurring Deposit Product" if the "Deposit Term" 
> and "Deposit every" are defined in Months and interest chart is defined in 
> weeks, It should be restricted to do so.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FINERACT-273) "Recurring Deposit Product" should not allowed to be created if the interest chart is not synched with Deposit Term and Frequency

[Santosh Math (JIRA)]

Santosh Math created FINERACT-273:
-

 Summary:  "Recurring Deposit Product" should not allowed to be 
created  if the interest chart is not synched with Deposit Term and Frequency
 Key: FINERACT-273
 URL: https://issues.apache.org/jira/browse/FINERACT-273
 Project: Apache Fineract
  Issue Type: Bug
  Components: Loan
Reporter: Santosh Math
Assignee: Markus Geiss
Priority: Minor


Posted by Subramany at https://mifosforge.jira.com/browse/MIFOSX-1167

Original Description:
 it is allowing to create "Recurring Deposit Product" if the "Deposit Term" and 
"Deposit every" are defined in Months and interest chart is defined in weeks, 
It should be restricted to do so.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-273) "Recurring Deposit Product" should not be allowed to be created if the interest chart is not synched with Deposit Term and Frequency

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-273:
--
Summary:  "Recurring Deposit Product" should not be allowed to be created  
if the interest chart is not synched with Deposit Term and Frequency  (was:  
"Recurring Deposit Product" should not allowed to be created  if the interest 
chart is not synched with Deposit Term and Frequency)

>  "Recurring Deposit Product" should not be allowed to be created  if the 
> interest chart is not synched with Deposit Term and Frequency
> --
>
> Key: FINERACT-273
> URL: https://issues.apache.org/jira/browse/FINERACT-273
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>
> Posted by Subramany at https://mifosforge.jira.com/browse/MIFOSX-1167
> Original Description:
>  it is allowing to create "Recurring Deposit Product" if the "Deposit Term" 
> and "Deposit every" are defined in Months and interest chart is defined in 
> weeks, It should be restricted to do so.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-271) Not able to Writeoff the loan if the writeoff date = any repayment date in periodic accrual

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-271:
--
Attachment: 2.png
1.png

> Not able to Writeoff the loan if the writeoff date = any repayment date in 
> periodic accrual
> ---
>
> Key: FINERACT-271
> URL: https://issues.apache.org/jira/browse/FINERACT-271
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: fineract-gci
> Attachments: 1.png, 2.png
>
>
> As reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1152.
> Original Description:
> 1. Create a loan product with periodic accrual accounting.
> 2. Create a client and attach the above mentioned loan product to that client.
> 3. Submit a new loan application on 02 April 2014 approve and disburse on the 
> same date.
> 4. Click on system -> Scheduler job -> Run the job " Add Accrual 
> Transactions".
> 5. In the above mentioned loan account page click on the Transactions - in 
> which accrual accounting with respect to each repayment is displayed.
> 6. Click on "More" tab and click on Writeoff button.
> 7. In loan writeoff page enter date as latest repayment date. (As displayed 
> in Transactions page) and click on submit button.
> Expected result:
> After the loan disbursement is done on any point of time it should allow to 
> writeoff the loan after last Transaction happened.(Here no transaction 
> happened after disbursement)
> Actual Result:
> Not able to writeoff the Loan since displayed error message as "The date of 
> the writeoff transaction must occur after the last transaction made against 
> this loan."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-272) Undo Loan transaction is not affecting the accrual accounting even if the loan is under " Non Performing Assets" (NPA) state

[Santosh Math (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-272:
--
Attachment: 3.png

> Undo Loan transaction is not affecting the accrual accounting even if the 
> loan is under " Non Performing Assets" (NPA) state
> 
>
> Key: FINERACT-272
> URL: https://issues.apache.org/jira/browse/FINERACT-272
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: fineract-gci
> Attachments: 3.png
>
>
> As posted by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1153
> Original Description:
> 1. Create a loan product with periodic accrual accounting and NPA as 10 days.
> 2. Create a client and attach the above mentioned loan product to that client.
> 3. Submit a new loan application on 01 April 2014 approve and disburse on the 
> same date.
> 4. Click on system -> Scheduler job -> Run the job "Update Non Performing 
> Assets".
> (In database m_loan table in "is_npa" column the status displayed as "1")
> 4. Again Run the job " Add Accrual Transactions".
> 5. Click on the Transaction button in the above created loan account in which 
> accrual accounting entries are not created because of loan under NPA state.
> 6. Make repayments on 08 April 2014 and 15 April 2014.
> 7. Click on system -> Scheduler job -> Run the job "Update Non Performing 
> Assets".
> (In database m_loan table in "is_npa" column the status displayed as "0")
> 8. Again Run the job " Add Accrual Transactions".
> 9. Click on the Transaction button in the above created loan account in which 
> accrual accrual accounting entries are created.
> 10. In the same transaction page delete the transaction on 15 April 2014.
> 11. Again Run the job " Add Accrual Transactions" and "Update Non Performing 
> Assets".
> Expected Result:
> Accrual entries created after NPA should get deleted in transaction page of 
> loan account.
> Actual Result:
> Accrual entries created after NPA staus is not getting deleted.
> (even In database m_loan table in "is_npa" column the status displayed as "1")



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FINERACT-272) Undo Loan transaction is not affecting the accrual accounting even if the loan is under " Non Performing Assets" (NPA) state

[Santosh Math (JIRA)]

Santosh Math created FINERACT-272:
-

 Summary: Undo Loan transaction is not affecting the accrual 
accounting even if the loan is under " Non Performing Assets" (NPA) state
 Key: FINERACT-272
 URL: https://issues.apache.org/jira/browse/FINERACT-272
 Project: Apache Fineract
  Issue Type: Bug
  Components: Loan
Reporter: Santosh Math
Assignee: Markus Geiss
Priority: Minor


As posted by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1153

Original Description:
1. Create a loan product with periodic accrual accounting and NPA as 10 days.
2. Create a client and attach the above mentioned loan product to that client.
3. Submit a new loan application on 01 April 2014 approve and disburse on the 
same date.
4. Click on system -> Scheduler job -> Run the job "Update Non Performing 
Assets".
(In database m_loan table in "is_npa" column the status displayed as "1")
4. Again Run the job " Add Accrual Transactions".
5. Click on the Transaction button in the above created loan account in which 
accrual accounting entries are not created because of loan under NPA state.
6. Make repayments on 08 April 2014 and 15 April 2014.
7. Click on system -> Scheduler job -> Run the job "Update Non Performing 
Assets".
(In database m_loan table in "is_npa" column the status displayed as "0")
8. Again Run the job " Add Accrual Transactions".
9. Click on the Transaction button in the above created loan account in which 
accrual accrual accounting entries are created.
10. In the same transaction page delete the transaction on 15 April 2014.
11. Again Run the job " Add Accrual Transactions" and "Update Non Performing 
Assets".
Expected Result:
Accrual entries created after NPA should get deleted in transaction page of 
loan account.
Actual Result:
Accrual entries created after NPA staus is not getting deleted.
(even In database m_loan table in "is_npa" column the status displayed as "1")



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FINERACT-271) Not able to Writeoff the loan if the writeoff date = any repayment date in periodic accrual

[Santosh Math (JIRA)]

Santosh Math created FINERACT-271:
-

 Summary: Not able to Writeoff the loan if the writeoff date = any 
repayment date in periodic accrual
 Key: FINERACT-271
 URL: https://issues.apache.org/jira/browse/FINERACT-271
 Project: Apache Fineract
  Issue Type: Bug
  Components: Loan
Reporter: Santosh Math
Assignee: Markus Geiss
Priority: Minor


As reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1152.
Original Description:

1. Create a loan product with periodic accrual accounting.
2. Create a client and attach the above mentioned loan product to that client.
3. Submit a new loan application on 02 April 2014 approve and disburse on the 
same date.
4. Click on system -> Scheduler job -> Run the job " Add Accrual Transactions".
5. In the above mentioned loan account page click on the Transactions - in 
which accrual accounting with respect to each repayment is displayed.
6. Click on "More" tab and click on Writeoff button.
7. In loan writeoff page enter date as latest repayment date. (As displayed in 
Transactions page) and click on submit button.
Expected result:
After the loan disbursement is done on any point of time it should allow to 
writeoff the loan after last Transaction happened.(Here no transaction happened 
after disbursement)
Actual Result:
Not able to writeoff the Loan since displayed error message as "The date of the 
writeoff transaction must occur after the last transaction made against this 
loan."



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-21) Waive overdue charge is not working as expected

[Abdul Aziz Ali (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15725047#comment-15725047
 ] 

Abdul Aziz Ali commented on FINERACT-21:


Potentially this is related to FINERACT-7 / MIFOS-2495

> Waive overdue charge is not working as expected
> ---
>
> Key: FINERACT-21
> URL: https://issues.apache.org/jira/browse/FINERACT-21
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>
> https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments
> 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply 
> the above created charge to it.
> 2. Submit new loan application for a client on 01 October 2015 approve and 
> disburse on same date.
> 3. Execute the scheduler job "Apply penalty for overdue loans",
> 4. Navigate back to the same loan account page and click on the charges and 
> waive charge on 01 November 2015.
> > Charge got waved, but in the repayment schedule wrong entries got created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-232) Ability to Post General Ledger Entries Directly to Customer Account

[Ippez Roberts (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ippez Roberts updated FINERACT-232:
---
Attachment: Enhancements for Journal Entry.pdf

Detailed Description for Batch Transaction improvement

> Ability to Post General Ledger Entries Directly to Customer Account
> ---
>
> Key: FINERACT-232
> URL: https://issues.apache.org/jira/browse/FINERACT-232
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Dayna Harp
>Assignee: Markus Geiss
> Attachments: Enhancements for Journal Entry.pdf
>
>
> https://mifosforge.jira.com/browse/MIFOSX-2182
> From MIFOS X: As an accountant, i would like to be able to make a transfer 
> from a client's account (Savings Account or Loan Account) to a GL Account and 
> also be able to make transfer from a GL Account (e.g Cash at Hand) to 
> Client's Account (e.g Savings Account or Loan Account)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-270) Unable to waive all Loan charges

[Abdul Aziz Ali (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abdul Aziz Ali updated FINERACT-270:

Attachment: pruned_catalina.log

Attached is a pruned tomcat log file with stacktrace

> Unable to waive all Loan charges
> 
>
> Key: FINERACT-270
> URL: https://issues.apache.org/jira/browse/FINERACT-270
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
> Environment: Reproducible on demo.openmf.org. 
> Create new client Loan with FINERACT_7-MIFOS_2495
>Reporter: Abdul Aziz Ali
>Assignee: Markus Geiss
>Priority: Trivial
> Attachments: pruned_catalina.log
>
>
> Create Loan and Charge similar to FINERACT-7
> 
> (verbatim from FINERACT-7)
> 1. Create Installment fee for a loan as 100-Flat-Regular. 
> 2. Create loan product with following datasets and attache above installment 
> fee to that.
> Terms vary based on loan cycle :  FALSE
> Principal:10,000 ( Min: , Max : )
> Number of Repayments: 12 ( Min: , Max
> Repay Every:  1 Months
> Nominal Interest Rate:1 ( Min: , Max Per month
> Minimum days between disbursal and first repayment date   
> Amortization  Equal installments
> Interest Method   Declining Balance
> Interest Calculation Period   Daily
> Repayment StrategyOverdue/Due Fee/Int,Principal
> Account moves out of NPA only after all arrears have been cleared?No
> Days in year  Actual
> Days in month Actual
> Principal Threshold (%) for Last Instalment   0
> Allow fixing of the installment amountNo
> Interest Recalculation
> Recalculate Interest  Yes
> Advance payments adjustment type  Reduce number of installments
> Pre-closure interest calculation rule Calculate till pre closure date
> Interest recalculation compounding on None
> Frequency for recalculate Outstanding Principal   Daily
> Frequency Interval for recalculation  1
> Frequency Date for recalculation  01-Jan-15
> Is Arrears recognization based on original schedule:No.
> 3. Submit new loan application on 01 October 2015. Approve and disburse loan 
> on same date.
> 4. Click on waive charge and select for 1st repayment.
> 5. Repayment schedule generated after waive charge is not proper
> >Waive charge is happening not for first installment instead for other 
> >installment it is happening.
> 6. For first repayment the due is getting displayed.
> 
> 7. Keep waiving all charges until the last one
> The last one does not get waived nor does the Exception get raised to the UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FINERACT-269) Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and Recuring Deposit Account

[Ippez Roberts (JIRA)]

Ippez Roberts created FINERACT-269:
--

 Summary: Add Info Base on Clients Account - Loans, Shares, Fixed 
Deposit, Loans and Recuring Deposit Account
 Key: FINERACT-269
 URL: https://issues.apache.org/jira/browse/FINERACT-269
 Project: Apache Fineract
  Issue Type: Improvement
Reporter: Ippez Roberts
Assignee: Markus Geiss
 Attachments: Infobase.pdf

Infobase
This allows you to add free-form descriptions or notes to certain accounts. 
These notes can be unlimited in size and can be used to provide all kind of 
additional information about any account or its owner.

Later then whenever this account will be accessed this information will be 
displayed on the screen as in following example.

See attachment for visual explanation
 





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-269) Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and Recuring Deposit Account

[Ippez Roberts (JIRA)]

 [ 
https://issues.apache.org/jira/browse/FINERACT-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ippez Roberts updated FINERACT-269:
---
Attachment: Infobase.pdf

> Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and 
> Recuring Deposit Account
> ---
>
> Key: FINERACT-269
> URL: https://issues.apache.org/jira/browse/FINERACT-269
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
> Attachments: Infobase.pdf
>
>
> Infobase
> This allows you to add free-form descriptions or notes to certain accounts. 
> These notes can be unlimited in size and can be used to provide all kind of 
> additional information about any account or its owner.
> Later then whenever this account will be accessed this information will be 
> displayed on the screen as in following example.
> See attachment for visual explanation
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-7) Repayment Schedule after waive fee not correct

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15725022#comment-15725022
 ] 

ASF GitHub Bot commented on FINERACT-7:
---

GitHub user abdulazizali77 opened a pull request:

https://github.com/apache/incubator-fineract/pull/256

FINERACT-7: Sort loanInstallmentCharges before updating

Less than ideal fix (sorting overhead), but most topically contained. 
Potentially we should change the Sets to Lists, and or redefine the Entities, 
but that would affect too many things.

Have left a potentially iffy corner case in updateInstallmentCharges as is.

Additionally there is a pre-existing defect where a PersistenceException 
caused by an FK constraint is raised when all of the charges are waived. Have 
not investigated, potentially there is an existing bug.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/abdulazizali77/incubator-fineract FINERACT-7

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-fineract/pull/256.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #256


commit ebea611024d237e5388d5ba987a1798321fbd58f
Author: abdulazizali77 
Date:   2016-12-06T10:09:03Z

FINERACT-7: Make LoanInstallmentCharge and LoanRepaymentSchedule sortable

commit 515a4a28c8a945f35229e7f60098f010091baee3
Author: abdulazizali77 
Date:   2016-12-06T10:10:14Z

FINERACT-7: Sort old loanInstallmentCharges and new lic before updating




> Repayment Schedule after waive fee not correct
> --
>
> Key: FINERACT-7
> URL: https://issues.apache.org/jira/browse/FINERACT-7
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Dayna Harp
>Assignee: Markus Geiss
> Attachments: 1.jpg, 2.jpg, 3.jpg
>
>
> https://mifosforge.jira.com/browse/MIFOSX-2495
> After waive installment fee the repayment schedule generated is not proper
> 1. Create Installment fee for a loan as 100-Flat-Regular. 
> 2. Create loan product with following datasets and attache above installment 
> fee to that.
> Terms vary based on loan cycle :  FALSE
> Principal:10,000   ( Min: , Max : )
> Number of Repayments: 12   ( Min: , Max
> Repay Every:  1  Months
> Nominal Interest Rate:1   ( Min: , Max  Per month
> Minimum days between disbursal and first repayment date   
> Amortization  Equal installments
> Interest Method   Declining Balance
> Interest Calculation Period   Daily
> Repayment StrategyOverdue/Due Fee/Int,Principal
> Account moves out of NPA only after all arrears have been cleared?No
> Days in year  Actual
> Days in month Actual
> Principal Threshold (%) for Last Instalment   0
> Allow fixing of the installment amountNo
> Interest Recalculation
> Recalculate Interest  Yes
> Advance payments adjustment type  Reduce number of installments
> Pre-closure interest calculation rule Calculate till pre closure date
> Interest recalculation compounding on None
> Frequency for recalculate Outstanding Principal   Daily
> Frequency Interval for recalculation  1
> Frequency Date for recalculation  01-Jan-15
> Is Arrears recognization based on original schedule:No.
> 3. Submit new loan application on 01 October 2015. Approve and disburse loan 
> on same date.
> 4. Click on waive charge and select for 1st repayment.
> 5. Repayment schedule generated after waive charge is not proper
> >Waive charge is happening not for first installment instead for other 
> >installment it is happening.
> 6. For first repayment the due is getting displayed.
> Attachments here: https://mifosforge.jira.com/browse/MIFOSX-2495



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (FINERACT-270) Unable to waive all Loan charges

[Abdul Aziz Ali (JIRA)]

Abdul Aziz Ali created FINERACT-270:
---

 Summary: Unable to waive all Loan charges
 Key: FINERACT-270
 URL: https://issues.apache.org/jira/browse/FINERACT-270
 Project: Apache Fineract
  Issue Type: Bug
  Components: Loan
 Environment: Reproducible on demo.openmf.org. 
Create new client Loan with FINERACT_7-MIFOS_2495
Reporter: Abdul Aziz Ali
Assignee: Markus Geiss
Priority: Trivial
 Attachments: pruned_catalina.log

Create Loan and Charge similar to FINERACT-7

(verbatim from FINERACT-7)
1. Create Installment fee for a loan as 100-Flat-Regular. 
2. Create loan product with following datasets and attache above installment 
fee to that.
Terms vary based on loan cycle :FALSE
Principal:  10,000 ( Min: , Max : )
Number of Repayments:   12 ( Min: , Max
Repay Every:1 Months
Nominal Interest Rate:  1 ( Min: , Max Per month
Minimum days between disbursal and first repayment date 
AmortizationEqual installments
Interest Method Declining Balance
Interest Calculation Period Daily
Repayment Strategy  Overdue/Due Fee/Int,Principal
Account moves out of NPA only after all arrears have been cleared?  No
Days in yearActual
Days in month   Actual
Principal Threshold (%) for Last Instalment 0
Allow fixing of the installment amount  No
Interest Recalculation  
Recalculate InterestYes
Advance payments adjustment typeReduce number of installments
Pre-closure interest calculation rule   Calculate till pre closure date
Interest recalculation compounding on   None
Frequency for recalculate Outstanding Principal Daily
Frequency Interval for recalculation1
Frequency Date for recalculation01-Jan-15
Is Arrears recognization based on original schedule:No.
3. Submit new loan application on 01 October 2015. Approve and disburse loan on 
same date.
4. Click on waive charge and select for 1st repayment.
5. Repayment schedule generated after waive charge is not proper
>Waive charge is happening not for first installment instead for other 
>installment it is happening.
6. For first repayment the due is getting displayed.

7. Keep waiving all charges until the last one
The last one does not get waived nor does the Exception get raised to the UI.






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)