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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0034752
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Web POSmajoralways2016-12-15 17:592016-12-21 17:31
ReporternataliagView Statuspublic 
Assigned Toranjith_qualiantech_com 
PrioritynormalResolutionfixedFixed in VersionRR17Q1
StatusclosedFix in branchFixed in SCM revision2573f3c2243d
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tomarvintm
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0034752: Duplicity in payment details in Layaways using shared payment method option

DescriptionIf there is a POS terminal with a payment method that has the option “Shared payment method” ticked and this payment method is used in a master terminal and in some of its sons when you pay a layaway with this payment method the payment details appears twice or as many times as terminals use this payment method.
Steps To ReproduceIn livebuilds:
1- Go to POS Terminal type window in backend.

2- Select “Shared VBS POS Terminal Type 1” and in payment method section open “Credit Card”. Tick the “Shared Payment Method” option and save it.

3- Go to Financial account window and create a new record for example TestAccount using “Multi Price Store” Organization and type “Bank”.

4-Now, go to POS Terminal window and select VBS1 terminal (Master terminal) and create a new record in payment Type section using as Payment method "Credit Card" and as financial account that created in step 3 (TestAccount).

5- After, in POS Terminal window select VBS2 terminal and create also a new record in payment Type section using “Credit Card” and Test Account in financial account field.

6- Go to WebPOS, select a product and layaway it.

7- Go to Sales order window in backend and pay the layaway ticket using as Payment Method "Pago mediante Tarjeta" and as financial Account, that one created in step 3 (TestAccount).

8- Back to WebPOS and load the layaway created in step 6. In payment details the payment appears twice. One for the Master terminal(VBS1) and the other one for the other VBS2 terminal.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0092904)
hgbot (developer)
2016-12-21 12:48

Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: 2573f3c2243defc8b1daeaeea21a0cb95537dc39
Author: Ranjith S R <ranjith <at> qualiantech.com>
Date: Wed Dec 21 17:18:04 2016 +0530
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/2573f3c2243defc8b1daeaeea21a0cb95537dc39 [^]

Fixes issue 34752 : Added Initial Validations for Shared Payment Methods

* Search Key & Name should be same in Master & Slave Terminal if both Payment Method & Financial Account are equal

---
M src-db/database/sourcedata/AD_MESSAGE.xml
M src/org/openbravo/retail/posterminal/InitialValidations.java
---

- Issue History
Date Modified Username Field Change
2016-12-15 17:59 nataliag New Issue
2016-12-15 17:59 nataliag Assigned To => Retail
2016-12-15 17:59 nataliag Resolution time => 1483570800
2016-12-15 17:59 nataliag Triggers an Emergency Pack => No
2016-12-19 11:41 heccam Issue Monitored: heccam
2016-12-20 13:31 ranjith_qualiantech_com Assigned To Retail => ranjith_qualiantech_com
2016-12-20 13:31 ranjith_qualiantech_com Status new => scheduled
2016-12-21 12:48 hgbot Checkin
2016-12-21 12:48 hgbot Note Added: 0092904
2016-12-21 12:48 hgbot Status scheduled => resolved
2016-12-21 12:48 hgbot Resolution open => fixed
2016-12-21 12:48 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/2573f3c2243defc8b1daeaeea21a0cb95537dc39 [^]
2016-12-21 17:31 marvintm Review Assigned To => marvintm
2016-12-21 17:31 marvintm Status resolved => closed
2016-12-21 17:31 marvintm Fixed in Version => RR17Q1


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker