Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0031805Retail ModulesWeb POSpublic2015-12-30 17:202016-02-01 17:04
Reportermaite 
Assigned Toguilleaer 
PriorityimmediateSeveritycriticalReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product VersionRR15Q3.3 
Target VersionFixed in VersionRR15Q3.3 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Support ticket39835
Regression levelProduction - Confirmed Stable
Regression date2015-02-18
Regression introduced in releaseRR15Q2
Regression introduced by commithttps://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/260e72a513b67a7fc6b1a28c4b74c959fe7b3a7d [^]
Triggers an Emergency PackNo
Summary0031805: Wrong Cashup date when register is imported from "Data Import Entries" window
DescriptionIn case a cashup import fails, record is left in "Error" status in "Data Import Entries" window (http://wiki.openbravo.com/wiki/Retail:Web_POS_User_Guide#Backend_Data_Processing:_Data_Import_Entries [^]). When it is set to "Initial" status again and considered by the process it is imported with today's date instead of cashup date (reconciliations are also created with today's date and so on...)
Steps To ReproduceI can provide environment where problem is reproducible as there are cash up records in "Data Import Entries" window
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
depends on backport 0031643RR15Q3.3 closed Orekaria invoice date is wrong in invoice created in cashup 
caused by defect 0028953 closed migueldejuana Invoice date is not set properly in created invoices using Web POS 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-12-30 17:20maiteNew Issue
2015-12-30 17:20maiteAssigned To => Retail
2015-12-30 17:20maiteOBNetwork customer => Yes
2015-12-30 17:20maiteSupport ticket => 39835
2015-12-30 17:20maiteResolution time => 1451948400
2015-12-30 17:20maiteTriggers an Emergency Pack => No
2015-12-30 17:20maiteIssue Monitored: networkb
2015-12-31 11:34OrekariaRelationship addeddepends on 0031643
2015-12-31 11:36OrekariaStatusnew => acknowledged
2016-01-26 10:05dmitry_mezentsevRelationship addedcaused by 0028953
2016-01-26 10:11dmitry_mezentsevRegression level => Production - Confirmed Stable
2016-01-26 10:11dmitry_mezentsevRegression date => 2015-02-18
2016-01-26 10:11dmitry_mezentsevRegression introduced in release => RR15Q2
2016-01-26 10:11dmitry_mezentsevRegression introduced by commit => https://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/260e72a513b67a7fc6b1a28c4b74c959fe7b3a7d [^]
2016-02-01 17:01guilleaerStatusacknowledged => scheduled
2016-02-01 17:01guilleaerAssigned ToRetail => guilleaer
2016-02-01 17:04guilleaerNote Added: 0083795
2016-02-01 17:04guilleaerStatusscheduled => resolved
2016-02-01 17:04guilleaerFixed in Version => RR15Q3.3
2016-02-01 17:04guilleaerResolutionopen => fixed
2016-02-01 17:04guilleaerStatusresolved => closed

Notes
(0083795)
guilleaer   
2016-02-01 17:04   
This Issue is already resolved in 15Q3.3 [https://issues.openbravo.com/view.php?id=31643 [^]] and 15Q4.1 [https://issues.openbravo.com/view.php?id=31642 [^]]

This customer was suffering this issue because data stored in import entry had old date formats