UNV Universe Documenter – biclever. Review of Information Design Tool 4.1. It’s been a while since I wrote my initial review on Information Design Tool (IDT) in SAP BusinessObjects 4.0.
If you’ve read that post, you know that I was frustrated with missing features in IDT, as compared to Universe Design Tool. Every time I found a missing feature, I opened an Idea on the SAP Idea Place, requesting that the missing feature be added. Well, as it turns out, I was the top contributor for new ideas for IDT 4.1. And nearly all of my requests were delivered in version 4.1. So, I’ve been using IDT 4.1 for quite some time now, and am ready to give my impressions.
The Good News IDT has some really nice features that I find very helpful when doing universe development. Families: Tables can be grouped into families, and each family can have its own color. The Bad News. Impressions of Information Design Tool. It’s been well over two years since I got my first look at the SAP BusinessObjects Information Design Tool (IDT).
However, that was pre-Beta, and the tool has undergone some changes since then. The version that went GA last September, 2011, wasn’t the same version that I originally saw in early 2010. Since the GA release, I’ve spent quite a bit of time with IDT, and would like to record my current impressions. It’s important to keep in mind that Universe Design Tool (Formerly known as Designer), is a very mature product, and quite stable.
IDT, on the other hand, is a relatively young tool, and, as such, has some quirks and bugs. Let’s Start With The Good News If you’ve read my earlier post on What’s New in Universe Design, you would know that the universe has a new structure, consisting of three different layers: Universe Design Best Practices. I’ve always avoided writing a blog on universe best practices, primarily because there have been many others who have written some excellent blogs on the topic.
However, I have had quite a few requests to write about it, and have finally agreed to compile my own list of Best Practices for universe design. After all, the universe is one of the best advantages SAP has over other BI tools. So, a well thought out, well built universe is key to a successful deployment. SAP BusinessObjects includes two tools for building and maintaining universes: Universe Design Tool (the legacy tool formerly known as Designer) and Information Design Tool (the newer tool, first released with version 4.0). These Best Practices will, for the most part, apply to both tools. An Introduction to Analytic Functions.
Purpose: Analytic Functions are database functions defined in the universe and passed through to the database server.
The functions perform a task on a result set that can order groups of rows or partitions. They are called by different names: RISQL - Redbrick OLAP Functions - Teradata Benefits: They reduce work by providing the functionality at the universe layer where it would have required extended syntax at the report level. They offer expanded calculation functionality. Oracle Security User Defined Context. This is an excerpt from the bestselling book "Oracle Privacy Security Auditing", a complete Oracle security reference with working Oracle security scripts.
Damit kann ein User_Kontext übergeben werden an Oracle für Row-Level Security. – ffink
User Defined Context Just as there is a system defined namespace context, the user can also define a context to hold application data.
This is done through the SQL statement CREATE CONTEXT. As we saw earlier, the context has a set of variables called attributes. The primary purpose of the context is to hold these variables in memory and provide them to whoever wants them. Let's define a context for our application called claim_app_ctx. Begin dbms_session.set_context( namespace => 'claim_app_ctx', attribute => 'analyst_role', value => 'senior' ) end; Note, executing the above SQL will return an error, the reason for which we will see in a moment.
Next, we will define a procedure to set the various attributes of the context as follows: The procedure will be created, but if it is executed, an error will be returned. Managing Contexts. Dave’s Adventures in Business Intelligence » Universe Design. I had a question from a business user the other day.
I was confident that I knew the answer as soon as I saw the first part of her question. To be sure, I waited until we got through the entire discussion. Her question started off with: I am doing date math — using nvl to set a date to jan 01 2099 when it is null… Right at that point I could have made good money by betting that she was getting a “non-numeric character was found where a numeric…” message. What’s wrong with that? Oracle Implied Conversions The problem is that if I don’t specifically tell Oracle how I want my string to be converted to a date, then it will make a guess. The way I have generally solved this is to remove any guessing from the process by explicitly defining my date format.
Now my string is converted to a date using my supplied format mask, and the dreaded “non-numeric found…” message can be avoided. Universe Development. Lately, I’ve seen a lot of heartache over universe Lists of Values (LOV).
Lists of Values can be a great benefit to users, as well as your worst nightmare for developers and DBAs. So, I thought it might be handy to document some of the best practices for keeping your LOVs user friendly and performing well. Let’s start by going over the various options for LOVs, just so we have a good understanding of what is available, and what makes sense.
There are two times when a user may see a list of values for an object. When they are building a filter in a query, based on a universe object, they may want to choose values for the filter from a List of Values. In Information Design Tool (IDT) LOVs can be created in the Data Foundation or in the Business Layer, as standalone objects. If you create the LOV in the Business Layer, you can use that LOV with any object in that Business Layer only. Associate a List of Values This check box determines if the object will have a List of Values. Category Archives: Semantic Layer.