Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
-
Re: subscription or contracts?
I think the contrary: contract is there for long time and it's rock solid, while subscription_oca is way far away in terms of features than the other. The only argument for now is that subscription_oca is simpler, which is true, but that's also because it has less features. And adding such features will get to the same complexity of contract. I agree things can be improved, like hiding some features like predecessor/successor under configuration options (or even extract it to another module), but that's something that is also "simple to improve".Regards.
by Pedro M. Baeza - 06:30 - 1 Apr 2024 -
Re: Help! Screen recording tool being discountinued
Hello Everyone,
You may try one of these two options- AnyDesk https://anydesk.com/en- TeamViewer https://www.teamviewer.com/en-mea/I use them alot during investigations and check with the customer.For Screen Recoridng you may use this optionAwesome Screenshot https://www.awesomescreenshot.comMany thanksOn Mar 19, 2024, at 1:22 PM, Francesco Foresti <notifications@odoo-community.org> wrote:Hi all,my question is not odoo-related but very relevant for operations in my company.We've been using this tool for screen recording and sharing: https://recordit.co/Unfortunately it will be discontinued by the end of the month and I'm looking for a replacement.This tool was specifically user friendly as installing the desktop app (mac/win covering 99% of customers) it allowed for:- having a quick shortcut to screen recording- when recording ended, a link was automatically generated for sharing the video- no storage limit or preservation issues (links would still be working after months)Now for this last point we'd be ok with paying a premium storage plan or something like that, the important thing is to provide anyone working with us an easy way to quickly record and share screen recording.What are your suggestions?Thanks!_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Abdalrhman Hassan عبدالرحمن حس ن" <abdo.towfeg@gmail.com> - 01:05 - 1 Apr 2024 -
RE: Help! Screen recording tool being discountinued
Or the Windows 10-11 integrated snipping tool, you can then share by e-mail, OneDrive, Teams, WhatsApp, …
From: Johan Van Hirtum <notifications@odoo-community.org>
Sent: 19 March 2024 15:22
To: Contributors <contributors@odoo-community.org>
Subject: RE: Help! Screen recording tool being discountinuedDear,
Maybe Teamviewer is what you need. You can take control of the screen of your customer and help him as if you are standing next to him.
With kind regards,
Van Hirtum Johan
Van: Francesco Foresti [mailto:notifications@odoo-community.org]
Verzonden: dinsdag 19 maart 2024 13:17
Aan: Contributors
Onderwerp: Re: Help! Screen recording tool being discountinuedJust for clarification: we're looking for tools to provide to the end users (anyone working in the customer's company), so when they have any issue with or question about a specific behavior we can see the exact steps to reproduce the behavior.
So the goal is to have users quickly report any behavior by sending us a screen recording of it :)
FrancescoIl giorno mar 19 mar 2024 alle ore 11:42 Jairo Llopis <notifications@odoo-community.org> ha scritto:
We are happy with loom.com, although they don't support Firefox or Linux very properly.
Another option is OBS, although it requires a bit more setup and manual work.
El mar, 19 mar 2024 a las 10:22, Francesco Foresti (<notifications@odoo-community.org>) escribió:
Hi all,
my question is not odoo-related but very relevant for operations in my company.
We've been using this tool for screen recording and sharing: https://recordit.co/
Unfortunately it will be discontinued by the end of the month and I'm looking for a replacement.
This tool was specifically user friendly as installing the desktop app (mac/win covering 99% of customers) it allowed for:
- having a quick shortcut to screen recording
- when recording ended, a link was automatically generated for sharing the video
- no storage limit or preservation issues (links would still be working after months)
Now for this last point we'd be ok with paying a premium storage plan or something like that, the important thing is to provide anyone working with us an easy way to quickly record and share screen recording.
What are your suggestions?
Thanks!
_______________________________________________
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_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by kinxton - 12:26 - 1 Apr 2024 -
RE: Proposing myself as CRM/Sales/Marketing PSC member
+1
De: Alexey Pelykh <notifications@odoo-community.org>
Enviado el: viernes, 8 de marzo de 2024 15:27
Para: Contributors <contributors@odoo-community.org>
Asunto: Proposing myself as CRM/Sales/Marketing PSC memberDear community,
My area of expertise is CRM/Sales/Marketing is limited to several modules, yet I can top it up by my other PSC membership for other repos.
Kind regards,
Alexey
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rafael Blasco (Moduon) - 12:47 - 31 Mar 2024 -
Re: subscription or contracts?
Hi,Our experience is that subscription is doing the stuff properly and natively.What cannot be done with subscription is mainly :* deal with different recurrent frequency on lines* make the quantity (invoiced/ordered) on dynamic data extracted from a python formulaEverything else is possible with subscription and mostly easier.So if you don't need one of those choose subscription.From now it's not available on the user portal but it will be simple to improve this.RegardsFlorent THOMAS
☎ +33 972 457 755
✉ florent.thomas@mind-and-go.comDe: "Jan Suhr | Nitrokey" <notifications@odoo-community.org>
À: "contributors" <contributors@odoo-community.org>
Envoyé: Vendredi 29 Mars 2024 22:22:13
Objet: subscription or contracts?Hi! I would like to use some functionality of recurring sales and/or recurring invoices. Looking at [1] I see "contract*" and subscription_oca. Both seem to do pretty much the same and I'm wondering which one to use. Subscriptions seem to be a bit easier to use. But are there any technical aspects which one solution can do but not the other? It seems that subscription_oca matches the official documentation [2] so maybe it's an OCA maintained former Odoo SA implementation? And contracts are an independent implementation? In this case which one has the more promising future path? Best regards, Jan [1] https://github.com/OCA/contract/ [2] https://www.odoo.com/documentation/15.0/applications/sales/subscriptions.html
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Florent THOMAS - 07:51 - 30 Mar 2024 -
subscription or contracts?
Hi! I would like to use some functionality of recurring sales and/or recurring invoices. Looking at [1] I see "contract*" and subscription_oca. Both seem to do pretty much the same and I'm wondering which one to use. Subscriptions seem to be a bit easier to use. But are there any technical aspects which one solution can do but not the other? It seems that subscription_oca matches the official documentation [2] so maybe it's an OCA maintained former Odoo SA implementation? And contracts are an independent implementation? In this case which one has the more promising future path? Best regards, Jan [1] https://github.com/OCA/contract/ [2] https://www.odoo.com/documentation/15.0/applications/sales/subscriptions.html
by Jan Suhr - 10:21 - 29 Mar 2024 -
Re: Group based editable tree vs form pop up edition?
BTW this is the POC PR for sales in v14 if you are interested:All in all the way to switch the tree view to editable or not is a bit different between v14 and v16 but the idea to do it in the _view_get method is the same.Thank you again for encouraging me to try it this way.On Thu, Mar 28, 2024 at 11:17 PM Raphaël Valyi <notifications@odoo-community.org> wrote:Hello,Thank you Holger, overriding _get_view and using user_has_group absolutely still works in v16!I tried something like this for instance:if self.user_has_groups('base.group_system'):
for sub_form_node in arch.xpath("//field[@name='invoice_line_ids']/tree"):
sub_form_node.attrib["editable"] = ""I initially assumed the result of the method might be cached but fortunately that is not where the cache happens(I could test with different users). So the change is pretty easy to deal with.On Wed, Mar 27, 2024 at 3:17 PM Holger Brunn <notifications@odoo-community.org> wrote:*Do you have an alternative solution to suggest for v16?* override get_view for your model, and do group specific things there. Or probably better, override _get_view_cache [1], and also override _get_view_cache_key to add self.env.user.has_group('the_group.youre_looking_for') or similar to the cache key. I mourned the loss of group-specific view inheritance quite a bit, because you can do very nifty things with it. So I'm still of a mind to eventually write an addon that brings it back for models with some mixin applied. [1] https://github.com/OCA/OCB/blob/16.0/odoo/addons/base/models/ ir_ui_view.py#L2635 -- Your partner for the hard Odoo problems https://hunki-enterprises.com_______________________________________________
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 ValyiFounder and consultant_______________________________________________
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 ValyiFounder and consultant
by "Raphaël Valyi" <rvalyi@akretion.com> - 08:40 - 29 Mar 2024 -
Re: Group based editable tree vs form pop up edition?
Hello,Thank you Holger, overriding _get_view and using user_has_group absolutely still works in v16!I tried something like this for instance:if self.user_has_groups('base.group_system'):
for sub_form_node in arch.xpath("//field[@name='invoice_line_ids']/tree"):
sub_form_node.attrib["editable"] = ""I initially assumed the result of the method might be cached but fortunately that is not where the cache happens(I could test with different users). So the change is pretty easy to deal with.On Wed, Mar 27, 2024 at 3:17 PM Holger Brunn <notifications@odoo-community.org> wrote:*Do you have an alternative solution to suggest for v16?* override get_view for your model, and do group specific things there. Or probably better, override _get_view_cache [1], and also override _get_view_cache_key to add self.env.user.has_group('the_group.youre_looking_for') or similar to the cache key. I mourned the loss of group-specific view inheritance quite a bit, because you can do very nifty things with it. So I'm still of a mind to eventually write an addon that brings it back for models with some mixin applied. [1] https://github.com/OCA/OCB/blob/16.0/odoo/addons/base/models/ ir_ui_view.py#L2635 -- Your partner for the hard Odoo problems https://hunki-enterprises.com_______________________________________________
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 ValyiFounder and consultant
by "Raphaël Valyi" <rvalyi@akretion.com> - 03:15 - 29 Mar 2024 -
Re: Group based editable tree vs form pop up edition?
*Do you have an alternative solution to suggest for v16?* override get_view for your model, and do group specific things there. Or probably better, override _get_view_cache [1], and also override _get_view_cache_key to add self.env.user.has_group('the_group.youre_looking_for') or similar to the cache key. I mourned the loss of group-specific view inheritance quite a bit, because you can do very nifty things with it. So I'm still of a mind to eventually write an addon that brings it back for models with some mixin applied. [1] https://github.com/OCA/OCB/blob/16.0/odoo/addons/base/models/ ir_ui_view.py#L2635 -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 07:16 - 27 Mar 2024 -
Group based editable tree vs form pop up edition?
Dear Odoo experts,CONTEXT:More and more we are being contacted by companies who already use Odoo in some countries and would like to use it in Brazil too using the multi-companies approach. For service companies it's nearly possible (and a no go for industries because still too many side effects to deal with).As we isolated most of the fiscal craziness in the l10n_br_fiscal module with its own tables and UI, we can inject the Brazilian localization pretty smoothly in other modules (specially through our l10n_br_account module mediation).PROBLEM:What is still a problem is about half of the users in a Brazilian company need to check or even edit many fiscal parameters in orders lines or invoice lines (see screenshots).So we used to force the popup form based edition for these lines, that is we inherit the tree element and remove the editable="bottom" attribute.This however is very invasive for the non Brazilian users (because it is slower, because they might have customized the tree view). It also causes friction with some other modules that expect the default inline tree edition.To fix this I recently made a POC where we would have advanced Brazilian fiscal groups where users would see use these popup forms while many users would use the default inline tree edition.The problem is that it was using the groups_id in ir.ui.view to enable or not the group based view selection. But this feature has been removed in Odoo v16 to make the view caching easier:Do you have an alternative solution to suggest for v16? As views will be cached without group consideration I imagine the selection between editable tree and form will need to happen on the client side...I tried to add a groups=... on the attribute tag that overrides the editable property but it is not effective...Do you know a simple Javascript approach?Alternatively would could have a button in the tree that would open the form popup. Ideally that would be a Javascript action that doesn't require saving the form (a server side action would also have trouble finding a proper non inline form view to inherit). Such a Javascript button to switch the view could even be a generic OCA module. Any pointers on how to do it?Thank you.
by "Raphaël Valyi" <rvalyi@akretion.com> - 05:16 - 27 Mar 2024 -
Re: Issues when running tests
I take the freedom to ask an additional tip, this time is about writing tests:I made this PR which is only failing code coverage check by a 0,01% diff compared to last commit.This diff though, is marked as an indirect change due to partial coverage of a line which is defined in another module: see on code coverage .Is it possible for me to fix this missing coverage in my PR? Any hint on how to manage this?Thank you again,Fra B.Il giorno mar 26 mar 2024 alle ore 22:26 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:Thanks @Michael Tietz @Isabelle RICHARD, my brain often goes into "low battery mode" at the end of the day. I was running tests in a db without demo datas enabled and confusing master-data and demo data. 😁Thank you very muchFrancesco B.Il giorno mar 26 mar 2024 alle ore 21:12 Isabelle RICHARD <notifications@odoo-community.org> ha scritto:Hi Francesco,You are talking about master data, but the product with the reference product.product_product_9 is a demo data.It's only present in your database if you enabled the Demo Data option, when you created your database.Data is defined in: https://github.com/odoo/odoo/blob/14.0/addons/product/data/product_demo.xmlWhich is referred as a demo file in manifest: https://github.com/odoo/odoo/blob/14.0/addons/product/__manifest__.py#L48Did you enable this?
Regards,--Isabelle RICHARDLe mar. 26 mars 2024 à 20:57, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hello,I am trying to run tests in my Odoo instance by adding --test enable but I'm having some issues. I am not used to run tests so I'm probably just missing something.When I try to run tests for module sale_product_multi_add by launching command:python3 odoo-bin -c odoo.conf -d dbname -u sale_product_multi_add --test-enabletests immediately fails because `self.env.ref()` cannot read external ids for master-datas. You can see the complete log in attached .txtI have also tried to run the same command for module sale_product_brand_exception which also checks for master-data and I got the same error.It seems like an issue with the environment, but addons path is defined in odoo.conf and working well outside of tests. I have also tried to pass --addons-path parameter in the CLI command but the result didn't changed.I hope I have provided enough informations, if not, let me know.Do you have any suggestions?Thanks,Fra B._______________________________________________
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
by Francesco Ballerini - 10:56 - 27 Mar 2024 -
Re: Issues when running tests
Thanks @Michael Tietz @Isabelle RICHARD, my brain often goes into "low battery mode" at the end of the day. I was running tests in a db without demo datas enabled and confusing master-data and demo data. 😁Thank you very muchFrancesco B.Il giorno mar 26 mar 2024 alle ore 21:12 Isabelle RICHARD <notifications@odoo-community.org> ha scritto:Hi Francesco,You are talking about master data, but the product with the reference product.product_product_9 is a demo data.It's only present in your database if you enabled the Demo Data option, when you created your database.Data is defined in: https://github.com/odoo/odoo/blob/14.0/addons/product/data/product_demo.xmlWhich is referred as a demo file in manifest: https://github.com/odoo/odoo/blob/14.0/addons/product/__manifest__.py#L48Did you enable this?
Regards,--Isabelle RICHARDLe mar. 26 mars 2024 à 20:57, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hello,I am trying to run tests in my Odoo instance by adding --test enable but I'm having some issues. I am not used to run tests so I'm probably just missing something.When I try to run tests for module sale_product_multi_add by launching command:python3 odoo-bin -c odoo.conf -d dbname -u sale_product_multi_add --test-enabletests immediately fails because `self.env.ref()` cannot read external ids for master-datas. You can see the complete log in attached .txtI have also tried to run the same command for module sale_product_brand_exception which also checks for master-data and I got the same error.It seems like an issue with the environment, but addons path is defined in odoo.conf and working well outside of tests. I have also tried to pass --addons-path parameter in the CLI command but the result didn't changed.I hope I have provided enough informations, if not, let me know.Do you have any suggestions?Thanks,Fra B._______________________________________________
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
by Francesco Ballerini - 10:31 - 26 Mar 2024 -
Re: Issues when running tests
Hi Francesco,You are talking about master data, but the product with the reference product.product_product_9 is a demo data.It's only present in your database if you enabled the Demo Data option, when you created your database.Data is defined in: https://github.com/odoo/odoo/blob/14.0/addons/product/data/product_demo.xmlWhich is referred as a demo file in manifest: https://github.com/odoo/odoo/blob/14.0/addons/product/__manifest__.py#L48Did you enable this?
Regards,--Isabelle RICHARDLe mar. 26 mars 2024 à 20:57, Francesco Ballerini <notifications@odoo-community.org> a écrit :Hello,I am trying to run tests in my Odoo instance by adding --test enable but I'm having some issues. I am not used to run tests so I'm probably just missing something.When I try to run tests for module sale_product_multi_add by launching command:python3 odoo-bin -c odoo.conf -d dbname -u sale_product_multi_add --test-enabletests immediately fails because `self.env.ref()` cannot read external ids for master-datas. You can see the complete log in attached .txtI have also tried to run the same command for module sale_product_brand_exception which also checks for master-data and I got the same error.It seems like an issue with the environment, but addons path is defined in odoo.conf and working well outside of tests. I have also tried to pass --addons-path parameter in the CLI command but the result didn't changed.I hope I have provided enough informations, if not, let me know.Do you have any suggestions?Thanks,Fra B._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Isabelle RICHARD - 09:10 - 26 Mar 2024 -
Re: Issues when running tests
Hello,
it seems that your database contains no demo data.
The tests are only running with demo data.
Ensure that you creating your database without this flat "--without-demo" https://www.odoo.com/documentation/17.0/developer/reference/cli.html?highlight=demo#cmdoption-odoo-bin-without-demo
Am 26.03.24 um 20:57 schrieb Francesco Ballerini:
Hello,
I am trying to run tests in my Odoo instance by adding --test enable but I'm having some issues. I am not used to run tests so I'm probably just missing something.
When I try to run tests for module sale_product_multi_add by launching command:
python3 odoo-bin -c odoo.conf -d dbname -u sale_product_multi_add --test-enable
tests immediately fails because `self.env.ref()` cannot read external ids for master-datas. You can see the complete log in attached .txt
I have also tried to run the same command for module sale_product_brand_exception which also checks for master-data and I got the same error.
It seems like an issue with the environment, but addons path is defined in odoo.conf and working well outside of tests. I have also tried to pass --addons-path parameter in the CLI command but the result didn't changed.
I hope I have provided enough informations, if not, let me know.Do you have any suggestions?
Thanks,Fra B.

Privo di virus.www.avast.com _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Michael Tietz - 09:06 - 26 Mar 2024 -
Issues when running tests
Hello,I am trying to run tests in my Odoo instance by adding --test enable but I'm having some issues. I am not used to run tests so I'm probably just missing something.When I try to run tests for module sale_product_multi_add by launching command:python3 odoo-bin -c odoo.conf -d dbname -u sale_product_multi_add --test-enabletests immediately fails because `self.env.ref()` cannot read external ids for master-datas. You can see the complete log in attached .txtI have also tried to run the same command for module sale_product_brand_exception which also checks for master-data and I got the same error.It seems like an issue with the environment, but addons path is defined in odoo.conf and working well outside of tests. I have also tried to pass --addons-path parameter in the CLI command but the result didn't changed.I hope I have provided enough informations, if not, let me know.Do you have any suggestions?Thanks,Fra B.
by Francesco Ballerini - 08:57 - 26 Mar 2024 -
Manufacturing Operations - Duration UoM
Hello, Community.For some types of manufacturing the Operation Duration can be planned in days, rather than in minutes.Are there any OCA modules available which will override the default Duration of the BoM / Operations?Thank you.
by Arthur Franklin Smith - 04:35 - 23 Mar 2024 -
Re: Stock valuation based on warehouse/location - food for thought ;-)
Hi! Check this Odoo Experience Video from 2021: https://www.youtube.com/watch?v=JHqrYn_Xgk0 Regards El 2024-03-21 06:56, Graeme Gellatly escribió: > Odoo had actual cost. Then removed it. Now it is available for select > odoo customers but not me. I have to do my own. > On Thu, 21 Mar 2024, 9:42 pm Frederik Kramer, < > notifications@odoo-community.org [1] > wrote: > Hi Graeme, > > you are right. I all to often forget that Odoos "Standard Price" > valuation method, is "only" using the default standard price not > the actual purchase price. (see > https://www.odoo.com/documentation/17.0/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.html > [2] ) > Though i do agree that this is mostly a reporting issue and should > be adjustable via specific journal items, i would still prefer a > valuation based on cost price. Can't imaging that i would be all > to hard to implement this. But it should definitly be done by Odoo > S.A. themselves. Did anybody ever raise this feature request? I > think if Odoo really wants to compete with say SAP it needs to > implement this. It'll be hard to manually adjust that for million > stock transaction multi warehouse case. > Best Frederik > > Am 21.03.24 um 08:57 schrieb Graeme > Gellatly: > > > Serialisation is neither a qualification nor > disqualification. IAS2 is a simple standard largely unchanged > since the 70s. Seperately identifiable refers mostly to > wjether the organisation seperately identifies it e.g. for a > particular customer. E.g a large order at special pricing or > a custom manufacture item could qualify. But a bunch of > serialised items for general sale that are easily exchanged do > not. > > Cost method won't do it because odoo does not > support it. In cases where everything is custom or non > fungible you basically have to use actual cost or serial track > svls using fifo. Either is custom dev. I've done both, serial > with fifo is easier but not without issues. More recently with > v16 making Fifo a bit difficult for my use cases I've > reimplemented actual over a small subset of non fungible > items. It is manageable but at an entire company catalog scale > i wouldn't trust it. > > But in truth it is only a reporting issue. If > your stock turn is high and you don't have a lot of it it is > usually immaterial or easily adjusted for manually during > report preparation. > > > On Thu, 21 Mar 2024, 8:36 pm Frederik Kramer, > < notifications@odoo-community.org [3] > > wrote: > > > What does "separately identifiable" mean? Is a serial > number enough? I generally don't see a reason why cost > price method wouldn't do the job. It is valuing based > on every single purchase transaction, isn't it? > > Best Frederik > > Am 21.03.24 um 01:42 schrieb Graeme Gellatly: > > Under ias2 if it is seperately > identifiable for a customer it should have its own > valuation regardless of warehouse location. The > usual 2 ways are actual cost with lot tracking not > in odoo standard or a seperate product. > > On Thu, 21 Mar 2024, 9:46 am Iryna > Vyshnevska, < notifications@odoo-community.org [4] > > wrote: > > > Cost method can be set per product per > company, so if warehouses A and B belong to > different companies valuation can be > different. I hardly can imagine a need to have > a different valuation approach for one product > in one company as this will create different > approaches in valuation in accounting. > > > > On Wed, Mar 20, 2024 at 10:00 PM > Abdalrhman Hassan عبدالرحمن حس ن < notifications@odoo-community.org > [5] > > wrote: > > What a methdolgoy !🤔 > First time hear about this scenario. > > > On Mar 20, 2024, at 9:02 PM, > Radovan Skolnik < notifications@odoo-community.org [6] > > wrote: > > Hi, > today I have had an interesting conversation about Odoo's shortcoming > regarding stock valuation. I was told it is common practice and in > some cases part of the legislation in here to have a different stock > valuation in different warehouses/locations. For example I commonly > purchase a certain type of notebook which I store in a warehouse A > from which I also sell it. Now I have won a big contract to supply 500 > of such notebooks somewhere. I contact my supplier, arrange a big > discount for the 500 notebooks and have them sent to warehouse B (a > project warehouse). The requirement would be that the valuation of > stock in warehouse B is different (based on that heavily discounted > purchase) from the one in warehouse A and these 2 shouldn't mix. > Have you ever encountered such requirement? Is this common situation? > I do not really need to solve this but it just got me curious. I guess > it should be possible to create such a thing but that would mean > patching stock_account, purchase_stock, stock_landed_costs and > mrp_subcontracting_[purchase|dropshipping] and we would have possible > as many stock valuation layer entries for each product as > warehouses/locations that we deal with separately. Any inputs/comments > would be welcome. > Best regards > Radovan Skolnik > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [7] > Post to: mailto: contributors@odoo-community.org [8] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [9] > > > > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [10] > Post to: mailto: contributors@odoo-community.org [11] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [12] > > > > > -- > > > > Вишневська Ірина > > Vyshnevska Iryna > > > > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [13] > Post to: mailto: contributors@odoo-community.org [14] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [15] > > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [16] > Post to: mailto:contributors@odoo-community.org [17] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [18] > > > -- > Dr.-Ing. Frederik Kramer > Geschäftsführer > initOS GmbH > Innungsstraße 7 > 21244 Buchholz i.d.N. > Tel: +49 (0) 4181 13503 12 > Fax: +49 (0) 4181 13503 10 > Mobil: +49 (0) 179 3901819 > Email: frederik.kramer@initos.com [19] > Internet: www.initos.com [20] > Geschäftsführung: > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke > Sitz der Gesellschaft: Buchholz i.d.N. > Amtsgericht Tostedt, HRB 205226 > USt-IdNr.: DE815580155 > Steuer-Nr: 15/200/53247 > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [21] > Post to: mailto: contributors@odoo-community.org [22] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [23] > > > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [24] > Post to: mailto:contributors@odoo-community.org [25] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [26] > > > -- > Dr.-Ing. Frederik Kramer > Geschäftsführer > initOS GmbH > Innungsstraße 7 > 21244 Buchholz i.d.N. > Tel: +49 (0) 4181 13503 12 > Fax: +49 (0) 4181 13503 10 > Mobil: +49 (0) 179 3901819 > Email: frederik.kramer@initos.com [27] > Internet: www.initos.com [28] > Geschäftsführung: > Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke > Sitz der Gesellschaft: Buchholz i.d.N. > Amtsgericht Tostedt, HRB 205226 > USt-IdNr.: DE815580155 > Steuer-Nr: 15/200/53247 > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [29] > Post to: mailto: contributors@odoo-community.org [30] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [31] > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [32] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [33] > > > > [1] mailto:notifications@odoo-community.org > [2] > https://www.odoo.com/documentation/17.0/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.html > [3] mailto:notifications@odoo-community.org > [4] mailto:notifications@odoo-community.org > [5] mailto:notifications@odoo-community.org > [6] mailto:notifications@odoo-community.org > [7] https://odoo-community.org/groups/contributors-15 > [8] mailto:contributors@odoo-community.org > [9] https://odoo-community.org/groups?unsubscribe > [10] https://odoo-community.org/groups/contributors-15 > [11] mailto:contributors@odoo-community.org > [12] https://odoo-community.org/groups?unsubscribe > [13] https://odoo-community.org/groups/contributors-15 > [14] mailto:contributors@odoo-community.org > [15] https://odoo-community.org/groups?unsubscribe > [16] https://odoo-community.org/groups/contributors-15 > [17] mailto:contributors@odoo-community.org > [18] https://odoo-community.org/groups?unsubscribe > [19] mailto:frederik.kramer@initos.com > [20] http://www.initos.com > [21] https://odoo-community.org/groups/contributors-15 > [22] mailto:contributors@odoo-community.org > [23] https://odoo-community.org/groups?unsubscribe > [24] https://odoo-community.org/groups/contributors-15 > [25] mailto:contributors@odoo-community.org > [26] https://odoo-community.org/groups?unsubscribe > [27] mailto:frederik.kramer@initos.com > [28] http://www.initos.com > [29] https://odoo-community.org/groups/contributors-15 > [30] mailto:contributors@odoo-community.org > [31] https://odoo-community.org/groups?unsubscribe > [32] https://odoo-community.org/groups/contributors-15 > [33] https://odoo-community.org/groups?unsubscribe
by info - 01:12 - 22 Mar 2024 -
Re: [POS][16.0]Any way to sell a same product in different UoM
Thank to all of you,Definitively Kit BoM is the right answer !RegardsFlorent THOMAS
☎ +33 972 457 755
✉ florent.thomas@mind-and-go.comDe: "Cyril VINH-TUNG" <notifications@odoo-community.org>
À: "contributors" <contributors@odoo-community.org>
Envoyé: Mercredi 20 Mars 2024 17:47:24
Objet: Re: [POS][16.0]Any way to sell a same product in different UoMHi FlorentFor a restaurant or a bar, we setup a UOM 'Bottle of 70cl' (type volume with factor of 0.7)And then a BOM (kit) : To do a glass of wine take 17cl of the bottle.You can do beers or cocktails with the same ideaBest regards--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.com
www.invitu.comLe mer. 20 mars 2024, 03:01, Florent Thomas <notifications@odoo-community.org> a écrit :Thanks Olger,Our use case is bottle of wine an dwine sold as a glass.Stock, sales and purchase are in uom = bottleglass = 1/6 of the bottleYour proposal implies a new product and a setup that could be difficult to maintain but you're right it should work.Thanks for sharing your thoughts !RegardsFlorent THOMAS
☎ +33 972 457 755
✉ florent.thomas@mind-and-go.comDe: "Holger Brunn" <notifications@odoo-community.org>
À: "contributors" <contributors@odoo-community.org>
Envoyé: Mercredi 20 Mars 2024 11:32:35
Objet: Re: [POS][16.0]Any way to sell a same product in different UoM> I'm wondering if there is any way to have a product in the pos where you can > choose the UoM you want tu use for the order. I' would like to prevent the > creation of a second product with different UoM and managing the inventory how about a kit product with a BOM that contains your original product? This also gives you a quite natural way to convert between the different UOM categories. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
_______________________________________________
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
by Florent THOMAS - 10:05 - 21 Mar 2024 -
Re: Stock valuation based on warehouse/location - food for thought ;-)
Odoo had actual cost. Then removed it. Now it is available for select odoo customers but not me. I have to do my own.On Thu, 21 Mar 2024, 9:42 pm Frederik Kramer, <notifications@odoo-community.org> wrote:Hi Graeme,
you are right. I all to often forget that Odoos "Standard Price" valuation method, is "only" using the default standard price not the actual purchase price. (see https://www.odoo.com/documentation/17.0/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.html) Though i do agree that this is mostly a reporting issue and should be adjustable via specific journal items, i would still prefer a valuation based on cost price. Can't imaging that i would be all to hard to implement this. But it should definitly be done by Odoo S.A. themselves. Did anybody ever raise this feature request? I think if Odoo really wants to compete with say SAP it needs to implement this. It'll be hard to manually adjust that for million stock transaction multi warehouse case.
Best Frederik
Am 21.03.24 um 08:57 schrieb Graeme Gellatly:
Serialisation is neither a qualification nor disqualification. IAS2 is a simple standard largely unchanged since the 70s. Seperately identifiable refers mostly to wjether the organisation seperately identifies it e.g. for a particular customer. E.g a large order at special pricing or a custom manufacture item could qualify. But a bunch of serialised items for general sale that are easily exchanged do not.
Cost method won't do it because odoo does not support it. In cases where everything is custom or non fungible you basically have to use actual cost or serial track svls using fifo. Either is custom dev. I've done both, serial with fifo is easier but not without issues. More recently with v16 making Fifo a bit difficult for my use cases I've reimplemented actual over a small subset of non fungible items. It is manageable but at an entire company catalog scale i wouldn't trust it.
But in truth it is only a reporting issue. If your stock turn is high and you don't have a lot of it it is usually immaterial or easily adjusted for manually during report preparation.
On Thu, 21 Mar 2024, 8:36 pm Frederik Kramer, <notifications@odoo-community.org> wrote:
What does "separately identifiable" mean? Is a serial number enough? I generally don't see a reason why cost price method wouldn't do the job. It is valuing based on every single purchase transaction, isn't it?
Best Frederik
Am 21.03.24 um 01:42 schrieb Graeme Gellatly:
Under ias2 if it is seperately identifiable for a customer it should have its own valuation regardless of warehouse location. The usual 2 ways are actual cost with lot tracking not in odoo standard or a seperate product.
On Thu, 21 Mar 2024, 9:46 am Iryna Vyshnevska, <notifications@odoo-community.org> wrote:
Cost method can be set per product per company, so if warehouses A and B belong to different companies valuation can be different. I hardly can imagine a need to have a different valuation approach for one product in one company as this will create different approaches in valuation in accounting.
On Wed, Mar 20, 2024 at 10:00 PM Abdalrhman Hassan عبدالرحمن حس ن <notifications@odoo-community.org> wrote:
What a methdolgoy !🤔
First time hear about this scenario.
On Mar 20, 2024, at 9:02 PM, Radovan Skolnik <notifications@odoo-community.org> wrote:
Hi, today I have had an interesting conversation about Odoo's shortcoming regarding stock valuation. I was told it is common practice and in some cases part of the legislation in here to have a different stock valuation in different warehouses/locations. For example I commonly purchase a certain type of notebook which I store in a warehouse A from which I also sell it. Now I have won a big contract to supply 500 of such notebooks somewhere. I contact my supplier, arrange a big discount for the 500 notebooks and have them sent to warehouse B (a project warehouse). The requirement would be that the valuation of stock in warehouse B is different (based on that heavily discounted purchase) from the one in warehouse A and these 2 shouldn't mix. Have you ever encountered such requirement? Is this common situation? I do not really need to solve this but it just got me curious. I guess it should be possible to create such a thing but that would mean patching stock_account, purchase_stock, stock_landed_costs and mrp_subcontracting_[purchase|dropshipping] and we would have possible as many stock valuation layer entries for each product as warehouses/locations that we deal with separately. Any inputs/comments would be welcome. Best regards Radovan Skolnik
_______________________________________________
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
--
Вишневська Ірина
Vyshnevska Iryna
_______________________________________________
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
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
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
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Graeme Gellatly" <graeme@moahub.nz> - 10:56 - 21 Mar 2024 -
Re: Stock valuation based on warehouse/location - food for thought ;-)
Hi Graeme,
you are right. I all to often forget that Odoos "Standard Price" valuation method, is "only" using the default standard price not the actual purchase price. (see https://www.odoo.com/documentation/17.0/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.html) Though i do agree that this is mostly a reporting issue and should be adjustable via specific journal items, i would still prefer a valuation based on cost price. Can't imaging that i would be all to hard to implement this. But it should definitly be done by Odoo S.A. themselves. Did anybody ever raise this feature request? I think if Odoo really wants to compete with say SAP it needs to implement this. It'll be hard to manually adjust that for million stock transaction multi warehouse case.
Best Frederik
Am 21.03.24 um 08:57 schrieb Graeme Gellatly:
Serialisation is neither a qualification nor disqualification. IAS2 is a simple standard largely unchanged since the 70s. Seperately identifiable refers mostly to wjether the organisation seperately identifies it e.g. for a particular customer. E.g a large order at special pricing or a custom manufacture item could qualify. But a bunch of serialised items for general sale that are easily exchanged do not.
Cost method won't do it because odoo does not support it. In cases where everything is custom or non fungible you basically have to use actual cost or serial track svls using fifo. Either is custom dev. I've done both, serial with fifo is easier but not without issues. More recently with v16 making Fifo a bit difficult for my use cases I've reimplemented actual over a small subset of non fungible items. It is manageable but at an entire company catalog scale i wouldn't trust it.
But in truth it is only a reporting issue. If your stock turn is high and you don't have a lot of it it is usually immaterial or easily adjusted for manually during report preparation.
On Thu, 21 Mar 2024, 8:36 pm Frederik Kramer, <notifications@odoo-community.org> wrote:
What does "separately identifiable" mean? Is a serial number enough? I generally don't see a reason why cost price method wouldn't do the job. It is valuing based on every single purchase transaction, isn't it?
Best Frederik
Am 21.03.24 um 01:42 schrieb Graeme Gellatly:
Under ias2 if it is seperately identifiable for a customer it should have its own valuation regardless of warehouse location. The usual 2 ways are actual cost with lot tracking not in odoo standard or a seperate product.
On Thu, 21 Mar 2024, 9:46 am Iryna Vyshnevska, <notifications@odoo-community.org> wrote:
Cost method can be set per product per company, so if warehouses A and B belong to different companies valuation can be different. I hardly can imagine a need to have a different valuation approach for one product in one company as this will create different approaches in valuation in accounting.
On Wed, Mar 20, 2024 at 10:00 PM Abdalrhman Hassan عبدالرحمن حس ن <notifications@odoo-community.org> wrote:
What a methdolgoy !🤔
First time hear about this scenario.
On Mar 20, 2024, at 9:02 PM, Radovan Skolnik <notifications@odoo-community.org> wrote:
Hi, today I have had an interesting conversation about Odoo's shortcoming regarding stock valuation. I was told it is common practice and in some cases part of the legislation in here to have a different stock valuation in different warehouses/locations. For example I commonly purchase a certain type of notebook which I store in a warehouse A from which I also sell it. Now I have won a big contract to supply 500 of such notebooks somewhere. I contact my supplier, arrange a big discount for the 500 notebooks and have them sent to warehouse B (a project warehouse). The requirement would be that the valuation of stock in warehouse B is different (based on that heavily discounted purchase) from the one in warehouse A and these 2 shouldn't mix. Have you ever encountered such requirement? Is this common situation? I do not really need to solve this but it just got me curious. I guess it should be possible to create such a thing but that would mean patching stock_account, purchase_stock, stock_landed_costs and mrp_subcontracting_[purchase|dropshipping] and we would have possible as many stock valuation layer entries for each product as warehouses/locations that we deal with separately. Any inputs/comments would be welcome. Best regards Radovan Skolnik
_______________________________________________
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
--
Вишневська Ірина
Vyshnevska Iryna
_______________________________________________
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
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
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
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer - 09:41 - 21 Mar 2024