Bookshelf Home | Contents | Index | PDF |
Siebel Business Analytics Server Administration Guide > Creating and Administering the Physical Layer in a Repository > Creating and Setting Up Physical Tables > Setting Up Hierarchies in the Physical Layer for a Multidimensional Data SourceThe following are some guidelines to follow when setting up hierarchies in the Physical layer.
To create and maintain hierarchies in the Physical Layer, perform the following tasks:
Adding a Hierarchy to a Physical Cube TableEach level in a hierarchy has a level key. The first cube column associated with (added to) the level of a hierarchy is the level key. This must match with the data source definition of the cube. The data source cube table cannot set one column as a level key and the Siebel Business Analytics physical layer table set a different column as a level key. The icon for the column that you select first changes to the key icon after it is associated with the level of a hierarchy. When you select columns to include in a hierarchy, it is recommended that you select them in hierarchical order, starting with the highest level. After adding columns to the hierarchy, you can change the sequence. If you select multiple columns and bring them into the hierarchy at the same time, the order of the selected group of columns remains the same. You can change the order of the columns in the Browse dialog box. If a member of a hierarchy is not explicitly referred to in a query, a default member must be used. Therefore, every hierarchy is associated with a default member, typically the ALL member. The Hierarchy dialog box contains a check box (Default member type ALL) that you use when you want to designate the ALL member as the default. The following list contains some guidelines about selecting the check box:
To add a hierarchy to a physical cube table
Verifying Hierarchy LevelsIt is strongly recommended that after setting up a hierarchy containing more than one level, you should verify the order of the levels in a hierarchy. To verify the levels in a hierarchy
Adding or Removing a Cube Column in an Existing HierarchyAfter setting up a hierarchy you may need to add or remove a column. You might want to remove a hierarchy if it has been built incorrectly and you want to start over. If you remove a cube column from a hierarchy, it is deleted from the hierarchy but remains in the cube table and is available for selection to add to other levels. To add a cube column to or remove a cube column from an existing hierarchy
Removing a Hierarchy from a Physical Cube TableYou might want to remove a hierarchy if it has been built incorrectly and you want to start over or to remove objects that are not accessed. Perhaps the business model does not reference any of the elements in that hierarchy. For example, you import an entire physical multidimensional schema and only want to keep parts of it in the business model. NOTE: When you delete a hierarchy in the Physical layer, you remove the hierarchy and the columns that are part of the hierarchy. This is different from deleting a hierarchy in the Business Model and Mapping layer. To remove a hierarchy from a physical cube table
Associating a Physical Cube Column with a Hierarchy LevelAttributes are used in the physical layer to represent columns that only exist at a particular level of a hierarchy. For example, if Population is an attribute that is associated with the level State in the Geography hierarchy, when you query for Population you are implicitly asking for data that is at the State level in the hierarchy. There can be zero or more attributes associated with a level. The first physical cube column that is associated with a level becomes the level key. If you associate subsequent columns with a level, they become attributes, not level keys. Example of Associating a Physical Cube Column with a HierarchyYou have a level called State and you want to associate a column called Population with this level.
|
Siebel Business Analytics Server Administration Guide |