Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0028531Openbravo ERP04. Warehouse managementpublic2015-01-07 13:332015-03-20 14:08
Reporterpsanjuan 
Assigned Toumartirena 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS20OS VersionUbuntu 8.04.1
Product Version 
Target VersionFixed in Version3.0PR15Q2 
Merge Request Status
Review Assigned ToSandrahuguet
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0028531: Fix Backdated From process button is not properly working as it only considers current date.
DescriptionFix Backdated From process button is not properly working as it only considers current date.
Steps To ReproduceAs F&B International Group Admin role, open Initial Organization setup window.
Create a new organization named F&B Portugal as a Legal with Accounting organization type. Select F&B International Group as parent organization.
Do not include accounting.
Press OK.

Go to Calendar window and create a new one for F&B Portugal organization.

Go to organization window and select the one just created. Select Allow Period Control, Select the calendar just created and select F&B International Group US/Dollar general ledger. Press Set as Ready.

Go to Costing Rule window and create a new record for F&B Portugal. Do not select anything but "Warehouse Dimension". Validate Costing Rule.

Realize that a costing rule has been created and validated.

Press now the process button "Fix Backdated From". Realize that Fix Backdated From date field does not have hours/minutes/seconds. That should be fixed.

Besides that, try to enter a date such as 01-01-2009, and press Done.
What the system does after running this process is always to put current date as Fix Backdated From date but:

(1) if a date previous to the starting date of the costing rule is entered, an error should be shown saying that Fix Backdated From date entered should be same or later than the starting date of the costing rule.

(2) if a date after the starting date of the costing rule is entered, that date should be the one to be shown in the field "Fix Backdated From" date.

Proposed Solutiontbd
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-01-07 13:33psanjuanNew Issue
2015-01-07 13:33psanjuanAssigned To => dmiguelez
2015-01-07 13:33psanjuanOBNetwork customer => No
2015-01-07 13:33psanjuanModules => Core
2015-01-07 13:33psanjuanTriggers an Emergency Pack => No
2015-01-07 13:44psanjuanAssigned Todmiguelez => umartirena
2015-01-07 13:44psanjuanDescription Updatedbug_revision_view_page.php?rev_id=7398#r7398
2015-01-07 13:44psanjuanSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=7400#r7400
2015-01-08 08:45hgbotCheckin
2015-01-08 08:45hgbotNote Added: 0073342
2015-01-08 08:45hgbotStatusnew => resolved
2015-01-08 08:45hgbotResolutionopen => fixed
2015-01-08 08:45hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/8b62e941c654019d52a56988fb37d097838ff928 [^]
2015-01-08 17:24hgbotCheckin
2015-01-08 17:24hgbotNote Added: 0073376
2015-01-13 17:53hgbotCheckin
2015-01-13 17:53hgbotNote Added: 0073475
2015-01-13 18:02SandrahuguetReview Assigned To => Sandrahuguet
2015-01-13 18:02SandrahuguetNote Added: 0073476
2015-01-13 18:02SandrahuguetStatusresolved => closed
2015-01-13 18:02SandrahuguetFixed in Version => 3.0PR15Q2
2015-02-04 20:33hudsonbotCheckin
2015-02-04 20:33hudsonbotNote Added: 0074119
2015-02-04 20:33hudsonbotCheckin
2015-02-04 20:33hudsonbotNote Added: 0074123
2015-02-04 20:34hudsonbotCheckin
2015-02-04 20:34hudsonbotNote Added: 0074142
2015-03-20 14:08hgbotCheckin
2015-03-20 14:08hgbotNote Added: 0075807

Notes
(0073342)
hgbot   
2015-01-08 08:45   
Repository: erp/devel/pi
Changeset: 8b62e941c654019d52a56988fb37d097838ff928
Author: Unai Martirena <unai.martirena <at> openbravo.com>
Date: Wed Jan 07 19:31:01 2015 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/8b62e941c654019d52a56988fb37d097838ff928 [^]

Fixes bug 28531: Fix Backdated fails when backdated from is before starting date.

A check has been added to be sure that fix backdated from date is not earlier than starting date of the costing rule.
Also some code has been changed to handle correctly the error messages and return them properly to the user.
Finally the reference of Fix Backdated From Parameter in Fix Backdated Transactions Process Definitio has been changed from Date to DateTime.

---
M src-db/database/sourcedata/AD_MESSAGE.xml
M src-db/database/sourcedata/OBUIAPP_PARAMETER.xml
M src/org/openbravo/costing/FixBackdatedTransactionsProcess.java
---
(0073376)
hgbot   
2015-01-08 17:24   
Repository: erp/devel/pi
Changeset: 07b6cde565a1e19dcac21561bc3385b4883806e4
Author: Unai Martirena <unai.martirena <at> openbravo.com>
Date: Thu Jan 08 12:50:05 2015 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/07b6cde565a1e19dcac21561bc3385b4883806e4 [^]

Related to Bug 28531: Fix backdated is not correctly set with big amount of data

createCostingRuleInits method inside CostingRuleProcess.java cleares session every 100 records, and if this happens then the reference to current Costing Rule is missed, so the code that sets the fix backdated from is not properly done (rule.setFixbackdatedfrom(startingDate)). To avoid this the Fix Backdated From is set before creating Costing Rule Inventories.

---
M src/org/openbravo/costing/CostingRuleProcess.java
---
(0073475)
hgbot   
2015-01-13 17:53   
Repository: erp/devel/pi
Changeset: 3942b30f49f1ba99fa045c2bc1e304bff8c8ccc1
Author: Sandra Huguet <sandra.huguet <at> openbravo.com>
Date: Tue Jan 13 17:52:27 2015 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/3942b30f49f1ba99fa045c2bc1e304bff8c8ccc1 [^]

Related to issue 28531 Update Copyright

---
M src/org/openbravo/costing/CostingRuleProcess.java
M src/org/openbravo/costing/FixBackdatedTransactionsProcess.java
---
(0073476)
Sandrahuguet   
2015-01-13 18:02   
Code review + testing OK
(0074119)
hudsonbot   
2015-02-04 20:33   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/f36c91d0ad63 [^]
Maturity status: Test
(0074123)
hudsonbot   
2015-02-04 20:33   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/f36c91d0ad63 [^]
Maturity status: Test
(0074142)
hudsonbot   
2015-02-04 20:34   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/f36c91d0ad63 [^]
Maturity status: Test
(0075807)
hgbot   
2015-03-20 14:08   
Repository: erp/pmods/org.openbravo.sepa.iso20022.coredirectdebit.customertobank
Changeset: 1bacb2db147d90f36eb8e2f8df3fcc6fdf511abc
Author: Jorge Garcia <jorge.garcia <at> openbravo.com>
Date: Wed Mar 18 16:41:26 2015 +0100
URL: http://code.openbravo.com/erp/pmods/org.openbravo.sepa.iso20022.coredirectdebit.customertobank/rev/1bacb2db147d90f36eb8e2f8df3fcc6fdf511abc [^]

Fixed issue 29262: Dataset duplication applying SEPA Direct Debit dataset

Related with the issue 28531the initial client setup process does not work for
SEPA dataset.

Dataset duplication in case of applying SEPA Direct Debit dataset more than
once.

We did a backout of the changeset that solved the issue 28531 because it was
causing problems applying SEPA Direct debit dataset more than once.

---
M referencedata/standard/Core_Direct_Debit_Scheme.xml
M src-db/database/sourcedata/AD_DATASET.xml
M src-db/database/sourcedata/AD_DATASET_TABLE.xml
---