Bridge to heirarchy level of dimension

Hi,
We have a fact table with sales records and customer dimension related to it.
The customer dimension has customerID as its PK. It also has at attribute of Customer Group, so several customer can belong to one customer group.
Now I've added a bridge table to connect a Conference dimension to the Customer Dimension (many to many) but if I join it by customer ID (not by group) then when slicing the cube by conference it only gives me the sales of the specific customers that participated
in the conference, while I would actually like to view sales of all the customer GROUPS that participated. (But I can't join the bridge on groups since group is not PK of customers dimension).
What is the correct procedure for this?
Thanks
Namnami
please help-

Hi,
From one dimension table you can create a alias table and from it create 2 hierarchy levels by giving different names.
One should look like Region-->Country-->City
second hierarchy Region-->Country
This way you can create 2 sheets for the users,so any one can be applied drill path.
Hope it helps you.
Best Wishes,
Kranthi.

Similar Messages

Problem in Aggregate with Multiple level of dimension

Hi,
I have a BI repository with a snowflake schema. I have also designed the business model with snowflake, It works with drilling and all but I am facing problem when I am
creating a logical column aggregating with a higher level of dimentation. Let me illustrate that :
I have the Following Hierarchy :
Tournament(id, Name) ---- > Round (id, name, tournament_id) -------> Match (id, Name, RoundId ) | Match is fact table and other 2 dimension.
I also created a logical dimension called tournament with 3 levels.
Now say I want to create a logical column Total Number of Matches , aggregating to the dimension level of Tournament. The result gives counts a 0 for every tournament. However
it is working perfectly when the dimension level is Round (which is the immediate next level after fact).
The Logical request generated (in case of Tournament level) :
   MatchId:[DAggr(Measure1.MATCHID by [ Matches$.TournamentId] SB Tournament)] as c1 GB.
    There is no such column as TournamentId in Matches$ table. How does the BI server got this ?
   The execution plan evaluate this:
     cast(NULL as INTEGER ) as c1 GB [for database 0:0,1]
   Can someone please explain why is this happening, is it because of the snowflake schema, but I guess if BI server can handle a snowflake schema it should work the Aggregate
   properly in multiple levels of dimensions, or it is something I am doing wrong.
   Execution Environment:
     Windows XP , OBI 10g on OC4J. Data source : MS Excel (ODBC 3.5)
Regards,
Ru

Hi,
With reference to your question.
Can any operator perform this task..I don't think any single operator will help you.
I suggest using an intermediate (staging) table by using a PL SQL procedure with output port to store the values of account number provided the number of accounts are limited. Else use an array variable for account of an employee.
In short no simple solution because of the bad source design else the pivot/unpivot operator would have helped you.
Cheers
- Mohammed

Lowest Level in Dimension

HI guys
i have rdbms 9.0.4
can i define lowest level of dimension that is not the primary key of the dim table ( this field has unique values)
or the lowest level of dimension should be the primary key of the dimension table.
thanks alot.
Brad

Hi Matt!
Glad to read you again!
I agree with you that in this simple example, I should be able to make this a star schema.
but :
- on a functional point of view, this date is an attribute of a vehicle, not of an invoice. But let's ignore this.
- this problem is the same as one we have in another part of the BM, which is much more complex. In this complex BM, I can't use star schemas because it removes some joins we need in order to perform some reports.
This is why I'm looking for another way to proceed.
If you have time to spend on the complex BM, here is a simplified description :
* in the physical layer, I have:
- a calendar table with multiple aliases to be used with each dates in the following,
- an invoice header table
- an invoice detail table
with
some header date -> header table -> detail table
some detail table -> detail table
* in the logical layer (stars), i have:
- my calendar dates with their dimensions
- an invoice dimension table with the two sources (header + detail) + its dimension
- an invoice header fact table
- an invoice detail fact table
header date -> header fact
invoice dim -> header facts
invoice dim -> detail facts
detail date -> detail facts
I mus be able to query details facts while showing or filtering the header date. In such a configuration, you'll understand it isn't possible as there isn't any relationship between the detail facts and the header date. This is why the header date should be kept as a dimension of the invoice dimension, which is similar to my basic example.
Unless I went wrong somewhere?
Thanks!
Ced.
Message was edited by:
ced

Populating cube on any level other than last level of dimension

I have an employee cube with three dimension in warehouse builder. i have a measure to count employees in this hierarchy division > department > sub_department. i have to sum salaries also but data is available up to division > department.
how can i do it in the same cube using same dimension while cube mapping provide me the last level of dimension sub_dept_code. can i populate at department level instead of sub_department for this measure only while not effecting other measures data.
thanks
muhammadimran

Muhammadimran,
I don't think you'll be able to do this. The FK relationships between the fact table object and dimension table objects (regardless of the dimension and cube representations) will join only to the lowest level. I'm not sure I quite understood your post - is it that you don't have data at the lowest (sub-dept) level, or that you want to be able to see the sub-department data, but also summarize it up to the department and division levels?
Assuming you mean the latter (i.e. you want to see subdepartment data, but also summarize it to department and division levels), you simply use a sum() in the SQL. Any and every BI tool you'd put on top of this will do that.
If this is more of a performance issue - i.e. it takes 20 minutes for data to come back at the summarized levels...then take a look at creating materialized views and using query rewrite. All in all, you don't want to try to store facts at different levels in the same fact table (although OWB was obviously set up to allow this....it doesn't work well in practice).
Hope this helps,
Scott

Displaying non-level determining dimension attributes in bibeans with cwm2

In the bibdemo example (defined using the CWM API), the attributes PROD_COLOR and PROD_SIZE are defined as dimension attributes of the Product dimension. They are then available to bibeans applications for use in the query editor/match condition (as where clauses e.g. where Size = LARGE).
When I define OLAP metadata objects using the CWM2 API, my non-level determining dimension attributes are not available in the bibeans query editor.
Has any one exprienced this problem? Is there a work-around or code fragment that explains how to get dimension attributes defined using CWM2 to work in bibeans apps.

basically there are list and hierarchical dimensions.
the first type doesnt have a hierarchy, so some sort of special case of the 2nd.
i used attributes on list dimensions successfully in the past.
the only thing i had to do is nevertheless define a "artificial" level.
let me know if you need more,
thomas

Drill down is not working in 3rd level of dimension hirarchy

Hi,
drill down is not working in 3rd level of dimension hirarchy,any issues. once i clicked on 3rd level it goes to detail level instead of going to 2nd level
thanks

any updates

OBI EE 10g: Bridge tables and Based on Dimensions Aggregation

hi experts,
i am working on OBI EE 10 g (10.1.3.4)
The BM&M layer consist of:
1) Logical fact table "Sale_Indicators"
Fields: SALE_ID (PK, FK),
D1_ID (FK),
D2_ID (FK),
Indicator1 (measure, level of granularity: SALE_ID),
Indicator2 (measure, level of granularity: SALE_ID),
Indicator3 (measure, level of granularity: SALE_ID)
2) Logical dimension table
"Sales" (PK: SALE_ID),
"D1" (PK: D1_ID),
"D2" (PK: D2_ID),
"Customers" (PK: SALE_ID, CUST_ID) - bridge table!
"Products" (PK: SALE_ID, PROD_ID) - bridge table!
3) Dimensions: SalesDim, D1Dim, D2Dim, CustomersDim, ProductsDim
If fact table is joined with bridge table, the number of rows in fact table is multiplied, for example:
D1_ID | SALE_ID | CUST_ID | Indicator1
777 | 1 | 14 | 10
777 | 1 | 17 | 10
777 | 2 | 15 | 12
888 | 3 | 16 | 20
888 | 3 | 17 | 20
888 | 4 | 19 | 30
I need to get report:
D1_ID | Indicator1 (SUM)
777 | 22
888 | 50
and with filter by customer, for example (CUST_ID = 17):
D1_ID | Indicator1 (SUM)
777 | 10
888 | 20
i am trying to use "based on dimension" aggregation, for example (Indicator1):
Dimension Formula
CustomersDim MIN
ProductsDim MIN
Others SUM
The generated physical SQL performs joining EVERY dimension to the fact table, even though they are not included in the final result set.
Is there any way to tweak logical or physical model in order to eliminate excessive joins?
Thanks in advance!
Edited by: 859688 on 31.10.2011 4:04
Edited by: 859688 on 31.10.2011 4:06
Edited by: 859688 on 31.10.2011 4:08

