Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Cash upmajoralways2022-03-11 12:432022-04-07 13:08
ReporteridiezView Statuspublic 
Assigned Torqueralta 
PriorityhighResolutionfixedFixed in VersionRR22Q3
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionRR21Q1.1SCM revision 
Review Assigned To
Regression level
Regression date2022-03-24
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0048768: Error cash register closing with master/slave terminal configuration and shared payment methods

DescriptionError cash register closing with master/slave terminal configuration and shared payment methods in the version 21q1

The video link: [^]
Steps To Reproduce1) Configure the terminal with the settings "master slay" and "shared payment method".

2) Make a ticket

3) Pay it with the payment method "Shared credit card".

4) Go to the second terminal

5) Make another ticket and use the payment method "Shared credit card".

6) Make a cash closing

7) Make another ticket in the same terminal and we pay again with the method "Shared credit card".

8) Return to make a new closing of the cash register.

9) Return to terminal 1

10) Make a cash closing and we can see that the last payment that was made in the previous ticket has not been taken into account.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
hgbot (developer)
2022-03-28 23:02

Merge Request created: [^]
eugeni (reporter)
2022-03-30 16:58
edited on: 2022-03-30 17:00

Note that in previous releases a SECOND cash up in the slave terminal was not allowed if master terminal was not previously cashed up (as there is an internal relation between slave cash up and master cash up). I remember a message like (more or less) "Please, do the cash up in the master terminal first".

May this control has been removed by error? We think this would a fair approach as well.

hgbot (developer)
2022-04-07 13:06

Merge request merged: [^]
hgbot (developer)
2022-04-07 13:06

Directly closing issue as related merge request is already approved.

Repository: [^]
Changeset: 93335e6622fffcb256b196b6176c8777a6dc8fe4
Author: Rafael Queralta <>
Date: 07-04-2022 11:06:04
URL: [^]

Fixed BUG-48768: Check if exits more than one cashup in slave terminal related with the marter terminal

M src/org/openbravo/retail/posterminal/
marvintm (manager)
2022-04-07 13:08

We haven't actually been able to reproduce the issue except in one case. In that case, there were more than one cashup created, and in that case it was possible to execute the cashup process twice in the slave terminal.

We have added an additional validation to detect this case, so that it is not possible to do cashup a second time in the slave terminal, without doing cashup in the master first, which is how it was designed to work.

- Issue History
Date Modified Username Field Change
2022-03-11 12:43 idiez New Issue
2022-03-11 12:43 idiez Assigned To => Retail
2022-03-11 12:43 idiez Regression date => 2022-03-24
2022-03-11 12:43 idiez Triggers an Emergency Pack => No
2022-03-21 05:04 rqueralta Assigned To Retail => rqueralta
2022-03-21 05:04 rqueralta Status new => scheduled
2022-03-28 23:02 hgbot Note Added: 0136120
2022-03-30 16:34 eugeni Issue Monitored: eugeni
2022-03-30 16:58 eugeni Note Added: 0136182
2022-03-30 17:00 eugeni Note Edited: 0136182 View Revisions
2022-04-07 13:06 hgbot Note Added: 0136395
2022-04-07 13:06 hgbot Resolution open => fixed
2022-04-07 13:06 hgbot Status scheduled => closed
2022-04-07 13:06 hgbot Fixed in Version => RR22Q3
2022-04-07 13:06 hgbot Note Added: 0136396
2022-04-07 13:08 marvintm Note Added: 0136397

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker