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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0032813
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Web POSmajoralways2016-04-29 11:582016-05-30 10:35
ReporterngarciaView Statuspublic 
Assigned ToRetail 
PriorityurgentResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tomarvintm
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0032813: 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
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
duplicate of defect 0032263RR16Q2 closedranjith_qualiantech_com Sales Order's "Total Net Amount" different from sum of sales order line's "line net amount", when price precision = 6 

-  Notes
(0086794)
marvintm (manager)
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.

- Issue History
Date Modified Username Field Change
2016-04-29 11:58 ngarcia New Issue
2016-04-29 11:58 ngarcia Assigned To => Retail
2016-04-29 11:58 ngarcia Resolution time => 1464472800
2016-04-29 11:58 ngarcia Triggers an Emergency Pack => No
2016-04-29 11:58 ngarcia Issue Monitored: networkb
2016-04-29 12:00 ngarcia Relationship added related to 0032263
2016-05-04 10:24 Orekaria Status new => acknowledged
2016-05-12 13:34 Orekaria Relationship replaced duplicate of 0032263
2016-05-12 13:35 Orekaria Description Updated View Revisions
2016-05-12 13:35 Orekaria Steps to Reproduce Updated View Revisions
2016-05-30 10:34 marvintm Status acknowledged => scheduled
2016-05-30 10:35 marvintm Review Assigned To => marvintm
2016-05-30 10:35 marvintm Note Added: 0086794
2016-05-30 10:35 marvintm Status scheduled => closed
2016-05-30 10:35 marvintm Resolution open => no change required


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker