Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #20504 All Revisions ] Back to Issue ]
Summary 0020504: "Copy Lines" process should shown proper error message instead of "Process failed during execution"
Revision 2012-05-15 13:29 by maite
Steps To Reproduce 1. Create new tax category "tc"
2. Go to GL Item window and create new gl item. Check "Enable in financial invoice" and set tax category= tc
3. Create new purchase invoice for any partner. Add line checking "Financial Invoice Line" and choosing your gl item. Set any price and tax and complete invoice.
4. Create new purchase invoice for same partner and press "Copy lines" button. Select invoice created previously and run process.

Error "Process failed during execution" will be raised.

If you have a look to log you can verify that "c_invoiceline_check2" restriction has been raised.

Possible missing configurations:
- tax category associated to product/glitem does not have tax rate associated

In that case, problem is that tax category "tc" associated to glitem does not have any tax rate associated.

Proper error should be raised indicating what is missed configuration causing this problem so user can correct it.
Revision 2012-05-15 13:23 by maite
Steps To Reproduce 1. Create new tax category "tc"
2. Go to GL Item window and create new gl item. Check "Enable in financial invoice" and set tax category= tc
3. Create new purchase invoice for any partner. Add line checking "Financial Invoice Line" and choosing your gl item. Set any price and tax and complete invoice.
4. Create new purchase invoice for same partner and press "Copy lines" button. Select invoice created previously and run process.

Error "Process failed during execution" will be raised.

If you have a look to log you can verify that "c_invoiceline_check2" restriction has been raised.

In that case, problem is that tax category "tc" associated to glitem does not have any tax rate associated.

Proper error should be raised indicating what is missed configuration causing this problem so user can correct it.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker