Hello Jordi,
unfortunately i can't find any situation where the outgoing_before field is
wrongly computed. Can you provide me such a use case?
For me, it's clear that the periods that should be considered are all the ones
that have a date_stop between
-the date_start of current period
-the day before the date_start of the period set on the stock planning
... and this is the case. In the case where current period = period set on the
stock planning, then it will give 0 and this is the logical behavior.
Where am i wrong?
Quentin
** Changed in: openobject-addons
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to OpenERP Project Group.
https://bugs.launchpad.net/bugs/802569
Title:
[6.0.2] stock_planning: outgoing_before field in stock.planing is not
correctly computed
Status in OpenERP Addons (modules):
Incomplete
Bug description:
[6.0.2] stock_planning: outgoing_before field in stock.planing is not
correctly computed.
The quantity in the 'Planned out' field (planned_outgoing) is not
added between the start date of the current period and one day before
the start of the computed period.
It works well doing this change in stock_planning/stock_planning.py
file:
@@ -338,7 +338,7 @@
FROM stock_planning AS planning \
LEFT JOIN stock_period AS period \
ON (planning.period_id = period.id) \
- WHERE (period.date_stop >= %s) AND (period.date_stop <=
%s) \
+ WHERE (period.date_stop >= %s) AND (period.date_start
<= %s) \
AND (planning.product_id = %s) AND
(planning.company_id = %s) \
GROUP BY planning.product_uom", \
(date_start, date_stop, val.product_id.id,
val.company_id.id,))
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/802569/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to : [email protected]
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help : https://help.launchpad.net/ListHelp
