git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31099 20353a03-c40f-0410-a6d1-a30d3c3de9de

Add an argument `aggregated_movement_list` to calculation script.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30914 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30865 20353a03-c40f-0410-a6d1-a30d3c3de9de

Add target level property which defines how trade model line is applied to movements and this changes getAggregatedAmountList behavior.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30853 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30608 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30021 20353a03-c40f-0410-a6d1-a30d3c3de9de

Until now, when using, for example, VAT, you put like this:

price=0.196, efficiency=1.0

so the result by getAggregatedAmountList is, if the base is 100:

price=0.196, efficiency=1.0, quantity=100

Thus, the total price is 19.6.

This works but not compatible with rounding, as, for instance, if we want to 
round it up to 20, the result is not saved at anywhere.

So, from now on, we do like this instead:

price=1.0, efficiency=0.196

so the result is:

price=1.0, efficiency=0.196, quantity=100, total price=19.6

The total price does not change. When we apply a rounding method, it would 
result in:

price=1.0, efficiency=0.196, quantity=100, total price=20

--

This modification is approved by YO and Yusei.

TODO: write some test-cases



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@30019 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@29133 20353a03-c40f-0410-a6d1-a30d3c3de9de

 - there is no need to use use category of resource to recognise if movements are put by user or by system, empty base_application suggest that movement is set by user


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28794 20353a03-c40f-0410-a6d1-a30d3c3de9de

- self is not the same than context, use context parameter instead
- get closest model from the paysheet
- condition for slice was wrong. if the slice is equal to the base_application, quantity is 0


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28123 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28045 20353a03-c40f-0410-a6d1-a30d3c3de9de

current model_line should be a child of an effictive model. So it's useless to look for an effective model : the parent of this line is good.
it's non sens to use another model than the parent one to get the calculation script to calculate this line.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28042 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28029 20353a03-c40f-0410-a6d1-a30d3c3de9de

  in case a calculation script is found, slice are not calculated in TradeModelLine class. This should be handle by the calculation script. This permit to create a customise behaviour for slices
- improve the error message in case of not found cells to make debugging easier


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28027 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28025 20353a03-c40f-0410-a6d1-a30d3c3de9de

- cartesianProduct is not needed : getCellKeyList can do the same thing in a better and cleaner way
- if movements already exists, we don't want to take only the first one, but all movements are needed
- improve error message to display the Line (title and relative_url) and the coordinates of the not found cell. This will make debugging much more easier
- to set quantity on new created movements, we search on movement_list if movements contribute to the current movement applied on, but we need to look also on already processed movements (current_aggregated_amount_list)
- the condition to check if the quantity of the current movement should be updated was wrong, fix it
- in TradeCondition, now one loop turn is enought to make all calculation
- change some variables names that where already used previously to avoid mistakes


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@28024 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27775 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27738 20353a03-c40f-0410-a6d1-a30d3c3de9de

Removing causality link from movement should make catalog a bit faster.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27690 20353a03-c40f-0410-a6d1-a30d3c3de9de

In this way, it's possible define that for a precise trade_phase, a precise source and destination will be set on movements.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27678 20353a03-c40f-0410-a6d1-a30d3c3de9de

- if the price is 0, we don't want to set it to 1. We want that only in the case it has not been defined (== None)
- typo


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27654 20353a03-c40f-0410-a6d1-a30d3c3de9de

 - reformat to use 2 spaces indentation


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27651 20353a03-c40f-0410-a6d1-a30d3c3de9de

 - workaround a problem for cell creation - it have to be split into two transactions in case of setting variation


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27613 20353a03-c40f-0410-a6d1-a30d3c3de9de

- fix comment to not use "we" form as it's explain in the wiki (http://www.erp5.org/GuidelinesForDocumentation?highlight=we)
- add context parameter to findEffectiveSpecialiseValueList to be more consistent with findSpecialiseValueList.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27612 20353a03-c40f-0410-a6d1-a30d3c3de9de

- cut line to 79 caracters


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27608 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27607 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27606 20353a03-c40f-0410-a6d1-a30d3c3de9de

 - code simplification (set properties of document while creating one)
 - rewrite comment


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27605 20353a03-c40f-0410-a6d1-a30d3c3de9de

 - do not analyse passed context in getAggregatedAmountList to simplify it, assume that movement or delivery is passed
 - add some comments and explanations to decision process
 - follow change for context in getAggregatedAmountList - TradeModelRule is passing simulation movement instead of applied rule


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27604 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27596 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27594 20353a03-c40f-0410-a6d1-a30d3c3de9de

- typo (remove unused spaces)


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27544 20353a03-c40f-0410-a6d1-a30d3c3de9de

- add start and stop_date properties to the created movments


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27537 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27513 20353a03-c40f-0410-a6d1-a30d3c3de9de

updateRelatedContent in CategoryTool calls edit(categories= which only works
with this property sheet


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27469 20353a03-c40f-0410-a6d1-a30d3c3de9de

- typo


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27468 20353a03-c40f-0410-a6d1-a30d3c3de9de

 - use accessor instead of getProperty for fetching reference on generated movement


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27419 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27417 20353a03-c40f-0410-a6d1-a30d3c3de9de

inheritate from Predicate. This permit to have the test method on TradeModelLine (used in getAggregatedAmountList)


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27412 20353a03-c40f-0410-a6d1-a30d3c3de9de

getAggregatedAmountList shall be updated or not
- add create_line property
- get quantity on previously generated movements only if there is variation_category_list on model line and if the quantity is not defined
- if there is slices define on the model_line change the quantity according to this slices


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27409 20353a03-c40f-0410-a6d1-a30d3c3de9de