Contributors

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