Archives
Contributors
Stock valuation by location drilldown
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
by Radovan Skolnik - 11:51 - 19 May 2021
Follow-Ups
-
Re: Stock valuation by location drilldown
Aaron, YES! Not exactly but very close. It reports on product quantity while I need value but it is easy to modify. Also uses that magic child_of for searching in read_group which I wanted to ask about (had it in my email but deleted it). Thank you very much! Best regards Radovan On streda 19. mája 2021 14:22:07 CEST Aarón Henríquez Quintana wrote: > I think this is what you are looking for, isn't it? > https://github.com/OCA/stock-logistics-reporting/tree/13.0/stock_report_qua > ntity_by_location [1] On Wed, 19 May 2021 at 14:07, Radovan Skolnik < > radovan@skolnik.info [2] > 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 [3] > > * 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 [4] > > > *Sent:* Wednesday, 19 May 2021 9:47 PM > > *To:* Contributors < contributors@odoo-community.org [5] > > > *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 [6] [1] > > > Post to: mailto: contributors@odoo-community.org [7] > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [8] [2] > > > > > > > > > > > > [1] https://odoo-community.org/groups/contributors-15 [9] > > > [2] https://odoo-community.org/groups?unsubscribe [10] > > > > _______________________________________________ > > > > Mailing-List: > > https://odoo-community.org/groups/contributors-15 [11] [2] > > > > Post to: mailto: contributors@odoo-community.org [12] > > > > Unsubscribe: > > https://odoo-community.org/groups?unsubscribe [13] [3] > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [14] [4] > > Post to: mailto: contributors@odoo-community.org [15] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [16] [5] > > > > > > > > [1] mailto: geoff.szentesi@willdooit.com [17] > > [2] https://odoo-community.org/groups/contributors-15 [18] > > [3] https://odoo-community.org/groups?unsubscribe [19] > > [4] https://odoo-community.org/groups/contributors-15 [20] > > [5] https://odoo-community.org/groups?unsubscribe [21] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [22] > Post to: mailto: contributors@odoo-community.org [23] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [24] > > -- > Aaron Henríquez Quintana * Technical Consultant ahenriquez@forgeflow.com > [25] Twitter: /AaronHForgeFlow | Linkedin: / > aaron-henriquez-quintana-84299869 None [26] > None [27] None [28] None [29] None [30] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [31] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [32] > > > > [1] > https://github.com/OCA/stock-logistics-reporting/tree/13.0/stock_report_qua > ntity_by_location [2] mailto:radovan@skolnik.info > [3] mailto:richard.demeester@willdooit.com > [4] mailto:radovan@skolnik.info > [5] mailto:contributors@odoo-community.org > [6] https://odoo-community.org/groups/contributors-15 > [7] mailto:contributors@odoo-community.org > [8] https://odoo-community.org/groups?unsubscribe > [9] https://odoo-community.org/groups/contributors-15 > [10] https://odoo-community.org/groups?unsubscribe > [11] https://odoo-community.org/groups/contributors-15 > [12] mailto:contributors@odoo-community.org > [13] https://odoo-community.org/groups?unsubscribe > [14] https://odoo-community.org/groups/contributors-15 > [15] mailto:contributors@odoo-community.org > [16] https://odoo-community.org/groups?unsubscribe > [17] mailto:geoff.szentesi@willdooit.com > [18] https://odoo-community.org/groups/contributors-15 > [19] https://odoo-community.org/groups?unsubscribe > [20] https://odoo-community.org/groups/contributors-15 > [21] https://odoo-community.org/groups?unsubscribe > [22] https://odoo-community.org/groups/contributors-15 > [23] mailto:contributors@odoo-community.org > [24] https://odoo-community.org/groups?unsubscribe > [25] mailto:judit.valls@forgeflow.com > [26] https://www.forgeflow.com/ > [27] https://github.com/ForgeFlow > [28] https://www.linkedin.com/company/2415389 > [29] https://www.youtube.com/channel/UC6tv8_do-x2jg2nDx4H_DnA > [30] https://twitter.com/ForgeFlow > [31] https://odoo-community.org/groups/contributors-15 > [32] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 02:36 - 19 May 2021 -
Re: Stock valuation by location drilldown
I think this is what you are looking for, isn't it? https://github.com/OCA/stock-logistics-reporting/tree/13.0/stock_report_quantity_by_locationOn 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 QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
by Aarón Henríquez - 02:21 - 19 May 2021 -
Re: Stock valuation by location drilldown
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
by Radovan Skolnik - 02:05 - 19 May 2021 -
Re: Stock valuation by location drilldown
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: 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 drilldownThis 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
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Richard deMeester" <richard.demeester@willdooit.com> - 01:51 - 19 May 2021 -
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
by Radovan Skolnik - 01:46 - 19 May 2021
