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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0035182
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Cash upmajoralways2017-02-07 11:112017-03-13 09:04
ReporternataliagView Statuspublic 
Assigned Tomario_castello 
PrioritynormalResolutionfixedFixed in VersionRR17Q2
StatusclosedFix in branchFixed in SCM revisionab1654cd987e
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

0035182: Cash to keep when doing cash up using a shared payment method in a slave terminal is not working

DescriptionIf you have two terminals, a master one and a slave which use a shared payment method and you do the cash up, when the quantity to keep is defined in the master terminal, it is not transferred also to the slave terminal. When you do the first sale in the slave terminal, no cash is available. If you use the master terminal it is. As you are using a shared payment method, the quantity to keep should be kept in both terminals, the master and the slave, not only the master one.
Steps To Reproduce1- Go to backend and configure a terminal as a master and another one as a slave. Select as payment method “Shared Cash” (a shared payment method) for both terminals.
2- Configure the payment method to have a quantity to keep when you are doing the cash up. (Check the “Allow variable Amount” box in Cash up section)
3- Go to web POS and do some sales in both terminals.
4- Do cash up in slave terminal. No money to count nor money to keep is shown, it is done in master terminal. Only click on “Post, Print & Close” button.
5- Now, do cash up in master terminal. Count the money and when the “Select Shared Cash (Shared) to keep” screen is shown, select a quantity to keep, for example 20. Click on next and “Post, Print & Close” button.
6- Go to the slave terminal again, try to do a sale and pay more than the product price, for example if the product price is 14.50€ pay 20€, so 5.50€ should be returned. A message saying “There is not enough cash available” is shown and the sale can’t be done. In step 5 we have keep 20€ so this quantity should have been kept in the terminal.
7- Go to master terminal and do the same as in step 6, the message is not shown and the sale is done correctly.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0094320)
marvintm (manager)
2017-02-14 15:44

When using Shared Payment Method functionality, the total available cash is neither known by the master nor the slave terminals, and as we need to support offline functionality for orders, a remote request cannot be done inside this flow.

Therefore, the fix for this problem is to disable the check that checks for available cash when the payment method is shared between terminals. This check must be disabled both for the master and slave terminals, as neither of them has the complete picture of the shared payment method status before the cashup operation is finally done.
(0094952)
hgbot (developer)
2017-03-10 21:09

Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: ab1654cd987e6e05393e36215e6d0b9e2c18bdaa
Author: Mario Castello <mario.castello <at> peoplewalking.com>
Date: Fri Mar 10 09:37:24 2017 -0600
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/ab1654cd987e6e05393e36215e6d0b9e2c18bdaa [^]

Fixed issue 0035182: Cash to keep when doing cash up using a shared payment method in a slave terminal is not working

- Added validation to avoid checking for shared payment method

---
M web/org.openbravo.retail.posterminal/js/pointofsale/view/payment.js
---

- Issue History
Date Modified Username Field Change
2017-02-07 11:11 nataliag New Issue
2017-02-07 11:11 nataliag Assigned To => Retail
2017-02-07 11:11 nataliag Resolution time => 1488236400
2017-02-07 11:11 nataliag Triggers an Emergency Pack => No
2017-02-07 17:39 eugeni Issue Monitored: eugeni
2017-02-13 21:35 mario_castello Assigned To Retail => mario_castello
2017-02-13 21:35 mario_castello Status new => acknowledged
2017-02-14 15:44 marvintm Note Added: 0094320
2017-02-15 00:04 mario_castello Status acknowledged => scheduled
2017-03-10 21:09 hgbot Checkin
2017-03-10 21:09 hgbot Note Added: 0094952
2017-03-10 21:09 hgbot Status scheduled => resolved
2017-03-10 21:09 hgbot Resolution open => fixed
2017-03-10 21:09 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/ab1654cd987e6e05393e36215e6d0b9e2c18bdaa [^]
2017-03-13 09:04 marvintm Review Assigned To => marvintm
2017-03-13 09:04 marvintm Status resolved => closed
2017-03-13 09:04 marvintm Fixed in Version => RR17Q2


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker