Openbravo Issue Tracking System - Retail Modules
View Issue Details
0044530Retail ModulesWeb POSpublic2020-07-01 15:452020-07-28 13:15
maite 
ranjith_qualiantech_com 
urgentmajoralways
closedfixed 
5
 
RR20Q3 
adrianromero
No
0044530: "Cannot calculate receipt taxes" error raised due to timezone conversion
When a ticket is synchronized its 'originalOrderDate' field is converted to GMT. In a local environment running in GMT+2 this means that a ticket registered today (01/07/2020) has an 'originalOrderDate' set to "2020-06-30T22:00:00.000Z"

This 'originalOrderDate' is used when calculating the return's tax rate. So in case the tax rate used has Valid Date From 01/07/2020 no tax is found and error is raised:

Cannot calculate receipt taxes

Cannot find taxes for partner 'CCC' and address 'AAA'. The line affected will be deleted. Please ensure that there is at least one tax rate and tax rate zone configured for the partner address.
1. Create new Tax Category
2. Create new Tax Rate similar to "Entregas IVA 21%", setting Valid From 01/07/2020 and previous tax category
3. Modify Avalanche Transceiver product to set previous tax category
4. Log into the POS and create new ticket with Avalanche Transceiver product. Realize that the new tax is used
5. Register Verified Return from the previous ticket and realize that "Cannot calculate receipt taxes" error is raised
No tags attached.
related to defect 0039864 closed ranjith_qualiantech_com Taxes are recalculated in Verified Returns receipts and it should not be done 
diff 44530_20Q1.diff (589) 2020-07-28 13:00
https://issues.openbravo.com/file_download.php?file_id=14836&type=bug
Issue History
2020-07-01 15:45maiteNew Issue
2020-07-01 15:45maiteAssigned To => Retail
2020-07-01 15:45maiteResolution time => 1595368800
2020-07-01 15:45maiteTriggers an Emergency Pack => No
2020-07-01 15:46maiteIssue Monitored: networkb
2020-07-10 06:34ranjith_qualiantech_comAssigned ToRetail => ranjith_qualiantech_com
2020-07-13 08:19ranjith_qualiantech_comStatusnew => scheduled
2020-07-15 16:18ngarciaIssue Monitored: ngarcia
2020-07-20 07:00ranjith_qualiantech_comRelationship addedrelated to 0039864
2020-07-20 15:02ranjith_qualiantech_comNote Added: 0121533
2020-07-20 15:02ranjith_qualiantech_comStatusscheduled => feedback
2020-07-20 15:02ranjith_qualiantech_comAssigned Toranjith_qualiantech_com => maite
2020-07-21 12:15LeyreNote Added: 0121548
2020-07-21 12:15LeyreAssigned Tomaite => ranjith_qualiantech_com
2020-07-21 12:15LeyreStatusfeedback => new
2020-07-22 04:01ranjith_qualiantech_comNote Added: 0121555
2020-07-22 13:31adrianromeroStatusnew => feedback
2020-07-28 13:00ranjith_qualiantech_comFile Added: 44530_20Q1.diff
2020-07-28 13:15adrianromeroReview Assigned To => adrianromero
2020-07-28 13:15adrianromeroNote Added: 0121660
2020-07-28 13:15adrianromeroStatusfeedback => closed
2020-07-28 13:15adrianromeroResolutionopen => fixed
2020-07-28 13:15adrianromeroFixed in Version => RR20Q3

Notes
(0121533)
ranjith_qualiantech_com   
2020-07-20 15:02   
Not able to reproduce the issue
https://drive.google.com/file/d/1a52Znzm5SWs78MQbP9WBhq30SkDazxXK/view?usp=sharing [^]
(0121548)
Leyre   
2020-07-21 12:15   
To reproduce the issue:
Change the system timezone to GMT+2 and test with a Tax Rate valid from today.
(0121555)
ranjith_qualiantech_com   
2020-07-22 04:01   
Not able to reproduce with GMT+2 timezone
https://drive.google.com/file/d/1Yo1Hmn7wWPklvd_3etHY8lztyFYA8pHl/view?usp=sharing [^]
(0121660)
adrianromero   
2020-07-28 13:15   
This issue is not reproducible because the new taxes engine does not have this problem with dates.

Previous versions: RR20Q2, RR20Q1 can be fixed applying the attached patch 44530_20Q1.diff