Mercurial Mercurial > erp > devel > pi / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | raw | help
Fixes bug 28266 ParentCostAdjustmentLine should always be assigned in the same order
authorAlvaro Ferraz <alvaro.ferraz@openbravo.com>
Mon, 01 Dec 2014 16:54:02 +0100
changeset 25640 4358cc01e873
parent 25639 816b718112f1
child 25641 f15df074a510
Fixes bug 28266 ParentCostAdjustmentLine should always be assigned in the same order

In order to help JUnit tests assert Cost Adjustment lines, an orderBy clause has been added when assigning the field "Parent Cost Adjustment Line" to follow always the same order
src/org/openbravo/costing/CostAdjustmentProcess.java file | annotate | diff | comparison | revisions 
--- a/src/org/openbravo/costing/CostAdjustmentProcess.java	Mon Dec 01 16:55:05 2014 +0100
+++ b/src/org/openbravo/costing/CostAdjustmentProcess.java	Mon Dec 01 16:54:02 2014 +0100
@@ -249,8 +249,9 @@
     critLines.createAlias(CostAdjustmentLine.PROPERTY_COSTADJUSTMENT, "ca");
     critLines.add(Restrictions.eq("ca.id", strCostAdjustmentId));
     critLines.add(Restrictions.eq(CostAdjustmentLine.PROPERTY_ISRELATEDTRANSACTIONADJUSTED, false));
+    critLines.addOrder(Order.asc("trx." + MaterialTransaction.PROPERTY_TRANSACTIONPROCESSDATE));
+    critLines.addOrder(Order.asc(CostAdjustmentLine.PROPERTY_ADJUSTMENTAMOUNT));
     critLines.addOrder(Order.asc("trx." + MaterialTransaction.PROPERTY_MOVEMENTDATE));
-    critLines.addOrder(Order.asc("trx." + MaterialTransaction.PROPERTY_TRANSACTIONPROCESSDATE));
     critLines.setMaxResults(1);
     return (CostAdjustmentLine) critLines.uniqueResult();
   }
devel/pi