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

Similar Messages

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.

How to create Hierarchies for a Dimension?

Hi,
How to create Hierarchies for a Dimension in Multidimensional Models? Could you please suggest some document provides step by step instructions to create Multidimensional Model?
Thanks
M Thiyagarajan

Hi M Thiyagarajan,
connect dimension to first level and after that connect that level to another one and so on. For level - each additional outgoing connection means additional hierarchy.
Philip

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

How to Create a Dimension Table in OBIEE11g

Hello,
Chapter 9, page 221(if pdf) of the Build Repository manual of OBIEE 11g explains following.
Creating Dimensions in Level-Based Hierarchies
After creating a dimension, each dimension can be associated with attributes
(columns) from one or more logical dimension tables and level-based measures from
logical fact tables. After you associate logical columns with a dimension level, the
tables in which these columns exist appear in the Tables tab of the Dimension dialog.
To create a dimension with a level-based hierarchy:
1. In the Business Model and Mapping layer of the Administration Tool, right-click a
business model and select New Object > Logical Dimension > Dimension with
Level-Based Hierarchy.
Note that this option is only available when there is at least one dimension table
that has no dimension associated with it.I am still learning OBIEE, and I can not see the dimension menu item as per point 1 becuse i do not have dimension table associated with it. All I have done at this point is to create logical tables based on few physical tables in physical layer.
How do I create Dimension Tables? using BI Admin tool?
Thanks,R

Hi Rich,
If you are new to Oracle BI, you would better start with the Oracle Learning Library; http://apex.oracle.com/pls/apex/f?p=9830:41:0::NO:RIR:IR_PRODUCT,IR_PRODUCT_SUITE,IR_PRODUCT_COMPONENT,IR_RELEASE,IR_TYPE,IRC_ROWFILTER,IR_FUNCTIONAL_CATEGORY:,BI,,,,,
You create dimensions based on your logical tables. In a plain star-schema you would have one logical fact table and at least one or more logical dimension tabes attached (joined) to the fact table. Just follow the documentation and you would be good to go.
Good Luck,
Daan Bakboord
http://obibb.wordpress.com

Best way to create hierarchies tables

Good morning all,
I wanted to discuss the best practices of creating hierarchies to be consumed by OBIEE. As far as I understand, OBIEE has been optimized to use flattened hierarchies, such as:
ROW_WID CITY COUNTRY
1 NEW YORK CITY USA
2 MOSCOW RUSSIA
3 KIEV UKRAINE
4 SYDNEY AUSTRALIA
5 ATLANTA USA
Let's call it option 1. The only problem with this is that it has a potential to grow very wide. Also, There's a chance for confusion when there're duplicate entries, such as "New York" (city) and "New York State". Also, it's not always possible to define hierarchical relationships between data in a flat table - so-called ragged hierarchies. I found two major way of dealing with those (stack and flattening them out). Are there any other ways to deal with those? Specifically, I'm interested in dealing with hierarchies that involve complex positioning (a person might be a manager vertically, but managed horizontally - or - a person can have 2 managers - on different levels).
Also, in the example above - can I create dimensional outriggers (assign surrogate keys instead of text values to the dim - such as having NEW YORK as 100, MOSCOW as 200)? Sort of snowflaking a dimension. I was asked to do a proof of concept for this - but haven't been successful so far. If yes, could you please provide a simple Dim Outrigger < Dim < Fact diagram.
Thank you

Thanks Peter - I've checked that document before (I believe it's based on Kurt Wolffe's document on Siebel Analytics which I checked as well).
This option is fine if you're not going to do frequent changes - but in my case - it'll be a hell to maintain. We're sort of trying to prototype best solution - and it seems as flattening hierarchies is the best option, of course, given its limitations.
Also, there's another option of taking a different path and splitting and then building separate hierarchies

Can I create a DIMENSION object mappign without a Dimension table?

I understand how I can create a dimension object and it's associated table. However, can I map my enterprise data directly to the dimension object itself and skip the loading of the dimension table? The enterprise data for most of my reporting warehouse for the greater part is fairly simple and requires only joins to some reference data.

