Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0032813Retail ModulesWeb POSpublic2016-04-29 11:582016-05-30 10:35
Reporterngarcia 
Assigned ToRetail 
PriorityurgentSeveritymajorReproducibilityalways
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
Summary0032813: During Cash Up Financial Transactions are not rounded to 2 (standard precision) and the reconciliation gets unbalanced
DescriptionDuring Cash Up Financial Transactions are not rounded to 2 (standard precision) and the reconciliation gets unbalanced
Steps To ReproduceNote that is not it is not reproducible any more after the fix for the 32263 issue

As group admin role:
   Check the configuration of the currency is:
      Standard Precision: 2
      Price Precision: 4
      POS Precision: empty
In the frontend:
   Do a cashup
   Create a new ticket
   Add two products
   Modify its price to 10.2129 and 12.3369
   Pay it with cash
   Do the cash up and don't leave any amount as cash
In the backend:
   Check a transaction of 0.0020 has been created against "GL Item: VBS Cash differences"
   Check the sum of the transactions does not match the balance of the reconciliation
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 0032263RR16Q2 closed ranjith_qualiantech_com Sales Order's "Total Net Amount" different from sum of sales order line's "line net amount", when price precision = 6 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-04-29 11:58ngarciaNew Issue
2016-04-29 11:58ngarciaAssigned To => Retail
2016-04-29 11:58ngarciaResolution time => 1464472800
2016-04-29 11:58ngarciaTriggers an Emergency Pack => No
2016-04-29 11:58ngarciaIssue Monitored: networkb
2016-04-29 12:00ngarciaRelationship addedrelated to 0032263
2016-05-04 10:24OrekariaStatusnew => acknowledged
2016-05-12 13:34OrekariaRelationship replacedduplicate of 0032263
2016-05-12 13:35OrekariaDescription Updatedbug_revision_view_page.php?rev_id=12083#r12083
2016-05-12 13:35OrekariaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=12085#r12085
2016-05-30 10:34marvintmStatusacknowledged => scheduled
2016-05-30 10:35marvintmReview Assigned To => marvintm
2016-05-30 10:35marvintmNote Added: 0086794
2016-05-30 10:35marvintmStatusscheduled => closed
2016-05-30 10:35marvintmResolutionopen => no change required

Notes
(0086794)
marvintm   
2016-05-30 10:35   
As it is mentioned in the steps to reproduce, the problem doesn't happen anymore after fix for issue 32263. The data for the customer needs to be fixed, but this will be handled separately.