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...

Similar Messages

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

Hiding a dimension column in report

Hi,
I want to use a dimension column in criteria with other columns. But i dont want to display it in the results. How can i hide this particular column in result.
Please suggest.

I got it.
It is availabe in column properties->column format->Hide.
Thanks.

Selecting Dimension Columns withut a Fact

I have multiple dimension tables that are shared among my multiple fact tables. I believe this is very common. My problem is that when I select a dimension column from two different dimension tables, without picking a fact table, I have no control over which fact table is used to create the join between the two dimension tables. This create some interesting results unless a fact is chosen.
For example. If we have 2 fact tables and two dimension tables D1, D2, F1, F2 where the following joins exist
D1 -> F1
D1 -> F2
D2 -> F1
D2 -> F2
If I select a value from D1 and a value from D2 without selecting a value from either fact table, then how can I control which fact table the join is performed on? Or is it common that the users should need to specify a fact? I can not let obi use the fact tables to get the values because they may not always be correct. I am using outer joins from the dimensions to the facts so that all values show up even if no fact exists. Hence the reason I need to use the dimensions. Any help is greatly appreciated.

When you are working with the aggregate fact tables the content of the dimensional levels should take care which fact table it hits based on the query selection.
How ever if it is everything at the detail level and you still need to control the fact and then You should be able to control it using the "Impilicit Fact Column" option in the Presentation layer
Right click on the Presentation catalog go to properties and it will allow you to set a Fact column there.
Hope it helps
Thanks
Prash

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

Missing Standard Dimension Column for data load (MSSQL to Essbase Data)

This is similar error to one posted by Sravan -- however I'm sure I have all dimensions covered -- going from MS SQL to SunOpsys Staging to Essbase. It is telling me missing standard dimension, however I have all accounted for:
org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last): File "<string>", line 23, in ? com.hyperion.odi.essbase.ODIEssbaseException: Missing standard dimension column for data load
at com.hyperion.odi.essbase.ODIEssbaseDataWriter.loadData(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
I'm using multiple time period inputs -- BegBalance,Jul,Aug,Sep,Oct,Nov,Dec,Jan,Feb,Mar,Apr,May,Jun (target has all of those in place of Time Periods)
I'm using hard coded input mapping for Metric, Scenario, Version, HSP_Rates and Currencies. -> 'Amount', 'Actual', 'Final', 'HSP_InputValue','Local' respectively.
The only thing I can think of is that since I'm loading to each of the months in the Time Periods dimension (the reversal was set up to accomodate that)... and now its somehow still looking for that? Time Periods as a dimension does not show up in the reversal -- only the individual months named above.
Any ideas on this one??

John -- I extracted the data to a file and created a data load rule in Essbase to load the data. All dimensions present and accounted for (five header items as similar here) and everything loads fine.
So not sure what else is wrong -- still getting the missing dimension error.
Any other thoughts?? Here's the entire error message. Thanks for all your help on this.
org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 23, in ?
com.hyperion.odi.essbase.ODIEssbaseException: Missing standard dimension column for data load
     at com.hyperion.odi.essbase.ODIEssbaseDataWriter.loadData(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)
     at org.python.core.PyMethod.__call__(PyMethod.java)
     at org.python.core.PyObject.__call__(PyObject.java)
     at org.python.core.PyInstance.invoke(PyInstance.java)
     at org.python.pycode._pyx8.f$0(<string>:23)
     at org.python.pycode._pyx8.call_function(<string>)
     at org.python.core.PyTableCode.call(PyTableCode.java)
     at org.python.core.PyCode.call(PyCode.java)
     at org.python.core.Py.runCode(Py.java)
     at org.python.core.Py.exec(Py.java)
     at org.python.util.PythonInterpreter.exec(PythonInterpreter.java)
     at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)
     at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.k(e.java)
     at com.sunopsis.dwg.cmd.g.A(g.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)
Caused by: com.hyperion.odi.essbase.ODIEssbaseException: Missing standard dimension column for data load
     at com.hyperion.odi.essbase.ODIEssbaseDataWriter.validateColumns(Unknown Source)
     ... 32 more
