Community: Inventory and MRP mailing list archives

expert-inventory@mail.odoo.com

Re: Fast search of stock available, incoming, outgoing, forecasted

by
Camptocamp SA, Joël Grand-Guillaume
- 11/22/2016 08:41:16
Oh yes, I didn't though about that use case ! On large database, running a "live SQL" query to get more complex search happen in a acceptable response time, I would go for your proposition Jordi. So yes, I would store the quantity on hand, out going, incoming and forecasted by location.

Though may be, as you can only consider stock.moves that aren't done or cancel, (as quants handle them) a live SQL query might work. I mean e.g.may be to compute the incoming quantity, as you'll filter out done and canceled stock moves, you can probably compute it quite fast. Same for outgoing and forecasted.

Then, in any case, if you want to user to for example order the displayed list based on incoming quantity, I think you're forced to store the info anyway :( I guess you'll have to go for the complexe solution...

Regards,

Joël




On Tue, Nov 22, 2016 at 10:12 AM, Jos Colpaert <jco@openerp.com> wrote:
There is quite some interesting things done in the module of Akretion (we don't really combine for the virtual quantity, but it would require combining two read_groups somehow) and I don't see why it could not work on your orderpoints. (location that changes? Might be passed in the context from the search of orderpoints... depending of your number of locations) 

On Mon, Nov 21, 2016 at 8:42 PM, Jordi Ballester Alomar <jordi.ballester@eficent.com> wrote:

Thanks Joël,

I have looked at v9 and higher and it has not been fixed.

Our problem with akretion's is that we need more complex searches, of the type 'show the orderpoints whose forecasted stock is above the minimum'. And it seems to me that we can resolve best this type of queries if we store the on hand, incoming, outgoing and forecasted by location.

An alternative is to construct complex sql queries to resolve the question.

Regards,
Jordi.


El 21 nov. 2016 8:07 p. m., "Joël Grand-Guillaume" <joel.grandguillaume@camptocamp.com> escribió:
+1 to keep Akretion's way here. BTW I think this has been fixed on v9 and higher...

On Mon, Nov 21, 2016 at 7:07 PM, Jordi Ballester Alomar <jordi.ballester@eficent.com> wrote:
Dear experts,

We're looking to implement a fast search of stock available, incoming, outgoing, forecasted, by location.

We have been working on this approach: https://github.com/Eficent/stock-logistics-warehouse/tree/8.0-product_stock_location, until we found this other from Akretion:


I feel that the approach from Akretion is better, because it does not require a change to the data model. Does anyone have an opinion or an alternative approach?

Regards,
-- 

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-inventory-and-mrp-66
Post to: mailto:expert-inventory@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-inventory-and-mrp-66
Post to: mailto:expert-inventory@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-inventory-and-mrp-66
Post to: mailto:expert-inventory@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-inventory-and-mrp-66
Post to: mailto:expert-inventory@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28