c2c-oerpscenario team mailing list archive

[Joël Grand-Guillaume @ CampToCamp <joel.grandguillaume@xxxxxxxxxxxxxx>]

Hi all,


I just want to share my experience here as I already implement part of that in OpenERP 5.0... Let's start with a state-of-the-art summary :

1) I completely agree with Graeme : The list price is less important
here, we do have a workaround that make it well enough for now : making
different price lists

2) We do want to handle one product stock quantity for all company
(actually work), but different costs price per company (this is missing)

3) We want to manage multi-currency in product costs (actually working
with one currency and cost per company)

4) We want to be FIFO/LIFO compliant for future version

5) We want the average price to compute correctly for each company

Already tested solution :
---------------------------------
a) Add a price_type field on the company as a property field, defining the product field and currency to use for costing operation in this company (by default : standard_price, EUR).

b) Add as many float field on the product as different costs price &
currency

c) Change all computation and on_change everywhere where it is needed
(finance, analytic, stock, ...) to take the right price for each company
and make the right currency rate convertions.

d) Add an historic_amount float field in the stock move to store the
historical amount of the operations.

PLUS/CONS:
----------------
 + Very simple, may be the simplest one
 + Very easy to update (import/export) a cost price, you have as many field as value
 + Usability is good : cost manager can see all cost on a product tab
 + Can compute a average price per company
 + The historic_amount in stock move allow to recompute everything in any case
 
 - One field per price could be bad if lots of company and difference cost price
 - ?

Others possible solution:
--------------------------------
a) Idem that the first solution, but with a price list field as a property on the company as well as a new price list type "costing"

PLUS/CONS:
----------------
 + Allow complex rule for price costing (but is this really needed ?)
 + Usability is good : cost manager can see all cost on a product tab
 + Can compute a average price per company
 + The historic_amount in stock move allow to recompute everything in any case

 - More difficult to update and see prices than first solution as stored in price list
 - More power required to compute cost as we'll use the compute method of price list

b) We make the standard price a property field and change everything
else accordingly and Add an historic_amount float field in the stock
move to store the historical amount of the operations.


PLUS/CONS:
----------------
 + One "multi"/property field for all company
 + Can compute a average price per company

 - No support for multi-cunrrency here, all cost will be in a same currency for all company
 - More difficult to update (import/export) and see prices
 - Very hard to work to achieve, lots of changes and side effect to be expected


I have to leave now, I hope this helps a bit !


Regards,

Joël

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/778170

Title:
  product - list price, average and standard cost are not multicompany
  capable

Status in OpenERP Modules (addons):
  Triaged

Bug description:
  To reproduce, create some companys

  say HQ with child Company A and Company B
  create a product which is visible in all company at Average cost

  Receive product in Company A.
  Average Cost updates correctly in Company A.
  but it also updates Company B and parent.

  For standard price just go to company B and change a standard price
  product and it will propagate throughout

  Surely in a multicompany environment we must allow for different cost
  prices for each company.  And if using average cost it is clearly
  incorrect to take the average cost of another company (or the combined
  results) as your own average cost.  As a side note we must also allow
  different companies to use different cost methods for the same
  products.  Additionally it violates all sorts of security rules - a
  company B user should not be able to affect the accounts of Company A
  and these 2 fields determine the values for a very large number of
  journal entries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/778170/+subscriptions