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

Similar Messages

How to create a Time Dimension

Hi
This is regarding a new topic which i could not find the answer in this forum.
Actually i want to create a time dimension to populate my source data which is in date/time format.
can anyone please reply back reagrding how to create a time dimension in ODI???
regards
Gourisankar

Hi Gourisankar,
I am not aware of time dimension. But when i searched in metalink i got the below note. I am not sure whether it will help you or not but still a small contribution. :)
The note as follows,
To create new time dimensions, run the following SQL instructions :
* Example to generate a calendar between 1999-01-01 and 2007-12-31 one row per day
SELECT to_date('1999-01-01','YYYY-MM-DD')+rownum
FROM DUAL
CONNECT BY
ROWNUM<=to_date('2007-12-31','YYYY-MM-DD')-to_date('1999-01-01','YYYY- MM-DD');
* Example for generating a calendar random number
SELECT DBMS_RANDOM.VALUE
FROM DUAL
CONNECT BY ROWNUM<=1000000;
May be you can create a VIEW out of this query ,reverse it and use that as a source in your interface.
Try this and let me know.
Thanks,
G
Edited by: Gurusank on Dec 22, 2008 4:19 PM

How to create an attribute dimension in Essbase Studio?

I cannot figure out how to create an attribute dimension using Essbase Studio. The online help states that I need to "Find the Attribute settings grouping in the center" of the member properties dialog box. I suspect that I'm having a problem figuring this out because I don't have the attribute dimension properly defined in the relational data source or in the mini-schema. I've tried creating a table with no key relationship to the other tables and with no logical joins defined, but that doesn't seem to help. Any ideas?

so in the 11.1.1 version you would click on the member name in the hierarchy you added to the Essbase model and in the center pane of the general tab should be the attributes settings section.
If I had a dimension called stores wth two groupings unser it region and store_type, I would click on store_type and add the attribute info

How to create set hierarchies from FI SL.

Hi Experts,
How to create set hierarchies from FI SL. Could you please tell me
Step by step procedures or send to this mail id [email protected]
Thanks
Regards,
Sathis.J

Hi,
FI-SL
http://help.sap.com/saphelp_nw2004s/helpdata/en/28/5ccfbb45b01140a3b59298c267604f/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/41/65be27836d300ae10000000a114b54/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ee/cd143c5db89b00e10000000a114084/frameset.htm
Hope This Helps.
Thanks,
Sankar M

How to create a Double dimension array dynamically

Hello,
If I have the following code running...
String[][] str = new String[1][3];
str[0]0] = "AAA";
str[0][1] = "BBB";
str[0][2] = "CCC";
I want to do the same code using runtime object creation. i.e.
String class_name = "java.lang.String";
How will I write the above mentioned code without using the hard code String class, i.e. I have to use class_name instead of "String".
Please help me.
Thanks in advance,
Anmol

