Am Freitag, 12. September 2014, 15:50:57 schrieb Cédric Krier: > On 12 Sep 06:26, Axel Braun wrote: > > > What are the use case of multi-company? > > > - 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. > > I don't understand. > What information at the client level?
Information on the client level can be something that is valid for all companies, like name of the product, size & weight, EAN-code, product hierarchy, indicators, e.g. for dangerous goods etc. On plant or sales region / company level you may have sales unit of measurement, tax codes or tax rules, minimum order quantities etc. By this you have integration on many information, but separate values for companies where it is required > > > - 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 > > This should be managed with by preference EDI. Because for each document > on one side, you have to create one on the other side but of course it > could be validated automatically. I would avoid EDI as much as I could. Complicated, expensive and error-prone unless you have tested it out completely. And requires additional EAI-software resp EDI converter > So clearly, this doesn't require at all to be on the same database. > Moreover, if someone develop such feature, it will work for companies on > the same hosts but also across any network. So this will be a truly > generic solution. > > > cross-company sourcing (one sourcing department servers several companies) > > I don't understand. You have a couple of sales companies, who do their sourcing via a central souring company or department, in order to take advantage from economies of scale. Physically they (the sales companies) may share the same warehouse, but sell for a different price. Example: small franchise chain with web-sales. all different legal units but from supply chain perspective with shared services. Quite a comon model nowadays. HTH Axel