I found this text on the help, but I didn't understand, because when I check the "based on dimensions" check box, I can choose aggregation rules for each dimension, not only the time dimension.
Also, I found in the help menu:
"In the Aggregation tab, select the Based on dimensions check box.
The Browse dialog box automatically opens.
In the Browse dialog box, click New, select a dimension over which you want to aggregate, and then click OK.
In the Aggregation tab, from the Formula drop-down list, select a rule."
I did the same steps suggested by the text above, but it didn't work.

Level based dimension

Hi All,
I have requirement to implement level based hierarchy using the fields from three different dimensions. The three columns are in three different tables. On all the examples I have seen all the components/fields for level based hierarchy are from one single dimension table( like country, region, state,district from Region table).Is there a way to create level based hierarchy from different dimension tables.
Thanks,
Virat

Hi All,
After I created the level based hierarchy dimension for logical table which have 3 LTS. I am getting the following warning.
"Logical table hierarchy has a source D1 that does not join to any fact source."
Thanks,
Virat

Querying Levels in Dimensions joined to the Facts

I created a location dimension using the standard levels, i.e., region > subregion > country > state > location_id. I then attached it to a sales fact that had the location_id as the key, but when I tried to query the cube by it's levels the only level I see is the location_id level which is at the state. None of the other levels appear or are queryable when I do something like:
SELECT * FROM vw_SALES_CUBE A, vw_LOCATION_DIM B
WHERE A.LOCATION_DIM = B.DIM_KEY
AND A.LEVEL = 'COUNTRY'
Only one level comes up although in the location_dim all the other levels exist the join does not carry them over. The data for the levels appears in the COUNTRY_LONG_DESCRIP column and not in the LEVEL column.
What am I doing wrong. Are there other objects I need to create like an MV.
jrod

I was thinking that is if I created a cube such as the one described in the thread and that I did a query along the LEVEL_NAME that the cube would fetch the data without the need for me to create say MV's aggregateing the data. For example,
/* The following is a basic query against a fact table */
SELECT T.CALENDAR_YEAR_DSC TIME, SUM(F.SALES) SALES
FROM TIME_DIM T, UNITS_FACT F
WHERE T.CALENDAR_YEAR_DSC IN ('2005', '2006')
AND T.MONTH_ID = F.MONTH_ID
GROUP BY T.CALENDAR_YEAR_DSC;
/* The next query fetches the exact same results from a cube using filters: */
SELECT T.LONG_DESCRIPTION TIME, F.SALES SALES
FROM TIME_CALENDAR_VIEW T,
PRODUCT_PRIMARY_VIEW P,
CUSTOMER_SHIPMENTS_VIEW CU,
CHANNEL_PRIMARY_VIEW CH,
UNITS_CUBE_VIEW F
/* Apply filters to every dimension */
WHERE T.LONG_DESCRIPTION IN ('2005', '2006')
AND P.LEVEL_NAME = 'TOTAL'
AND CU.LEVEL_NAME = 'TOTAL'
AND CH.LEVEL_NAME = 'TOTAL'
/* Join dimension views to cube view */
AND T.DIM_KEY = F.TIME
AND P.DIM_KEY = F.PRODUCT
AND CU.DIM_KEY = F.CUSTOMER
AND CH.DIM_KEY = F.CHANNEL
ORDER BY TIME;
In these two queries I fetch the same grain. So why is it that the cube has not precomputed these factors. What do I need to do this?

About levels in dimensions

When creating a cube I can choose the level of the dimension when creating the foreign keys. Why does OWB support other than the lowest level? I tried to use another one (month instead of day) but I got an error when validating. So I have to create another dimension with lowest level month?
Regards,
Torsten

Unfortunately, this is currently not supported in OWB.
Regards:
Igor

Restrict the number of detail level of dimension hierarchy

Hi,
I must restrict the hierarchy level on each answers report differently.
For Example,
For Report A -> Region - Country-City
For Report B -> Region - Country
is there any way to do that using one dimension table?
Thanks..

Hi,
From one dimension table you can create a alias table and from it create 2 hierarchy levels by giving different names.
One should look like Region-->Country-->City
second hierarchy Region-->Country
This way you can create 2 sheets for the users,so any one can be applied drill path.
Hope it helps you.
Best Wishes,
Kranthi.

Bridge table to Role Playing Dimension

Hi,
Fact Sales table has role playing Customer dimension table related to it. For each role it had a relationship in the DSV. One on CustomerA the other on CustomerB.
Now I have a trip dimension which should have a many to many relationship to the customers table. So I set a bridge table relating trip to customer.
But when I slice by trip it only displays the sales that have CustomerA in the trip.
I want it to display the sales that have CustomerB in the trip.
How can I affect that?
Thank you
Namnami

When you create a M2M relationship, you specify 2 dimensions and one intermediate measure Group.
Even if the bridge table is loaded once in the DSV (even if you can just duplicate it to simplify its naming), you define two measure groups for the bridge table, one connected to Customer A and Trip A, and the other to Customer B and Trip B. Then, you define
M2M relationship between Trip A and Customer A using bridgeA as intermediate, and do the same for B.
Again, please, since M2M require understanding how it works internally, I suggest you to read the White paper I mentioned, because you have all the information there that will allow you to design the model you need. I think it's not a discussion that is
easy to complete in a forum thread, because M2M involves many side consequences in calculation (e.g. what happen to unrelated dimensions involved in calculation?).
Marco Russo (Blog,
Twitter,
LinkedIn) - sqlbi.com:
Articles, Videos,
Tools, Consultancy,
Training
Format with DAX Formatter and design with
DAX Patterns. Learn
Power Pivot and SSAS Tabular.

Heirarchy Level in BW Rerports

Hello Experts,
Need to show the Activated Hierarchy Level in the reporting header (Upper left corner of the Excel Sheet). Is there any way. I tried out the option of activating the display option if the "Value of Nodes" in the properties of the hierarchy. Did not work. Do help me out.
Thank you,

Hi Marc,
In the query designer screen when you choose an hierarchy. In the Properties below it you have the option of choosing 'Expand to Level'. It gives a number by default. But you can change that also. so I want this number to be displayed in the Excel sheet with the Hierarchy 'Text' or 'Key' which ever option we choose. Hope I am clear.
Thank you..

Help on Setting logical Levels in Fact tables and on Dimension tables

Hi all
Can any body provide any blogs or any king of material on what exactly is levelling .
Like after creating the Dimensional hierarchies we need to set the logical levels for the LTS of fact tabels ri8 .So what is the difference between setting logical levels to fact tabels and also Setting levelling on Dimension tables .
Any kind of help is appreciated
Thanks
Xavier.
Edited by: Xavier on Aug 4, 2011 10:50 AM

I have read these blogs ,but what my question is
Setting the logical levels in LTS of Fact tables i understood .
But we can also set the logical levels for dimensions also ri8 .I didn't understand why do we set the logical levels for dimensions .Is there any reason why we go with the levelling at dimensions
Thanks
Xavier
Edited by: Xavier on Aug 4, 2011 2:03 PM
Edited by: Xavier on Aug 4, 2011 2:32 PM

Incorrect pdf dimension shown in Bridge CS3

I didn't see that this problem has been posted previously, but the dimensions shown for pdf documents in Bridge are much smaller than the actual document dimensions. It would be nice if I could confirm the page dimensions without opening a pdf in Acrobat, but that's not possible when Bridge reports page dimensions like 2.6" x 3.5" for an 8.5" x 11" page size pdf document.

I'm also looking for an answer to this one. It's been bugging me for over a year now. Does anyone have any clues at to how to get Bridge to display the correct dimensions for PDF files? It would be even better if it would display the dimensions of the TrimBox as a separate option too - although I'd just be happy with anything that worked at this stage!

Bridge to heirarchy level of dimension

Similar Messages

Maybe you are looking for