About Hierarchical dimension

Hi experts
I have some doubts about hierarchical dimension (only obiee 11g)
I've a dimension with some levels:
+Total
---+Level1a
---+Level1b
-------Level2b.1
-------Level2b.2
----+Level1c
My first question is how to begin my report with childs of "Total". I get this in selection steps pane and choose all elements of level1. Obiee shows me hardcoded so...if in the future there is new members on level1 I will not see it... I need a function like "childs of Total".
Second question: I want to apply a different Conditional format depending level of hierarchy and I have to choose all members hardcoded...not "childs of"
Any help about it??
Thanks!

Hi Alex,
I need a function like "childs of Total".In Selection steps, start with all members, in step 2, click on New Step-> "Select members Based on Hierarchy" ->In the pop up Action select "Keep Only Members of" -> select all the levels except Total. This will display the report with all child s of total
I want to apply a different Conditional format depending level of hierarchy and I have to choose all members hardcoded...not "child of"Possible.In Criteria tab, click on + icon to display all the levels.If you want to apply conditional format at Level 2 ->Click on Hierarchy Level Properties of Level 2->Conditional Format->Add condition->select your hierarchy column->In the filter click on Search ->In "At Level" drop down select "Level 2" and click on Search-> This will display all the members at level 2->Move the members to the right pane->OK and apply formatting.
Regards,
Dpka

Similar Messages

Detailed analysis about the dimension tables of a cube

Hi Experts,
how can I get a detailed analysis about the dimension tables of a cube? (E.g. how many records include the fact tables, dimension tables and how much percent are these records compared with the whole records of the cube?!)
Thx in advance for your answers!

Hi,
You will get most of the information in LISTSCHEMA transaction code. If you want to see further you can see the records in SE11.
Regards
Githen

How to .... create a hierarchical dimension in ODI?

What are the steps to create a hierarchical dimension in ODI? For example: Employee dimension with 3 levels: L1, L2, L3 (will include SID, ID, ...)
Any suggestions are appreciated !

Hi,
Specify your PROJECT CODE while calling the variable.
In your case
ArchiveFolder variable =#<YOUR_PROJECT_CODE>.RootFolder\Archive
If RootFolder variable is a GLOBAL variable then
ArchiveFolder variable =#GLOBAL.RootFolder\Archive
Thanks,
Sutirtha

Creating Hierarchical Dimensions - OEID 3.0

Does anyone have an example of a graph that can be used to create hierarchical dimensions? For example, if I want to create an organizational structure like this:
Organizational Unit 1..N
Organizational Division 1..N
Organizational Department 1..N
Organizational Section 1..N
Employee A
Employee B
Where each layer is it's own attribute field in the data set:
Tier1,Tier2,Tier3,Tier4,Tier5
Organizational Unit 1,Organizational Division 1,Organizational Department 1,Organizational Section 1,Employee A
Is this possible?
Thanks

Hi Patrick,
Thanks for your response. I did try and follow the Load Managed Values graph as shown in the Integrator User's Guide, however it seemed to create a multi-valued Component attribute instead of a tiered structure as shown above. That's why I wanted to know if there were any other examples around that creates the tiered structure as I've seen it mentioned theoretically in the guides but never implemented.
Thanks!
Rachel

Creating hierarchical dimension for products

I have to customize the hierarchical dimension id generation using property accessor for products. OOB category-dim-output-config.xml includes the definition to generate the hierarchical dimension ids till category, using custom property accessor I'm able to create the dimension ids for categories.
My Endeca application needs the hierarchical dimension ids till product hierarchy, so I have added the following <item /> definition for child product.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE item PUBLIC "-//Art Technology Group, Inc.//DTD Repository Ouput Specifier 1.0//EN" "http://www.atg.com/dtds/search/indexing-dependency-schema.dtd">
<item item-descriptor-name="category" xml-combine="replace">
<title property-name="displayName"/>
<meta-properties>
<property name="dimval.spec" type="string" property-accessor="/atg/commerce/endeca/index/accessor/MyCustomDimensionIdGenerator" output-name="dimval.spec" is-non-repository-property="true"/>
<property name="$url" suppress="true"/>
<property name="$baseUrl" suppress="true"/>
<property name="$siteId" output-name="dimval.prop.category.siteId" filter="/atg/commerce/endeca/index/ConcatFilter"/>
<property name="rootCatalogId" property-accessor="/atg/commerce/endeca/index/accessor/RootCatalogPropertyAccessor" output-name="dimval.prop.category.rootCatalogId" is-non-repository-property="true"/>
<property name="ancestorCatalogIds" property-accessor="/atg/commerce/endeca/index/accessor/AncestorCatalogsPropertyAccessor" output-name="dimval.prop.category.ancestorCatalogIds" is-non-repository-property="true"/>
<property name="$repository.repositoryName" suppress="true"/>
<property name="$itemDescriptor.itemDescriptorName" suppress="true"/>
<property name="dimval.dimension_spec" default-value="product.parentNode.id" type="string" property-accessor="/atg/commerce/endeca/index/accessor/DimensionSpecPropertyAccessor" output-name="dimval.dimension_spec" is-non-repository-property="true"/>
<property name="dimval.parent_spec" type="string" output-name="dimval.parent_spec" property-accessor="/atg/commerce/endeca/index/accessor/ParentSpecPropertyAccessor" is-non-repository-property="true"/>
<property name="dimval.display_order" type="integer" output-name="dimval.display_order" property-accessor="/atg/commerce/endeca/index/accessor/DisplayOrderPropertyAccessor" is-non-repository-property="true"/>
<property name="$repositoryId" output-name="dimval.prop.category.repositoryId"/> 
</meta-properties>
<text-properties>
<property name="displayName" output-name="dimval.display_name"/>

<property name="keywords" suppress="true" filter="concat"/>
</text-properties>
<item property-name="parentCategoriesForCatalog">
<meta-properties>
<property name="$repositoryId" suppress="true"/>
<property name="$repository.repositoryName" suppress="true"/>
<property name="$itemDescriptor.itemDescriptorName" type="string" suppress="true" filter="unique"/>
</meta-properties>
<monitor>

<property name="$repositoryId"/>
</monitor>
</item>
<item property-name="parentCatalog">
<meta-properties>
<property name="$repositoryId" suppress="true"/>
<property name="$repository.repositoryName" suppress="true"/>
<property name="$itemDescriptor.itemDescriptorName" suppress="true"/>
</meta-properties>
<monitor>

<property name="$repositoryId"/>
</monitor>
</item>
<item is-multi="true" property-name="catalogs">
<meta-properties>
<property name="$repositoryId" output-name="dimval.prop.category.catalogs.repositoryId" filter="/atg/commerce/endeca/index/ConcatFilter"/>
<property name="$repository.repositoryName" suppress="true"/>
<property name="$itemDescriptor.itemDescriptorName" suppress="true"/>
</meta-properties>
</item>
<item is-multi="true" property-name="childProducts" is-document="true">
<meta-properties>
<property name="$repositoryId" output-name="dimval.prop.category.childProduct.repositoryId"/>
<property name="$repository.repositoryName" suppress="true"/>
<property name="$itemDescriptor.itemDescriptorName" suppress="true"/>
</meta-properties>
<monitor>

<property name="$repositoryId"/>
</monitor>
</item>
</item>
This is generating the dimension id for categories only but not for products as I have added "dimval_spec" at category level. I i add the "dimval_spec" property in product item then product record includes two "dimval_spec" property values. Actually a record should have only one "dimval_spec" property and its value.
My queries are "
1) does the definition file I have defined is correct?
1) How can I have only one dimension id property in the definition xml for both category and product, so that each record will contain only one dimension id?
Appreciate the help if any one has worked on this and provide some guidance ... !