Matthew,
Like you stated, the dimension object in OWB will generate scripts for two object types. The first is a dimension object and the second is a table. In the dimension object the hierarchical structure(s) (meta data) is stored and the table stores the data. So you always have to load your enterprise data into the table.
Hope this helps.
With kind regards,
Bas Roelands

Create Hierarchies in BPC

Hi
can anyone let me know how to create Hierarchies in SAP BPC in detail.
Regards
ark

Hi Ark,
Unfortunately, I don't know if any "how to" guides exist for hierarchies. To get a general understanding via BPC 7.0, I recommend going into BPC Administration. Select the ApShell appset, and select Manage Dimensions. Select the P_ACCT dimension. Select "Maintain dimension members". Select "View member report". This will provide you with an indented (hierarchical) view of the accounts.
Basically, hierarchies are created using the PARENTH1 (PARENTH2, PARENTH3, etc.) column. You may have the following IDs in an account dimension:
_ID_
Total_Revenue
Europe_Rev
German_Rev
Americas_Rev
By placing some IDs in the PARENTH1 column, you make those IDs parents and you've created a hierarchy.
_ID_                _PARENTH1_
Total_Revenue
Europe_Rev          Total_Revenue
German_Rev          Europe_Rev
Americas_Rev        Total_Revenue
So in an indented view, you now have the following:
Total_Revenue
Europe_Rev
    German_Rev
Americas_Rev
So German_Rev roles up to Europe_Rev. Both Europe_Rev and Americas_Rev role up to Total_Revenue. In this example, all IDs are roll-up IDs except for German_Rev and Americas_Rev, so only German_Rev and Americas_Rev can be used to input data.
Hopefully that helps.
Thanks,
Scott

Error while creating user dimension in awm

Hi,
I am new to awm. I am trying to create a dimension in my workspace, but i receive an error after i click 'create'. When i check the detailed error, i think its something to do with the OLAP_TABLE. Please find the error message below,
===================================================
Your metadata changes have been saved, with the following errors
Invalid Metadata Objects:
Invalid Object "TAN.TICKERSYMBOL": "CREATE OR REPLACE VIEW "TAN"."TICKERSYMBOL_VIEW" AS    SELECT      "DIM_KEY",      "LEVEL_NAME",      "MEMBER_TYPE",      "DIM_ORDER",      "LONG_DESCRIPTION",      "SHORT_DESCRIPTION"   FROM TABLE(CUBE_TABLE('"TAN"."TICKERSYMBOL"') )
ORA-00902: invalid datatype "
====================================================
Please advise.

Which version of the database (not AWM!) are you using? (e.g. 11.2.0.3)
My guess is that there is a problem with your OLAP installation and that you will need to open a service request to get it resolved. But the following may help us to track down the problem.
alter session set events='902 trace name errorstack';
alter session set tracefile_identifier=OLAP;
SELECT
   "DIM_KEY",
   "LEVEL_NAME",
   "MEMBER_TYPE",
   "DIM_ORDER",
   "LONG_DESCRIPTION",
   "SHORT_DESCRIPTION"
FROM TABLE(CUBE_TABLE('"TAN"."TICKERSYMBOL"') )
Once you have run this (in a single session), look for a trace file containing the word OLAP in its file name. It should contain a stack trace that will tell us where the ORA-00902 is being raised. The trace file will be long, but the interesting part begins like this:
----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
skdstdst()+29        call     kgdsdst()            7FFFADE14590 ? 000000000 ?
                                                   7FFFADDF6E50 ? 7FFFADDF6F68 ?
                                                   7FFFADE14C48 ? 7FFFADE14540 ?
ksedst()+112         call     skdstdst()           7FFFADE14590 ? 000000000 ?
If you can find this, please copy it in reply.

Unable to create logical dimension in bmm layer

Hi all,
I am not able to create a logical dimension hierarchy in the bmm layer of the rpd.
when I right click on the table I am not able to find the create logical dimension option in the popup window.
could you please help me out in this?
In the logical table we have data from sql statement also.
Thanks!

Create Dimensions is only available if the selected logical table is a dimension table (defined by 1:N logical joins) and no dimension has been associated with this table.
To create a dimension automatically, the Administration Tool examines the logical
table sources and the column mappings in those sources and uses the joins between physical tables
in the logical table sources to determine logical levels and level keys.
Hope you have defined the Logical join in BMM before looking for this option. If joins are not defined, this option won't come.
Refer http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf
Page 133, Creating Dimensions Automatically
Hope its useful

