Openbravo Issue Tracking System - POS2
View Issue Details
0048400POS2POSpublic2022-01-13 19:102022-01-21 09:10
timothee_catteeuw 
cberner 
normalmajorhave not tried
closedfixed 
5
 
 
guilleaer
No
0048400: JIRA 2600 - It's possible to pay twice a ticket and remove discounts from it
In TAP version it is possible to pay a ticket twice and remove discount from it.
It is just enough to open it and pay it again, cf use case below done on livebuild.

Go to https://livebuilds.openbravo.com/retail_pos2_tap_pgsql/web/pos/?terminal=VBS-2 [^]

Go to WebPos as Vallblanca
Add Hiking boots and Balaclava Cap
Click on Hiking boots and then press discount
select disc_5_ var_perc discount and press apply
pay the transaction by cash

Go to Backoffice as Vallblanca user and open sales order window in order to open the previous sale
Go to payment plan tab and check outstanding which is equal to 0.00
And go to Payment details, as you can see one payment was done

Go back to WebPOS and open the transaction you have previously done
Amount of the transaction is 329.55 € and the discount is still present
But it is possible to pay --> it shouldn't be possible to pay again this ticket
And when you pay, the discount disappears and you can add another payment in cash (8.45 €) to the ticket
And then press "done"

Go to Backoffice as Vallblanca user and open sales order window in order to open the previous sale
Go to payment plan tab and check outstanding which is equal to -8.45
In payment details there is 2 payment lines instead of initially one
--> KO it is not normal to change a transaction like that after paying it during the first ticket
Deactivate the pay button when the ticket is completely paid and you open it
Or completely keep the same ticket (when included discount for example ) after switching to payment mode and don't save a new payment again (just print a duplicata, the ticket has not to be changed)
No tags attached.
depends on backport 0048438TAP closed cberner JIRA 2600 - It's possible to pay twice a ticket and remove discounts from it 
Issue History
2022-01-13 19:10timothee_catteeuwNew Issue
2022-01-13 19:10timothee_catteeuwAssigned To => Retail
2022-01-13 19:10timothee_catteeuwTriggers an Emergency Pack => No
2022-01-13 20:09sntgrealeAssigned ToRetail => sntgreale
2022-01-13 20:09sntgrealeStatusnew => scheduled
2022-01-13 20:35sntgrealeAssigned Tosntgreale => Retail
2022-01-13 20:35sntgrealeStatusscheduled => acknowledged
2022-01-14 09:50timothee_catteeuwProposed Solution updated
2022-01-19 16:07jmelinNote Added: 0134395
2022-01-19 16:47cbernerAssigned ToRetail => cberner
2022-01-19 16:47guilleaerStatusacknowledged => scheduled
2022-01-19 16:47guilleaerTarget VersionTAP =>
2022-01-21 09:09cbernerNote Added: 0134459
2022-01-21 09:09cbernerNote Edited: 0134459bug_revision_view_page.php?bugnote_id=0134459#r23563
2022-01-21 09:09cbernerStatusscheduled => resolved
2022-01-21 09:09cbernerResolutionopen => fixed
2022-01-21 09:10cbernerReview Assigned To => guilleaer
2022-01-21 09:10cbernerStatusresolved => closed

Notes
(0134395)
jmelin   
2022-01-19 16:07   
Another side effet on the same kind is it's duplicate menu component line.

For example, you have a return order with a menu that has 3 components

You open the return ticket, click on "Pay" then "Done"
=> a new message is sent to the BO that update the order

Now, your menu have 6 line menu order line for its components (2 of each initial components)
(0134459)
cberner   
2022-01-21 09:09   
This issue is already fixed in master/FS by the following fixed issue changesets: https://issues.openbravo.com/view.php?id=46701 [^]

Closing this one with no change necessary. Backport to TAP was done in another related issue.