Loading Planning attribute dimension alternate hierarchies with ODI

Does anyone know how to load an attribute dimension alternate hierarchy via an ODI interface? I'm assuming that alternate hierarchies are allowed in attribute dimensions?
Edited by: jayfin on Mar 28, 2011 5:59 PM

If you are talking about created a shared hieararchy then no this is not possible as you shouldn't be able to do it in planning.
If it is just another hierarchy in your attribute dimension then you should be able to load parent/child members to build it using ODI.
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

ODI Planning Attribute Dimension

I have an existing Product dimension that was created via ODI 10.1.5.6 to Planning 11.1.1.3.03 -- the Product Dim loads fine. Then I attached an attribute dimension called "Product Line" to it using custom attributes. I added four attributes to attach to products. Then re-reversed the Planning application in ODI Planning Model. I can see "Product Line" attribute load dimension (to load new attributes) in the Dimension hierarchy in ODI. However I cannot see a new Column for "Product Line" under the "Product" dimension in ODI. Am I missing something??

So adding the manual dimension seemed like it would work. However it gave me an error as it didn't recognize it when I executed the integration. In any event, deleted the planning model, recreated it and reversed it and the field showed up. Fun stuff! Thanks again.

Load rule to update alternate hierarchy with shared members more than once

I have a aso cube with an alternate hierarchy that is not stored because the shared members appear more than once. Below is how my alternate hierarchy looks.
Dept
Class
VolumeLevel
StoreNum
where StoreNum is the shared member.
I build the cube using eis every weekend. The VolumeGroup changes everyday, so I was thinking of using a sql load rule to update the outline everyday. Assuming that the data and the aggregation does not get cleared. Is it possible to do it using sql load rule?
Thanks,

You can check here if you are satisfying the conditions for creating shared members under the Hierarchy (refer to Alternate Hierarchies). Plz note that rules for shared members are different in ASO world.
http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/frameset.htm?acrtapdb.html
Otherwise there is no reason why you should not be able to create a shared member.
I am able to create a hierarchy using a sample file like this ->
EN_MAIN, EN_500000
EN_500000, EN_49999
EN_ALT, C_500000
C_500000, EN_49999
ENTITY (Multiple Hierarchies Enabled)
|-EN_MAIN (Stored)
|--EN_500000
|---EN_49999
|-EN_ALT (Stored)
|--C_500000
|---EN_49999 (Shared)
The rule file has only "Allow Property Changes" on.
Thanks,
Sunil

Attribute Dimension and association with multi level base members

I am trying to associate attribute dimension members with base members that can be at different levels (level 0 or level 1 or level 2 ).
First question - Is that possible ? Second how do I do that.
I am building the dimensions(base and attribute) members first and then trying to associate.
I get the following error message :
Base member (xxxxxxx) association level does not match base dimension association level
The base dimension looks like
Supplier
|-----Supplier Group
|---------Supplier ID (Associate this member to an attrbiute dimension)
|---------------Invoice Number
Sometimes the Supplier ID may not have a Supplier Group or an Invoice Number (hence it can be a level 0 or directly under the dimension name - Gen2)
The Attrbute Dimension looks like
Supplier Value
|---High
|---Medium
|---Low
Edited by: 816875 on 30-Nov-2010 07:01

First to clarify, base mambers by definition would all be level 0 members, but to your question, attributres can only be associated to a single level within a dimension. your problem is sometimes the supplier is level 0 and other times level 1. This can't be done.

Load Plan Restartability features not visiable from ODI console (EWR)

Hi,
We are trying to use ODI console in TEST environment(Execution work Repository) to perform restartability of Load Plan. But when we right click on the failed LP, Restart link is not visible. I can do the same functionality using ODI console in DEV (Development work repository). Does this restartability feature is not available using ODI console of EWR?
Thanks
Sanjeet

Hi Sanjeet,
Based on the documentation here (http://www.orastudy.com/oradoc/selfstu/fusion/integrate.1111/e12643/odi_console.htm#CIAEGCDE), it looks like the Load Plan must be in error state and another instance of the Load Plan cannot be running in order to restart.
Regards,
Michael Rainey

Planning, Attribute Dimensions, FR

I have a situation where we are creating reports in FR
We are trying to leverage the attribute dimension. If we point to FR in Essbase we can leverage it. If we point FR to Planning it doesn't give us that option. Is this functioning as designed or are we missing a step

Yes that is the way it works unfortunately, it has to be an essbase connection.
Cheers
John
http://john-goodwin.blogspot.com/

Error reverse engineering Hyperion Planning 11.1.2.1 with ODI 11.1.1.5

I have the port set to 11333 Hyperion RMI service is running.. still getting this error..
By the way it looks like this 11.1.1.5 release of ODI has too many bugs when loading data and metadata to Hyperion..
It seems that I need ODI to be installed on Planning server.. I had it running on the other (essbase) server originally and it could not even access Planning unless I used the Agent.. Now I am getting this error:
org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File "<string>", line 41, in <module>
     java.io.InvalidClassException: com.hyperion.planning.HspException; local class incompatible: stream classdesc serialVersionUID = -2065834634290912749, local class serialVersionUID = 1173493819024915347
     at com.hyperion.odi.planning.wrapper.PlanningWrapper.login(Unknown Source)
     at com.hyperion.odi.planning.ODIPlanningConnection.connect(Unknown Source)
     at com.hyperion.odi.common.ODIModelImporter.importModels(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
com.hyperion.odi.planning.ODIPlanningException: com.hyperion.odi.planning.ODIPlanningException: Error unmarshaling return; nested exception is:
     java.io.InvalidClassException: com.hyperion.planning.HspException; local class incompatible: stream classdesc serialVersionUID = -2065834634290912749, local class serialVersionUID = 1173493819024915347
     at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
     at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:346)
     at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2457)
     at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:47)
     at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
     at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2906)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2609)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:537)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:453)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1740)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:338)
     at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:214)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:272)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:263)
     at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:822)
     at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:123)
     at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
     at java.lang.Thread.run(Thread.java:619)

Thank you, John, for a quick reply, but unfortunately these files did not help either. Still getting the same error:
org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File "<string>", line 23, in <module>
     at com.hyperion.odi.planning.ODIPlanningWriter.validateColumns(Unknown Source)
     at com.hyperion.odi.planning.ODIPlanningWriter.loadData(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
com.hyperion.odi.planning.ODIPlanningException: com.hyperion.odi.planning.ODIPlanningException: The source result set contains column [C1_CHILD] which has no corresponding column on the planning side.

Maintain attribute dimensions in Hyperion Planning, via ODI

How can I move/maintain attribute members in Hyperion Planning, preferably via ODI?
I have been loading an attribute dimension into Hyperion Planning, via ODI. The problem is that some children have been previously loaded to incorrect parents. However, a reload does not seem to move the children to their rightful place in the hierarchy.
There are no errors being generated.
Cheers

Are you definitely sure it is not on the planning side the issue lies, I would create a file and then use the outline loader to compare load times to see where the issue is first.
Cheers
John
http://john-goodwin.blogspot.com/

Attribute dimension mapping

Hi to all,
I have my application with 11 dimensions and 3 attribute dimensions... . When we generate our metada.ads for loading to the app, we see the diferent elements for the dimension SKU mapped with the attributes, but when we make the load for the dimension, we don´t have any element of the SKU dimension (product dimension) mapped with the attributes, and we have no error message........
Any suggestion?
We generate the metadata.ads through EPMA File generator in Excel 2007....
Thanks in advance
David.

Hi David,
A couple of pointers maybe:
- Have you applied the latest EPMA patches?
- What version are you on exactly? 11.1.1.3 or 11.1.2.x?
- We had a similar issue where some attribute dimension mappings werent exported caused by the fact that although the attribute dimension was associated with a base dimension in Planning, this association did not exist in EPMA. The strange thing is that we were still able to deploy the app with no errors. In our Planning app properties we do have a EDIT_DIM_ENABLED - true propery that enables to make changes to Planning directly. I think this is where the issue started.
Hope this helps.
Seb

Why should we associate attribute dimension to base sparse dimension only

hi experts,
I have query, please suggest that.
Why should we associate attribute dimension to base sparse dimension only ? any reason is there.
thanks in advance

Have a read of - why attribute dimension attached to sparse dimension and Attribute Dimension and association with multi level base members
Cheers
John
http://john-goodwin.blogspot.com/

Building Attribute Dimensions in VB

I am writing a VB program to update an attribute dimension. I have followed the documented approach to populate the ESB_MBRINFO_T structure but continue to get errors 8 - ESB_OUTERROR2_ILLEGALDATATYPE and 64 = ESB_OUTERROR2_ATTRDIMNOTASSOCIATED.
The code is
Public Function esbMoveOrAddMember(rsChild As String, _
rsParent As String, _
rsAlias As String) As Integer
Dim sts As Long
Dim stsInfo As Long
Dim hChild As Long
Dim hCurrentParent As Long
Dim hParent As Long
Dim uNewMemInfo As ESB_MBRINFO_T
Dim szAlias As String * ESB_MBRNAMELEN
esbMoveOrAddMember = 0
If esbFindMember(rsParent, hParent) Then 'Find Parent
If esbFindMember(rsChild, hChild) Then 'Find member
' Found parent and child so see if a move is needed
' Get the current parent handle
stsInfo = EsbOtlGetParent(mhOutline, hChild, hCurrentParent)
If hParent <> hCurrentParent Then
sts = EsbOtlMoveMember(mhOutline, hChild, hParent, ESB_NULL)
If sts <> 0 Then
esbMoveOrAddMember = 1
Call essGetAndDisplayMessage(sts)
End If
End If
Else
'Good Parent, new member so add it
Call SetupAttributeMemberForAdd(rsChild, uNewMemInfo)
sts = EsbOtlAddMember(mhOutline, uNewMemInfo, ESB_NULL, hParent, hChild)
If sts <> 0 Then
esbMoveOrAddMember = 2
Call essGetAndDisplayMessage(sts)
End If
End If
Else
esbMoveOrAddMember = 3
sts = 5
End If
'* Set the alias of the child member
If sts = 0 And hChild <> 0 And Len(rsAlias) > 0 Then
szAlias = rsAlias
sts = EsbOtlSetMemberAlias(mhOutline, hChild, "", szAlias)
If sts <> 0 And sts <> 1060023 Then
esbMoveOrAddMember = 4
Call essGetAndDisplayMessage(sts)
End If
End If
End Function
Sub SetupAttributeMemberForAdd(rsChild As String, uMemInfo As ESB_MBRINFO_T)
With uMemInfo
.szMember = rsChild
.usConsolidation = ESB_UCALC_NOOP
.fTwoPass = ESB_FALSE
.fExpense = ESB_FALSE
.usConversion = ESB_CONV_NONE
.usTimeBalance = ESB_TIMEBAL_NONE
.usSkip = ESB_SKIP_NONE
.usShare = ESB_SHARE_DYNCALCNOSTORE
.usStorage = ESB_DIMTYPE_SPARSE
.usCategory = ESB_CAT_ATTRIBUTE
.usStorageCategory = ESB_STORECAT_ATTRIBUTE
.Attribute = ESB_ATTRMBRDT_NONE
End With
End Sub
Any help will be appreciated as Oracle support is none so far.

Hi,
Your error "ESB_OUTERROR2_ILLEGALDATATYPE and 64 = ESB_OUTERROR2_ATTRDIMNOTASSOCIATED." indicates problem with attribute dimension association
kindly check is there any duplicate member in attribute dimension.
or same attribute dimension is associated with some other dimensions

Load hierarchical attribute dimensions with Integration Services?

Hi everybody,
I need to load product dimension which is organized in a relational table like this:
Product (parent_code, member_code, member_alias, brand, consolidation, formula)
Every product has a brand and I need to load brand as attribute dimension. The thing is Brand is not flat but it has it's own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
Brand (brand_parent_code, brand_child_code, brand_child_alias).
I have used in the past Integration Services but with flat attribute dimensions.
Can I load hierarchical attribute dimensions with Integration Services? If yes, how do I do it, how do I specify the hierarchy?
Thank you,
Daniela

Graham,
This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
When you run your dim build it will set up your attribute dimension correctly.
Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
Good luck, let me know if you run into trouble.

How to design Flat file for loading attribute dimension in a planning application

Dear Gurus,
I have a requirement to extract attribute dimensions from an essbase application and load it to another planning application. I have a dimension called Program and two attribute dimensions Sales Manager, Accounts manager associated with Program dimension in Essbase application. I will Extract these dimensions using Essbase outline extractor. After Extracting the attribute dimensions I have to load these dimensions to planning applications using outline load utility. Kindly guide me how to design the flat file for loading attribute dimensions in planning application.
Thanks and Regards
SC

You could dig through the docs and try to figure out the file format manually, or you could do this the easy way. Simply use the Outline Load Utility to export your attribute dimension from Planning. The export file format is the same as the import file format. You might have to manually add a couple of test members to your attribute dimension so that your export file has some content. Then simply update the file you exported, and import it.
(I am assuming you have already manually created the Attribute dimension in Planning, and that you simply need to add members to it.)
Hope this helps,
- Jake

Hyperion Planning- Account dimension - Sort Order Issue with ODI 11.1.1.5

Hello Experts,
First of all, I thank you everybody in this forum for posting their valuable suggestions.
I am facing a strange issue with ODI (Version 11.1.1.5) while loading metadata to Planning ACCOUNT dimension (Version 11.1.2.x). I am using a Oracle view to load metadata to this dimension. I have defined the sort order in the view and enabled SORT_ORDER_BY_INPUT. For the fresh load to the dimension, everything is working fine. But, when I move a member from one parent to another parent, and define it as the top member of new parent, it is missing its sort order.
But it is working fine if you define it as the second, third...or last member under new parent. I have tried all the possible ways by flipping all the properties but unable to fix it.
Please help me here to resolve this issue.
Your help is greatly appreciated!!
Thanks
Edited by: user11965311 on Sep 20, 2011 7:07 PM

To be honest I think you are best logging it with Oracle because it sounds like you are doing everything correctly so it could be a bug.
Have you tested this on any previous versions of ODI or is it a new installation?
If it does get logged with Oracle please keep me informed of the outcome as I would be interested to hear.
Cheers
John
http://john-goodwin.blogspot.com/

Hierarchical attribute dimension with Essbase Studio

Hi everybody,
I need to load product dimension which is organized in a relational parent-child table like this:
(parent_code, member_code, member_alias, brand, consolidation, formula)
Every product has a brand and I need to load brand as attribute dimension. The thing is Brand is not flat but it has its own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
(brand_parent, brand_child, brand_alias).
I need to do this load with Essbase Studio but I do not known how to create the Product hierarchy in cube schema in order to load the hierarchical parent-child attributes. Documentation and tutorials only show examples for flat attributes. I thought of these two ways but not sure if will work:
case 1) Product hierarchy like this:
Parent_code
Member_code
Brand_parent
Brand_child
Member_code
case 2) Product hierarchy like this:
Parent_code
Member_code
Brand_parent
Brand
Member_code
Has anyone had to this? How did you do it?
Any help will be very appreciate.
Thank you,
Daniela

I've not tried it, but you should be able to build the attribute hierarchy within the product hierarchy. sort of like
Parent Code
---member Code
Brand Parent
---Brand Code
-----Member Code.
A couple of things
1. Remember to create the self join between Parent_code and Member code
2. IF this does not work, I suggest creating either a user defined table or a view that just gives you distinct brand parent and Brand Code. Join the Brand Code to the product table on brand_code = brand code and use that table to build that hierarchy.

Loading Planning attribute dimension alternate hierarchies with ODI

Similar Messages

Maybe you are looking for