My company is co-locating with another company that runs BaaN A&D 4C. This co-location is unique in that the 2 companies desire to share services in some areas (purchasing, mfg,shipping) under a common overhead rate structure yet have the ability to segrsgate the finances in order to report P&Las 2 seperate companies. In other words act as 2 seperate companies living together and sharing services under a common rate structure. In our initial meetings with the (BaaN) host company the financial people and IT staff believed that the proper approach would be to run under one instance of BaaN, use the dimension features to provide the detail necessary to cull out the finances. After a more thorough examination the finance people discovered that the menon feature did not provide the single solution global discriminator that they needed to create 2 sets of books in the backend. For example: we desire the ability to enable purchasing to place a single purchase order for mixed jobs of both companies without losing the segregation in the GL.
I'm looking for people or recommendations of others who have any experience with company consolidations under BaaN for the purpose participating in a round table discussion determine the best approach for this project. Formal requests have already been sent to BSP and few others but I'm open for suggestions.
Thanks

This seems like a challenging task.
However when I see your problem, my first reaction is to create 2 financial companies, linked to one logistic company. Your single Purchase order can be shared for your 2 financial companies, but not one single PO line (at least not directly). I f you need any assistance just mail.
Regards,
Marc

The solution posted by "invensys user" is correct in terms of Baan functionality. It is termed "multi-financial/single-logistic". However that configuration is somewhat rare and you may have some trouble finding examples where it has been implemented before for guidance. That is opposed to "single-financial/multi-logistic", which is much more common and includes a set of standard Baan documentatrion outlining how to configure your logical tables.

If you cannot find a good example for the above for guidance, then I would suggest for "Plan B" would be to create two seperate companies. The first would be "single/single" and the second would be "single-financial/multi-logistic". This "third logistic company" would be your overall demand planning companyu (the fact that it is linked to one of tghe companies should be irrevelant. creating a third "single/single" would be another option). All purchasing would take place from this thir company, which would be the overall suplier to the first two cokmpanies. This way you could aggregate demand in one place for purchasing and tracking.

I have set up similar systems before both for purchasing and sales. It is not too difficult and offers some tracking advantages as well as making the assimilation of future organizations easier.

Stephen Ruger
Lodestar Consulting
+1.215.785.6756
sr@mylodestar.com

Currently I'm involved in a multi financial/ single logistics implementation (BaanVb) and I've done a few in the past for Baan IV as well. It really depends on your requirements to make a well thought decision.
Regards,
Marc:p

Does Baan have a "standard" list of logical tables available for "multi-financial/single-logistic" available on help the same way it does for "single-financial/multi-logistic"? If so, it would help setup a great deal.

I've attached a list of tables/ modules shared for a financial company, not beeing the group company. Group company is the financial group company, and the logistic company as well.

I appreciate the response here but does the A&D version limit my options?
The version we are running is BaaN 4.03C with A&D 2.2B and it is currently set up as a single log/single fin.

The A&D 2.2 version does effect how you do table sharing. I have clients that have run into this. I have discussed the general topic with them but due to the work I was doing for them never got into the detail of which specific tables could be shared.

-- Jim