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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0051712
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Web POSminoralways2023-02-27 23:342023-03-08 13:19
ReporteraxelmercadoView Statuspublic 
Assigned ToTriage Omni OMS 
PriorityurgentResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Versionpi
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned Toaferraz
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0051712: Tax application error in POS

DescriptionWhen we have 2 taxes that are applicable in a country and we make a sale of a product where these taxes apply, we can observe that both apply.
Steps To ReproduceIn livebuilds:
1- For example, 2 similar taxes are configured: Entregas IVA 21% and Entregas IVA 22.

2- In the POS if we sell any product, both taxes are applied.

3- In the backoffice, if we go to the Sales Order window, we can see that it has as tax Entregas IVA 21%, but in the lines appear both taxes.

Video: https://drive.google.com/file/d/1NmDg6Ytw2a6Tfpz5xKrvjh4G1mhuEv9D/view [^]
Proposed SolutionCreate an Event Handler to warn end user when creating or updating a Tax Rate with an already existing configuration in the back office.
TagsNo tags attached.
Attached Filespng file icon Screenshot from 2023-02-28 12-00-20.png [^] (111,912 bytes) 2023-02-28 12:00


png file icon Screenshot from 2023-02-28 12-00-46.png [^] (130,216 bytes) 2023-02-28 12:00


png file icon Screenshot from 2023-02-28 12-59-53.png [^] (91,920 bytes) 2023-02-28 13:00


png file icon Screenshot from 2023-02-28 13-01-28.png [^] (161,557 bytes) 2023-02-28 13:01


png file icon Screenshot from 2023-02-28 13-01-48.png [^] (232,337 bytes) 2023-02-28 13:01


png file icon Screenshot from 2023-02-28 13-44-37.png [^] (236,272 bytes) 2023-02-28 13:52


png file icon Screenshot from 2023-02-28 13-44-39.png [^] (234,718 bytes) 2023-02-28 13:52


png file icon Screenshot from 2023-02-28 13-49-00.png [^] (237,005 bytes) 2023-02-28 13:52


png file icon Screenshot from 2023-02-28 13-51-35.png [^] (297,058 bytes) 2023-02-28 13:52

- Relationships [ Relation Graph ] [ Dependency Graph ]
duplicate of defect 0048580 closedebecerra POS2 2693: Tax engine is not working well when several tax zones are defined 
related to defect 0048737 closedaferraz Retail Modules Performance problem in Tax Engine having tax rules with many tax zones 

-  Notes
(0147086)
psanjuan (manager)
2023-02-28 09:23

 Hello Axel,
Please attached 2 images in which we can see the full set up of these two tax rates.
Let us also know the OB version, and the customer being used (setup of the customer, mainly location).
thanks,
Patricia.
(0147087)
Practics (reporter)
2023-02-28 09:26

 Hola Patricia, has visto el video que grabé yo mismo? Que te falta en ese video?
(0147088)
psanjuan (manager)
2023-02-28 09:28

 Why this issue is critical. First thing I see is that these two taxes should not belong to the same tax category as the rate is not the same. One is 21 and the other one is 22. Is this a real example or just a test?.
Please remove critical severity.
(0147106)
psanjuan (manager)
2023-02-28 11:55
edited on: 2023-02-28 13:05

 Steps to reproduce:
- configure a tax rate (1=Exportaciones) that includes Spain as From Country and UK as Destination country with no Destination Region.
- configure a second tax rate (2) sames as above one, but just adding a Destination region "Avon" (of UK).
-Create a BP located in UK with no region.
- Create a Sales in the POS for that UK customer, Delivery Terms = Home Delivery, verify that both tax rates (1) and (2) are selected. This is not correct as in this case the one without region should have been taken into account as the BP does not have a region.

Moreover, If a region is configured in the BP, the POS selects the proper one, but as the POS does not allow the creation of BP with Region, if two tax rates apply one with region, and another one without, the one without region should be used.
(0147107)
psanjuan (manager)
2023-02-28 12:55
edited on: 2023-02-28 13:05

 This issue can be reproduced in 21Q3.
It can not be reproduce in main (see images attached).

To be analized.

In any case, if two tax rates are exactly the same, both will be shown in the POS.
(0147108)
aferraz (manager)
2023-02-28 13:47

 When we define two tax rates with exactly the same configuration (same tax category, starting date, origin/destination country, origin/destination region, etc.) both taxes will apply to the sale.