Hi,
There is as no thmb rule for it. Generally we try to balance the dimension when we create them. For example, It is not advisable to include Material and Vendor in a single dimension.(otherwise it will lead to dimension explosion...large no. of records in a single dimension.)
The idea of dimension tables is to group associated characteristics to reduce the number of fields in the fact table and to reduce redundancies in storing frequent combinations of
characteristics values in a table. Examples of characteristics typically grouped into one dimension include Customer, Customer Group, and Zip Code grouped into a Customer
dimension, and Material, Material Group, Color grouped into a Material dimension.
A special case of a dimension is the line-item dimension, which is used for characteristics with a very high cardinality. Atypical example is the document number in a lineitem-
level InfoCube.
Regards,
Gunjan.

Creating hierarchical dimension for products in ATG - Endeca integration

Hi,
I need to generate the hierarchical dimensions till product hierarchy, OOB feature creates the dimension till category hierarchy.
If anyone has worked or have idea on this, please provide the steps to be followed and the sample category-din-output-config.xml to generate hierarchical dimension till products.
Regards,
Sudheer

Are you planning to create articles in ExpManager OR the content will come from some other system and you just want to manage the pages to display the content in Exp Manager?
On a high level:
If it is case #1 you have to integrate ATG & Endeca and write some cartridges for managing the content.
If it is case #2 you have to integrate ATG & Endeca and modify the auto generated pipeline to pull in your content from the other system.
Pankaj.

Loading hierarchical dimension in planning

Hi,
I'm trying to load an Account dimension in Planning..
It is a flat table with the following levels. The table basically created P&l and balance sheet hierarchies..
L1 L2 L3 L4 ACCOUNTID ACCOUNTDESC
Do I need to convert this table in parent child format before loading it using ODI?
If not how do I load it in a flat format using ODI..
Any same query for converting it in parent child format will be helpful..
Any responses will be much appreciated!!

A simple way would be to have multiple loads L1, L2 then L2, L3..... or load the file into a table and create a view on it.
Cheers
John
http://john-goodwin.blogspot.com/

Drilling, Hierarchies, Dimensions, AWM

Hi,
I'm new to OLAP, cubes, star schemas...
I'm using Analytic Workspace Manager Version 10.2.0.1.0.
Is it possible to drill down without creating hierachies ?
Once hierarchies are created and i want to do the mapping, it seems that every level needs to have a key, am I wrong ?
Therefore, if I take a Time table that I have to map, I should have this king of physical structure :
year_id, year_desc,
quarter_id, quarter_desc,
month_id, month_desc.
Another example, if I have a Product table, I should have this kind of physical structure :
product_id, product_desc,
category_id, category_desc...
Thank you for your help.

The dimension members have to be unique in OLAP.
You can concatenate level id with the dimension member to make dimension members unique at each level of OLAP dimension. This is a common practice.
Lets say one row in your relational TIME dimension table is:
year_id = 1
year_desc = '2011'
quarter_id = 1
quarter_desc = 'Q1-2011'
month_id = 1
month_desc = 'Jan-2011'
and you level ids in olap are defined as 'YR_LVL', 'QTR_LVL', MTH_LVL'
This can be loaded into your OLAP time dimension as 3 time dimension members:
time = 'YR_LVL_1'
time_long_description = '2011'
time = 'QTR_LVL_1'
time_long_description = 'Q1-2011'
time = 'MTH_LVL_1'
time_long_description = 'Jan-2011'
You can either do the concatenation setting in OLAP time dimension definition in AWM (without making any change in relational table or view)
or in your source sql view that is "mapped" to OLAP time dimension.

About Hierarchical Header in ALV

hi, all
How can i set the hierarchical header in alv?
Thanks for your help!

hi, all
If you think about this problem, can you tell me the answer?
Thank you very much!

Question about Create Dimension

Good morning,
I am reading the Oracle Concepts document and on page 4-22 it presents a "CREATE DIMENSION" statement used to create the "customers_dim" dimension in the sample schema SH.
The statement presented is:
CREATE DIMENSION customers_dim
   LEVEL customer IS (customers.cust_id)
   LEVEL city IS (customers.cust_city)
   LEVEL state IS (customers.cust_state_province)
   LEVEL country IS (countries.country_id)
   LEVEL subregion IS (countries.country_subregion)
   LEVEL region IS (countries.country_region)
   HIERARCHY geog_rollup (
     customer CHILD OF
     city CHILD OF
     state CHILD OF
     country CHILD OF
     subregion CHILD OF
     region
JOIN KEY (customers.country_id) REFERENCES country )
ATTRIBUTE customer DETERMINES
    (cust_first_name, cust_last_name, cust_gender,
    cust_marital_status, cust_year_of_birth,
    cust_income_level, cust_credit_limit)
ATTRIBUTE country DETERMINES (countries.country_name);When I issued the above statement (verbatim from the document), I got the following error:
SQL> @customers_dim
LEVEL customer IS (customers.cust_id)
ERROR at line 2:
ORA-30371: column cannot define a level in more than one dimensionI found the following using Google:
Cause:     A column was used in the definition of a level after it had already
        been used to define a level in a different dimension.But, I don't see how the cust_id is defining a level in more than one dimension. There is probably a trivial error someplace but, I don't know enough yet about dimensions to figure it out.
Help is appreciated, thank you,
John.

SB and Hoek,
Thank you both. :)
I will give Dion Cho's version in PL/SQL a try :)
For those that might be interested, Dion Cho posted this link:
http://yong321.freeshell.org/freeware/Windowsoerr.htmlwhere you can get the *nix version which is a perl script. If you are on Windows and don't want to depend on perl and/or CIGWIN, the script can be compiled using perl2exe (as Yong Huang - the author - suggests on his web page).

Question about the dimensions of a multiprovider

Hi all,
I need to create a multiprovider based on 2 infocubes. They have 22 dimensions altogether, without taking the default ones in account.
I'm able to group 6 dimensions into 2 because they have characteristics in common, but after this action there will still be 16 dimensions.
My question is: is there any problem in putting unrelated dimensions together? Would there be some problem related to the multiprovider design?
Thanks and regards,
Tiago.

HI,
This mainly depends on the reporting requirements you have. If you want to do better on the reporting performance since the requirement is on the two cube with more number of characteristics. While design the cube take only those char which are useful for reporting. Group the char in dimension as per the reportign requirements like the two char collectively used in a query can be used in one dimension.
assigning dimensions in a multiprovider
Use of Dimensions in Multiprovider?
http://help.sap.com/saphelp_nw70/helpdata/en/52/1ddc37a3f57a07e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/cf/bc734190ba137de10000000a155106/frameset.htm
Tarak

Question about extending dimension and fact tables

We have our data warehouse completely loaded with several years of historical data. We now want to extend one of our dimension tables by performing a type 1 customization to add an additional column to that dimension table.
Is there a way for the ETL to update all of the historical records in the dimension table by filling in the data for the new column? Assume that we made the necessary changes in the database and updated the ETL mapping accordingly. We want to avoid having to truncate the table or doing a full load again -- even just for that table and the corresponding facts.

Remove the last refresh date for the table in the DAC repository...that will force an ujpdate of the whole table without you needing to reload everything.
Oh yeah and you're in the wrong forum: Business Intelligence Applications
C.

Hierarchical Dimension with a leaf node w/o any parent

