Thu, 07 May 2015 12:11:39 +0200Fixed bug 29808: Impossible to create several calendars for the same organization
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Thu, 07 May 2015 12:11:39 +0200] rev 26691
Fixed bug 29808: Impossible to create several calendars for the same organization

Two pieces of code were affected by this bug:
PeriodEventHandler.java: EntityPersistenceEventObserver in charge of checking overlap in manual inserts/updates (or any java process) in c_period table
C_YEARPERIODS: db function associated to the create periods process inside the Fiscal Calendar | Year tab. It also verifies the periods don't overlap other periods.

The fix consists in checking that there is no date overlap per calendar. Before this fix the calendar wasn't taken into account, so it was not possible to define several calendars for the same organization with the same periods.

Mon, 11 May 2015 10:15:38 +0200Fixes bug 29836: Avoid creating unnecessary backdated adjustments.
Unai Martirena <unai.martirena@openbravo.com> [Mon, 11 May 2015 10:15:38 +0200] rev 26690
Fixes bug 29836: Avoid creating unnecessary backdated adjustments.

The problem was happening when costing precision was different from standard precision. When calculating the expected cost of a transaction to know if an adjustment is necessary to be created, it has to be rounded to standard precision because the amounts always have to be created in standard precision. In this case, while comparing expected cost with actual cost from database, as in database values are rounded to standard precision, and expected cost was being rounded to cost precission, an adjustment was being created with the difference, that corresponds just to the precision lost, and finally an adjustment of Zero amount was being created.

Wed, 06 May 2015 11:09:24 +0200Fixed bug 29780 The done button appears disabled when it should not
Sandra Huguet <sandra.huguet@openbravo.com> [Wed, 06 May 2015 11:09:24 +0200] rev 26689
Fixed bug 29780 The done button appears disabled when it should not

null parameter when it should be the view in recalcDisplayLogicOrReadOnlyLogic
call in updateDifference function

Thu, 21 May 2015 09:19:25 +0000Merge temporary head for 3.0PR15Q1.4
RM packaging bot <staff.rm@openbravo.com> [Thu, 21 May 2015 09:19:25 +0000] rev 26688
Merge temporary head for 3.0PR15Q1.4

Tue, 19 May 2015 12:57:06 +0000Added signature for changeset ac3537eef819
RM packaging bot <staff.rm@openbravo.com> [Tue, 19 May 2015 12:57:06 +0000] rev 26687
Added signature for changeset ac3537eef819

Tue, 19 May 2015 12:57:05 +0000Added tag 3.0PR15Q1.4 for changeset d5ec99ff8e8e
RM packaging bot <staff.rm@openbravo.com> [Tue, 19 May 2015 12:57:05 +0000] rev 26686
Added tag 3.0PR15Q1.4 for changeset d5ec99ff8e8e

Tue, 19 May 2015 12:57:05 +0000Update AD_MODULE version to 3.0PR15Q1.4 3.0PR15Q1.4
RM packaging bot <staff.rm@openbravo.com> [Tue, 19 May 2015 12:57:05 +0000] rev 26685
Update AD_MODULE version to 3.0PR15Q1.4

Thu, 07 May 2015 12:11:39 +0200Fixed bug 29809: Impossible to create several calendars for the same organization
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Thu, 07 May 2015 12:11:39 +0200] rev 26684
Fixed bug 29809: Impossible to create several calendars for the same organization

Two pieces of code were affected by this bug:
PeriodEventHandler.java: EntityPersistenceEventObserver in charge of checking overlap in manual inserts/updates (or any java process) in c_period table
C_YEARPERIODS: db function associated to the create periods process inside the Fiscal Calendar | Year tab. It also verifies the periods don't overlap other periods.

The fix consists in checking that there is no date overlap per calendar. Before this fix the calendar wasn't taken into account, so it was not possible to define several calendars for the same organization with the same periods.

Tue, 19 May 2015 14:04:18 +0200Related to issue 29809: Backout wrong changeset
Víctor Martínez Romanos <victor.martinez@openbravo.com> [Tue, 19 May 2015 14:04:18 +0200] rev 26683
Related to issue 29809: Backout wrong changeset

The changeset pushed was not the good one, and failed in Oracle

Mon, 18 May 2015 17:22:42 +0200Related to bug 29885: Code Review
Unai Martirena <unai.martirena@openbravo.com> [Mon, 18 May 2015 17:22:42 +0200] rev 26682
Related to bug 29885: Code Review

Add coalesce in case there is no batch associated to set GL Journal Org, in order to avoid issues in the if condition done right after the query if null values are compared