Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012754Openbravo ERP09. Financial managementpublic2010-03-22 09:082012-04-24 15:52
Reportermanishkp 
Assigned Tonaiaramartinez 
PriorityhighSeveritymajorReproducibilityalways
StatusscheduledResolutionopen 
PlatformOS10OS VersionXP
Product Version2.50MP9 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0012754: We Can Have Duplicate Tax Zone
DescriptionWe Can Have Duplicate Tax Zone which is a bug.
Steps To ReproduceOpen ERP application ->
Click Financial Management - >
Accounting -> Setup -> Tax Rate form ->
click new Tax Zone icon -> then add already available Tax Zone ->
Click Save button
Proposed Solution
Additional Information
TagsVMA-Reviewed
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-03-22 09:08manishkpNew Issue
2010-03-22 09:08manishkpAssigned To => dalsasua
2010-03-28 18:22dalsasuaStatusnew => acknowledged
2011-07-20 18:18dalsasuaAssigned Todalsasua => jonalegriaesarte
2012-04-03 12:20jonalegriaesarteAssigned Tojonalegriaesarte => vmromanos
2012-04-10 15:11vmromanosTag Attached: VMA-Reviewed
2012-04-16 13:59naiaramartinezAssigned Tovmromanos => naiaramartinez
2012-04-16 14:00naiaramartinezStatusacknowledged => scheduled
2012-04-16 14:00naiaramartinezfix_in_branch => pi
2012-04-24 15:52vmromanosOBNetwork customer => No
2012-04-24 15:52vmromanosNote Added: 0047918
2012-04-24 15:52vmromanosTypedefect => design defect
2012-04-24 15:52vmromanosfix_in_branchpi =>

Notes
(0047918)
vmromanos   
2012-04-24 15:52   
It's currently possible to have duplicated tax zones for the same tax rate which is something wrong that should be fixed.
However, the impact from a functional perspective is null, because the system only takes into account the first occurrence found in this table, so it doesn't matter the number of times the same tax zone has been defined.

The fix consists in creating a check constraint in a table, but this change could generate important problems when updating any instance that has already duplicated tax zones. That's why we have decided to move this issue to "design defect", that should be fixed in the next Openbravo major version.