Hi
We have a Product Dimension with five levels L0, L1, L2, L3 and L4 (L0-lowestlevel, L4-HighestLevel).
With one Hierarchy STANDARD as
L4, NULL (Parent)
L3, L4 (L4 is the parent of L3)
L2, L3
L1, L2
L0, L1 (L1 is the parent of L0)
The product dimension table has a record with values only for L0 and NULL values for other Levels..
(ie) We have a requirement to create a value in L0 which will have no parents.. The rest of the values in L0 will have parents.
Would like to know if this is possible in AW. This was possible in Express Server
regards
uma

HI
yes we have run into a big problem. We have created leaf nodes w/o parent in aw and created relational views of those. The measure views thus created has data for these dimension values but when accessed thru BI Beans (ie in the cross-tab if we have this measure) the data is not getting displayed for these dimension values (Which do not have parent)
Any immediate response will be of greate help to us.

Hierarchical dimension column

Hi All,
Even though I have placed hiearchial dimension column in the first order in presentation table . In obiee answer, it shows last after all the presentation columns. Is there a way to change the sort order so it will be seen on the top of other presentation columns?
Thanks,
Vishal

Ok, this one is on me. The reason for this behaviour is:
The country field has a sort field defined, but (we are still in development) this is allways zero, therefore OBI sorts by zero and assumes, the column is sorted now...

About Hierarchies and Drill Up/Down

Hi Forum !!
I need some light about this topic. I have a Materialized view that holds some calculations for me in this way:
MY_M_VIEW:
Date_of_year (Is a date)
CITY
ENTITY (Is the name of an entity)
CATEGORY (Name of a category)
SUBCATEGORY (Name of a Subcategory)
INDICATOR (Name of an Indicator)
SCORE (Is a numeric measure)
TYPE_SCORE(Is a flag for the score)
For each Entity are many Categories, for each Category are many Subcategories, and for each Subcategory are many Indicators.
The score for Indicator is a number calculated in view's sql definition. The score for each subcategory is the average of the indicator's score belonging to the subcategory. The score for category is a sum of each subcategory's score by N (N is a number obtained by view's definition) SUM(score*N). The score for entity is a sum for each category's score by M (M is a number obtained by view's definition) SUM(score*M).
TYPE_SCORE is 'ENT' when holds an entity's score, 'CAT' for a category's score, 'SUB' for a subcategory's score and 'IND' for an Indicator's score.
Some records in MY_M_VIEW looks as follows:
Date_of_year; CITY; ENTITY; CATEGORY; SUBCATEGORY; INDICATOR; SCORE; TYPE_SCORE
01/01/2006; 'CITY 1'; 'Entity 1'; null; null; null; 1.2; 'ENT'
01/01/2006; 'CITY 1'; 'Entity 1'; 'Category1'; null; null; 2.3; 'CAT'
01/01/2006; 'CITY 1'; 'Entity 1'; 'Category1'; 'Subcategory 1'; null; 1.9; 'SUB'
01/01/2006; 'CITY 1'; 'Entity 1'; 'Category1'; 'Subcategory 1'; Indicator 1'; 2; 'IND'
01/01/2006; 'CITY 1'; 'Entity 1'; 'Category1'; 'Subcategory 1'; Indicator 2'; 0; 'IND'
I need a Crosstab report in Discoverer Plus using a Hierarchy composed by entity, category, subcategory and Indicator (Hierarchy builded in Disc. Administrator), looking like this (Date_of_year is a Page item):
   DataPoint: SCORE
ENTITY
    CATEGORY
       SUBCATEGORY
           INDICATOR
CITY            score
Keeping in Mind the discoverer's way for aggregations, How can I implement a correct Drill Down, Drill Up behavior for such a crosstab ?

Hi Arun
Find the above text - 3DDRILL_TO_LEVEL%26LEVEL%3D2 & replace it with text below
3DDRILL_TO_LEVEL%26LEVEL%3D3. this will unable you to drilldown to third node. Like wise you enter the number after "%3D_" to get required level of drill down.
I hope this will work,
regards
Sandeep

About Hierarchical dimension

Similar Messages

Maybe you are looking for