Hide unrelated dimension members in cube?

Hi!
I have built a dimension that is used by a few cubes. The thing is that the dimension has a lot of members (consist of all articles in the company) and one of my cube is only relating to a few of these dimension members (articles). Which means that I get ALOT of empty members in the cube. Is there anyway that I can "filter out" these members that have no relation in the cube?
Example:
The dimension consist of these members: Article01, Article02, Article03. The fact table/cube only got rows/values for Article01 and Article02, but I still got Article03 as a member in the cube. I don't want to have this Article03 dimension member showing up in this cube, but Article03 needs to show in other cubes that uses this dimension.
Is there any way to solve this problem. Tryed to look after some attributesettings to solve the problem, but couldn't find any? Is this problem even possible to solve or do I have to make a new dimension?
Thanks in advance
AndersO

Just a note on this issue. It seems to me that it would be a good idea to include a dimension key attribute property that allows a designer to restrict dimension members to only those that are related to at least one row in any fact table-measure group partition it is joined to. Role playing dimensions (dimensions that are reused over and over again such as location or organization), have many members that only apply to certain "roles" but are managed in one dimension for the purposes of achieving enterprise wide conformation (data linkages across datamarts). A property to limit members to only those found in the fact table / measure group partition would be great. I assume from this thread no such property yet exists.
Cognos Transformer has this. I like SSAS better but...

Similar Messages

How to check for a large cube (100K or more dimension members)

Hi Experts,
We have a customer with trouble returning large data sets. How can I check for a large cube (100K or more dimension members) on BI7?
Is there a tuning parameter in BW to increase the result buffer?
Thanks!
Sapna

You can do a count of the n° of entries in the dimension tables.
But that's a pain in the ***.
You might consider running program SAP_INFOCUBE_DESIGNS.
This program gives a list of all infocubes with a ratio between the dimensions and fact table.
So you can see if a cube is well-designed or not.

Using intersection of dimension members in a SINGLE column/row name

I need help understanding how a single row/column name in a report can be populated with an intersection of two different dimension members of an Essbase cube (ASO). For example, suppose I have two dimensions members in my cube - Sales and Qtr1. Now I want to create a single column-name in my Smartview or FR report called "Sales in Qtr1" that would store values for Qtr1->Sales. Also, i want to have a single column name such as (Qtr1->Sales % Qtr2->Sales).
Is this done via a report script or some other method?
My report would look as follows:
Sales in Qtr1 | Sales in Qtr2 | Qtr1 Sales as a percent of Qtr2 Sales
Region1 100 | 200 | 50%
Region2 25 | 100 | 25%
Would appreciate any guidance.
Thanks.
Axe

Getting the data the way you've described is really easy, just nest the dimensions in Excel (or whatever reporting tool), one dimension over the other.
It's the same for rows as it is columns (okay, in rows instead of columns).
Essbase is very good about doing asymmetrical reports. Take a look at the DBAG and scroll down for the section labelled "Generating Symmetric Reports" -- the second example shows a asymmetric report.
Making the label one cell? A bit hard in Excel -- you'd have to create separate retrieve ranges and report ranges or play a game with hiding rows. Very easy indeed in Financial Reports -- you basically hide a row and put whatever custom label you want in the dimension that remains (technically speaking you could hide both rows and do this with a text row -- whatever you prefer -- but I've generally seen this with the former technique.
Regards,
Cameron Lackpour

How can I manage access to dimension members in a layout?

Hello,
I have a dimension member list of materials (400) on a "material" dimension. But some people have access to one portion of the whole group and others may have access to other groups. But the materials can be shared between groups so I cannot group them in differents hierarchies.
The problem is in the layout you need to select a hierachy to show various rows (the whole group of materiales). The layout shows all the list of materials. Even if the user only have access to 10 of them. I don't know how is the best way for presenting this to the user? It should presents only the 10 rows corresponding to his materials.
One way that I found (but I don't find it acceptable because of the hard effort that represents the maintenance) is to create differents member access profiles and denied the access to each material (dimension member - 390) that the user cannot modified. Then in excel I have to run a macro that hides all the rows that have an empty description in the cell of the material name.
How can I achive this?
Is there a function in BPC to see if a user have access or not to a dimension member?
The only way to show in a layout various rows is to set in the view a hierarchy?
Thanks & Regards
SU

hi
pl. verify whether this will suit your requirements:
Material           UG1           UG2
MAT1               Y
MAT2                                 Y
MAT3               Y
MAT4                                 Y
MAT5               Y               Y
Now UG1,UG2 diff user groups and property in Material. Assignment of Y is one time job.
At the time of accessing the dimension members can restrict on the basis of UG1="Y" or UG2="Y" property
Here MAT5 is common in both UG1 and UG2
(Hardly may have 3-4 set of users: Accordingly can have UG1,UG2,UG3,UG4 etc.)
sri

SSRS with calculated dimension members SSAS

Hello everybody,
I have an interesting scenario involving a SSRS report with a matrix connected to a SSAS cube containing calculated dimension members.
One of the parameters is "Reference Week". Based on that parameter, I need the measures for the previous 5 weeks.
So I created an anchor dimension "Analysis Weeks" with the members "Week -1" to "Week -5".
Everything is working fine. The only problem is the names of the columns on the report.
Currently I have "Current Week", "Week -1", etc. as column names, I'd like to show the real dates.
For example, if I choose "2014-02-15" as the reference week, I want the first column to show "2014-02-15" instead of "Current Week". The second would show "2014-02-08" instead of "Week -1", etc.
I tried to get the current column position in the matrix, which I could use the with @ReferenceWeek parameter, but I can't access that property.
Any suggestion?
Thanks

If I understand correctly, your column group is on "Analysis Weeks", is that right? If so just get the value of that field and use it to get the dates.
=DateAdd("d",-1*CInt(Right(Fields!AnalysisWeeks.Value,1))*7,Fields!ReferenceWeek.Value)
"You will find a fortune, though it will not be the one you seek." -
Blind Seer, O Brother Where Art Thou
Please Mark posts as answers or helpful so that others may find the fortune they seek.

Automatic creation of new dimension members

Hello all,
Bit of a long post so please bear with me.
I am about to embark on only my third BPC project after having spent several years implementing solutions using BusinessObjects Planning (formerly SRC software), and am still struggling to come up with an elegant solution to the fact that I cannot save data to dimension elements unless they are already explicitly defined in the dimension member list (presumably due to cube architecture).
Those of you who have used BOP/SRC will remember this as unvalidated dimensions.
I find having to first go to admin and pre create members before being able to use an input schedule to save data against them is very restrictive.
I'm hoping one of you guys can help me improve on the workaround I currently use.
For example I have a 'bid submission' input schedule that is used by the user to submit bids for increased budget, capital or revenue, capturing basic costs and commentary. The user selects a bid number from a combo box which is populated by using an EVLST formula to read in pre created dimension members. I have to save a flag to the db which I then use to exclude already used numbers when feeding the combo box on future submissions.
Which works ok but if I have a hierarchy on bid number based on say, cost centre, how do I get around the fact that number ranges have to be pre-assigned to cost centre, Cost Centre A = 1 to 1000, Cost Centre B = 1001 to 2000 etc. What happens if I go over the 1000 on Cost centre A? I then get non contiguous ranges per cost centre.
Is it possible for the bid number to be dictated by the user when they start to fill in the bid submission? Or give the impression that they are?
Or if the client has a bid number format that cannot be pre created? Eg incorporating things like year or person etc. This information could be save separately but not within the bid number. Is it possible to save data to dimension property columns from an input schedule?
Hope you guys can help
Many thanks
Phil

Philip,
few questions.
Which versio of BPC.
What is your data Source
there are few post on the below link you may find helpful
Please list your Question in short with the tings you want.
Re: AdminTask_MakeDim.dts
Thanks

Top 10 lowest level dimension members based on measure

Hi,
I'm trying to create a condition with JDeveloper to show the top 10 dimension members based on a measure for the lowest level of the hierarchy, but doesn't work.
All other conditions are working well, including top 10 dimension members in other levels of the hierarchy (not in the lowest).
Any suggestion??
I think the dimension is defined ok, all other conditions are working well and the lowest level could be shown with other conditions and drills.
Thanks in advanced....

Hi,
First, my BI Beans version is 9.0.3.5 and my database version is 9.2.0.2.1
I will try to clarify my problem. I am trying to create a graph to show the top10 members of a dimension based on my measure. When I define this condition
to show the top 10 members of a middle level (not de low level), it works fine, I mean, it shows the top 10 members of that level. But, when I define the condition
to show the top 10 members of the low level, it displays me that there is no data to display (The data has an insufficient number of columns and rows).
I have been testing this case, and I have seen that if I change the low level column (number type) of the dimension to a varchar type column, it works. This low level is
the primary key of the dimension table, and it's referenced by a foreign key in the fact table.
Which could be the problem?? Is it not possible to define a level of a dimension with a number column??
I have a demo sample to see this problem (two simple dimensionS with three levels and a fact table). It's a bit large to post it complete, so I post here an extract of it.
-- Dimension and fact tables
CREATE TABLE PR_DIM_A (DIM_A_KEY NUMBER,
               LOW_A_LEVEL_NAME VARCHAR2(50),
               ALL_A_LEVEL_ID VARCHAR2(50), ALL_A_LEVEL_NAME VARCHAR2(50),
               GROUP_A_LEVEL_ID VARCHAR2(50), GROUP_A_LEVEL_NAME VARCHAR2(50),
               CONSTRAINT PK_DIM_A PRIMARY KEY (DIM_A_KEY));
CREATE TABLE PR_DIM_B (DIM_B_KEY NUMBER,
               LOW_B_LEVEL_NAME VARCHAR2(50),
               ALL_B_LEVEL_ID VARCHAR2(50), ALL_B_LEVEL_NAME VARCHAR2(50),
               GROUP_B_LEVEL_ID VARCHAR2(50), GROUP_B_LEVEL_NAME VARCHAR2(50),
               CONSTRAINT PK_DIM_B PRIMARY KEY (DIM_B_KEY));
CREATE TABLE PR_FACTS (FACT_KEY NUMBER, DIM_A_KEY NUMBER, DIM_B_KEY NUMBER,
               MEASURE_1 NUMBER, MEASURE_2 NUMBER,
               CONSTRAINT PK_FACTS PRIMARY KEY (FACT_KEY));
ALTER TABLE PR_FACTS ADD CONSTRAINT FK_DIM_A FOREIGN KEY (DIM_A_KEY)
               REFERENCES PR_DIM_A (DIM_A_KEY);
ALTER TABLE PR_FACTS ADD CONSTRAINT FK_DIM_B FOREIGN KEY (DIM_B_KEY)
               REFERENCES PR_DIM_B (DIM_B_KEY);
-- Data inserts in the dimensions
INSERT INTO PR_DIM_A VALUES (1,'ALL','ALL_NAMEa','GROUP1a','GROUP1_NAMEa','LOW1a','LOW_NAME1a');
INSERT INTO PR_DIM_A VALUES (2,'ALL','ALL_NAMEa','GROUP1a','GROUP1_NAMEa','LOW2a','LOW_NAME2a');
-- ......... dimension B is the same kind of data.
-- OLAP dimension A creation script
cwm2_olap_dimension.create_dimension('BI02', 'PR_A_DIM', 'DimA Diaplay name', 'DimA Plural name', 'DimA Short Description','DimA Description');
cwm2_olap_dimension_attribute.create_dimension_attribute('BI02', 'PR_A_DIM', 'Short Description', 'Short Descriptions', 'Short Desc', 'Description', TRUE);
cwm2_olap_hierarchy.create_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'HIER_DIM_A Display name', 'HIER_DIM_A ShortDesc', 'HIER_DIM_A Desc','Unsolved Level-Based');
cwm2_olap_dimension.set_default_display_hierarchy( 'BI02', 'PR_A_DIM', 'HIER_DIM_A' );
cwm2_olap_level.create_level('BI02', 'PR_A_DIM', 'ALL_LEVEL_A', 'ALL_LEVEL_A DisplayName', 'ALL_LEVEL_A PluralName', 'ALL_LEVEL_A ShortDesc', 'ALL_LEVEL_A Desc');
cwm2_olap_level.create_level('BI02', 'PR_A_DIM', 'GROUP_LEVEL_A', 'GROUP_LEVEL_A DisplayName', 'GROUP_LEVEL_A PluralName', 'GROUP_LEVEL_A ShortDesc', 'GROUP_LEVEL_A Desc' );
cwm2_olap_level.create_level('BI02', 'PR_A_DIM', 'LOW_LEVEL_A', 'LOW_LEVEL_A DisplayName', 'LOW_LEVEL_A PluralName', 'LOW_LEVEL_A ShortDesc', 'LOW_LEVEL_A Desc' );
cwm2_olap_level_attribute.create_level_attribute('BI02', 'PR_A_DIM', 'Short Description', 'ALL_LEVEL_A', 'Short Description', 'All_LEVEL_A DisplayName', 'ALL_LEVEL_A ShortDesc', 'ALL_LABEL Desc', TRUE );
cwm2_olap_level_attribute.create_level_attribute('BI02', 'PR_A_DIM', 'Short Description', 'GROUP_LEVEL_A', 'Short Description', 'GROUP_LEVEL_A DisplayName', 'GROUP_LEVEL_A ShortDesc', 'GROUP_LEVEL_A Desc', TRUE );
cwm2_olap_level_attribute.create_level_attribute('BI02', 'PR_A_DIM', 'Short Description', 'LOW_LEVEL_A', 'Short Description', 'LOW_LEVEL_A DisplayName', 'LOW_LEVEL_A ShortDesc', 'LOW_LEVEL_A Desc', TRUE );
cwm2_olap_level.add_level_to_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'LOW_LEVEL_A', 'GROUP_LEVEL_A' );
cwm2_olap_level.add_level_to_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'GROUP_LEVEL_A', 'ALL_LEVEL_A' );
cwm2_olap_level.add_level_to_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'ALL_LEVEL_A' );
cwm2_olap_table_map.map_dimtbl_hierlevel('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'ALL_LEVEL_A', 'BI02', dim_table, 'ALL_A_LEVEL_ID' );
cwm2_olap_table_map.map_dimtbl_hierlevel('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'GROUP_LEVEL_A', 'BI02', dim_table, 'GROUP_A_LEVEL_ID' );
cwm2_olap_table_map.map_dimtbl_hierlevel('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'LOW_LEVEL_A', 'BI02', dim_table, 'DIM_A_KEY' );
cwm2_olap_table_map.map_dimtbl_hierlevelattr('BI02', 'PR_A_DIM', 'Short Description', 'HIER_DIM_A', 'ALL_LEVEL_A', 'Short Description', 'BI02', dim_table, 'ALL_A_LEVEL_NAME' );
cwm2_olap_table_map.map_dimtbl_hierlevelattr('BI02', 'PR_A_DIM', 'Short Description', 'HIER_DIM_A', 'GROUP_LEVEL_A', 'Short Description', 'BI02', dim_table, 'GROUP_A_LEVEL_NAME' );
cwm2_olap_table_map.map_dimtbl_hierlevelattr('BI02', 'PR_A_DIM', 'Short Description', 'HIER_DIM_A', 'LOW_LEVEL_A', 'Short Description', 'BI02', dim_table, 'LOW_A_LEVEL_NAME' );
-- OLAP dimension B creation script is similar than A.
-- OLAP CUBE creation script
cwm2_olap_cube.create_cube( 'BI02', 'PR_CUBE', 'Sample Cube', 'Sample Cube', 'Sample Cube' );
cwm2_olap_measure.create_measure('BI02', 'PR_CUBE', 'MEAS1', 'MES1 DisplayName', 'MES1 ShortDesc', 'MES1 Desc');
cwm2_olap_measure.create_measure('BI02', 'PR_CUBE', 'MEAS2', 'MES2 DisplayName', 'MES2 ShortDesc', 'MES2 Desc');
cwm2_olap_cube.add_dimension_to_cube( 'BI02', 'PR_CUBE', 'BI02', 'PR_A_DIM' );
cwm2_olap_cube.add_dimension_to_cube( 'BI02', 'PR_CUBE', 'BI02', 'PR_B_DIM' );
dimkeymap :=
     'DIM:'
|| 'BI02'
|| '.PR_A_DIM/HIER:HIER_DIM_A/LVL:LOW_LEVEL_A/COL:DIM_A_KEY;DIM:'
|| 'BI02'
|| '.PR_B_DIM/HIER:HIER_DIM_B/LVL:LOW_LEVEL_B/COL:DIM_B_KEY;';
cwm2_olap_table_map.map_facttbl_levelkey( 'BI02', 'PR_CUBE', 'BI02', fact_t, /*'ET'*/ 'LOWESTLEVEL', dimkeymap );
cwm2_olap_table_map.map_facttbl_measure( 'BI02', 'PR_CUBE', 'MEAS1', 'BI02', fact_t, 'MEASURE_1', dimkeymap );
cwm2_olap_table_map.map_facttbl_measure( 'BI02', 'PR_CUBE', 'MEAS2', 'BI02', fact_t, 'MEASURE_2', dimkeymap );
Thanks a lot for your help....

Number of dimension members

Hi! :) Can anyone advise on what are recommendations on the max number of dimension members for each HP dimension taking into account that the cube can be alone and can be partitioned? Thanx! :-)
Edited by: user10129034 on 29.05.2009 0:24

I will take a stab at this...just went to Essbase boot camp and the question you ask is a loaded question.
Because of its multi-dimensional architecture and its data storage in 'blocks'...the answer is 'it depends'.
One of the critical issue with dimensions and its members is 'Is the dimension Spare or Dense'?
Best practices is to have minimal amount of Dense dimensions (which makes up your block size) than of Spare dimensions (which determines the amount of blocks you have)
In my training this question was asked from a DBA used to transactional database and asked what the max is.
The instructor indicated there really isn't a limit, clearly defined.
I thought I saw something in the essbase admin but I am unable to find it if someone could add it would be great
so if you have several dimensions or dimensions with several members you need to determine their density which in turn dictates the system performance and functionality.
JTS
Edited by: jts on May 29, 2009 7:18 AM

Dimension and dimension members

Hi Friends
Please can you educate us about the Dimension and Dimension members with few example please
Thank you and Kindest Regards
Srikaanth

Hi,
Are you familiar with SAP BI?
Dimension is similar to characteristics. These are assigned to an application (similar to cubes). Members are the master data. You will get more information in the below links from help.sap:
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/cd/30ffa271b4463b8cc2c8b671fb0459/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/bpc_nw_index.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/0f/19c0ca01d843b794af11629e4593ab/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/51/0166ff49e5496f87bfbf6096fc0fda/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/7c/6782a29233467d9a9c55971c167270/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/30/ad1aa7479946be8221cdd1dfa56ca3/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/c9/31cc0adc39455482630f8e978ae6c3/content.htm
http://help.sap.com/saphelp_bpc75_nw/helpdata/en/79/3643be0cec44cc819cf3c7e697b2b7/content.htm
Hope this helps.

Show all dimension members

I´m not an experienced user of ssas...
I have a Dimension in a cube with more than 1000 members. Now I want to define a role where I only want to give access on a few of this members. Therefore I choose the register 'Dimension Data' in a role design and I plan to 'Deselect all members' and
check the appropriate members which I want to give access in the treeview with all members. Unfortunately not all members are shown in the treeview but only about 1000 --- and the last entry in the treeview is 'Filter members'.
Can anyone help me how I can show ALL members of the choosen dimension in the treeview so that I can choose my members by selecting them in the treeview.
Thank you for any help.
Karsten
Karsten

Hi Karsten,
It's the very useful limit. Imagine that dimension contains over 100 000 or 1000 000 members. Will be easy to select the required members? And you could get the performance problem for this reason.
So, you may use Filter members or specify the required member set by MDX
on Advansed tab.
Best regards.

Deleting dimension members

We have an AW with cubes refreshing every day. Fast solve of these cubes with incremental set of data finishes usually within an hour or two.
Our recent requirement needs for us to remove some old facts as well as a few dimension members. The facts can be cleared but we noticed that deleting dimension members (using synch load) is causing a full cube solve due to changed relations. With the amount of data existing in this AW, full solve takes about 2 days to complete. Deleting dimension members for which we never ever loaded any facts also causes the same result as above.
I was wondering if there is any way we can delete these dimension members without triggering a full cube solve.
Another question is if it is possible to update dimension primary keys inside of the AW?
Any help is really appreciated.
Database Version 11.2.0.3

These types of questions have been answered in the past by David Greenfield.
There are two ways to delete a dimension member through commands.
(1). OLAP dml command "REMOVE_DIMENSION_MEMBER" explained here: http://docs.oracle.com/cd/E11882_01/olap.112/e17122/dml_commands_2042.htm#OLADM2692
OR
(2). dbms_cube.build command:
exec dbms_cube.build(q'! "TIME" USING (DELETE FROM DIMENSION WHERE MEMBER = 'APR-2011') !');
Take a look at this old post, where David Greenfield explained it.
https://forums.oracle.com/message/9426946
There is no way to rename a dimension member in a standard-form analytical workspace. There is "MAINTAIN RENAME" olap dml command, but it will not work with dimensions created through AWM. You can add the new dimension member, then copy cube data associated with old/existing member to the new member and then delete the old member.
For cube copy data example, take a look at these old (15-Feb-2011, 16-Feb-2011 and 17-Feb-2011) posts by David Greenfield:
https://forums.oracle.com/thread/2176409

Rebuild the Dimension Flushes out Cube data

Hi David ,
I want to change the implementation details of one of my dimesion from Surrogate key to "use key data sources" . After Applying my dimension data gone ..
Now ran below :
exec dbms_cube.build('CUSTOMER using (LOAD NO SYNCH,COMPILE)');
I expect the cube compilation would be done retaining my old data with the change in dimenisons only .But all the Cube data flushes out . Any way to get this back without running complete cube load again .
Many thanks,
DxP

No, I am afraid you will need to reload the cube. Switching to "use key data sources" means that we have to remove all of the existing dimension members and hence associated cube data.

ODI Export pianning Dimension members error

HI all
ODI Export pianning Dimension members in essbase database error ：
The ODI version is 10.1.3.5
Error message:
Org.apache.bsf.BSFException:exception from Jython:
Traceback (innermost last):
File "<String>",line 89,in?
Com.hyperion.odi essbase.ODIEssbaseException:Cannot open cube view.Analytic Server Error(1030011):Invalid character in name(????) in ESSAPI function EssSetActive
At
Com.hyperion.odiessbase.ODIEssbaseMetaReader.validateSourceMetadata(Unknown Source)
At
Com.hyperion.odiessbase.ODIEssbaseMetaReader.validateExtractOptions(Unknown Source)
please help me ! think you!

Hi
Post on the ODI forum for help on this one .....
Data Integrator
Cheers
David

Deleting custom Period dimension members

Hi,
We are in Planning 11.1.2.1. and we created custom period dimension members (while creating application). Now we would like to delete one of those members (whcih is at level0). Obviously we don't see an option of delete in planning web interface. One option is to recreate the application but is there any way we can delete this member in oracle database. If yes, it would be great if you can provide us the table details.
Thanks,
Siva

As John suggested it is not advisible, however you can delete in Essbase using Planning:
1. Edit custom dimsion
2. un-select all plan type
3. cube referesh
Hope this will help.

How to Delete the dimension from the cube ?

Hi ,
how to Delete the dimension from the cube ?
i have added the new dimension by assiging one characteristic to that dimension .
now i want to delete it ,
but system saying that Dimension ZXXX contains InfoObjects; deletion not possible .
how to delete it ? any help .
Thanks

Make sure you donot have any data in cube. If you have some data in cube, then you will not be able to see Delete option.
Right click on the cube-->Delete data.
Then double click on the cube>Goto Edit mode> select the IO under that Dimension> right click> now you will be able to see the Delete option (provided you have deleted all the date from Cube)
Then right click on Dimension-->Delete
Regards,
Pavan

Hide unrelated dimension members in cube?

Similar Messages

Maybe you are looking for