Recusive hierarchy in essbase studio

do we really need a recursive hierarchy, which is based on self-joined table, to build parent-child hierarchy?
i can build parent-child hierarchy based on parent/child column in a table, and parent/child column don't have to be joined.

understand essbase studio support recursive hierarchy, but i can build a hierarchy based on parent/child column in a table (not self joined), no need to use a recursive hierarchy.
not sure if the concept of "recursive hierarchy" related to drill-through report? because there is "Advanced settings" for recursive hierarchy when create context for report.

Similar Messages

DTS in Recursive Hierarchy through Essbase Studio

I have a recursive hierarchy (PARENT | CHILD) that I have used to build my period dimension through studio. I have run into an issue indicating at which generation i would like to specify the DTS members, as my hiearchy is as follows, and Studio can only recognize that i have 2 generations... "parent" and "child".
My Hierarchy (4 gens):
Period
|-BegBal
|-YearTotal
|-|-Half 1
|-|-|-Q1
|-|-|-|-Apr
|-|-|-|-May
|-|-|-|-Jun
|-|-|-Q2
|-|-Half 2
|-|-|-Q3
Do i have to use a level-based hierarchy with columns (Lev 1 | Lev 2 | Lev 3 | Lev 4) for this?
Thanks in advance!
- Mike

Mike:
Did you ever figure this out? I was able to get DTS to work by simply just configuring it directly in the outline after building it from Studio. But one side affect is that it works fine Classic Essbase addin but does not in Smart View. I get the always helpful "Cannot perform cube view operation.null" error in Smart View.

How to get multiple measures in measure hierarchy in Essbase Studio

Hi All,
Previously we are using one measure column which will gives the count.Now the current requirement is to get multiple measures in measure hierarchy.
For Example
Measure
Count
SalesCount(count*Sales/10)
CustomerCount(count*customer/10)
In the fact we will be having only column called "count".
So,I created the remaining two user defined dimension elements and applied formula in filters.
When i am using individual dimension element in measure hierarchy the data is coming correct,However when I am combing these three hierarchies under measure hierarchiy I am getting no data.Can someone help me out how to resolve this issue
Thanks,
SatyaB

Thanks Gleen.
This is how the actual scenerio,currently i am creating a cube for testing domain.
For all defects we will having a column called defect count.Now there are asking a new requirement to add addtional metrics contains sev1open defect,sev2 open defect etc...
So,I created hierarchy like this
Measures(Hierarchy)
Count
SalesMeasure
For this member I returned in filter as ( 'contains'( connection : 'STATUS', "New" ) and 'contains'( 'TESTING_SEVERITY', "2-High" ))
However when I am trying build this individually working fine getting correct data
When I am combining due to overwrite it seems getting no data.Like this I have to create 16 metrics
Is there any other method where I can proceed further to resolve this issue
So,can you help me on this Gleen.Thanks
Regards,
SatyaB

Unable to create Measures dimension in proper relationshipin Essbase Studio

I am planning to build measure hierarchy in Essbase studio with TBCSample(SQL Server 2005) which is came by default with Essbase Studio installation
I built the hierarchy with parent child relationship.
However the hierarchies is not coming in the proper order
Generally Sales,COGS should come under “Margin ” and it should be under “Profit”
Eg:      Profit
     Margin
          Sales
          COGS
However it is showing differently in “Preview” mode.
Profit
Margin
Margin
Sales
COGS
When I deployed the cube I got the below errors because of the duplicate members
The error file is located on the server at: E:\Hyperion\products\Essbase\EssbaseStudio\Server\.\ess_japihome\data\TBCSampl.TBCSampl_03-29-11_23-16-00.err
\\Record #6 - Member name (Measures) already used
Measures Inventory
\\Record #7 - Member name (Measures) already used
Measures Profit
\\Record #8 - Member name (Measures) already used
Measures Ratios
\\Record #9 - Member name (Margin) already used
Profit Margin
\\Record #14 - Member name (Total Expenses) already used
Total Expenses Marketing
\\Record #15 - Member name (Total Expenses) already used
Total Expenses Misc
\\Record #16 - Member name (Total Expenses) already used
Total Expenses Payroll
Please let me know how to resolve this issue
Database: SQL Server 2005
EPM Version : 11.1.1.3
Thanks,
SatyaB

open the minischema and in the graphic go to your measures table. highlight either the parent or child member and right click. select create join. In the screen that comes up, selet the other column from the same table. It will create the join. You wnat an inner join. You can also click on the member and drag and drop the join line to the child member to create the join

Essbase Studio Alternate Hierarchy Creation error

Hi All,
I'm using Essbase Studio to create an alternate hierarchy. I have a dim which has shared members and I'm getting the following error msg during cube deployment:
1. Record #1- Member Name (SKU) already used i.e. the member for which I m trying to create shared member
     I m following the same procedure mentioned in the user guide i.e.
        Step1: create a copy of the dimension element that you want to designate as a shared member(Renamed SKU_copy with SKU_Diet). By making a copy, the binding expression for this element is the same as the original dimension element (SKU_Diet).
       Step2: when you create the second hierarchy in the chain, which is the alternate hierarchy, add a user-defined membas the parent and add the new dimension element (SKU_Diet) as the child, which will be the shared member.
     Even I m able to see the shared members (SKU_Diet) under user defined member "Diet" under the preview window (both by key binding and caption binding) as wel..
     But I m unable to see the shared members in EAS console after deploying the cube from Essbase Studio to EAS Console.
I m not able to understand what I m missing exactly,.and suggest me other ways as well for creating alternate hierarchies in Essbase Studio.
Thanks in advance..!!

looks like similar issue..
https://forums.oracle.com/thread/1555956
It will work in genaration 2 not in genration 1.
Thanks,
mady

Essbase Studio Drill-through for Recursive Hierarchy - Generation 1

I'm using Essbase Studio 11.1.2.3 to build an ASO cube. All my hierarchies are recursive (parent-child). I would like to define a drill-through report and I understand that I have to use the Advanced Settings option to specify my intersections. Now one of my dimensions is optional for the users - they don't have to specify a member (they can leave it at the highest level - dimension name on the spreadsheet). Under 'Advanced Settings' for DT report in Studio I have to specify a Generation value of 2 or greater than 2. How do I enable drill through in cells where one of the dimension is at Gen1 ? Specifying the level number didn't work. I think if you specify Level in 'Advanced Settings', drill through is allowed only if that specified level of the dimension is chosen, if Gen 2 is specified, then drill through is allowed as long as the dimension-members specified are at or above Gen2. But what about Gen1?

Yep, this is a limitation. I suggest you create two reports one that takes your "optional" dimension out and a second one that has it in. if they don't need the dimension, select the first report and if they need the filter then the second. I m always a little leery with recursive hierarchies and Gen 2 or 3 sine they create a list of level 0 members under the selection in the query and there are limits to the number of members in an in clause and at high levels in the hierarchy it is easy to surpass it (In Oracle it is 1000 members)

Essbase Studio :: Measure Hierarchy :: "accounts not from fact"

Hello,
I am trying to build a Measure dimension in Essbase Studio not from fact table, but from parent-child metamodel table.
[http://docs.oracle.com/cd/E17236_01/epm.1112/est_user/frameset.htm?ch10s03s02s05.html]
Here I've read that I should add loose measure creating cube schema to Measures/Measure Hierarchy field.
What loose measure? I added column from fact table. In Essbase metamodel it created Measure dimension with that one member.
Is it even possible to create measure dimension not from fact table?
Thanx in advance,
L00ka
Edited by: 990463 on Feb 26, 2013 7:40 AM

The approach to take is to create a hierarchy from your measures table, then use the data column from your fact table to populate the measures box in the schema. When building the Essbase model, select the accounts dimension manually.
Oracle recommend that you build the measures dimension directly from your fact table, the above approach deems it a loose measure, that is it isn't based off the fact table.
Steve

Essbase Studio - Create Cube Schema without a Measure or Measures Hierarchy

Using Essbase Studio V 11.1.2.1 I'm trying to create a cube schema. The wizard needs a measures or measures hierarchy in order to proceed. My cube doesn't have a dimension that falls under this category. All dimensions are under the Hierarchies. Is there a way to skip adding anything in the Measures/Measures Hierarchies in order to continue building the cube schema/Model? Any work around?

Hi GlennS, I that I need atleast one measure and thats the dollar amount field from the fact table. So I have done that now...
I'm trying to recreate a cube using Essbase Studio. I'm using EIS from an older essbase version as a template.
While doing a member load In EIS, in the olapisvr.log file, I could see the individual select statements for every dimension/member load. Something like "Member load SQL statement (for dimension CURRENCY_CD) has been generated, start adding member to outline". I cannot locate where I specified this sql or how EIS generates this. The sql is very specific so looks like the EIS generated sql for Member load is being overridden.
Once I figure that out, I need to replicate that in Essbase Studio. Any ideas?

Essbase Studio (parent-child hierarchy + attributes)

There is a problem with the parent-child hierarchy and attributes (for example, structural units of the enterprise).
Composition data (source - table in Oracle):
id (ID of the structural unit - a surrogate key, it is PK)
idParent (ID of the parent structural unit)
code (code of the structural unit - the natural key)
name (the name of the structural unit)
type (type of structural unit)
address (address structural unit)
In this case, parent-child relationship is defined fields idParent -> id, all the rest - should serve as attributes for the various disclosures in the reports.
In all the examples that are found in the network, parent-child built without creating attributes, and it really works. But how "to enrich" the attributes of a hierarchy - and sample solutions are not found.
Most requested help: link, advice, examples from life, either by pointing out that "so definitely not!".

Dear guru of essbase,
I am quite sure that this problem can still be solved by Essbase Studio.
I can not believe that the Studio developers could not include this feature. It is very important to resolve this issue it is through this component, help please both. Thanks

Unable to load data into Essbase cube using Essbase Studio

Hi
We are creating an essbase cube using Essbase Studio using flat files as data sources.
We have taken different hierarchies into different flat files and created one fact file having dimension intersection along with data.
We are able to create the cube and the hierarchy but not able to load any data.
We are getting the following error
Failed to deploy Essbase cube.
Caused by: Unable to perform dataload from more than one flat file.
Could anyone please help on this?

Oh this was killing me, so I did this test in 11.1.1.3:
1) Excel 2007 format -- no go, Essbase didn't see it
2) Excel 2003 format, three sheets -- only the first sheet was read into an empty rule
3) Excel 2003 format, one sheet -- the first sheet was read into an empty rule
4) Excel 95 format, one sheet -- the first sheet was read into an empty rule
The lesson?
1) Excel 2007/2010 sheets don't work (no surprise there as the .xlsx format isn't supported).
2) Excel 2003 and lower (hey, if you have Excel 4, I'll bet that works as well) work, but only the first sheet is recognized.
Regards,
Cameron Lackpour

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

Parent-Child Relationships in Essbase Studio

In Essbase Studio, I am defining a hierarchy in which a parent member (Wholesaler) is from one dimension table and child member (Rep) is from another. When I preview this hierarchy or build an outline to include it, a few of the Reps that should rollup to a certain Wholesaler are missing. They are not dropped, but Essbase Studio just never recognizes these Reps as being children of that Wholesaler in the first place. However, if I run a sql query against the source data mart with the correct joins, these missing reps do show up in the records of that Wholesaler. Also, the missing Reps are showing up fine in the hierarchy preview as long as I don't make them children of anything in the Wholesaler dim. So Essbase Studio is able to see these Reps, but just can't figure out how they are related to the given Wholesaler. Again, this is only happening for about 10% of the Reps for the Wholesaler. Other Reps are showing up fine in the parent-child relationship.
In the source data mart, I don't see any NULLs or anything amiss in the records for the missing Reps. What other reasons would Essbase Studio not recognize a particular joined record?

it really does sound like a join issue. You say if you just load the children without the parent, they load, but if you associte them to the parent, they don't. You might try when creating the joins to do a full outter join to see if they load and to what.
One other thing you could try would be to create a user defined table that has the join in it. I've found data atype issues in joins from different tables before. Studio is very pickey about this
Edited by: GlennS_3 on Oct 20, 2010 9:12 AM

Essbase Studio: Failed to deploy Essbase cube

Hi
I have started working with Essbase studio sometime back and I am able to deploy BSO cube with success using the TBCSample Database which comes along with Essbase. Now I wanted to deploy ASO cube, as no sample database is available I thought to create one, I extracted ASOSamp using ODI to CSV files. Then I bulk inserted the csv extracts into MSSQL 2003 server which created 11 tables (Age, Geography, IncomeLevel, Measures, PaymentType, Product, Stores, Time TransactionType, Year). The above mentioned table does not have any keys(Primary, Foreign) as it is an Essbase export.
I then successful created ASO Cube Schema using the newly created sample database in MSSQL, validated cube schema without any errors.
Essbase Property Setting:
Measures Hierarchy is tagged as Dynamic Compression at dimension level
Time, Product and Year Hierarchy is tagged as Multiple Hierarchies Enabled, Year does not have multiple hierarchies but it has formulas for Variance and Variance % member. Is there a way to tag Year as Dynamic hierarchy?
But when I try to deploy the cube to Essbase I receive following errors:
Failed to deploy Essbase cube
Caused By: Cannot end incremental build. Essbase Error(1060053): Outline has errors
\\Record #1 - Member name (Time) already used
+ S Time + S
\\Record #6 - Member name (1st Half) already used
MTD + S 1st Half + S
\\Record #7 - Member name (2nd Half) already used
MTD + S 2nd Half + S
\\Record #21 - Member name (Qtr1) already used
Qtr1 + S Feb + S
\\Record #22 - Member name (Qtr1) already used
Qtr1 + S Jan + S
\\Record #23 - Member name (Qtr1) already used
Qtr1 + S Mar + S
\\Record #24 - Member name (Qtr2) already used
Qtr2 + S Apr + S
\\Record #25 - Member name (Qtr2) already used
Qtr2 + S Jun + S
\\Record #26 - Member name (Qtr2) already used
Qtr2 + S May + S
\\Record #27 - Member name (Qtr3) already used
Qtr3 + S Aug + S
\\Record #28 - Member name (Qtr3) already used
Qtr3 + S Jul + S
\\Record #29 - Member name (Qtr3) already used
Qtr3 + S Sep + S
\\Record #30 - Member name (Qtr4) already used
Qtr4 + S Dec + S
\\Record #31 - Member name (Qtr4) already used
Qtr4 + S Nov + S
\\Record #32 - Member name (Qtr4) already used
Qtr4 + S Oct + S
\\Record #33 - Member name (Time) already used
Time + S MTD + S
\\Record #34 - Member name (Time) already used
Time ~ S QTD ~ S
\\Record #35 - Member name (Time) already used
Time ~ S YTD ~ S
\\Record #9 - Error adding Attribute to member QTD(Jan) (3320)
\\Record #9 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD + S QTD(Jan) + S [Jan]
\\Record #10 - Error adding Attribute to member QTD(Apr) (3320)
\\Record #10 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Apr) ~ S [Apr]
\\Record #11 - Error adding Attribute to member QTD(Aug) (3320)
\\Record #11 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Aug) ~ S [Jul]+[Aug]
\\Record #12 - Error adding Attribute to member QTD(Dec) (3320)
\\Record #12 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Dec) ~ S [Oct]+[Nov]+[Dec]
\\Record #13 - Error adding Attribute to member QTD(Feb) (3320)
\\Record #13 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Feb) ~ S [Jan]+[Feb]
\\Record #14 - Error adding Attribute to member QTD(Jul) (3320)
\\Record #14 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Jul) ~ S [Jul]
\\Record #15 - Error adding Attribute to member QTD(Jun) (3320)
\\Record #15 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Jun) ~ S [Apr]+[May]+[Jun]
\\Record #16 - Error adding Attribute to member QTD(Mar) (3320)
\\Record #16 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Mar) ~ S [Jan]+[Feb]+[Mar]
\\Record #17 - Error adding Attribute to member QTD(May) (3320)
\\Record #17 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(May) ~ S [Apr]+[May]
\\Record #18 - Error adding Attribute to member QTD(Nov) (3320)
\\Record #18 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Nov) ~ S [Oct]+[Nov]
\\Record #19 - Error adding Attribute to member QTD(Oct) (3320)
\\Record #19 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Oct) ~ S [Oct]
\\Record #20 - Error adding Attribute to member QTD(Sep) (3320)
\\Record #20 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Sep) ~ S [Jul]+[Aug]+[Sep]
\\Record #36 - Error adding Attribute to member YTD(Jan) (3320)
\\Record #36 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD + S YTD(Jan) + S [Jan]
\\Record #37 - Error adding Attribute to member YTD(Apr) (3320)
\\Record #37 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Apr) ~ S [Qtr1]+[Apr]
\\Record #38 - Error adding Attribute to member YTD(Aug) (3320)
\\Record #38 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Aug) ~ S [1st Half]+[Jul]+[Aug]
\\Record #39 - Error adding Attribute to member YTD(Dec) (3320)
\\Record #39 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Dec) ~ S [1st Half]+[Qtr3]+[Qtr4]
\\Record #40 - Error adding Attribute to member YTD(Feb) (3320)
\\Record #40 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Feb) ~ S [Jan]+[Feb]
\\Record #41 - Error adding Attribute to member YTD(Jul) (3320)
\\Record #41 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Jul) ~ S [1st Half]+[Jul]
\\Record #42 - Error adding Attribute to member YTD(Jun) (3320)
\\Record #42 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Jun) ~ S [1st Half]
\\Record #43 - Error adding Attribute to member YTD(Mar) (3320)
\\Record #43 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Mar) ~ S [Qtr1]
\\Record #44 - Error adding Attribute to member YTD(May) (3320)
\\Record #44 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(May) ~ S [Qtr1]+[Apr]+[May]
\\Record #45 - Error adding Attribute to member YTD(Nov) (3320)
\\Record #45 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Nov) ~ S [1st Half]+[Qtr3]+[Oct]+[Nov]
\\Record #46 - Error adding Attribute to member YTD(Oct) (3320)
\\Record #46 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Oct) ~ S [1st Half]+[Qtr3]+[Oct]
\\Record #47 - Error adding Attribute to member YTD(Sep) (3320)
\\Record #47 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Sep) ~ S [1st Half]+[Qtr3]
\\Record #2 - Incorrect Dimension [Year] For Member [ParentName] (3308)
ParentName Consolidation DataStorage MemberName Consolidation DataStorage Formula
\\Record #1 - Member name (Promotions) already used
S Promotions S
\\Record #2 - Incorrect Dimension [Promotions] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #3 - Member name (Promotions) already used
Promotions S Coupon S
\\Record #4 - Member name (Promotions) already used
Promotions S Newspaper Ad S
\\Record #5 - Member name (Promotions) already used
Promotions S No Promotion S
\\Record #6 - Member name (Promotions) already used
Promotions S Temporary Price Reduction S
\\Record #7 - Member name (Promotions) already used
Promotions S Year End Sale S
\\Record #2 - Incorrect Dimension [Payment Type] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #2 - Incorrect Dimension [Transation Type] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #22 - Member name (Home Entertainment) already used
Home Entertainment + S Home Audio/Video + S
\\Record #23 - Member name (Home Entertainment) already used
Home Entertainment + S Televisions + S
\\Record #24 - Member name (Other) already used
Other + S Computers and Peripherals + S
\\Record #25 - Incorrect Dimension [Product] For Member [ParentName] (3308)
ParentName Consolidation DataStorage MemberName Consolidation DataStorage
\\Record #26 - Member name (Personal Electronics) already used
Personal Electronics + S Digital Cameras/Camcorders + S
\\Record #27 - Member name (Personal Electronics) already used
Personal Electronics + S Handhelds/PDAs + S
\\Record #28 - Member name (Personal Electronics) already used
Personal Electronics + S Portable Audio + S
\\Record #31 - Member name (All Merchandise) already used
Products + S All Merchandise + S
\\Record #32 - Member name (High End Merchandise) already used
Products ~ S High End Merchandise ~ S
\\Record #33 - Member name (Systems) already used
Systems + S Desktops + S
\\Record #34 - Member name (Systems) already used
Systems + S Notebooks + S
\\Record #18 - Error adding Attribute to member Digital Recorders (3320)
Home Audio/Video + S Digital Recorders + S
\\Record #36 - Error adding Attribute to member Flat Panel (3320)
Televisions + S Flat Panel + S
\\Record #37 - Error adding Attribute to member HDTV (3320)
Televisions + S HDTV + S
\\Record #8 - Incorrect Dimension [Income Level] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #1 - Member name (Geography) already used
S Geography S
\\Record #2 - Error adding member 27425 (3317)
\\Record #2 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
A M F GREENSBORO - NC S 27425 S 336
\\Record #3 - Error adding member 36310 (3317)
\\Record #3 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABBEVILLE - AL S 36310 S 334
\\Record #4 - Error adding member 29620 (3317)
\\Record #4 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABBEVILLE - SC S 29620 S 864
\\Record #5 - Error adding member 67510 (3317)
\\Record #5 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABBYVILLE - KS S 67510 S 316
\\Record #6 - Error adding member 58001 (3317)
\\Record #6 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERCROMBIE - ND S 58001 S 701
\\Record #7 - Error adding member 42201 (3317)
\\Record #7 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - KY S 42201 S 502
\\Record #8 - Error adding member 21001 (3317)
\\Record #8 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - MD S 21001 S 410
\\Record #9 - Error adding member 39730 (3317)
\\Record #9 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - MS S 39730 S 601
\\Record #10 - Error adding member 28315 (3317)
\\Record #10 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - NC S 28315 S 910
\\Record #11 - Error adding member 79311 (3317)
\\Record #11 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERNATHY - TX S 79311 S 806
\\Record #12 - Error adding member 79601 (3317)
\\Record #12 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABILENE - TX S 79601 S 915
\\Record #13 - Error adding member 79608 (3317)
\\Record #13 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABILENE - TX S 79608 S 915
\\Record #14 - Error adding member 79698 (3317)
\\Record #14 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
Are these errors due to data source, if yes what could be possible work around?
Is there any problem with Essbase properties which I have set if so then when I validate cube schema why I dn't get any errors?
Please help me, I am stuck here not able to deploy ASO Cube.
Thanks in advance

Hii
I have the same problem , you have.
did you manage to solve it ??
Thanks in advance

Essbase Studio- DTS Issue 11.1.2.1

Hi Everyone,
A few months ago, we built our cube through Essbase Studio so that we could allow drill through reports on the cube.
We set Dynamic Time Series on our PERIOD dimension at the Year and Quarter Level.
Our hierarchy looks like this:
PERIOD
|--BEGBALANCE
|--YEARTOTAL
|--|--H1
|--|--|--Q1
|--|--|--|--APR
|--|--|--|--MAY
|--|--|--|--JUN
|--|--|--Q2
|--|--|--|--JUL
|--|--|--|--AUG
|--|--|--|--SEP
|--|--H2
|--|--|--Q3
|--|--|--|--OCT
|--|--|--|--NOV
|--|--|--|--DEC
|--|--|--Q4
|--|--|--|--JAN
|--|--|--|--FEB
|--|--|--|--MAR
In Studio, we built this dimension as a recursive hierarchy and NOT level based.
Our settings are Time (DTS) however we can only choose generation 1 or 2 and cannot put it at gen 2 and 4 where it should be.
We set it as a dense dimension, no two pass, and label only and no formulas or UDAs.
When we run a smart view query with dynamic time series for October (for example), we get an error message [cannot perform cube operation.null].
My coworker then converted the recursive hierarchy to level based just for testing purposes (because we thought the issue was that we built a recursive hierarchy and could only set DTS at gen 1 or 2). After building the hierarchy as level based, we hit the same issue regardless of whether we set the DTS at level or generation.
I am just wondering if anyone has run into this issue before and has a resolution. We are running 11.1.2.1 for version. We have an SR logged with Oracle as of a couple of months ago and they told us they would have a resolution in a week since they were able to duplicate the issue. We have escalated the SR numberous times and have not received a solution yet.
I appreciate your help,
Thanks,
Daniel

I have run into the exact same problem. Did you ever get a resolution? I have also logged a support call so would be interested to know if it is resolved.
Thanks
Steve

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.

Recusive hierarchy in essbase studio

Similar Messages

Maybe you are looking for