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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0047063
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[POS2] POSmajoralways2021-06-11 11:112021-10-06 11:35
ReporterjmelinView Statuspublic 
Assigned Tojorge-garcia 
PrioritynormalResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Statusapproved
Review Assigned Tomarvintm
OBNetwork customerGold
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0047063: JIRA 2078 - Safebox/Counting - Intial count in BO

DescriptionThe data entered on POS when performing counting (cashup or safebox) must be available in BO.

Currently, in the cashup history tab, we store the "starting amount" of each payment method, that corresponds to the "amount to keep" of the last cashup.

However, for some payment methods, depending on the configuration, an "initial count" operation may be performed by the cashier. Depending on the result of this operation, the available amount may be lower or greater than the theoretical starting amount.

This is currently properly reflected by a transaction for differences that is created in the corresponding financial account. However, this is not reflected in the Cashup History, and it would be very useful to keep track of this.

So, the proposal is to add a new column, "Initlally counted amount", besides the "Starting amount" on each payment method on the Cashup History tab. This amount will be equal to the "Starting amount" in case the payment method is not counted. If it is counted, then it will be the amount provided by the user when he counts.
Steps To ReproduceThe data entered on POS when performing counting (cashup or safebox) must be available in BO.

Currently, in the cashup history tab, we store the "starting amount" of each payment method, that corresponds to the "amount to keep" of the last cashup.

However, for some payment methods, depending on the configuration, an "initial count" operation may be performed by the cashier. Depending on the result of this operation, the available amount may be lower or greater than the theoretical starting amount.

This is currently properly reflected by a transaction for differences that is created in the corresponding financial account. However, this is not reflected in the Cashup History, and it would be very useful to keep track of this.

So, the proposal is to add a new column, "Initlally counted amount", besides the "Starting amount" on each payment method on the Cashup History tab. This amount will be equal to the "Starting amount" in case the payment method is not counted. If it is counted, then it will be the amount provided by the user when he counts.
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]

-  Notes
(0132085)
hgbot (developer)
2021-09-30 15:57

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/583 [^]
(0132086)
hgbot (developer)
2021-09-30 16:00

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/689 [^]
(0132184)
hgbot (developer)
2021-10-06 11:13

 Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal [^]
Changeset: c3927b30061e0eded7dcd11e709444f7ebbdc940
Author: Jorge Garcia <jorge.garcia@openbravo.com>
Date: 2021-10-04T07:58:55+02:00
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/commit/c3927b30061e0eded7dcd11e709444f7ebbdc940 [^]

Fixed ISSUE-47063: Include a new column to know the initial count
for a payment method in cashup history

If no initial count is done, the value is the same as the starting
cash value.

---
M src-db/database/model/tables/OBPOS_PAYMENTMETHODCASHUP.xml
M src-db/database/sourcedata/AD_COLUMN.xml
M src-db/database/sourcedata/AD_ELEMENT.xml
M src-db/database/sourcedata/AD_FIELD.xml
M web/org.openbravo.retail.posterminal/app/model/business-object/cashup/PaymentMethodUtils.js
---
(0132185)
hgbot (developer)
2021-10-06 11:13

 Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal [^]
Changeset: 9da836134cd8bb00297523fa0811d93b147ddf06
Author: Jorge Garcia <jorge.garcia@openbravo.com>
Date: 2021-10-04T09:29:18+02:00
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/commit/9da836134cd8bb00297523fa0811d93b147ddf06 [^]

Related to ISSUE-47063: Update test to take into account new variable in cashup

---
M web-test/model/business-object/cashup/Cashup-initCashup-StateAction-fromLocal.test.js
M web-test/model/business-object/cashup/test-data/cashupAfterComplete.js
M web-test/model/business-object/cashup/test-data/cashupAfterLoadCashupFromBackendWithoutPayments.js
M web-test/model/business-object/cashup/test-data/cashupCreatedFromScratch.js
M web-test/model/business-object/cashup/test-data/cashupCreatedFromScratchWithoutLastCashupPayments.js
M web-test/model/business-object/cashup/test-data/cashupMessageSharedPayments.js
M web-test/model/business-object/cashup/test-data/messagesAfterCompleteCashupSharedPayments.js
---
(0132186)
hgbot (developer)
2021-10-06 11:13

 Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal [^]
Changeset: 825eb5138ce0e69c34165ac86312633754dfa3a5
Author: Antonio Moreno <anmorenoperez@gmail.com>
Date: 2021-10-06T11:12:08+02:00
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/commit/825eb5138ce0e69c34165ac86312633754dfa3a5 [^]

Related to ISSUE-47063: Adjusted order of fields in form and grid

---
M src-db/database/sourcedata/AD_FIELD.xml
---
(0132187)
hgbot (developer)
2021-10-06 11:13

 Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/583 [^]
(0132188)
hgbot (developer)
2021-10-06 11:14

 Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: d9cd932b44fdd285ea54c1d624f6bef66b97fddd
Author: Jorge Garcia <jorge.garcia@openbravo.com>
Date: 2021-10-06T09:12:53+00:00
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/d9cd932b44fdd285ea54c1d624f6bef66b97fddd [^]

Related to ISSUE-47063: Update cashup initial counting for safe boxes
payment methods

For standard payment method, it is not to decalre any kind of
differences so the starting cash amount will always be the initial
counted amount

---
A web-jspack/org.openbravo.pos2/src/model/user-interface/actions/cashup/UpdateCashUpWithInitialCount.js
M web-jspack/org.openbravo.pos2/src/model/cashup/CashupExtension.js
---
(0132189)
hgbot (developer)
2021-10-06 11:14

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

- Issue History
Date Modified Username Field Change
2021-06-11 11:11 jmelin New Issue
2021-06-11 11:11 jmelin Assigned To => Retail
2021-06-11 11:11 jmelin OBNetwork customer => Gold
2021-06-11 11:11 jmelin Triggers an Emergency Pack => No
2021-06-14 10:35 marvintm Severity critical => minor
2021-06-14 10:46 marvintm Note Added: 0129451
2021-06-14 10:46 marvintm Assigned To Retail => jmelin
2021-06-14 10:46 marvintm Status new => feedback
2021-06-17 12:53 marvintm Description Updated View Revisions
2021-06-17 12:53 marvintm Steps to Reproduce Updated View Revisions
2021-06-17 12:53 marvintm Status feedback => scheduled
2021-06-17 12:53 marvintm Assigned To jmelin => Retail
2021-06-17 12:54 marvintm Status scheduled => acknowledged
2021-06-17 17:55 dmiguelez Resolution time => 1625090400
2021-06-21 16:23 dmiguelez Severity minor => critical
2021-06-22 11:18 guilleaer Note Deleted: 0129451
2021-06-22 19:29 guilleaer Resolution time 1625090400 => 1628978400
2021-06-23 12:04 dmiguelez Status acknowledged => scheduled
2021-06-23 12:04 dmiguelez Status scheduled => acknowledged
2021-06-23 12:05 dmiguelez Status acknowledged => scheduled
2021-06-23 12:05 dmiguelez Steps to Reproduce Updated View Revisions
2021-06-23 12:05 dmiguelez Status scheduled => acknowledged
2021-06-23 12:05 dmiguelez Status acknowledged => scheduled
2021-06-23 12:05 dmiguelez Assigned To Retail => pablobessone
2021-06-24 11:36 dmiguelez Status scheduled => acknowledged
2021-06-29 16:52 guilleaer Assigned To pablobessone => Retail
2021-08-16 14:38 guilleaer Resolution time 1628978400 => 1631656800
2021-09-30 15:57 hgbot Merge Request Status => open
2021-09-30 15:57 hgbot Note Added: 0132085
2021-09-30 16:00 hgbot Note Added: 0132086
2021-10-01 08:04 marvintm Severity critical => major
2021-10-06 07:54 jorge-garcia Status acknowledged => scheduled
2021-10-06 07:54 jorge-garcia Review Assigned To => marvintm
2021-10-06 11:13 hgbot Merge Request Status open => approved
2021-10-06 11:13 hgbot Resolution open => fixed
2021-10-06 11:13 hgbot Status scheduled => closed
2021-10-06 11:13 hgbot Fixed in Version => RR22Q1
2021-10-06 11:13 hgbot Note Added: 0132184
2021-10-06 11:13 hgbot Note Added: 0132185
2021-10-06 11:13 hgbot Note Added: 0132186
2021-10-06 11:13 hgbot Note Added: 0132187
2021-10-06 11:14 hgbot Note Added: 0132188
2021-10-06 11:14 hgbot Note Added: 0132189
2021-10-06 11:35 marvintm Assigned To Retail => jorge-garcia

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker