Separate Dimension or Property?

Dear Friends,
One of the dimension that i'm building has 6 level of hierarchy, and client wants to display it from up to bottom, not left to right.
In that case, if i set the hierarchy to 1 dimension and utilize the properties, can i set the evdre to show it top to bottom?
On the other hand, if i set it to different dimension (i notice that we can not use same dimension twice), what is the impact? Would the performance degrades?
Thanks a lot for the assistance.
CW

Hi,
Can you refine your question, I could not understand your question.
Thanks
Sharath

Similar Messages

Force OBIEE to display attribute as dimension property and not separate dimension

Hello,
I have following question - in my project which utilizes Essbase and OBIEE I am interested in display of attribute as a characteristic of dimension and not as separate dimension.
OBIEE generates following mdx statement:
With
set [_Prod.Manufacturer2] as '[Prod.Manufacturer].Generations(2).members'
set [_Product6] as 'Filter(Descendants([Product], 8), (([Product].CurrentMember.MEMBER_Name = "P3336" OR [Product].CurrentMember.MEMBER_ALIAS = "P3336")))'
select
{ [Measure].[Volume] } on columns,
NON EMPTY {crossjoin({[_Prod.Manufacturer2]},{[_Product6]})} properties MEMBER_NAME, GEN_NUMBER, [Prod.Manufacturer].[MEMBER_UNIQUE_NAME], [Prod.Manufacturer].[Memnor], [Product].[MEMBER_UNIQUE_NAME], [Product].[Memnor], [Product].[Alias_table_1] on rows
from [APP.DB]
while I am interested in achieving following - where attribute Prod.Manufacturer is displayed as property of Product dimension and not as separate attribute
With
set [_Axis1Set] as '{Filter(Descendants([Product], 8), (([Product].CurrentMember.MEMBER_Name = "P3336" OR [Product].CurrentMember.MEMBER_ALIAS = "P3336")))}'
select
{[Measure].[Volume]} on columns, {[_Axis1Set]} properties [Product].[Prod.Manufacturer],MEMBER_NAME, GEN_NUMBER, [Product].[Memnor], [Product].[Alias_table_1] on rows
from [APP.DB]
OBIEE generates expected syntax for Alias tables, is same possible with attributes?
How ?
thx
Tomek

Thanks heaps for your answer, Vladim!
That's funny, huh? As mentioned, in respect to the Workstatus control, SAP made that functionality available for the Owner property of the Entity dimension (i.e. more than one user can be declared as an owner of a e.g. Cost Center and could hence change a particular Work Status).
Any ideas for a workaround ?
Have a good weekend...
Claus

Material attributes in separate dimension?

Hi BW experts,
As a new member I have been looking for a similar topic but unfortunately I can't find anything on it so I was hoping one of you could help me out.
I want to redesign our stock/movement cube due to performance issues. One step is to have the 0MAT_PLANT as a separate (line-item) dimension as opposed to a charateristic of 0MATERIAL. I assume this will help a great deal since 0MAT_PLANT has over 8.5 M entries which does not really help to speed up any queries. (fact table has about 40M records)
Another thing is that I would like to create a separate dimension with 0MAT_PLANT navigational attributes like service level, ABC indicator etc. These fields are now in the material dimension and I reckon these nav attr blow up the dimension massively since one material has multiple service levels and ABC indicators. Can I just drag in these field into a new dimension, say Material Attributes and still have them in there as master data?!
In other words, can I create a dimension with only 0MAT_PLANT navigational attributes and what are the consequences of this?
Thanks heaps!
Cheers,
Niels

Thanks Pizzaman.
I do not think it will be a good idea to physically put the master data in the cube in my case so I have to keep it as master data.
Can you explain to me what happens when I take the following steps:
I take out the 0MAT_PLANT characteristic (which has 8.5M records) and create a separate (line item) dimension for it and I leave the NA for 0MAT_PLANT (like service level and ABC indicator) in the Material dimension.
Would this have any impact on the number of records to be read when I run a query for plant, material and ABC indicator?
Doesn't the query still have to read the 8.5M records which are now in the 0MAT_PLANT dimension instead of the 0MATERIAL dimension?
So does creating a separate 0MAT_PLANT dimension have any impact on query performance?
I do understand you point about the indexes and that might work.
Hope you can help me with this
Thanks.
Cheers

When should an attribute be placed in a separate dimension

heyyyyy
when should an attribute be placed in separte dimension

