Openbravo Issue Tracking System - Retail Modules |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0050054 | Retail Modules | Cash up | public | 2022-08-24 17:19 | 2022-09-05 06:52 |
|
| Reporter | ludmila_ursu | |
| Assigned To | ranjith_qualiantech_com | |
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 30 | OS Version | Openbravo Appliance 14.04 |
| Product Version | RR22Q3 | |
| Target Version | | Fixed in Version | RR22Q4 | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0050054: "Updated" field, in "Cashup History" lines is not set to date/time of the processed cashup |
| Description | During the cashup in the Web POS, if for a certain payment method the "Total Counted" amount is 0, lines in "Cashup History" will not be updated with the date/time of the processed cashup.
Field "Updated" is not changed for those lines, having a "Total Counted" = 0 .
This, even if there are sales registered. |
| Steps To Reproduce | Connect to Web POS.
Create a few sales orders, pay with multiple payment methods (cash, card, voucher, manual card, etc).
Do the cashup.
During the counting step, for one of the payment methods for which there were sales registered, set the "counted" amount to 0.
Add this not registered amount to another payment method, in order to have a 0 difference in the end, for the counting process.
FInish the cashup.
Go to the backoffice, and search the processed cashup.
Check the "updated" field for the header of the concerned cashup.
Compare it to the "updated" field for the lines of this cashup.
Remark that, for payment methods for which the "total counted" is 0, the "updated" field is different than of the header of the window.
Even if there are sales that are registered for that specific payment method.
Check the behavior for the rest of the lines for that cashup.
Remark that "updated" field corresponds (a few seconds of difference), to the "updated" field of the header.
Please see enclosed tests done in livebuilds, on 24th of August 2022.
Behavior is reproduced every time. |
| Proposed Solution | Update all the lines related to a cashup, during the process of the cashup.
All lines of a processed cashup should have the "updated" field = to the "updated field of the header's cashup. |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files |  cashup lines not updated - %22updated%22 field.png (307,341) 2022-08-24 17:19
https://issues.openbravo.com/file_download.php?file_id=17446&type=bug |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2022-08-24 17:19 | ludmila_ursu | New Issue | |
| 2022-08-24 17:19 | ludmila_ursu | Assigned To | => Retail |
| 2022-08-24 17:19 | ludmila_ursu | File Added: cashup lines not updated - %22updated%22 field.png | |
| 2022-08-24 17:19 | ludmila_ursu | Triggers an Emergency Pack | => No |
| 2022-08-30 09:38 | ranjith_qualiantech_com | Assigned To | Retail => ranjith_qualiantech_com |
| 2022-08-30 14:02 | ranjith_qualiantech_com | Status | new => scheduled |
| 2022-08-31 07:30 | hgbot | Note Added: 0140520 | |
| 2022-09-05 06:52 | hgbot | Resolution | open => fixed |
| 2022-09-05 06:52 | hgbot | Status | scheduled => closed |
| 2022-09-05 06:52 | hgbot | Note Added: 0140661 | |
| 2022-09-05 06:52 | hgbot | Fixed in Version | => RR22Q4 |
| 2022-09-05 06:52 | hgbot | Note Added: 0140662 | |