By frank.buytendijk on Jan 03, 2010
In the previous post, I mentioned how a reader reacted, asking some questions about the architectural consequences on not routing general ledger information to the data warehouse, but directly to the financial consolidation tool.
Freddy Holwerda comments that I didn't address the full question. He writes:
In the readers reaction, the real problem seems to be the understanding of the reader that: 'Same information at the same time" sounds as bad architectural practice'. You don't seem to address that (mis) understanding in your post. From my point of few, this is not a bad architectural practice at all, as long as the interfaces between systems are well-defined, and ideally in a service-oriented way.
With Freddy, I agree there doesn't have to be an architectural issue. At first sight indeed it doesn't look nice to have the same data in both the DW and the Financial Consolidation tool. However, you should see them as different versions.
You could load GL data directly into the DW, and that would be a preliminary load. Then it goes to the Financial Consolidation system to be enriched, closed, reported etc. Then the final results are loaded into the DW too. So, it wouldn't be the same data, and wouldn't be at the same time.
Does that make sense?