1. Mailing Lists
  2. Contributors
  3. Re: Stock valuation by location drilldown

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Stock valuation by location drilldown

Re: Stock valuation by location drilldown

Avatar

Re: Stock valuation by location drilldown

by
ForgeFlow, S.L., Aarón Henríquez
- 19/05/2021 14:17:28

On Wed, 19 May 2021 at 14:07, Radovan Skolnik <radovan@skolnik.info> wrote:
I guess I understand but: as I described in my initial post I need to be able 
to make the sum of stock.quant values recursively. Let's say a single location 
represents a warehouse or store room (first level location), with racks (second 
level location) and shelfs (third level location). Now I need to be able to 
see value of that top level location which should incorporate value of all of 
its children and their children... Hope I am making myself clear.

Best regards

	Radovan

On streda 19. mája 2021 13:56:49 CEST Richard deMeester wrote:


> If your context has a warehouse, or a location_id, then all the figures that


> are computed on product will be contextually constrained based on that


> context.  Exactly what compute figures are available on product.product


> varies from version to version, but the context should already be enough to


> achieve what you need.


> 


> 


> 


> 


> 


> 


> 


> 


> 


> 


> 


> 


> * Richard deMeester *


> 


> Senior Development Analyst


> 


> * WilldooIT Pty Ltd ** *


> * E: *   None [1] richard.demeester@willdooit.com


> * M: *   +61 403 76 76 76


> * P: *   +61 3 9135 1900


> * A: *   10/435 Williamstown Road, Port Melbourne, Vic 3207


> 


> 


> 


> 


> 


> 


> Making growth through technology easy *


> 


> 


> 


> *   *


> * DISCLAIMER *   | This electronic message together with any attachments is


> confidential. If you are not the recipient, do not copy, disclose, or use


> the contents in any way. Please also advise us by e-mail that you have


> received this message in error and then please destroy this email and any


> of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes


> made to this message and/or any attachments after sending by WilldooIT Pty.


> Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all


> liability for virus or anything similar in this email or attachment.


> 


> 


> 


> 


> 


> 


> 


> *From:* Radovan Skolnik <radovan@skolnik.info>


> *Sent:* Wednesday, 19 May 2021 9:47 PM


> *To:* Contributors <contributors@odoo-community.org>


> *Subject:* Re: Stock valuation by location drilldown


> 


> This idea came to mind (please comment on its viability): in stock_account


> there is computed field value of stock.quant that calculates the value.


> stock.location has quant_ids. So it should be easily possible to create a


> computed field for stock.location that would make sum of its stock.quants as


> well as its child stock.locations. I guess there could be some magic that


> would allow to prevent recursive call to sum of stock.location children.


> Any pointers on how to do that?


> Thank you. Best regards


> Radovan Skolnik


> 


> On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote:


> > Hello,


> > I might be stupid not to see how todo that but let me ask. We have


> > locations design in a hierarchical way (as I guess is designed). So for


> > example we have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts


> > / RowNo / ShelfNo. Now the stock resides at the leaf nodes in this


> > hierarchy (shelfs). Is there a simple way to do stock valuation by some


> > sort of drilldown? Or at least to get stock value of top location


> > including all its children recursively? The need stems from the


> > requirement to compare this calculation to other Inventory software which


> > is to be replaced by Odoo. But first we have to be sure the calculations


> > match. Thank you. Best regards


> > Radovan Skolnik


> > 


> > 


> > _______________________________________________


> > Mailing-List: https://odoo-community.org/groups/contributors-15 [1]


> > Post to: mailto:contributors@odoo-community.org


> > Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]


> > 


> > 


> > 


> > [1] https://odoo-community.org/groups/contributors-15


> > [2] https://odoo-community.org/groups?unsubscribe


> 


> _______________________________________________


> Mailing-List:


> https://odoo-community.org/groups/contributors-15 [2]


> Post to: mailto:contributors@odoo-community.org


> Unsubscribe:


> https://odoo-community.org/groups?unsubscribe [3]


> 


> 


> 


> _______________________________________________


> Mailing-List: https://odoo-community.org/groups/contributors-15 [4]


> Post to: mailto:contributors@odoo-community.org


> Unsubscribe: https://odoo-community.org/groups?unsubscribe [5]


> 


> 


> 


> [1] mailto:geoff.szentesi@willdooit.com


> [2] https://odoo-community.org/groups/contributors-15


> [3] https://odoo-community.org/groups?unsubscribe


> [4] https://odoo-community.org/groups/contributors-15


> [5] https://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



--
Aaron Henríquez Quintana
Technical Consultant
Twitter: /AaronHForgeFlow  |  Linkedin: /aaron-henriquez-quintana-84299869


      

Reference