HI,
you can't keep any attribute in separe dimension, but you can keep Charecter in separate dimension, i.e. Line Item Dimension. See the following link
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Thanks
Reddy

Linked Dimension by property , in Input Template

Dear All,
I had input template with two dimension in X Axis, Dimension Project and Dimension Account.
Each member in dimension project has account as property.
If i create input template by report editor, i use the option dimension relation selection by property.
My needs is, due my dynamic input template. I need to use selection in page axis to change the project , does anyone know how i link my account dimension to follow each project that change due my EPMDIMENSION OVERRIDE.
Thanks,
Suprapto

Hi Raju,
In Page AXIS , i use epmselect member, then i use EPMDIMENSION OVERRIDE to change the dimension Project.
My Case is Dimension Project has lot of SAP - WBS in one project.
Every SAP - WBS has different account, which is mapping at property in Dimension Project.
So my question is , is there BPC Function that can display at Row Axis
SAP - WBS ( PROJECT ) : ACCOUNT
Which is linked as dimension project property
Thanks,
Suprapto

Dimension,Dimension Member,Property and Cube in BPC

I am learning BPC. I've knowledge on relational database.
Please help me in understanding Dimension,Dimension Member,Property and Cube.

Hi,
Please refer to the below link from help.sap:
http://help.sap.com/saphelp_bpc75/helpdata/en/5A/69200C88AA40C9B18844A25259F147/frameset.htm
This link will guide you through all the BPC concepts.
Hope this helps.

Variable for one Dimension based on another Dimension's Property

Hi all,
This is a Acript Logic question.
I have a dimension called P_BUDGET_MODEL. It has a property called PROFIT_CTR.
I also have a dimension called P_PCA.
I would like to have a variable that defines the values of P_PCA based on the values of PROFIT_CTR once the user selected the P_BUDGET_MODEL.
Please note:
1. One value of PROFIT_CTR might yield fiew values of P_PCA based on a well defined logic that I can code in the script using some sort of Concatenation.
2. I want to use the variable in *XDIM_MEMBERSET P_PCA to improve performance.
3. I have authorizations defined both for P_PCA and P_BUDGET_MODEL.
4. I would like to use similar logic to define the time dimension based on the category dimension.
Any ideas?
Kind regards,
Avihay

Hello Nilanjan,
First of all thanks for your response.
I am not sure I understood. Allow me to elaborate the business scenario.
I have a distributed planning process. Various planners are responsible for various P_BUDGET_MODEL values, which are organized in a hierarchy based on these responsibilities.
When the user selects in a planning package the P_BUDGET_MODEL values, I want to run a logic that will perform calculations. In the logic I need to create data with various values of P_PCA. The values of P_PCA can be derived from the property P_BUDGET_MODEL.PROFIT_CTR.
I also have authorizations on P_PCA and they are synchronized with the authorizations on P_BUDGET_MODEL. The reason I have authorizations on P_PCA is that in various reports I have P_PCA as the display criteria and I do not want users to see all of the values. I also plan to base planning approval processes on this dimension in the future.
Since I have few users basically I needed a simple IF inside my logic, but there is no such statement.
I am a veteran BPS and IP consultant. Such a request was very easy to implement in those tools (using characteristic relations for example and also in FOX). It surprises me that it is so hard to implement in BPC.
Any new ideas?

Expanding Dimension Members Filtered by another Dimension members property.

I use BPC for SAP NetWeaver 7.5.
Iu2019ve FI_ Acc dimension. And on the property FLOWTYPE, I define which FLOW types it uses.
FI Acc dimension members as follows:
Cash   (FLOWTYPE: Cashflows)
Treade Receivales (FLOWTYPE: TRflows)
Trade Payables (FLOWTYPE: TPflows)
FLOW dimension members as follows:
    Cas_flows (PARENTH1)
       Cash Openning
       Cash In
       Cash Out
       Cash from Credit
TR_flows (PARENTH1)
    TR Openning
    TR addition from sales
    TR recived
TP_flows (PARENTH1)
    TP Openning
    TP addition from purchases
    TP paid
I want to expand FI_ Acc dimension and according to its FLOWTYPE property it expands FLOWs next to it as follows:
FI_ Acc              FLOW
CASH                      Cash Openning
                               Cash In
                               Cash Out
                               Cash from Credit
Trade Receivables    TR Openning
                                  TR addition from sales
                                  TR recived
Trade Payables        TP Openning
                                 TP addition from purchased
                                 TP paid
I have one EVEXP which expands FI_Acc dimension and another EVEXP which expands FLOW dimension. On the FILTER I write [FLOW].currentmember.properties("PARENTH1")=[FI_Acc].currentmember.properties("FLOWTYPE")
I could not get the result. Where do I make mistake? Is there someone can help me on this issue?
Or is there any other way to do this?
Edited by: Recep Budak on Nov 4, 2010 12:25 PM

Hi Bike,
According to your description, you want to add another dimension attribute based on the record dimension name, right? If in this case, you can use Case When statement to achieve it. Here is a sample query for your reference.
With Member [Measures].[Test]
As
Case [Product].[Category].CurrentMember.Name
When [Product].[Category].&[4].Name Then "4"
When [Product].[Category].&[1].Name Then "1"
When [Product].[Category].&[3].Name Then "3"
When [Product].[Category].&[2].Name Then '2'
Else "Null"
End
Select {[Measures].[Test]} on columns,
[Product].[Category].[Category].members on rows
from [Adventure Works]
Results
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Combains 2 facts (witth two separate dimensions)

Hello,
my question is- how two combain two facts, when each of them has it's own dimension?
I've got F1-D1 and F2-D2, i need to combain them by D1-D2, which contains same information- five letters code
F1, F2, D1 and D2 are in the same subject area.
Thanks for all hints:)

You could make 1 dimension in the RPD with 2 branches ending in a shared level (your 5 letter code).
regards
John
http://obiee101.blogspot.com

Concatenate text and property of dimension in script logic

hello experts,
how to concatenate text and property of dimension in script logic?
as example:
dimension : interco
property : mgmtallocdefcc
*WHEN TIME.YEAR
*IS %YEAR_VAR%
*REC(EXPRESSION=%VALUE%,ACCOUNT=12345,ENTITY="I_" [INTERCO],MGMTALLOCDEFCC)
*NEXT
then it will read all as text: I_[INTERCO].MGMTALLOCDEFCC
for example the value of property mgmtallocdefcc in interco dimension (INTERCO.MGMTALLOCDEFCC) is ABCDE.
what i expect is :I_ABCDE
thanks!

Hi Yoki,
Concatenation is only possible between text and variables %VAR% or $VAR$.
Like ENTITY=I_%SOMEVAR%
But in your case instead of concatenate you have to use other property like TARGETENTITY having valid ENTITY members:
ENTITY=INTERCO.TARGETENTITY
B.R. Vadim

How to assign One Dimension Property value to another Dimension ID

Business senario:
There are two dimensions Entity and Plant. Plant also has a property Entity.
In my Input Form, I need to derive Entity Property based on PLANT selection and should map it to ENTITY Dimension.
I have selected PLANT Dimension and ENTITY Dimension in Page Axis. I have updated EPMOLAPMember() formula with EPMMemberProperty() for deriving Entity values. When I tried to save data an error message appears saying TOT_Code is not a base level member. So I checked Edit Report window and found that ENTITY Dimension is automatically moved to default left panel from Row Axis and Entity Dimension Context Menu is mapped to TOT_Code which is the top node of the total hierarchy.
I tried EPMMemberOverride() function to overwrite ENTITY Dimension values with Entity Property of PLANT Dimension but unable to overwrite it.
In Simple Words:
ENTITY Dimension = PLANT Dimension (Entity Property)
Is there any way to map/assign property value to another dimension??? Please help me.
Thanks in advance.

Hi,
see please this thread for a possible solution http://scn.sap.com/thread/3230754
Regards
Roberto

Using multiple physical tables in a single logical dimension table

I have two physical tables that are related on a 1 to 1 basis based on a natural key. One of these tables is already part of my RPD file (actually, it is the W_EMPLOYEE_D from the Oracle BI Applications). The second table contains additional employee attributes from a custom table added to the data warehouse. Unfortunately, I don't seem to be able to display ANY data from this newly added custom table! I'm running on OBIEE 11.1.1.6.
Here's what I've tried to do. Lets call the original table E1 and the new one E2. E1 is part of the repository already, and has functioned perfectly for years.
- In my physical model, I have imported E2 and defined the join between E1 and E2.
- In my logical table for E1, I've mapped E2 to E1 (E2 appears as a source), set up an INNER JOIN in the joins section for E1 and added the attributes from E2 in the folder
- In the SOURCES for this logical table, I've set the logical level of the content for E2 appropriately (detail level, same as E1)
- In my presentation folder for E1, I've copied in the attributes from E2 that were included in my logical table
Consistency check runs smoothly, no warnings or errors. Note: E2 contains hundreds of rows, all of which have matching records in E1.
Now, when I create an analysis that includes only an attribute sourced from E2, I get a single row returned, with a NULL value. If I create an analysis that includes one attrribute from E1 and one from E2, I get all the valid E1 records with data showing, but with NULL for the E2 attributes. Remember, I have an inner join, which means that the query is "seeing" E2 data, it is just choosing not to show it to me! Additionally, I can grab the query from the NQQuery.log file - when I run this SQL in SQL*Developer, I get PERFECT results - both E1 and E2 attributes show up in the SQL - the query engine is generating valid SQL. The log file does not indicate there are any errors either; it does show the correct number of rows being added to cache. If I create a report that includes attributes from E1, E2 and associated fact metrics I get similar results. The reports seem to run fine, but all my E2 attributes are NULL in Answers. I've verified basics, like data types, etc. and when I "Query Related Objects" in the repository, everything looks consistent across all 3 layers and all objects. E2 is located in the same (Oracle) database and schema as E1, and there are no security constraints in effect.
I've experimented with a lot of different things without success, but I expected that the above configuration should have worked. Note that I cannot set up E2 as a new separate dimension, as it does not contain the key value used to join to the facts, nor do the facts contain the natural key that is in both E1 and E2.
Sorry for the long post - just trying to head off some of the questions you might have.
Any ideas welcomed! Many thanks!
Eric

Hi Eric,
I would like you to re-check on the content level settings here as they are the primary causes of this kind of behavior. You could notice that the same information might have written down in the logical plan of the query too.
Also, as per your description
"In the SOURCES for this logical table, I've set the logical level of the content for E2 appropriately (detail level, same as E1)"
I would like to check on this point again, as if you had mapped E2 to E1 in the same logical source with an inner join, you would get to set the content level at E1 levels themselves but not E2 (Now, that E2 would become a part of the E1 hierarchy too). This might be the reason, the BI Server is choosing to elimiate(null) the values from E2 too (even you could see them in the sql client)
Hope this helps.
Thank you,
Dhar

One dimension used twice in a cube

I have one dimension, but it has two meanings. How can i use the same dimension twice in the same cube as it was two separate dimension?
Example:
There is dimension "Region". The fact table has two keys. First key means - "region of birth", and second "region of living". So one dimension has two meanings.
I tried put the same dimension twice with two different aliases in one cube. OEM shows such cube as valid, but querrying it through OLAP API, or building analytic workspace based on this cube is impossible (error ORA-1007).
The only workaround i see is to build two separate but identical dimensions.The bad side of this is that i have to create two separate but identical tables of data for those dimensions (i can't create two levels from the same column).
Raf
i work with Oracle9iR2

i did the same on Oracle9iR2 with OEM 9.2.0.1.0.
Creating the cube with two aliases for one dimension was ok.
But creating MOLAP cube from that source cube using AWM was impossible .
Also querrying that cube (the one created in OEM) for example through Discoverer or Excel is imposible.
I searched forums on that question, and some people had the same problem, but no answer.
Raf

[BPC 10] Member/property specific formatting

Hi,
I am trying to use specific member/property formatting in an input form in BPC 10. My account dimension has a property called format and I have used 3 different indicators, T,R and P.
In my input form I have activated the EPMFormattingSheet and under the dimension member/property formatting I have activated column formatting on specific member/property.
If I add one rule on my account dimension (such as FORMAT = P) the formatting is applied. However, I would like to have two different formats, once for FORMAT = R and one for FORMAT = P.
However, irrespective of the order, the second format is ignored.
Does anyone know how I can get two such formats working?
Thanks,
Arnold

Apparently property formatting only works for one member per property ...

Fact Tables without Dimension Tables.

Hi,
I am currently working on a project where a data warehouse is being developed using an application database as the source. Since the application database is already normalised, the tables are being loaded in as they are and the consultant involved is creating
data marts for them. I have asked about why he is not creating separate dimension and fact tables as data marts, and he has told me that he will create a fact table with the dimensions as column names without any dimension tables created as you might expect
as per star/snowflake schema.
Is this right, as I always thought you had to have dimension and fact tables, especially if you want to start using SSAS?
Regards,
W.

create a fact table with the dimensions as column names without any dimension tables created as you might expect as per star/snowflake schema.
This is the trouble with denormalization: where is the stopping point?
If the data warehouse is the source for SSAS OLAP cubes, it is better to go with the usual star schema.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

Separate Dimension or Property?

Similar Messages

Maybe you are looking for