|< Day Day Up >||
BusinessObjects allows you to build one particular hierarchy, even if the
In order for the Time feature to be available, the database column and universe Object must be in date format. As an example, use the Island Resorts Marketing (BEACH.UNV) universe, Reservation Date. (Note: similar time objects already exist in this universe, so the following example is for instructional purposes only and not intended to replace the existing time objects.)
Select the object Reservation Date and double-click to bring up the Edit Properties screen.
On the Definition tab, ensure that the Object Type is set to Date.
On the Properties tab, click Automatic Time Hierarchy.
Click OK to close the Automatic Time Hierarchy box and OK again to save the Object changes.
Notice that Designer has created three dimension objects under Reservation Date , shown next. Once you Save and Export the universe, users can access the objects when building a query.
Chapter 19 discusses multidimensional analysis from the user's viewpoint in more depth; however, it is important for you, as the designer, to understand how these new time objects work. When a
SELECT DatePart('YYYY', Reservations.res_date), DatePart('Q', Reservations.res_date), DatePart('M', Reservations.res_date) FROM Reservations
Using an Oracle data source, the SQL appears as
SELECT TO_NUMBER(TO_CHAR(RESERVATIONS.RES_DATE,'YYYY')), TO_NUMBER(TO_CHAR(RESERVATIONS.RES_DATE,'Q')), TO_NUMBER(TO_CHAR(RESERVATIONS.RES_DATE,'MM')) FROM RESERVATIONS
Notice that BusinessObjects is using the same advanced SQL that you learned about in Chapter 10. This poses two main problems: First, if a user
Finally, when users build a query intended for multidimensional analysis, the users can specify a scope of analysis. For example, a user may want to start by analyzing reservations by Year and
My recommendation is to build the Year, Quarter, and Month objects yourself as regular dimension objects.
BusinessObjects has two types of hierarchies:
that are based on the order of the objects within a class, and
that you, as the designer, specify. If you have ordered your objects from largest to smallest
From Designer, open the Test Fashion universe.
From the pull-down menu, select Tools Hierarchies or click the Hierarchies button on the toolbar.
Designer presents you with the list of classes and objects, as shown next. You will first build the drill path for Article. You can add either individual objects or entire classes. Select the Article Lookup class and click Add>>.
Under Custom Hierarchies, expand the Article Lookup class. Organize the objects so that they go from Family Name at the top to Category to Article Name. You can use drag and drop or select the objects and use the Move Up button.
In the drill path, it does not make sense to drill down from Family Name to Family Code, as they are at the same level. Therefore, remove Family Code, Article Code, and Sales Price by selecting each object and clicking Remove. The objects are only removed from the drill path. They still exist as dimension objects for query purposes.
Modify the hierarchy name Article Lookup to Article Name by clicking Article Lookup and typing over the name.
To create a separate hierarchy for the code objects, click New. Enter a hierarchy name Article Code .
So that users do not drill from a name object at one level to a code object at the same level, create two hierarchies, one for name objects and one for code objects.
Under Default Hierarchies, select the two objects Article Code and Family Code and click Add to add them under the new hierarchy Article Code. You may CTRL -click to select noncontiguous objects.
The custom hierarchies should appear as follows:
You can organize the hierarchies in any way that makes business sense. You may choose to follow agreed-upon corporate levels or
Once you begin using custom hierarchies, you must continue to use them for all dimension objects by which users will want to drill. In the
|< Day Day Up >||