Openbravo Issue Tracking System - Retail Modules
View Issue Details
0027600Retail ModulesWeb POSpublic2014-09-12 13:342015-03-08 00:09
normalmajorhave not tried
0027600: Problem with layaways when generated in one terminal and paid in a different one
Currently there is a problem when you create a layaway in one terminal and then pay it in a different one. The transaction for the payment is created in the first terminal, not reconciled when the cash up is done in the second terminal, and the cash up PDF reports (and also the Web POS report in the second terminal) contain wrong information.

When the fix is done, it should be verified that the financial information is correct, that the three cash up reports (Web POS report, printed report, and PDF report) are generated correctly, and also that the Sales Invoice generated in the cash up is generated correctly.
- Create a layaway in terminal 1.
- Load it in terminal 2. Pay it.
- Verify that the financial account information of both terminals is wrong. Verify that the cash up is not done correctly.

No tags attached.
depends on feature request 0028130RR15Q2 closed Orekaria Support creating tickets through multiple terminals with payment in other (central) devices 
has duplicate defect 0027607 closed Orekaria Layaways are not saved when generated in one terminal and paid in a different one 
Issue History
2014-09-12 13:34marvintmNew Issue
2014-09-12 13:34marvintmAssigned To => marvintm
2014-09-12 13:34marvintmTriggers an Emergency Pack => No
2014-09-12 17:38dmitry_mezentsevTypedefect => design defect
2014-09-15 16:29adrianromeroRelationship addedrelated to 0027607
2014-09-15 17:17adrianromeroRelationship deletedrelated to 0027607
2014-09-15 17:17adrianromeroRelationship addedhas duplicate 0027607
2015-02-13 16:23OrekariaRelationship addeddepends on 0028130
2015-03-08 00:09OrekariaReview Assigned To => Orekaria
2015-03-08 00:09OrekariaNote Added: 0075266
2015-03-08 00:09OrekariaStatusnew => closed
2015-03-08 00:09OrekariaResolutionopen => fixed
2015-03-08 00:09OrekariaFixed in Version => RR15Q2

2015-03-08 00:09   
Fixed as part of the [^] project