Skip to Content

Contributors

  • Re: Accounting PSC Member apply
    Hi,

    I've added you to the PSC. you should get an invitation soon.

    Cheers

    On Wed, May 19, 2021 at 10:17 AM Harald Panten Lopez <harald.panten@sygel.es> wrote:
    Hi Community,

    I would like to apply for PSC member on Accounting repositories.

    Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

    You can have a look at my profile https://github.com/HaraldPanten

    THX!

    --

    Harald Panten López

    CEO

    Sygel Technology S.L

    +34 637 88 42 41
    harald.panten@sygel.es
    https://www.sygel.es
    C/ Àlaba 61, 5ª planta, 08005, Barcelona

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



    --
    Simone Orsi

    Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

    by Simone Orsi - 09:36 - 20 May 2021
  • Re: Accounting PSC Member apply
    +1

    Il gio 20 mag 2021, 19:12 Enric Tobella <etobella@creublanca.es> ha scritto:
    +1

    On 20 May 2021 18:27, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
    +1

    On Wed, May 19, 2021, 15:17 Harald Panten Lopez <harald.panten@sygel.es> wrote:
    Hi Community,

    I would like to apply for PSC member on Accounting repositories.

    Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

    You can have a look at my profile https://github.com/HaraldPanten

    THX!

    --

    Harald Panten López

    CEO

    Sygel Technology S.L

    +34 637 88 42 41
    harald.panten@sygel.es
    https://www.sygel.es
    C/ Àlaba 61, 5ª planta, 08005, Barcelona

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: 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






    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.

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


    by Sergio Corato - 07:21 - 20 May 2021
  • Re: Accounting PSC Member apply
    +1

    On 20 May 2021 18:27, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:
    +1

    On Wed, May 19, 2021, 15:17 Harald Panten Lopez <harald.panten@sygel.es> wrote:
    Hi Community,

    I would like to apply for PSC member on Accounting repositories.

    Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

    You can have a look at my profile https://github.com/HaraldPanten

    THX!

    --

    Harald Panten López

    CEO

    Sygel Technology S.L

    +34 637 88 42 41
    harald.panten@sygel.es
    https://www.sygel.es
    C/ Àlaba 61, 5ª planta, 08005, Barcelona

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: 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






    Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
    pueden contener información reservada y/o confidencial, destinada exclusivamente
    para el uso del destinatario o la persona responsable de entregarlo al mismo,
    estando su uso no autorizado prohibido legalmente.
    Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
    salvo ratificación escrita por ambas partes. En caso de su recepción por error,
    rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
    o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
    a su eliminación.

    by Enric Tobella Alomar - 07:10 - 20 May 2021
  • Re: Accounting PSC Member apply
    +1

    On Wed, May 19, 2021, 15:17 Harald Panten Lopez <harald.panten@sygel.es> wrote:
    Hi Community,

    I would like to apply for PSC member on Accounting repositories.

    Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

    You can have a look at my profile https://github.com/HaraldPanten

    THX!

    --

    Harald Panten López

    CEO

    Sygel Technology S.L

    +34 637 88 42 41
    harald.panten@sygel.es
    https://www.sygel.es
    C/ Àlaba 61, 5ª planta, 08005, Barcelona

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


    by Kitti Upariphutthiphong - 06:26 - 20 May 2021
  • Re: Accounting PSC Member apply
    OK for me.

    by Pedro M. Baeza - 06:20 - 20 May 2021
  • Re: Accounting PSC Member apply
    +1

    El 19 may 2021, a las 10:17, Harald Panten Lopez <harald.panten@sygel.es> escribió:

    Hi Community,

    I would like to apply for PSC member on Accounting repositories.

    Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

    You can have a look at my profile https://github.com/HaraldPanten

    THX!

    --

    Harald Panten López

    CEO
    Sygel Technology S.L
    +34 637 88 42 41
    harald.panten@sygel.es
    https://www.sygel.es
    C/ Àlaba 61, 5ª planta, 08005, Barcelona


    by Valentín Vinagre - 05:40 - 19 May 2021
  • 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

    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


          


    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 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
    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
  • RE: Stock valuation by location drilldown

    Not a drilldown but you may get the data you want via this module:

    https://github.com/CannaICT/canna-erp-third-party/tree/13.0/stock_level_export_xls

     

    Regards,

    Luc

     

    From: Radovan Skolnik <radovan@skolnik.info>
    Sent: Wednesday, 19 May 2021 11:52
    To: Contributors <contributors@odoo-community.org>
    Subject: 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 Luc De Meyer. - 12:20 - 19 May 2021
  • 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
  • Re: Project consumable (v14.0)
    Ok then if it's very different. I don't see the conversion to account.analytic.line. For me that should be the final result (project.task.material generates account.analytic.line when an analytic account is generated). Also to force consumable instead allowing stockable/consumable is something I don't see.

    Regards.

    by Pedro M. Baeza - 10:46 - 19 May 2021
  • Re: Project consumable (v14.0)
    I've seen that module and this is why I've chosen to not use it:

    * I'm not sure it's the same purpose
    * I do not require to enforce consumable to be linked to a specific task only to the project
    * I'm not sure we need an extra model (`project.task.material`)
    for my needs and I'm a bit afraid about keep consistency between such model
    and `account.analytic.line`. Or do you agree that I move `project.task.material` to
    use `account.analytic.line` instead ?
    If so I can change the behaviour and provide a migration script to smoothly go ahead.

    Let me know what you think !


    Le mer. 19 mai 2021 à 10:26, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
    I would go with using and expanding if needed project_task_material.

    Regards.

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



    --
    Pierre

    by Pierre Verkest - 10:41 - 19 May 2021
  • Re: Project consumable (v14.0)
    I would go with using and expanding if needed project_task_material.

    Regards.

    by Pedro M. Baeza - 10:26 - 19 May 2021
  • Accounting PSC Member apply
    Hi Community,

    I would like to apply for PSC member on Accounting repositories.

    Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.

    You can have a look at my profile https://github.com/HaraldPanten

    THX!

    --

    Harald Panten López

    CEO

    Sygel Technology S.L

    +34 637 88 42 41
    harald.panten@sygel.es
    https://www.sygel.es
    C/ Àlaba 61, 5ª planta, 08005, Barcelona

    by Harald Panten Lopez - 10:16 - 19 May 2021
  • Project consumable (v14.0)
    Hi there,

    I've the need to follow the analytic cost of consumables per project.

    As far when consumables are purchase we don't know how they will be used and while creating the quotation we don't know how exactly how many consumable to be sale, I'll create a new module probably called project_consumable in oca/project repo that will let users to record used consumable that will create relevant analytic account line linked to the consumable product and project (likes hr_timesheet which record time per project/task). I'll take care we get proper analysis.

    I plan later to generate sale order (I know this is not very suitable. Add products in the generated invoice would make more sense in odoo... could be done in different modules anyway ) from some of those account move lines.

    Are there already such efforts? I'll be happy to hear your comments :)

    regards,

    --
    Pierre Verkest
    06 81 12 25 20
    Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest

    by Pierre Verkest - 10:01 - 19 May 2021
  • Re: Mail cc
    Hello everyone,
    I'm proposing the module to OCA with https://github.com/OCA/social/pull/711


    On Wed, 17 Mar 2021 at 11:17, Lorenzo Battistini <elbaddy@gmail.com> wrote:
    I am interested!

    On Sun, 27 Dec 2020 at 22:47, Rafael Blasco <rblasco@rbnpro.com> wrote:

    Hello,

     

    I would recommend as best approach this one: https://github.com/sygel-technology/sy-server-backend/tree/12.0/mail_show_follower

     

    I’m sure Valentin can propose this module to OCA if there is interest.

     

    Regards,

    Rafael

     

     

    De: Sergio Corato <sergiocorato@gmail.com>
    Enviado el: martes, 1 de diciembre de 2020 10:47
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Mail cc

     

    Hi all,

     

    AFAIK there isn't a generic approach to send mail with CC instead of A, or I miss something?

     

    The use case would be something like: if a mail is sent to 1 recipient, go with A. If there are multiple recipients, 1 go with A and the other with CC.

     

    So an 'integrated' logic, without user intervention (except to optionally change the A recipient, or something other).

     

    Thanks in advance!

     

    Sergio Corato

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



    --


    --

    by Lorenzo Battistini. - 03:40 - 18 May 2021
  • Re: Account financial reserve naming

    On Mon, May 17, 2021 at 10:11 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:
    That's not exactly the same purpose (we use both in our project).

    I think for v14, we can base our thinking on the new voucher module in that flow (I will do soon a PR with a wallet-voucher or sth similar).

    A migration PR for sale_promotion_rule is currently draft there. IMHO, we need to split the coupon flow accordingly too.

    On Mon, May 17, 2021 at 10:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:
    Hi,

    We addressed a similar need with (oca/sale_workflow) sale_promotion_rule.
    The "deposit" is simply a voucher. It can be splitted (partial use in a SO), increased, and expiration can be set.

    Ok for account-wallet , may be move sale_promotion_rule there?

    Regards,

    Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> a écrit :
    +1 account-wallet

    Antonio M. Vigliotti

    Mobile (+39) 342.8740910



    Il 12/05/21 17:11, Bruno Joliveau ha scritto:
    +1 for account-wallet

    Bruno Joliveau - Président
    NUMIGI SOLUTIONS INC.
    (514) 317-7944

    Longueuil, Québec, Canada

    linkedin youtube custom-icon twitter


    Le mer. 12 mai 2021 à 11:06, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
    Hi all,


    I'm requesting the creation of a new repository named account-wallet.

    I hope this will help to fulfill people request. I will add PR's for 14 soon.

    I think we can add it to accounting-maintainers PSC.


    Thanks all for the little brainstorming.

    On Tue, May 11, 2021 at 2:45 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
    Yes.

    I think that will not conflict with future Odoo sale gift card (but they change their mind meantime).

    Maybe account-wallet (for repo)? 

    Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
    wallet is an interesting name too.

    I guess it's best to create a new repo, since this is a suite of modules covering several areas ?

    -sbi

    On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> wrote:
    May be intresting for other countries, if I understand the request.

    The financial reserve is a sort of payment down but not specific for any order.

    In Italy is called "anticipo" (like payment down but it is not the same meaning) or portafoglio (Italian term for "wallet"). The account should be a <credit account type>.
    We have to develop a module with this feature, can we share the thinks ena eventually the code, if you agred.

    Antonio M. Vigliotti

    Mobile (+39) 342.8740910



    Il 11/05/21 13:37, Roussel, Denis ha scritto:
    I like it.

    One thing more is the fact that that fund can be partner agnostic. As it can represent a 'gift voucher' which has a certain balance corresponding to the voucher value (if not used yet).

    Apart of that consideration, is it a good idea to create a repo for those modules or to go in an existing one ?

    On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    Hi,

    Maybe a good name would be account_partner_fund ?

    In a nutshell, we have the following concepts in these modules (as I understand it after a quick reminder from Cedric, errors and imprecisions are mine, but the general idea should be this):

    - funds (cagnottes) are created
    - a balance sheet account is used to track the funds, with all journal items in this account having a m2o to the corresponding fund + partner_id
    - funds can be credited with balance sheet movements (bank to fund, no VAT impact)
    - funds can be used as payment means
    - when funds expire, there is a debit fund / credit revenue, and at that moment some VAT is due

    Best regards,

    --
    Stéphane Bidoul | @SBidoul
    Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120

    On Mon, May 10, 2021 at 6:37 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
    Hi all,


    We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.

    We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account. 

    These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).

    If we can have a little feedback from some of you on our future baby name.


    Regards,

    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: 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



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: 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

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



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

    _______________________________________________
    Mailing-List: https://odoo-community.org/groups/contributors-15
    Post to: mailto:contributors@odoo-community.org
    Unsubscribe: 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


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



    --
    Raphaël Reverdy
    Mobile +33 6 38 02 03 93
    Fixe +33 4 82 53 84 60

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



    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg


    --
    __________________________________________
    Denis Roussel
    Software Engineer
    Acsone SA, Succursale de Liège (Val Benoît)
    Tel    : +32 2 888 31 49
    Fax   : +32 2 888 31 59
    Gsm : +32 472 22 00 57

    Acsone sa/nv
    Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels  | Belgium
    Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
    Zone Industrielle 22 | L-8287 Kehlen | Luxembourg

    by Denis Roussel - 10:16 - 17 May 2021