Am Donnerstag, 11. September 2014 12:37:33 UTC+2 schrieb Cédric Krier: > > Hi, > > Following my attempt to improve the situation of multi-company [1], I > faced so much problem that I only see to solution: > > - a very complicate one where many things will become a list per > company. For example on product, the prices, the accounts etc. > This will make the code very complicate but also the user > interface. > > - a very simple, drop company. > > > I start thinking that the last one is the right move even if it will > prevent none single company database to migrate. >
Oops. We are just in the step to move to a multi-company approach... > What are the use case of multi-company? > > - accounting consolidation > > It is a reporting issue that should be fixed by BI > > - sharing party > > That's a good one if you forget that parties have many properties > directly linked to the company like the accounts, tax rules etc. > And I think this can be acheived by using a synchronisation of the > common data using for example the CardDAV or any other similar > protocol. > You may have a syncronization, but not an integration. Integration would mean that some common information is held at the client level, while each company has a separate segment e.g. with specific sales or accounting information. > > - sharing product > > Quite similar to party expect that it has much more company related > properties. > So again it could be implemented using a synchronisation mechanism. > I know there are product description message in EDI, so it could be > a way. > > I don't see any other cases. > intercompany trades and billing for example cross-company sourcing (one sourcing department servers several companies) I feel this move would limit the capabilities of Tryton. And the companies using Tryton. Cheers/Axel
