Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0027607Retail ModulesLayaway orderpublic2014-09-15 16:292015-03-08 00:11
Reporteradrianromero 
Assigned ToOrekaria 
PriorityurgentSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in VersionRR15Q2 
Merge Request Status
Review Assigned ToOrekaria
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0027607: Layaways are not saved when generated in one terminal and paid in a different one
DescriptionWhen paying and closing a layaway in a different terminal where it was created the layaway is not saved and the following message is raised in the log:

Problem with layaways when generated in one terminal and paid in a different one.

6445122 [http-8080-3] WARN org.openbravo.mobile.core.process.DataSynchronizationProcess - Record in process org.openbravo.retail.posterminal.OrderLoaderduplicated with id: DDDD8FB3E5B18F2238BD56C299301248 Error not saved.

It seems that the problem is near the code that checks duplicated orders in the server side:

This is the check for duplicates:

https://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/file/8832275f1f14/src/org/openbravo/mobile/core/process/DataSynchronizationProcess.java#l148 [^]

This is the function for orders:
https://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/file/ce99bd7da191/src/org/openbravo/retail/posterminal/OrderLoader.java#l289 [^]

Steps To ReproduceIn an store with at least two terminals follow the steps:

* Create a layaway order in one terminal.
* Open the layaway in a second terminal.
* Pay it completely and close the layaway

Verify that in the log appears the message "Error not saved", and in the ERP verify that the layaway order has not been paid.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of design defect 0027600 closed marvintm Problem with layaways when generated in one terminal and paid in a different one 
related to defect 0026458RR15Q2 closed Osmany After paying completely a layaway order, when the cash up is performed, taxes information in report is wrong 
depends on feature request 0028130RR15Q2 closed Orekaria Support creating tickets through multiple terminals with payment in other (central) devices 
related to defect 0027609 closed marvintm If saving a layaways fails, it is detected as duplicated and not saved the error 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-09-15 16:29adrianromeroNew Issue
2014-09-15 16:29adrianromeroAssigned To => marvintm
2014-09-15 16:29adrianromeroTriggers an Emergency Pack => No
2014-09-15 16:29adrianromeroRelationship addedrelated to 0027600
2014-09-15 16:56adrianromeroNote Added: 0070127
2014-09-15 17:17adrianromeroRelationship addedrelated to 0027609
2014-09-15 17:17adrianromeroRelationship deletedrelated to 0027600
2014-09-15 17:17adrianromeroRelationship addedduplicate of 0027600
2015-01-29 16:42OsmanyAssigned Tomarvintm => Osmany
2015-02-13 15:00malsasuaRelationship addedrelated to 0026458
2015-02-13 15:01malsasuaAssigned ToOsmany => Orekaria
2015-02-13 16:23OrekariaRelationship addeddepends on 0028130
2015-03-08 00:11OrekariaReview Assigned To => Orekaria
2015-03-08 00:11OrekariaNote Added: 0075267
2015-03-08 00:11OrekariaStatusnew => closed
2015-03-08 00:11OrekariaResolutionopen => fixed
2015-03-08 00:11OrekariaFixed in Version => RR15Q2

Notes
(0070127)
adrianromero   
2014-09-15 16:56   
It seems that the problem is reproduced in the case the terminal that initially creates layaways does not have payment methods defined.

It does not need to have to create layaways.
(0075267)
Orekaria   
2015-03-08 00:11   
Fixed as part of the https://issues.openbravo.com/view.php?id=28130 [^] project