The company Im working for has several "subsidiaries" that are treated as separate companies and have setup separate GP databases for each. I am still new to GP, but not to SQL. Initially, I was being tasked with setting up a data warehouse that incorporated the data in GP. I just realized that due to other projects getting in the way, this has been on the "to do list" for almost a year now.
So now its come to my attention that there isnt just one GP database, but 3 and soon to be 4. This makes using a single set of analysis cubes impossible, does it not?
Now I am leaning back toward building my own DW schema - partly because the source data that ultimately feeds GP has more of the data I need, and secondly because of the multiple GP databases.
Ok Im rambling a bit....here is my question.
How many of you in this situation have moved to suggest or actually do the "merging" yourself? I see references to add-ons / products that help manage the activity of separate legal entities within the same database.
From a DBA & developer standpoint, this would make my life much easier it would seem.
*This post is locked for comments
Binary Stream also makes a product called Multi Entity Management which enables multiple companies to live in one GP database with all appropriate user security set by entity (company). We have quite a number of customers using this product and it works well. It also allows for centralized AP and AR.
In additional to the reasons Susan mentions, there may be other reasons the companies or subsidiaries are in separate GP companies - for example, it may be the users in one subsidiary should not have access to data from another.
On the other hand, it may be that it would make business sense to consolidate these into one GP company. If that is the case, you most likely do not want to do this yourself, as it can get very complicated very quickly. Talk to either your GP partner or Microsoft about having this done for you as a service.
We have 17 companies with 17 GP databases, the solution I did was created another database, which we call IntegrationGP where we created amalgamated views and stored procedures. Which is used for Integration , reports , consolidation process.. what not. So coming back to your question I think own warehouse will be a good option.
Hope this helps, let me know what direction you took!
Due to the fact that they are separate legal entities, you have to separate out the databases. And your accounts are able to do the merging on the Financials for your company thru the use of MR. Also, there are a whole lot of Multi-company queries that come with Great Plains to make it easier for you. You might want to check but I thought there were some that called multi-company even in the cubes.
I've had clients that have had over 20 legal entities and therefore, 20 db's but you can write sql queries and views that can be used in SmartList thru SmartList Builder to run reports that cross the companies. it isn't that big a deal and for Accounting reasons you need to keep them separate.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156