Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0040834Retail ModulesWeb POSpublic2019-05-10 09:412019-08-01 08:08
Reporterfrancisco 
Assigned Tojorgewederago 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0040834: wrong conversion rate
DescriptionThe conversion rate is rounded weird and doesn't apply the correct amount
Steps To ReproduceGo to conversion rate windows

Set the conversion rate EUR to USD multiply rate by 4100
Set the conversion rate USD to EUR divide rate by 4100

Go to the POS and buy something,
ex: mini gps 100EUR, pay in USD and the value should be 410000 but instead is 409836.07
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2019-05-10 09:41franciscoNew Issue
2019-05-10 09:41franciscoAssigned To => platform
2019-05-10 09:41franciscoModules => Core
2019-05-10 09:41franciscoResolution time => 1559253600
2019-05-10 09:41franciscoTriggers an Emergency Pack => No
2019-05-10 09:55franciscoSummarywrong rate conversion => wrong conversion rate
2019-05-10 10:16alostaleAssigned Toplatform => Triage Finance
2019-05-10 12:44SandrahuguetAssigned ToTriage Finance => Retail
2019-05-11 13:47rqueraltaAssigned ToRetail => rqueralta
2019-05-11 13:48rqueraltaStatusnew => scheduled
2019-05-16 11:22egoitzProjectOpenbravo ERP => Retail Modules
2019-05-16 11:22egoitzCategoryA. Platform => Web POS
2019-05-16 15:30franciscoSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=18783#r18783
2019-05-31 15:38marvintmNote Added: 0112307
2019-05-31 15:38marvintmAssigned Torqueralta => jorgewederago
2019-05-31 15:38marvintmStatusscheduled => feedback
2019-06-19 16:33malsasuaNote Added: 0112903
2019-06-19 16:33malsasuaStatusfeedback => new
2019-06-19 16:34malsasuaResolution time1559253600 => 1563141600
2019-07-11 11:27ngarciaNote Edited: 0112903bug_revision_view_page.php?bugnote_id=0112903#r19093
2019-07-11 11:27ngarciaNote Edited: 0112903bug_revision_view_page.php?bugnote_id=0112903#r19094
2019-08-01 08:08marvintmReview Assigned To => marvintm
2019-08-01 08:08marvintmNote Added: 0113745
2019-08-01 08:08marvintmStatusnew => closed
2019-08-01 08:08marvintmResolutionopen => no change required

Notes
(0112307)
marvintm   
2019-05-31 15:38   
We need to clarify in the customer exactly the problem, because we think this functionality is working as designed
(0112903)
malsasua   
2019-06-19 16:33   
(edited on: 2019-07-11 11:27)
with multichange project, it is required a higher precision in backoffice - conversion rate

Should a buildvalidation or similar be created to prevent this problem?
(0113745)
marvintm   
2019-08-01 08:08   
Discussed internally, a modulescript should not be needed because only one customer received the initial version of this project, and it has since been updated to a recent version which contains the final version of the project.