Replace dimension with renamed dimension

Hi
We have the following situation. We are currently in the development stage and use Essbase. We have already developed a set of reports but now some the names and aliases of our dimensions need to be changed. In one case, the name of the dimension is changed from "ACCOUNT" to "Account".
However, the reports do not seem to pick up the change. They keep referring to ACCOUNT and error out because they cannot find this dimension anymore. Any suggestions on how to deal with this issue?
yours
Arie

First, is this FR or WA. WA does have a renamer utility that can be quite cumbersome to work with, but if you export the WA report and open up in a text editor, you can do a search and replace on your dimension member.
The same goes with FR, depending on how many objects you have in your report you might have to do a trial and error, but doing an export of the report and doing a search and replaces usually works for me. Any further issues might require a little rework of your reports in there respective design client.
Hope this helps.

Similar Messages

Joining a dimension with another dimension

I have a customer dimension, which had the registration date as an attribute. I want to join to this column in the date dimenion so that I can do rollups and drilldowns. Couple of questions:
- Is this design violating the star schema model?
- How do I accomplish this in OWB, if I have customer and date modeled as dimensions?
Appreciate your help.

Hi,
Yes it would be a violation of a pure Kimball design star schema, but my question is do you have a pure customer dimension, or do you have a customer dimension and should there possible also be a fact table with customer related measures(facts) so you can do the slicing and dicing?
When dealing with designing your datamodel or changes to the datamodel, always try to stay true to the architecture you chose at the start. Keep going back to the rules that came with the design decisions. So if you chose star schema, try stick to that and with each change, review the change against the rules for star schema design. In my opinion you may deviate, but in those cases always do that for the right reasons and document the rationale for that in the design.
grts,
Ed

SSM7.5 - Dimension with Multiple Hierarchies

Hi all,
I'm facing here one problem in the SSM front-end when I'm trying to use one the possibilities that PAS database offers, in this case the use of a dimension with multiple hierarchies.
As you can see in this image, the dimension is created in PAS and works without problems in the dataview.
Hierarchy one:
[http://img121.imageshack.us/img121/334/pas1y.jpg]
Hierarchy two:
[http://img831.imageshack.us/img831/2586/pas2.jpg]
In the SSM front-end, when I try to use that dimension, by default appears the first hierarchy:
[http://img826.imageshack.us/img826/4043/hier3.jpg]
In the dimensional selector the dimension appears fine for the first hierarchy:
[http://img30.imageshack.us/img30/3103/hier1.jpg]
But when I select the second hierarchy...
[http://img34.imageshack.us/img34/1722/hier2.jpg]
The Internet Explorer crashes and close all the open windows. This happens in the scorecard and also in the reports.
Is not possible to use dimensions with multiple hierarchies in SSM? Did anyone had this problem before?
Thanks in advance
Pedro
Edited by: Pedro S. Costa on Sep 13, 2010 11:03 AM

Hi Shashi,
first of all, thanks for your answer.
But I don't understand when you say that "we cannot have two hierarchies on the same dimensions"?!?!?
I already have some years of experience with PAS database and it's not the first time I create a dimension with more than one hierarchy. I use also that in a productive system (before this SSM front-end) without problems. And in this latest version of PAS (version 7.5.6) it's still possible to use that feature. As you can see in my initial post, I put two screen shots of the dimension with two hierarchies in PAS dataview, and works fine, without problems in the drill-down/up.
From PAS online help:
HIERARCHY is a Dimension command that defines the members and levels that comprise a particular hierarchy level within a dimension. It also allows multiple consolidation structures that stem from a central root of inputs. Use hierarchies when the input members are consolidated into more than one output member. When a dimension has hierarchies, members can have more than one path for rolling up into output levels. If a dimension has only one hierarchy, no HIERARCHY statement is necessary.
Based on this, I create my example of a dimension (named MULTI) with two hierarchies (REGION and TYPE). Maybe the name I use for the second hierarchy create some confusion to you, because of the TYPE dimension that can exist in SSM. I just hope the problem I'm having in the SSM front-end is not related with the name I used for the second hierarchy!!!!
I will rename that and test again.
Regards
Pedro

Problem in .rtf template with 2 dimensions in rows section

There is a problem with standard .rtf template: if we select two dimensions in rows, table header (with months) moves left to the position of the second column of row dimension like there is only one dimension in rows (i tested even with 4 dimension in rows, header still starts from the position of the second column of row dimension), in any case default template acts like there is only one dimension in a rows section when a report is being formed, if anybody has already faced that problem maybe you could share an advice to fix it?
p.s. We usually use 1 and 2 dimension in rows

i have a suggestion that there is a problem with colspan parameter in xml file that is built when HP starts creating pdf report, could anybody advise where i can find this xml that is used for creating report?
Edited by: s0uLr1pPeR on 18.05.2012 16:31

Two Cube dimensions with the same name.

Hi
If I have a cube dimension that has the same name as another cube dimension, will this be an issue when quering the cube through 1) Excel 2) SSRS or Cognos Reports?
For instance: The Database dimension DimOrganization exists in cube A as well as
DimOrganization_Dep. Both dimension has the same attribute names and the same hierarchy names.
Their database names are different. (object_ID and Object_name differs)
In the cube I change the name of DimOrganization_Dep to DimOrganization.
This seem to work when I query the cube in Excel, the mdx looks like this;
SELECT NON EMPTY { [Measures].[AntalNotNull] } ON COLUMNS, NON EMPTY { ([Dim Organization].[Yes- No].[ Yes- No].ALLMEMBERS * [Dim Organization].[Yes- No].[Yes- No].ALLMEMBERS ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME
ON ROWS FROM [TEST] CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
Anyone knows if this kind of setup will result in problems when quering from SSRS reports or Cognos?
And/or if even though I get it right in the cube (quering from Excel) it might as well give me the wrong result the next time?
Cheers
/Martin

Hi
Thanks for the reply.
I have tried and yes I can change then cube dimension namn to that of another cube dimension.
For instance if i have Cube Dimension "DimA" and "DimB" to begin with , then I change the name of the cube dimension "DimB" to "DimA". So now I have two Cube dimensions with the same name.
It works to deploy and process and Excel somehow understands which one is which.
Both is present in the same cube as you can see from the MDX above.
The tricky part is how does the mdx return the correct result when the mdx looks like this (and it dpoes return the correct result).?
Cheers
/Martin

The Dimension with ID ... doesn't exist in the collection

BPC 7.5 SP3, MS SQL 2005
I am processing an applicaiton using the Admin console. Choosing "Modify Application", checking the "Process Application" checkbox and clicking "Modify Application" to rebuild the app. The result is successful completion with an error on the details portion of the display under "Modify Fact Table" that lists and exception in the Log. The log in the management console shows the error
Microsoft.AnalysisServices.ItemNotFoundException: The "Dimension" with "ID" = PROFITCENTER doesn't exist in the collection.
The ProfitCenter dimension is one of the application's dimensions.
I can process the ProfitCenter dimension and process this application as part of the dimension processing and it is successful.
I can optimize this application and it is successful.
The application appears to be working properly.
I can open the cube in SQL Server Analysis Services and I can see the ProfitCenter dimension and browse its members. I can open the application cube and browse it.
I checked the profitcenter dimension member table and compared it to the fact tables and all the facts are base level members that are not calculated members.
Has anyone seen this error? Is this just a spurious message I can ignore or is there something really wrong?

We were able to solve this issue today. We turned off Insight and reprocessed the application. The error did not appear. I hope this works for you too.

How to tag attribute member with standard dimension member in EIS

hi,
would any one please help me how to tag attribute member with standard dimension member in EIS
THANK U IN ADVANCE

In your OLAP model, view columns for the base dimension table. Go into the column properties and for the columns that have Attribute values highlight them and click the Attribute button.
Go into Metadata Model and those fields will be available to drag into your outline as attribute members.
Once in the outline, go into the properties of the attribute and assign the level of the base dimension they associate with.

In Top 10 with two dimension i need to add others in my MDX query

Hi this is code working fine and return top 2 product in a state. i need to add other sales also how can we do
with set FIPS as [Geography].[State-Province].[State-Province]
set TCat as
Generate( {FIPS}, CrossJoin( {[Geography].[State-Province].CurrentMember},
TOPCount(
         ([Product].[Subcategory].[Subcategory]),
         2,
         [Measures].[Sales Amount]
SELECT { [Measures].[Sales Amount] } ON COLUMNS,
TCat ON ROWS
FROM [Adventure Works]
hi fond one code it is work for one dimension only, i need for two dimension
WITH
SET [TCat] AS
TopCount([Product].[Subcategory].[Subcategory],10,[Measures].[Sales Amount])
MEMBER [Product].[Subcategory].[Other] AS
Aggregate([Product].[Subcategory].[Subcategory] - TCat)
SELECT { [Measures].[Sales Amount] } ON COLUMNS,
TCat + [Other] ON ROWS
FROM [Adventure Works]

Hi,
We will have to generate a set of tuples that includes both dimensions:
WITH
SET [Top2] AS
Generate
{[Customer].[State-Province].[State-Province].MEMBERS}
[Customer].[State-Province].CurrentMember
,TopCount
(EXISTING
[Product].[Subcategory].[Subcategory].MEMBERS)
,2
,[Measures].[Internet Sales Amount]
MEMBER [Product].[Subcategory].[All].[top2Aggr] AS
Aggregate((EXISTING [Top2]))
MEMBER [Product].[Subcategory].[All].[all Subcat] AS
[Product].[Subcategory].[All]
MEMBER [Product].[Subcategory].[All].[others] AS
Aggregate
(EXISTING
[Customer].[State-Province].CurrentMember
,[Product].[Subcategory].[Subcategory].MEMBERS
[Top2])
SELECT
{[Measures].[Internet Sales Amount]} ON COLUMNS
[Customer].[State-Province].[State-Province].MEMBERS
[Product].[Subcategory].[top2Aggr]
,[Product].[Subcategory].[others]
,[Product].[Subcategory].[all Subcat]
} ON ROWS
FROM [Adventure Works];
If you plan to tweek this solution, you may want to align the dimensionality of the [all Subcat] member with the others members by changing its definition:
MEMBER [Product].[Subcategory].[All].[all Subcat] AS
aggregate(EXISTING
[Customer].[State-Province].CurrentMember
,[Product].[Subcategory].[All]
The former defintion also works in our case because it's a singleton set and it is put in a tuple when crossjoined with the axis 1 giving it the right dimensionality.
Philip,

Join fact table with higher dimension level

how do i join fact tables with higher dimension levels with discoverer?
fact with detail at level C
measure X
dimension with
D->C->B->A
E->C
level
A B C
1------1------1
2------2------1
3------2------1
join between fact X and dimension level C
X=3*C because of sum(X) in discoverer and 3xC in dimension
is there a way to get correct values for X without creating a dimension like
D->C
E->

another way of asking this is whether you can create a summary table in Discoverer at a higher level than a dimension's fundamental grain. In other words - the summary examples in the documentation all describe leaving out one or more of your dimensions... they are either left in or completely taken out. But, some of the most effective summarization occurs when you summarize daily data to a monthly level. Assuming that I have a sales table (at a daily level, and a key value sales_date), and a table date_dim (primary key sales_date), I would like to create a summary sales_month_summary where the sales are grouped on month_year (which is a field in the sales_date table).
How is this done? I suspect that we can't use the date_dim table with the summary (due to the problems noted by the poster above). Do we have to create another table "month_dim"? Do we have to fold all of the desired date attributes (month, quarter, year) into the summary? Obviously we'd like to re-use all of the pertinent already existing date items (quarter, month, year, etc.), not recreate them over again, which would result in essentially two sets of items in the EUL. [One used for this month summary, and another used for the detail.]
I searched the forum - someone asked this same question back in 2000 - there was no answer provided.
The only other thought I have is to "snowflake" the date_dim into two tables and two folders, one at a date level, another at the month level. Then the detail tables can connect to date_dim (which is linked to month_dim), while the summary data can connect directly to month_dim.

Two fact tables with same dimensions

Good Morning,
I am just assigned to a new project. This is my first maintenance request: two fact tables F1 and F2 that shares same set of dimemsion tables D1 and D2. In the Answers report, if I use a foreign key in either F1 or F2, for example F1.k1, I get an error of meta data inconsistency. But if I use same column from dimension table D1.k1, then no error.
Your help is very much appreciated.
May

This is proberly #3 on the most popular topics list, behind SSO and a variables. Please use the search, what you need to do to set up conformed dimensions with multiple facts in the same report has been covererd many times.

Logical fact table with fragmented data sources with different dimensions

Hello.
I have a logical fact table with four logical table sources. Three of the LTS's share the same dimensions, but the fourth LTS has one dimension (called Dim_A) less. In the physical layer the dimension Dim_A is joined to the first three physical fact tables, but not to the fourth fact table (since it doesn't have that dimensionality). In the BMM layer the logical fact table is joines to the logical dimansion Dim_A.
When I run an analysis on this RPD the measures from the logical fact is aggregated correctly (union of all four table sources) as long as I doesn't include Dim_A, but as soon as I include dimension Dim_A I get the error message:
+State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14052] Internal Error: Logical column Dim_A.Column_X has no physical sources that can be joined to the physical fact table source [Logical table sources (Priority=0): Fact_B.Fact_Y]. (HY000)+
I would like a solution where the analysis returns correctly aggregated measures also for the LTS with the "missing" dimension, but with a dimension value NULL for this LTS. Or something like this.
Is there a way to set this up in the RPD.
Thanks,
Henning Eriksen

The SQL could look something like this.
SELECT dim_a.col_1, fact_a.measure_1
FROM db.dim_a
JOIN
db.fact_a
ON fact_a.col_2 = dim_a.col_2
WHERE fact_a.date = '28-nov-2012'
UNION ALL
SELECT dim_a.col_1, SUM (fact_b.measure_1)
FROM db.dim_a
JOIN
db.fact_b
ON fact_b.col_2 = dim_a.col_2
WHERE fact_b.date = '28-nov-2012'
UNION ALL
SELECT dim_a.col_1, SUM (fact_c.measure_1)
FROM db.dim_a
JOIN
db.fact_c
ON fact_c.col_2 = dim_a.col_2
WHERE fact_c.date = '28-nov-2012'
UNION ALL
SELECT NULL, SUM (fact_d.measure_1)
FROM db.fact_d
WHERE fact_d.date = '28-nov-2012'
I would appreciate if you could give me some hints for the RPD.
Thanks,
Henning

OWB10gR2 - Cube with relations to a dimension with more than one hierarchy

Hi,
I have defined a time dimension with two hierarchies. The standard hierarchy with the levels year-> month-> day,
and a week hierarchy with the levels year-> week-> day.
When I define the cube i choose dim_time on the dimension tab of the cube and select the level day for that dimension since this is the lowest level of both hierarchies.
When I validate the cube I get the following error Message: VLD-0398: In the Cube test_cube, the dimension DIM_TIME has 2 hierarchies but Cube does not have reference to all lowest levels of these hierarchies.
Validation details: The Cube should refer to a leaf levels of all multiple hierarchies of the Dimension.
Do I have to add the dimension to the cube several times? or is it maybe another way to fix this? To me it seems a bit messy to add a dimension for each hierarchy.
And just as a comment, Yes i know OWB now has a time dimension wizard but I have chosen not to use this at the moment.. ;)
Regards Ragnar

Hi, i assume this logic is for Dimension formula?
If you have multiple hierarchy like ParentH1 and ParentH2 you should use FormulaH1 and FormulaH2 and not FORMULA column.
in FORMULAH1
[Account.H1].[Account_A] / [Account.H1].[Account_B]

Summary Report with 4 Dimensions and 5 Facts

Hello OBIEE Czars:
I have a problem.
I am trying to make a summary report with 4 Dimensions and 5 Facts.
Out of that only 2 Dimensions are Confirmed.
Now when I try to bring in all the facts, I get view display error.
I searched forum for similar issues.
So I have tried following so far.
1) Add other dimensions as source and set level to Total for those dims.
- After doing this, I dont get view display error, but I get blank rows for couple of facts.
2) I am already aggregating all the measures.
Please help me out.
This forum has been very helpful so far.
Thanks.
~Vinay

Hi
This method seems fine until you run a request that includes a filter on an unconformed dimension.
The SQL itself should be quite straightforward (see below) but the BI Server instance does not seem to be joining this data correctly after posting the 2 separate queries to the database.
SELECT
x.dim1, x.dim2
x.fact1_agg_measure
y.fact2_agg_measure
FROM
SELECT
dim1, dim2
SUM(fact1.measure) fact1_agg_measure
FROM
dim1,
dim2, --UNCONFORMED+
fact1
WHERE
.... .... join fact1 to dimensions as normal
AND dim2 = 'BUSINESS_IDENTFIER'
GROUP BY
dim1, dim2
) x,
SELECT
dim1
SUM(fact2.measure) fact2_agg_measure
FROM
dim1,
fact2
WHERE
.... .... join fact2 to dimensions as normal
GROUP BY
dim1
) y
WHERE
x.dim1 = y.dim1
The result set returned in Answers is firstly a correctly aggregated record plus ALL rows from the second query above ??
Just wondering if anyone else has come across this issue?
cheers
Tony

#Multivalue error with merged dimension

Hello Experts,
I have a report which has two queries 1 and 2. Query 1 has Year,Month,DB,UserID and NOQ(measure) obejcts. Query 2 has User ID and Username Objects.
The requirement is to display Username along with UserID and other objects in Query 1.
I have merged UserID from both queries and the merged object is named as "LANID" and non merged dimensions are created as Detail Objects for year month and DB with associated dimension as LANID.
If I drag year-detail,month-detail,DB-detail,UserID (from LANID) and Username,I get #MULTIVALUE error in month column for User IDs which have multiple records for the same year,different months and same DB.
I came across a similar thread,http://www.forumtopics.com/busobj/viewtopic.php?p=856502 where Dave Rathbun mentions that merged dimensions work only where there is unique record or same level of granularity between two dataproviders which is not the case here.
Request you to share any workarounds (asap) to achieve this.
Thanks,
Sowrabha

Is there some sort of aggregation occurring that's causing multiple values for one row?
Check the table settings and select "avoid duplicate row aggregation" and see if that helps.
Also, with merged dimensions when you're missing individual query objects with merged objects, dimensional context becomes unknown or the wrong context is assumed, so you may be able to clear up the error by adding in a dimensional context (such as [Month-Detail] In ([User ID]).
I hope that helps,
Carly

Report with multiple dimensions in Row and Column with EvEXP

Hi
We are currently running BPC 7.0 SP3 and try to create the report(or schedule) with more 2 x 2 dimensions in the row and column.
e.g.
row dimension : Outer row is Entity, Inner row is Account
column dimension : Outer column is Time, Inner row is Category
We created the report with 2 x 2 dimensions like above e.g. with EvEXP and EvNXP, NOT EvDRE
based on default dynamic template:Template13.xlt(Nested Row, 2 x 1 dimensions defined by EvEXP and EvNXP formula).
However, when expanding the dimension with double click these dimensions or change CV of the report with 2 x 2 dimensions defined by EvEXP and EvNXP formula,
error occurs on EvEXP and EvNXP formula and can't retrieve the result correctly.
[Question]
Can't we create the report with more 2 x 2 dimensions in the row and column using EvEXP and EvNXP function ?
We understand that we can make the report with more 2 x 2 dimensions in the row and column if using EvDRE.
Thank You in advance
Kenya

Thank you for your advice.
I understand that we should use EvDRE when creating the report with multiple dimension in the row/column　because EvEXP have some erros, poor performance, etc.
Then, we have two questions.
1)
>plus they had some errors in the designs.
what kind of errors they have as an example?
2)
>If you must build the EVEXP and EVNXP, I would suggest building the template from scratch
We built the simple template with just 2 x 2 dimension from scratch.
But this report doesn't work well when double-click the dimension or changing CV...
Would you please check the following template?
<https://sapmats-de.sap-ag.de/download/download.cgi?id=RCZE1ME4YSORY3DCDO4NNMANZLBL1L5ZBUOB2F71YVNVS8XDJW>
It would be greatly appreciated if you could give me your advice for the template.
Thank you again
And my best regards,
Kenya

Replace dimension with renamed dimension

Similar Messages

Maybe you are looking for