In case both tax rates have the same configuration, but with a different destination region, the tax with destination region equals the store region (when delivering at store) or equals the customer region (when doing home delivery) will apply.
(0147152)
psanjuan (manager)
2023-03-01 09:27

 Backport of issue 48580 to 21Q3 to be created.
(0147379)
aferraz (manager)
2023-03-08 13:10
edited on: 2023-03-08 13:22

 Reopening the issue as it describes the scenario of having two tax rates with exactly the same configuration.
Severity changed to minor as this is a configuration problem and proposed solution updated to warn the end user when creating this wrong configuration in the backoffice.

Openbravo POS Tax Engine is not going to be changed, under the assumption that two tax rates must not be exactly the same.

The scenario about having two tax rates with the same configuration but different destination region is already fixed in 0048580.

- Issue History
Date Modified Username Field Change
2023-02-27 23:34 axelmercado New Issue
2023-02-27 23:34 axelmercado Assigned To => Retail
2023-02-27 23:34 axelmercado Triggers an Emergency Pack => No
2023-02-28 07:51 Practics Issue Monitored: Practics
2023-02-28 09:23 psanjuan Note Added: 0147086
2023-02-28 09:23 psanjuan Assigned To Retail => axelmercado
2023-02-28 09:23 psanjuan Status new => feedback
2023-02-28 09:26 Practics Note Added: 0147087
2023-02-28 09:28 psanjuan Note Added: 0147088
2023-02-28 11:55 psanjuan Note Added: 0147106
2023-02-28 11:55 psanjuan Assigned To axelmercado => aferraz
2023-02-28 11:55 psanjuan Severity critical => major
2023-02-28 11:55 psanjuan Status feedback => scheduled
2023-02-28 11:59 psanjuan Note Edited: 0147106 View Revisions
2023-02-28 11:59 psanjuan File Added: Screenshot from 2023-02-28 11-49-59.png
2023-02-28 12:00 psanjuan File Deleted: Screenshot from 2023-02-28 11-49-59.png
2023-02-28 12:00 psanjuan File Added: Screenshot from 2023-02-28 12-00-20.png
2023-02-28 12:00 psanjuan File Added: Screenshot from 2023-02-28 12-00-46.png
2023-02-28 12:01 psanjuan File Added: Screenshot from 2023-02-28 12-01-02.png
2023-02-28 12:54 psanjuan Note Edited: 0147106 View Revisions
2023-02-28 12:55 psanjuan Note Added: 0147107
2023-02-28 12:57 psanjuan Note Edited: 0147107 View Revisions
2023-02-28 12:59 psanjuan File Deleted: Screenshot from 2023-02-28 12-01-02.png
2023-02-28 13:00 psanjuan File Added: Screenshot from 2023-02-28 12-59-53.png
2023-02-28 13:01 psanjuan File Added: Screenshot from 2023-02-28 13-01-28.png
2023-02-28 13:01 psanjuan File Added: Screenshot from 2023-02-28 13-01-48.png
2023-02-28 13:05 psanjuan Note Edited: 0147106 View Revisions
2023-02-28 13:05 psanjuan Note Edited: 0147107 View Revisions
2023-02-28 13:29 aferraz Relationship added related to 0048580
2023-02-28 13:31 aferraz Relationship added related to 0048737
2023-02-28 13:47 aferraz Review Assigned To => aferraz
2023-02-28 13:47 aferraz Relationship replaced duplicate of 0048580
2023-02-28 13:47 aferraz Note Added: 0147108
2023-02-28 13:47 aferraz Status scheduled => closed
2023-02-28 13:47 aferraz Resolution open => duplicate
2023-02-28 13:52 aferraz File Added: Screenshot from 2023-02-28 13-44-37.png
2023-02-28 13:52 aferraz File Added: Screenshot from 2023-02-28 13-44-39.png
2023-02-28 13:52 aferraz File Added: Screenshot from 2023-02-28 13-49-00.png
2023-02-28 13:52 aferraz File Added: Screenshot from 2023-02-28 13-51-35.png
2023-03-01 09:27 psanjuan Note Added: 0147152
2023-03-08 13:10 aferraz Note Added: 0147379
2023-03-08 13:10 aferraz Status closed => new
2023-03-08 13:10 aferraz Resolution duplicate => open
2023-03-08 13:10 aferraz Assigned To aferraz => Triage Omni OMS
2023-03-08 13:10 aferraz Severity major => minor
2023-03-08 13:12 aferraz Proposed Solution updated
2023-03-08 13:19 aferraz Proposed Solution updated
2023-03-08 13:22 psanjuan Note Edited: 0147379 View Revisions

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker