openerp-india team mailing list archive

["Olivier Dony \(OpenERP\)" <939435@xxxxxxxxxxxxxxxxxx>]

Hello Pierre,

This is in fact a design choice. There are a few options when setting up
a multi-company OpenERP instance:

a) Assume a fully separate company is desired, and create all the
company-specific elements that could be necessary: chart of accounts,
warehouses and stock locations, fiscal periods/years, journal sequences,
and so on. The downside is that this may create a lot of useless data
that will be difficult to clean up if it is not needed. A manual review
of multi-company elements is still needed, for defining cross-company
record visibility policy, access control, etc.

b) Assume the new company will need a few company-specific elements but
not many, and let the admin create them appropriately as part of the
manual review of multi-company elements.

c) Create a complicated assistant to help the admin during the setup of
the multi-company instance: asking which of the company-specific
elements need to be created, which kind of cross-company record
visibility policy and access control should be set by default, etc.


OpenERP has currently chosen option b), because a complete analysis of all multi-company aspects is necessary in all cases anyway. Every multi-company environment has its own needs in terms of shared/separate data, consolidation, etc, and there are several questions that must be answered before even considering to start a multi-company database, such as whether products will be shared between companies, whether multi-currency consolidation will be needed, etc.
This is a crucial step that cannot be taken lightly, and requires a good expertise with the product. It seems natural to let the admin create the few company-specific elements at the same time, in a precise and controlled manner.

Assuming some generic defaults as in solution a) would only delay the
need for the careful manual review (as you noticed yourself in comment
#1), and require more manual actions than would be needed for option a)
in most cases.

In the long run the best option would probably be option c), but that is not available yet.
Feel free to start contributing ideas or code for this option... :-)

I hope this clarifies the topic a little bit...

Do not hesitate to ask questions on [1] or contact the support team if
you need further assistance in the setup of a multi-company instance.

[1] https://answers.launchpad.net/openobject-addons

** Changed in: openobject-server
       Status: New => Opinion

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/939435

Title:
  Multi-Companies : company creation don't create default wharehouses
  and locations archtecture.

Status in OpenERP Server:
  Opinion

Bug description:
  Products view
  Invoices, ...

  won't work without this.

  The same problem concerne the default price lists.

  It seem to be ok for accounting.

  Multi_company creation process should be review ?

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