Duplicate attribute key found when creating a dimension

Good Afternoon,
I created a cube with dimesnions and all is working fine. I created three dimension ZONE,BLOCK and STREET and these are reltated to the FACT table and all is well. But i was thinking since these 3 dimensions are related and coming from the same table, why
not just create one dimension with ZONE as the primary key and the heirarchy as zone>block>streetname. In the DSV i created a named query.
SELECT DISTINCT ZONE, BLOCK, STREET
FROM dbo.MYTABLE
group by zone,block,street
order by zone,block,street
Please see the sample dataset as well, where when i process the DIMENSION fails with an error that the "Duplicate attribute key was found, column name:Zone, value:1). I know zone and also the other two columns when processed are repeated more than once
and hence this, is there a way to get what i want.
ZONE BLOCK STREET
1 0 Chesapeake
1 0 East Market
1 0 East Maryland
1 0 East Washington
1 0 North Capital
1 0 North Delaware
1 0 North Illinois
1 0 North Meridian
1 0 North Penn
1 0 South Delaware
1 0 South Illinois
1 0 South Meridian
1 0 South Penn
1 0 Virginia
1 0 West Georgia
1 0 West Jackson
1 0 West Market
1 0 West Maryland
1 0 West New York
1 0 West Washington
1 100 East Washington
1 100 East Market
1 100 East Maryland
1 100 East New York
1 100 East Ohio
1 100 East Washington
1 100 North Alabama
1 100 North Capitol
Thanks
SV

Thanks Richard and SS. This is what i did.
1) In the DSV i created a new named query, the same one i used.
2) Set Primary Key on Street.
3) Created a dimension STG_ZBS_DIM and while creating the heirarchy , i draged and dropped the fileds in the following order (zone>block>street).
4) Tired to process , but getting the same error, except this time at the street level.
What else i did was changed the primary key back to Zone, went into the attribute relations and set the relation from Zone to Block and then Block to Street, saved and processed and this time i got the error at the block level :-(
Thanks
SV

How do you create hierarchical folders in Forms Central to organize and manage multiple forms?

How do you create hierarchical folders in Forms Central to organize and manage multiple forms?

Hi,
We do not support this feature right now. Someone else has posted this to our ideas forum, here - http://forums.adobe.com/ideas/1587. I suggest you vote for it, because we look at the popular ideas to help guide us on what new features work on.
Thanks,
Todd

Can We Create Custom Dimension ontop of BI Infocube

Hello Guys,
I need help on below questions. i appreciate all your help in advance.
Can we create Custom Dimension ontop of SAP BI Infocube ? Does it support all functions like SQL and ORACLE database supports ? Can any body have list what kind of function it supports ? Does it support If..else ..if condition ??
Ex. If Account = 410000 and Profit center inlist 100,200,500,999 Then u201CSales Revenueu201D else ifu2026.etc., Can we write this kind of condition in Universe on top of SAP BI Infocube ?
Regards,
Komik Shah

Hi,
here are some examples of what you can create:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0a45246-ce76-2b10-e688-f5c8206203eb
Ingo

How to create hierarchies in Bex queries?

Hi All,
I am new to query designer tool,
can you please help me how to create hierarchies in Bex queries using query designer tool?
Thanks in advance...

Hi,
directly you can't create hierarchy at bex level.
First you have to maintain hierarchy data source at source or bw side, based on your needs.
Later you can load data to hierarchy, after that at bex level you can activate hierarchy options to related info object properties.
To maintain hierarchy we need to enable hierarchy options at related info object(RSD1, hierarchy tab, select with hierarchies) maintenance level.
For example: info object - 0GL_ACCOUNT and you need hierarchy structure on gl account.
For that we need to have hierarchy data source and will load data from ecc.
Later we can develop reports on gl account in hierarchy fashion.
On what object infoo bject you want create hierarchy report and have loaded hierarchy data?
Thanks

Creating Hierarchical Dimensions - OEID 3.0

Similar Messages

Maybe you are looking for