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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0057531
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[POS2] POSmajoralways2024-12-23 12:122025-01-10 17:43
ReportergowthamveeramuthuView Statuspublic 
Assigned ToBimla_vm 
PriorityhighResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version24Q2
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0057531: in Backoffice Sales order Payment details is not same as customer paid

DescriptionThe amount paid by customer is not showing correctly in Sales order's -> payment Details tab.
sales total amount is 18.90
customer paid
1. 0.60 as cash
2. 100 as voucher/card (overpayment)

in Sales order -> payment details tab its showing as
1. cash => received amount as 1 (linked payment_in shows 0.60)
2. voucher => received amount as 18.50 (linked payment_in shows 100)
3. cash => received amount as -0.60 (there was no -0.60 showed in POS while doing payment. but in receipt shown as change)
Steps To Reproducehttps://livebuilds.openbravo.com/context/retail_pos2_modules_pgsql [^]

add product "HeadLamp Ultralight" (18.90)
click on pay
enter 0.60 in keypad and click cash.
now cash payment 0.60 is registered.
enter 100 in keypad and click on voucher
now voucher payment 100 is registered.
click on "Done"
check the sales order details in Backoffice
TagsNo tags attached.
Attached Filespng file icon POS Receipt.png [^] (158,048 bytes) 2024-12-23 12:13


png file icon POS payment .png [^] (144,023 bytes) 2024-12-23 12:13


png file icon PaymentDeatils-all.png [^] (333,983 bytes) 2024-12-23 12:13
png file icon PaymentDeatils1.png [^] (97,418 bytes) 2024-12-23 12:13


png file icon PaymentDeatils2.png [^] (95,858 bytes) 2024-12-23 12:13


png file icon PaymentDeatils3.png [^] (99,724 bytes) 2024-12-23 12:13

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0174015)
aaroncalero (manager)
2025-01-10 17:43

Moving to design defect. We need input from product management to define the behavior in this cases and then implement what it is specified.

For context: the code that is triggering this strange behavior has existed for almost 10 years

- Issue History
Date Modified Username Field Change
2024-12-23 12:12 gowthamveeramuthu New Issue
2024-12-23 12:12 gowthamveeramuthu Assigned To => Retail
2024-12-23 12:12 gowthamveeramuthu Triggers an Emergency Pack => No
2024-12-23 12:13 gowthamveeramuthu File Added: POS Receipt.png
2024-12-23 12:13 gowthamveeramuthu File Added: POS payment .png
2024-12-23 12:13 gowthamveeramuthu File Added: PaymentDeatils-all.png
2024-12-23 12:13 gowthamveeramuthu File Added: PaymentDeatils1.png
2024-12-23 12:13 gowthamveeramuthu File Added: PaymentDeatils2.png
2024-12-23 12:13 gowthamveeramuthu File Added: PaymentDeatils3.png
2024-12-24 07:12 guillermogil Assigned To Retail => jorgewederago
2024-12-24 07:12 guillermogil Status new => acknowledged
2024-12-26 07:34 Bimla_vm Assigned To jorgewederago => Bimla_vm
2024-12-26 07:34 Bimla_vm Status acknowledged => scheduled
2025-01-10 17:43 aaroncalero Note Added: 0174015
2025-01-10 17:43 aaroncalero Type defect => design defect


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker