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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0048321
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[POS2] POSmajorhave not tried2021-12-24 10:372022-01-12 07:40
ReporteraferrazView Statuspublic 
Assigned TojavierRodriguez 
PrioritynormalResolutionfixedFixed in Versionpi
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Statusapproved
Review Assigned Tomarvintm
OBNetwork customerNo
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0048321: Payment change is not correctly managed when overpaying with cash

DescriptionPayment change is not correctly managed when overpaying with cash
Steps To Reproduce- Create a ticket with one unit of Avalanche Transceiver (150.50€) and pay 200€ in Card. Check payment panel shows 49.50€ overpayment. This is correct.
- Complete the ticket and check in backoffice (Payment In window) the order is created with a payment with two lines: one of 150.50€ and another one of overpayment of 49.50€. This is correct.

- Create a ticket with one unit of Avalanche Transceiver (150.50€) and pay 200€ in Cash. Check payment panel shows 49.50€ change. This is correct.
- Complete the ticket and check in backoffice (Payment In window) the order is created with a payment with two lines: one of 150.50€ and another one of overpayment of 49.50€. This is not correct, the second payment line should not exists.

This flow works fine in POS1.
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
related to defect 0048394 closedelara Payment change is not correctly managed when overpaying with cash having split payments 

-  Notes
(0134231)
hgbot (developer)
2022-01-11 17:32

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/773 [^]
(0134239)
hgbot (developer)
2022-01-12 07:39

 Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: e9a4245d1bbe7db6160414ef807748c3f883c19e
Author: Javier Rodriguez Regueiro <javier.rodriguez@openbravo.com>
Date: 11-01-2022 16:58:27
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/e9a4245d1bbe7db6160414ef807748c3f883c19e [^]

Fix ISSUE-48321: Set the split change always as true in complete ticket

The "WebPOS Split Change in Different Payment Details" preference was created to mantain the previous behaivor in old clients and, using this preference, use the new flow

- old flow: If the client pay with 200e a ticket and the total amout is 150e, the payment saved in BO is 150e
- new flow: If the client pay with 200e a ticket and the total amout is 150e, the payment saved is 200e and other payment with -50e.

This preference must be used only in the old webpos, in pos2 the only valid flow is the new one. This is the reason why pos2 does not check the preference and just set splitChange as true

---
M web-jspack/org.openbravo.pos2/src/model/ticket/user-actions/CompleteTicket.js
---
(0134240)
hgbot (developer)
2022-01-12 07:39

 Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/773 [^]

- Issue History
Date Modified Username Field Change
2021-12-24 10:37 aferraz New Issue
2021-12-24 10:37 aferraz Assigned To => Retail
2021-12-24 10:37 aferraz OBNetwork customer => No
2021-12-24 10:37 aferraz Triggers an Emergency Pack => No
2021-12-29 23:53 AugustoMauch Assigned To Retail => ablasco
2021-12-29 23:53 AugustoMauch Status new => scheduled
2021-12-30 10:15 AugustoMauch Steps to Reproduce Updated View Revisions
2022-01-04 13:40 AugustoMauch Assigned To ablasco => Retail
2022-01-04 13:40 AugustoMauch Status scheduled => acknowledged
2022-01-05 14:23 javierRodriguez Assigned To Retail => javierRodriguez
2022-01-11 17:32 hgbot Merge Request Status => open
2022-01-11 17:32 hgbot Note Added: 0134231
2022-01-12 07:39 hgbot Merge Request Status open => approved
2022-01-12 07:39 hgbot Note Added: 0134239
2022-01-12 07:39 hgbot Note Added: 0134240
2022-01-12 07:40 marvintm Status acknowledged => scheduled
2022-01-12 07:40 marvintm Status scheduled => resolved
2022-01-12 07:40 marvintm Fixed in Version => pi
2022-01-12 07:40 marvintm Resolution open => fixed
2022-01-12 07:40 marvintm Review Assigned To => marvintm
2022-01-12 07:40 marvintm Status resolved => closed
2022-01-13 12:33 aferraz Relationship added related to 0048394

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker