Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0039793 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Retail Modules] Web POS | major | always | 2018-12-12 16:55 | 2018-12-19 10:42 | |||
| Reporter | samuel_nicuesa | View Status | public | |||||
| Assigned To | ranjith_qualiantech_com | |||||||
| Priority | normal | Resolution | no change required | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | pi | SCM revision | ||||||
| Review Assigned To | marvintm | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0039793: Remaining field is not working properly executing cash up with 3 decimals. | |||||||
| Description | Remaining field is not working properly executing cash up with 3 decimals. | |||||||
| Steps To Reproduce | [BO] Configure 3 decimals for product price and Web POS. Change product price for one product setting amount 0.002 [POS] Create a new ticket and add the product Pay the ticket Do cash up You will see in Count Cash that Total = 0.002 and Remaining = -0.002 If you count 0.010 remaining changes to 0.010 but it is not correct because Total = 0.002 and Counted = 0.010 See attached images | |||||||
| Tags | No tags attached. | |||||||
| Attached Files |  Cashup1.png [^] (61,378 bytes) 2018-12-12 16:55
Cashup2.png [^] (62,526 bytes) 2018-12-12 16:56
Cashup3.png [^] (64,835 bytes) 2018-12-12 16:56
| |||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0108669) marvintm (manager) 2018-12-19 10:42 |
After some further discussion, we have concluded that the current behaviour is correct. The problem comes from the fact that the customer is using decimal precision 3 in the currency, but the created coins only have two decimals precision. Therefore, when paying tickets, it's not possible to pay the exact amount. The WebPOS assumes that the change will be returned to the customer, but it is kept in the till instead. Therefore, in the end the amount Openbravo assumed that was kept in the till is different from reality. This explains why later on, in the cashup, the expected amount doesn't match with the counted amount. There is a new functionality in 19Q1 version of Openbravo called "multichange" which was designed to cover this particular case, and could be used to avoid this problem. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2018-12-12 16:55 | samuel_nicuesa | New Issue | |
| 2018-12-12 16:55 | samuel_nicuesa | Assigned To | => Retail |
| 2018-12-12 16:55 | samuel_nicuesa | Resolution time | => 1546383600 |
| 2018-12-12 16:55 | samuel_nicuesa | Triggers an Emergency Pack | => No |
| 2018-12-12 16:55 | samuel_nicuesa | File Added: Cashup1.png | |
| 2018-12-12 16:56 | samuel_nicuesa | File Added: Cashup2.png | |
| 2018-12-12 16:56 | samuel_nicuesa | File Added: Cashup3.png | |
| 2018-12-12 17:11 | rafaroda | Issue Monitored: rafaroda | |
| 2018-12-13 11:03 | ranjith_qualiantech_com | Assigned To | Retail => ranjith_qualiantech_com |
| 2018-12-13 11:04 | ranjith_qualiantech_com | Status | new => scheduled |
| 2018-12-13 12:15 | ranjith_qualiantech_com | Relationship added | caused by 0031962 |
| 2018-12-19 10:42 | marvintm | Review Assigned To | => marvintm |
| 2018-12-19 10:42 | marvintm | Note Added: 0108669 | |
| 2018-12-19 10:42 | marvintm | Status | scheduled => closed |
| 2018-12-19 10:42 | marvintm | Resolution | open => no change required |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |