If you are unable to create a new account, please email support@bspsoftware.com

 

Best Modeling Practice: How to handle SCD within the model for end users?

Started by charmingberry, 12 Jul 2010 03:03:39 PM

Previous topic - Next topic

charmingberry

I have a fact table that has a number of SCD on it.   I am trying to figure out as a Framework Modeler, what is the best ways to deal with SCDs for the end users?   Some end users will need Current Data while others may want a point in time data set.

For current reporting, I have report studio writers that can filter on the current record and will be fine.  However, an average manager using query studio, might not know they are to filter on the current record. 
I have considered in the presentation layer having two namespaces; Current Reporting and Point in Time Reporting.  The current reporting namespace would have the filters in place on the query subjects for the end user.

Is there a better way of dealing with this?  I am new to modeling but I do understand my end users needs and abilities.  Making things clear and easy is key.

blom0344

You might consider creating 2 packages on the model. If sales managers are going to deal solely with 'current' data, then it would be a matter of authorizing them for the package that automatically offers that and only that.
Your report writer can then have access to the full model making their own choices. Sales managers can then still have execute rights on 'canned' reports..