com.hyperion.odi.essbase.ODIEssbaseException: com.hyperion.odi.essbase.ODIEssbaseException: Missing standard dimension column for data load
     at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
     at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.k(e.java)
     at com.sunopsis.dwg.cmd.g.A(g.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)

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.

Showing Multiple dimension columns in same report

We need to show revenue data in one report (pivot table) with column headings as Month, Qtr and Year coming from the same dimension.
The Report should be like,
Jul Aug Sep Q3-2007 2007
Revenue
We are able to create separate views for month, year and quarter in the same report but we need all of them to show up in one line in the same view. If we create 3 separate views then they are not correctly aligned on the dashboard page. Can we create a single view using these columns.
Any suggestions on how to solve this?
Thanks.

use min(month), min(month)+1 , max(month) , quarter, year at qurter level report

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/

Finder - Image Dimensions column

Hi I have thousands of files I am organizing and want the image dimensions in column view. You can do this on windows 95 how come not Mac OS X (which I love)!??
Can somebody tell me how to do this - it would be a lot of help!
Thanks

Alas you cannot have it ALL ways...
Column view is basically a cleaner version of List view - without any of the file information visible at a glance. If you click any item shown in column view - the preview to the right should show the dimensions at the bottom, along with other data.
If you want to see all of the dimensions at a glance, you can set them in Icon View. I have the View Options for all of my folders that are full of images (which is the bulk of my folders, as I am a designer) set as below.
Double-click on the folder containing the images
Click on the Icon View thumbnail at the top of the finder window
Go to View / Show View Options
Select "Always open in icon view"
Slide the "Icon size" all the way to the right (to 128 x 128)
Slide the "Grid spacing" all the way to the left (to keep them grouped close together)
Select "*_Show item info_*" (*this is what you are after*)
Select "Show icon preview" (if this is not selected)
Select an option in "Arrange by" (this will sort / arrange them after the changes)
Select "Use as defaults" at the bottom, if you want this to be the default settings for any folder that has been set to Icon View.
This setting shows me everything I need to see quickly, and allows me to bypass the Cover Flow view, which I love - but it is only useful on the odd occasion for two reasons:
1.) It doesn't play friendly with all of my image files, it usually looks horrible (BIG deal breaker!)
2.) If I am looking over a folder FULL of images, I can usually find what I am looking for quicker by using the overview that Icon View allows, rather than flipping though the images one at a time.

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.

Displaying Hierarchies in columns (i.e. across not drill down)

Hi Guys,
My client needs me to display the Organisational Hierarchy and its attribute (manager of each org unit) in columns. i.e. org unit level1, org unit level1 manager, org unit level2, org unit level2 manager, org unit level3, org unit level3 manager,.........
Typically the hierarchies are displayed in rows that is higher node on top and when drill down the subsequent levels underneath it.
Please guys help me out. my client is behind me for this

Hi Raj,
I think we need some clarification what exactly you need.
The standard way of showing hierarchies is to show them in one column with different indents depending on the level of nodes. Another columns are to show key figures.
If you want to show the next level of hierarchy not only in the next row but also in the next column then this is not a standard solution and I'd propose to use VBA coding.
So, the answer depends on your needs.
Best regards,
Eugene

Dimension columns to be displayed in one column

Is there a way to show like "Product Type" and "Product" in ONE column in a report? (displayed as dimension)
where "Product Type" and "Product" are from different levels
Example: The first column in the report should look like this:
Product Type 1
Product 01
Product 02
Product 03
Product Type 2
Product 04
Product 05
Product 06
Thanks
Janne

Hi
one way is like going for union
Other way is: add type, product columns in criteria select list.. go to pivot
I assume product Type is first then product will come next...
Now, apply subtotal on producttype > Before then hide this product type column...
And, to get the same values as the product type there.. instead of "Product type 0 Total"..
click on sigma button then "Format Labels", keep @ in caption field..
Edited by: Kishore Guggilla on Jul 29, 2010 1:18 PM

Hierarchical dimension column

Similar Messages

Maybe you are looking for