If the companies belonging to the organisation are separate legal entities it might be unwanted (business risk wise) to share the same system. Great burdens will be there to prove that separations of functions and processes have been implemented correctly.
Sharing the same codebase, but in separate instantiations, might be wiser in that case. Sending documents related to transactions ( via web services) is fairly easy to achieve. This also applies to reporting. In the IMAGINE project regarding Dynamic Manufacturing Networks we are currently working on a proof of concept where one OFBiz instantiation (the customer) creating artefacts (tenders, opportunities) in its tenant environment automatically sees its public document in another (shared OFBiz) instantiation, and when a potential partner associates a particular document to himself it automatically creates a new document in his own OFBiz instantiation with his own perspective applied. The same applies to contracts, orders, invoices, returns, work assignments, etc. On Thu, May 23, 2013 at 9:33 AM, Hans Bakker <[email protected]>wrote: > We are currently implementing OFBiz in a large organization (300M$ > reveneu) )which intends to use all major components of OFBiz including > accounting. > > This means that every company in the holding will do his own accounting > and operation concerning orders, invoices and payments, so orders are sent > between ofbiz internal organizations as well as shipments, invoices and > payments. > > So, in other words, a purchase order for the originating organization is > send to another internal organization which needs to be converted to a > sales order for the receiving organization. The same for shipments, > invoices and payments. These documents can also be sent via web services > between completely separated OFBiz installations. > > Anybody having experiences with this and want to share? > > Regards, > Hans > -- Pierre Smits ApacheCon EU 2012 <http://www.apachecon.eu> - Sinsheim, Germany Apache OFBiz <http://ofbiz.apache.org>
