I am very much familiar with the Universe Design concepts,But i havent created any universes so far.Since,I have just upgraded my professional profile,so now i have to create universes in real time,If any one could provide some snapshots of universes that they have worked on,if theres no copyright or confidential issues,it would be a big help for me.Thanks.
What do you think you will get out of a snapshot? (I am assuming you’re talking about a screen shot / screen capture here.) Without having the universe around to “play with” a screen shot is not going to do you much good. You need to be able to open the universe, check out the contexts, and most of all you need to be able to run queries to see how the universe behaves, what issues were faced, and how they were solved.
The eFashion universe is actually a very good example of a bad universe. There are many issues and errors that can be corrected. So despite the fact that you dismissed that out of hand earlier I suggest that you do go through the eFashion universe and see what errors or issues you can identify and fix them.
I thought screenshot would give me a basic knowledge of how a good universe looks(I thought its enough,besides how can i expect some one to share the universes,considering the effort which have gone into build it).I was expecting a screenshot of a well made universe,which has no errors and all the context and joins are properly placed.Still,i think its enough for me,i can learn from it,anyone please!
The problem with screen shots, as I mentioned, is you have no way to review the contexts. Without seeing that, you have no idea if the universe is “good” or not. A person would have to post multiple screen shots, one for each context in the universe, in order to provide that information.
How a universe ‘looks’ visually has very little to do with whether it’s ‘good’ or ‘bad’. Anyone can arange the squares into pretty little organizational units and it might look great. You can also take a fully optimized universe, hit that simple little “Arrange Tables” button and viola! Your universe now looks like crap.
The only thing I can advise about universe creation other than the normal functional options, is utilize the TEXT feature. That is clicking on a white space and typing (many don’t realize you can do that). I use a small section off to my left where I put the Universe Name, Version Number, Creator contact information as well as a small changelog when major changes are done from one version to another. It really helps when developers open a universe and can easily see who to contact as well as a small history of changes.
The best advice I can give is to start small! When creating my universes for the first time, I tend to bring in one or two fact tables only, and a few dimension tables… build some objects and then go play in WeBI building queries and looking at the SQL. That exercise tends to tell me whether or not the joins I’ve done work properly or are optimized, especially if I’m using Short-Cut joins, contexts and aggregate aware properly.
Good luck, and welcome to the wonderful world of Universe Design. Try not to build too many black holes.
EDIT: oh and If you’ve not already done so, check out some of the blogs of those posters in Green… many have great ‘tips’ on universe creation on the blogs as well as old presentations from previous development conferences. I don’t know how many are available on the internet, but the authors are often lurking on the boards here. Two titles that come to mind are “This Old Universe” and “Tricks of the Universe Masters”… I remember both of those were very useful when I started out designing.
Thanks for your valuable suggestions,i was expecting something that provides me a starting point or just a clue to start.Yeah,i understand the look of the universe doesnt have to match its quality,
I have only been working with Universes for about 6 months now but in that short time I have found that (and having inheritted a fair few universes that don’t do what they should!), a good universe will have addressed the main concerns of loops, contexts, etc, but the main thing is that it when you report from it, it gives users the correct answers and gives them no headaches trying to report from it!
Check the results direct against the database using tools like TOAD, get access to the front end systems and talk with the users to get an idea of how things work, what tricks they use to get things to work (amazing how much ‘fudging’ goes on in the front end) and what their business processes are, then create your universe, testing as you go. A schema for the database and the support desk of the company providing the database is a bonus! If you come across issues, BOB has the answers or links to the answers (Rakesh - great link! Haven’t seen that page before).
As for visually looking like a good universe, it can look a mess - as long as it does what it is meant to and users get the correct answers, that is all that matters.
As for sample universes, they are good to get a feel for things but getting stuck in and finding your way is the best approach I have found.
Thanks for the insight,Rolls.So,the requirement anlaysis plays a very important role than the actual process of building the universe.Is there any standard or streamlined process or methodology or recommendations for designing a universe,i see a lots of nice ideas about designing a universe,but they are not documented well to know the enitre process,it would be a great help for beginners like me if some mentor or a collective effort could deliver such one.
That has actually already been done. SAP Business Objects and their worldwide partners provide training course on universe design. This would be ideal for you.
At this risk of sounding like a broken record (scratched compact disc?) you should investigate the universe designer training course. It’s a three day course that covers a wide variety of standard universe challenges as well as best practices.
I really sympathise with you, I had the same thing when I started at my place - designer training and a manual then ‘please can you look after these 25 universes, create new ones and develop reports’, not to mention having to do helpdesk, user administration and migration to XI R3; not great. My approach is below as to what I did to get going but at my place there is one chap who know everything, who is a nice chap and really helpful - hopefully there will be someone at your place like this who can help, 5 minutes with these people can help you for weeks!
Get SQL books on the databases you use (oracle, sql server) and learn your functions (www.techonthenet.com) - plenty of reading on universe design - get access to the front end systems (even if only View access) and have a play - get access to a sql tool like TOAD (again with view access to the database) and try to match the front end with the backend - spend time with the users of the front end systems and get to know their processes (universes are not a map of the database, they represent business processes - get to grips with that and you will be on your way) - find your fact table and start adding the dimension tables (always test everything you do at each stage, in BO and front end system - get it right first time and save yourself some hassle later on) - build your objects and measures. Keep a note book with everything you learn.
When things go wrong - Check BoB first every time! - test the SQL (there is usually a clue there) - keep in touch with DBA’s (they know when changes have been made to tables, etc. A DBA at my place has been a great help from this perspective and I would have been lost without his help!) - check with system administrators on any changes to workflow, etc - be persistant.
3 main points:
The only way to get over the worry about starting a universe is to just get stuck in.
Enjoy things going wrong - you learn more things from fixing things that having things go right all the time
If you are starting from the point I started (which sounds familiar) you will learn the hard way but will great at your job in 6 months.
Hope it all goes well for you, I am sure you will find your way.