Thanks Drake,
I got the solution i.e.
String class_name = "java.lang.String";
String ele_type = "java.lang.String";
int ele_size = 3;
String s1 = new String("AAA");
String s2 = new String("BBB");
String s3 = new String("CCC");
ArrayList ar = new ArrayList();
ar.add(s1);
ar.add(s2);
ar.add(s3);
Object base_obj = java.lang.reflect.Array.newInstance(Class.forName(class_name), new int[]{1,ele_size});
Object child_obj = java.lang.reflect.Array.newInstance(Class.forName(ele_type), ele_size);
for(int i=0;i<ele_size;i++){
Array.set(child_obj, i, ar.get(i));
Array.set(base_obj,0,child_obj);
// base_obj object is same as str shown in the above code
Thanks,
Anmol

Creating a DWMQY DIMENSION using Analytic Workspace Manager

Hi everyone,
I need some help creating a "time aware" (DAY, WEEK, MONTH, QUARTER, and YEAR) dimension using Analytic Workspace Manager.
Let me give you some background. I'm coming from a traditional "Oracle Express" OLAP background where all our data is stored in cubes and these are defined, populated and operated on using OLAP DML, there is no SQL or traditional relational tables involved.
I now want to pull data from relational tables into some OLAP cubes and am using Analytic Workspace Manager to do this (maybe this is not the best way?)
Let me explain what I'm trying to achieve. In OLAP worksheet I can type the following DML commands:
DEFINE MY_DAY DIMENSION DAY
MAINTAIN MY_DAY ADD TODAY '01JAN2011'
What this will do is create a "day dimension" and will populate it with values for each and every day between 1st Jan 2011 and today. It will be fully "time aware" and thus you can use date functions such as DAYOF to limit the MY_DAY dimension to all the Fridays etc. Similarly if I define a "month dimension" there will be an automatic implicit relationship between these two dimensions, this relationship and time aware cleverness is built into Oracle.
However, a dimension defined using DML commands (and indeed all objects created using DML language) is not visible in Analytic Workspace Manager (as there is no metadata for them?) and for the life of me I cannot work out how to create such a dimension using AWM. If I create a "Time Dimension" then, as far as I can tell, this is not a proper time dimension but merely a text dimension and I, presume, I have to teach it time awareness.
Can anyone help me? I have no issues creating, and populating cubes from relational tables using Analytic Workspace Manager, the only issue I have is creating a "proper" time aware dimension.
Many thanks in anticipation.
Ian.

When a dimension is of type "TIME" in AWM, then for each member of that dimension, you need END_DATE and TIMESPAN attributes in addition to the key column and description column.
So in your case, if there are 5 levels: DAY->WEEK->MONTH->QTR->YEAR
then you will need atleast 15 columns in your source sql table/view
or 20 columns if you have separate column for description.
For example the columns in your source table/view could be:
DAY_ID,
DAY_DESC,
DAY_END_DATE, (which will be that day's date)
DAY_TIMESPAN, (which will be 1)
WEEK_ID,
WEEK_DESC,
WEEK_END_DATE,
WEEK_TIMESPAN,
MONTH_ID,
MONTH_DESC,
MONTH_END_DATE,
MONTH_TIMESPAN,
QTR_ID,
QTR_DESC,
QTR_END_DATE,
QTR_TIMESPAN,
YEAR_ID,
YEAR_DESC,
YEAR_END_DATE,
YEAR_TIMESPAN
Just "map" this table/view to the 5-level time dimension in AWM.
NOTE that behind-the-scenes lot of useful structures are automatically defined to support time-series measures,
and there are lot of calculation templates available also.
Since you came from Express background, I have to say that try to use new OLAP Expression Syntax when creating calculated measures instead of OLAP DML.
Its very rare these days that we need OLAP DML.
Edited by: Nasar on Nov 22, 2012 12:11 PM

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 role-playing Date dimension?

I have created a date dimension Date_Dim with three levels DayL, MonthL, YearL and one hierarchy YearL-Monthy-DayL. In the fact table, I need to refer to two date dimension: Start_Date and End_Date. For the Start_Date, we can refer it to the created physical date dimension Date_Dim. For the End_date, Ralph Kimball recommended to use a role-playing dimension. That is, create a view End_Date_Vw from the dimension table Date_Dim. My question is how to create it in OWB? Should we need to define the levels and hierarchies for the view in order to leverage the query-rewrite power? How to do that? Any advice or information is appreciated.
Lushu

Balaji,
You can refer to the same dimension more than once in the design of a cube (fact table). In a star schema implementation, you just end up with multiple foreign keys to the same times dimension (table). Once you integrate with a reporting tool, you refer to the same dimension using different names. Warehouse Builder supports this in the integration with Oracle Discoverer. The user's guide tells you how to do this (see http://download-west.oracle.com/docs/html/B12146_01/integrating.htm#sthref3659).
Thanks,
Mark.

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.

How to create a custom measure for each level of a dimension

Hi all!
Can Anyone please explain me with an example, how to create a custom measure for each level for a dimension? I dont mine if you use
one or more measures.
thanks in advance
hope someone helps me.

For example:I create a dimension for product_dim witch has 4 levels:total, class, family and item:
d_aben18
n1_aben18
n2_aben18
n3_aben18
n4_aben18
herarchy:h_aben18
cube:cubo_aben18
measure:med_aben18
I create this code to fetch the data to the dimension:
TRAP ON CLEANUP
SQL DECLARE c1 CURSOR FOR SELECT-
total_product_id,1,'N1_ABEN18',total_product_dsc,-
class_id,1,'N2_ABEN18',total_product_id,class_dsc,-
family_id,1,'N3_ABEN18', class_id, family_dsc,-
item_id,1,'N4_ABEN18',family_id,item_dsc-
FROM PRODUCT_DIM
"OPEN THE CURSOR
SQL OPEN c1
"FETCH THE DATA
SQL FETCH c1 LOOP INTO-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N1_aben18_LEVELDEF,:D_ABEN18_long_description,-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N2_aben18_LEVELDEF,:D_ABEN18_parentrel,-
:D_ABEN18_long_description,-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N3_aben18_LEVELDEF,:D_ABEN18_parentrel,-
:D_ABEN18_long_description,-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N4_aben18_LEVELDEF,:D_ABEN18_parentrel,-
:D_ABEN18_long_description,-
"SAVE THE CHANGES
UPDATE
COMMIT
CLEANUP:
SQL CLOSE c1
SHOW 'KK2'
Then I create a cube with use compression off, and in rules sum for example.
After, I create a measure and I select Override the aggregation specification for the cube, in rules I put nonadditive and I would like to create aprogram to assign distinct values to each level of the dimension. For example, I put 1, 2 3, and 4 values, but at the end I would like to put count(distinct(values)).
for that I create another program:
VRB D_RETURN DECIMAL
if D_ABEN18_N1_ABEN18_LEVELDEF eq 'N1_ABEN18'
then D_RETURN = 1
if D_ABEN18_N2_ABEN18_LEVELDEF eq 'N2_ABEN18'
then D_RETURN = 2
if D_ABEN18_N3_ABEN18_LEVELDEF eq 'N3_ABEN18'
then D_RETURN = 3
if D_ABEN18_N4_ABEN18_LEVELDEF eq 'N4_ABEN18'
then D_RETURN = 4
else d_return=26
return d_return
"SHOW D_RETURN
cubo_aben18_med_aben18_stored=d_return
but it doesnt work.I dont know how to put to assign or to see what I want.
I report the measure, or I report the program, but then how can I see the values of the measure?
thanks in advance

How can I create accurate decimal dimensions when creating a new document or using the art board in Illustrator CS6? When I type in a number with a decimal, it automatically rounds the number up.

How can I create accurate decimal dimensions when creating a new document or using the art board in Illustrator CS6? When I type in a number with a decimal, it automatically rounds the number up.

For my part you are welcome, sdowers.
Unfortunately, the uncertainty arising from the rounding has been up several times here in this forum.
I just came to remember a warning that needs to be given:
The rounding of the representation of a numerical value may be harmless in itself, but if you use it for any operation that changes the value, such as multiplication or whatever, things will go wrong because the operation will be made on the basis of the rounded value instead of the true value. So, as in your first case in post #2, 39.625 rounded to 39.63 will become 79.26 instead of 79.25.

How to create Base Dimensions with MaxL and Text File?

Hi,
Doing a scratch rebuild of a cube every month. Don't want to have a 'dummy' outline with base dimensions to copy over every build. Instead want to build from text file somehow. Thus my plan is to: 1) Delete the existing app/db 2) Create a new blank app/db 3) Create the base dimensions in the outline via text file and 4) Build entire outline via a text file. I'm stuck on #3 how to get the 'base dimensions' built via text file. I need:
ACCOUNTS
PERIOD
VALUE
VIEWS
SCENARIO
CUSTOM4
YEAR
CUSTOM3
CUSTOM2
ENTITY
CUSTOM1
I see this MaxL, but it uses a 'rules file' and I never have built a rules file to create base dims so I'm confused if it's possible or not...
import database sample.basic dimensions
from data_file '/data/calcdat.txt'
using rules_file '/data/rulesfile.rul'
on error append to '/logs/dimbuild.log';

We rebuild our Departments and Organization from an enterprise hierarchy master each week.
The way we implemented (what you call #3) was to not do #1 and #2, but to have a "destructive" load rule for each of these dimensions using a text file. (in the "Dimension Build Settings" for the load rule, select "Remove Unspecified" to make it destructive)
The text file just has the dimension name (parent) and any children we needed defined in a parent/child relationship. For instance
"Sales Departments" "0100-All Departments"
This essentially works the same as deleting the app because the destructive load rules will drop all the blocks of data that were unspecified.
Then we run our SQL load rule to build the rest of the dimensions from the Location Master.
We perform a level-0 export prior to this process, then reload the level-0 data and execute all the consolidation scripts to get the data back (now in a current enterprise defined hierarchy)

How do you create Marketing hierarchies in your company?

Hello,
What procedure you follow to create Marketing plans, elements and campaigns in your company? Is it not painful to create each element manually with so many fields. And this activity usually is repeated every fiscal.
Want to get ideas on the best possible way to create Marketing hierarchies. We are looking for some functionality like upload from Excel . Can somebody comment if this is possible with 7.0?
We received reply from SAP that MS project integration is no more possible with SAP CRM Marketing. So this option is ruled out.
Best Regards,
Shaik

hi, in our project, we develop some RFC interface, and when external BPM process finish their workflow, it will call the RFC, then create TP in CRM to execute.
In my opinion, so many content is not suitable to user to input in CRM UI. And the CRM UI is not friendly enough to user.
But to create a TP in backgroud is also a difficult task, you will meet some problem like how to fill the BPS plan of TP in background, how to generate the fund usage correctly in background. We have spend a log of time to solve them, fortunately we compalished. So this way can be achieve, but it need effort. Please aware this, and do your judgement.

How to create a array with variables dimensions?

I try to create a array like that:
Object[][] data;
data = new Object[] [];
But that's doesn't work!
Apparently I must specify the dimension of my array
So I have done like that :
Object[][] data;
data = new Object[3] [3];
And that work!
But the problem is when I need to add extra elements to my array.
If I write :
data[4][1] = "123";
I have the error message :
java.lang.ArrayIndexOutOfBoundsException
So, how can I defined a array with variables dimensions OR how can I add a dimension to a array?

if you have:
Object[][] data;
data = new Object[3] [3];you end yo getting ArrayIndexOutOfBoundException if you try to point to some other Indexes. You can increase the size by doing new:
Object[][] data;
data = new Object[4] [3];and then copy the old Arrays to this one... this is heavy.
Other thing to consider then is using some other datastructure, such as Vector, which grows along you add elements to it.
P_trg

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

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

Similar Messages

Maybe you are looking for