Ask the Expert

Data warehouse management: General Ledger Business Process analysis

We are in the process of building a data warehouse for our General Ledger Business Process. What is the recommended level of detail for performing user General Ledger analysis? What should be our grain as it pertains to General Ledger? Should we keep it at a very generic level? Or, should we go for a classification of balances into revenue, expenses, profit and loss, cost of goods sold, etc?

    Requires Free Membership to View

In general (no pun intended), although the majority of data warehouse (including General Ledger) queries are run against summary data, the majority of the ROI from a data warehouse comes from the detailed data. So, you may think that you are providing "most" of the requirements by providing only summary data, and you are, but you are not providing the most "value." You can always summarize up from the detailed data, but cannot go the other way. I would suggest starting your General Ledger data warehouse project on the right foot - by sourcing the most granular detail you can. It sounds like your users will want different cuts of that data. You may have to classify, summarize, etc. from there before turning users on to it, but that is how I would begin.

 

This was first published in December 2005

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: