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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0046877
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[POS2] POSmajoralways2021-05-27 17:082021-09-02 10:28
ReporterpsanjuanView Statuspublic 
Assigned Tovmromanos 
PriorityurgentResolutioninvalidFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSLinux 64 bitDatabasePostgreSQLJava version7.x
OS VersionOpenbravo Appliance 14.04Database version9.3.xAnt version1.9.x
Product VersionSCM revision 
Review Assigned Tovmromanos
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0046877: Credit Note feature does not manage properly the credit do not used.

DescriptionCredit Note feature does not manage properly the credit do not used.
Steps To Reproduce0-Login POS2 as vallblanca with Credit Notes configuration completed.
1-Run a cash up process to be sure that there are no pending receipts, that all the amount has been counted and nothing has been kept in the terminal.
1-Add 1x "of any product. Note that the total sale is 12€ for instance.
2-Pay the sale with the payment method that has been configured to generate credit in case there is an "Overpaument", for instance "Voucher".
3-Pay a higher amount, for instance with a voucher of 20€
4-Complete the sale.
5-Verify that a credit note receipt is printed for an amount of 20-12=8€
6-Create another sale for an amount of 3€
7-Use that credit to pay that sale. Verify that current balance shown is 8€ so it is possible to pay that sale with that credit.
8-Complete the sale
9- Create another sale of 3€, by trying to pay with the same credit.
10-Realize that it is not possible as the balance has turned automatically to 0,00€
11- Close the till
12-Verify that there is no management of the remaining amount of credit do not used.


The cash up information shown to count is 20€ of voucher and 8 of the credit. The report print is also not correct as it shows:
Sales 12 € - correct
Retail transactions - 12 € correct
Expected amount = 28€ (this is not correct, it should be 20)
Counted amount = 28 (this is not correct, it should be 20)
Total to keep = 20 (this is correct)
Total to deposit = 8 (not correct it should be 0)
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
depends on backport 0047103TAP closedvmromanos Credit Note feature does not manage properly the credit do not used. 
related to defect 0046874 closedvmromanos Cash up not correct while using Credit Notes feature 

-  Notes
(0128732)
psanjuan (developer)
2021-05-27 17:12

To review once it is possible to have an updated environment running with this feature properly configured, that is related to a "Ticket Restaurant" payment method.

I am not sure about the correct configuration of this feature because it is not explained in this document, whether the payment method "Credit Note" of the Channel Touch point must be configured as "Leave as Credit" or "Cash" (I think it should be Leave as Credit)??).

See: https://docs.google.com/document/d/1fl1MLX7UVexVNazL_B6sCju2a93bOBXkeR9ZvNI8ifY/edit# [^] [^] (see section Create a Touchpoint Type Payment Method)

It should be properly defined how the remaining cash do not used needs to be managed.
(0130466)
dmiguelez (developer)
2021-07-14 13:02

We are not sure if this is a real issue or a configuration problem, it must be reviewed properly.

Therefore, the severity has been updated.
(0130867)
dmiguelez (developer)
2021-07-29 10:05

Verify as a reproducible major issue that has to be fixed
(0131504)
vmromanos (developer)
2021-09-02 10:28

Tested and working fine.

Most likely you have activated the "Use Credit Note Once" flag at Organization level, which allows to consume the credit note just one time.

When this flag is not enabled, you can consume the credit note more than one time (meanwhile you have available credit)

- Issue History
Date Modified Username Field Change
2021-05-27 17:08 psanjuan New Issue
2021-05-27 17:08 psanjuan Assigned To => Retail
2021-05-27 17:08 psanjuan Triggers an Emergency Pack => No
2021-05-27 17:11 psanjuan Steps to Reproduce Updated View Revisions
2021-05-27 17:12 psanjuan Note Added: 0128732
2021-06-14 10:00 guilleaer Resolution time => 1624572000
2021-06-14 10:00 guilleaer Status new => scheduled
2021-06-14 10:00 guilleaer Status scheduled => acknowledged
2021-07-14 13:02 dmiguelez Note Added: 0130466
2021-07-14 13:02 dmiguelez Resolution time 1624572000 => 1628028000
2021-07-14 13:02 dmiguelez Severity major => minor
2021-07-29 10:05 dmiguelez Relationship added related to 0046874
2021-07-29 10:05 dmiguelez Severity minor => major
2021-07-29 10:05 dmiguelez Note Added: 0130867
2021-08-06 11:33 dmiguelez Resolution time 1628028000 => 1629410400
2021-08-31 13:39 vmromanos Assigned To Retail => vmromanos
2021-09-02 09:34 vmromanos Status acknowledged => scheduled
2021-09-02 10:28 vmromanos Review Assigned To => vmromanos
2021-09-02 10:28 vmromanos Note Added: 0131504
2021-09-02 10:28 vmromanos Status scheduled => closed
2021-09-02 10:28 vmromanos Resolution open => invalid


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker