Arranging Hierarchy tables in BMM layer

Hi
I have a different structure of dimensions in the database.
Year->Season->Quarter->Month->Week
For every level in Hierarchy I have table i.e, Dim_Year, Dim_Season, Dim_Quarter, Dim_Month, DIm_Week
They are joined in physical layer in as per the hierarchy thats is Dim_Year is joined to DIm_Season by Year_id, Dim_Season is joined to Dim_Qaurter by Season id and so on.
In BMM layer I have to craete an Hierrarchy.
How should i keep these tables
Option1: Pull the all the tables separately
Create comples join between all the dim tables year->Season->Quarter->Month->Week
Create hierarchy from these tables
Option2:
Create a logical tables as Time
Pull all the tables into Time table with different Logical table sources.
Then create a hierarchy from these tables.
This will avoid the comples join in BMM layer
Please suggest which option will lead to less performance issue and which is ideal approach in such scenarios.
Thanks in Advance

Hi,
I am new to OBIEE but still I am suggesting one option....
Drag and drop any one of the Time table (for ex Dim_Year) from physical layer to bmm layer. create a complex join of this table with the other tables in the bmm layer. then simply drag and drop the columns from other tables (Dim_Season, Dim_Quarter, Dim_Month, DIm_Week) from the physical layer one by one on the LTS of Dim_Year.
Hope I haven't given you a funny answer.
Edited by: user9149257 on Mar 8, 2010 9:20 PM

Similar Messages

What is the use of Multiple source in Logical Table under BMM Layer?

what is the use of Multiple source in Logical Table under BMM Layer?
thanks in advance

Or more generally speaking:
To create a "logical table" consisting of multiple "physical tables"...hence the names. It's the backbone of the whole BI server concept and the way the rpd handles the requests.
I.e.: how would you otherwise proceed for making an analyzable table from SAP, Teradata, Oracle and a flat file with no full change-access to all the data sources?

Facts and dimension tables in BMM layer

HI Experts,
i have one doubts that is.... i have 7 Fact and 20 dimension tables in my current project ( this is mine first project ) how can i join these tables in BMM layer...
Regard's
Harish

Harish,
Just explicitly mentioning # of facts and dimensions won't fetch you any help. Extract a simple business scenario containing a fact and dimension tables.
e.g.
1. firstly, how many of the fact tables built are associated with different subject areas?
2. of the fact tables belonging to each subject areas, how many of them are aggregate tables?
3. if step 1 is not true, do they have conformed dimensions to access? <-- a caveat exists which your user MUST definitely know.
4. are there any partitions?
5. are they aggregate or summarized tables?
etc,....
based on which your modelling will start.
-bifacts :-)
http://www.obinotes.com

How to determine the logical Keys of logical fact table in BMM layer?

Hello guys
I'd like to know more about how to know what columns of the logical fact table should be used as key in BMM layer. How OBIEE behaving differently when different keys are selected?
In my situation, I have 1 fact table that physically joins to 20 dimensions in physical layer. Therefore, in physical layer, this fact table has about 20 foreign keys but no primary keys..
In the logical layer, this fact table is logically joined to the same group of dimension tables. So in this case, how do I know what columns in logical fact table I should use as keys?
Please advice
Thanks

thanks for the reply...
The interesting thing I notice is that, when I start using fragmentation with the fact tables in its LTS, if not primary key is defined in the logical fact table, then I will be getting errors:
[nQSError: 10058] A general error has occurred. [nQSError: 14023] None of the fact sources for columns are compatible with the detail filter []. (HY000)
When I create the key by choosing random columns from the fact table as the logical key columns, this error goes way and the correct SQL is generated according to the frag..
Because of such behavior, I'd really like to know how logical key really works in BMM layer.

How to create logical fact table in BMM layer ?

Hello,
I have 3 Dimension table - 2 are in one schema and last is another schema. Using this 3 dimension tables, I need to create a logical fact table.
So, my question is whether we can create this fact table by joining these 3 dimension table which are in 2 different schema s ?
Thanks

Fiaz,
you are correct. We can use tables from different subject area to create a report. However, my question was related to rpd design. Sorry, I was not very clear about the queries earlier.
Here is the whole scenario in the physical layer of the rpd
Table name      Databse name      Connection pool name      Schema name
AV          AV_PXRPAM     AVAILABILITY          CRMODDEV
OUTAGE          AV_PXRPAM     AVAILABILITY          CRMODDEV
COMPANY          PXRPAM          PXRPAM_POOL          CRMODDEV
AV and OUTAGE have the joins already. I want to make a join between COMPANY with OUTAGE. And then I want to include a column from each of above tables to the logical fact table in the BMM layer. then I want to do a star schema with the logical fact table to the above 3 tables in the BMM layer.
Thanks

Display of yellow colour icon to a table in BMM layer

Hello all,
Please ignore my previous thread. By mistake it went without any description of problem. Sorry for that.
I have two tables org details, emp details
org details having columns like orgname, year, quarter1 results, quarter 2,quarter 3, quarter 4
emp details having columns like org, year, emp in quarter1, quarter2,quarter 3, quarter 4.
Spread sheet as datasource and imported to physical layer....when i drag drop to BMM layer...emp details table icon showing yellow.
But it's not a fact table...those two are normal tables....why is it showing yellow colour icon?
please let me know the concept of how OBI administrator tool decides that the table is fact table or dimension table.
regards
chandra kanth.

By default OBIEE will show yellow colour.Once you create joins in BMM layer then it will show colours accordingly.Table on n side in 1:n join will be shown as yellow(Fact).So create joins in BMM layer.
Regards,
Sandeep

Unable to create logical dimension in bmm layer

Hi all,
I am not able to create a logical dimension hierarchy in the bmm layer of the rpd.
when I right click on the table I am not able to find the create logical dimension option in the popup window.
could you please help me out in this?
In the logical table we have data from sql statement also.
Thanks!

Create Dimensions is only available if the selected logical table is a dimension table (defined by 1:N logical joins) and no dimension has been associated with this table.
To create a dimension automatically, the Administration Tool examines the logical
table sources and the column mappings in those sources and uses the joins between physical tables
in the logical table sources to determine logical levels and level keys.
Hope you have defined the Logical join in BMM before looking for this option. If joins are not defined, this option won't come.
Refer http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf
Page 133, Creating Dimensions Automatically
Hope its useful

Problem with BMM layer warning messages.

Hi,
I have modelled with the following tables in BMM layer.
Dimension tables: Regions,Countries,Departments, locations, Employees, jobs, job history
Fact table: HR Facts (measured columns like salary, max salary, min salary, commission)
The model is consistent with the following warnings:
Logical dimension table REGIONS has a source REGIONS that does not join to any fact source.
Logical dimension table DEPARTMENTS has a source DEPARTMENTS that does not join to any fact source.
Logical dimension table COUNTRIES has a source COUNTRIES that does not join to any fact source.
Logical dimension table LOCATIONS has a source LOCATIONS that does not join to any fact source.
and also in the answers section (Presentation services) i could not able to view data, it's giving the following error (when i am trying to display REGION NAME field values)
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: REGIONS.REGION_NAME. Please fix the metadata consistency warnings. (HY000).
I could not able to trace the problem where exactly is to be fixed.
regards
chandra kanth.

Hi,
Thanks for the information. Ideally that works out without any hierarchies. But the problem with which i was facing is somewhat different.
Let me explain the problem scenario exactly:
I have an employee, region tables in physical layer. Employee table has SALARY Column. Region table dont have any
join with Employee table. In BMM layer i have created a fact table "HR Facts" and crated a logical fact column SALARY.
The logical fact table source is Employee table. I have drag dropped Region table into BMM layer and joined with HR
Facts table. While consistency check its given a warining message: Logical dimension table REGIONS has a source
REGIONS that does not join to any fact source.
What is the problem exaclty?
regards
chandra kanth.

Drilldown in answers without creating dimensional hierarchy in BMM layer?

Hello All,
HELP! I have a main report like this:
title: Region EAST (prompted field- user entered: North, South.... )
heading: Departments Total Sales
rows: Meat (01) 500,000.00
Produce (02) 100,000.00
Organic Items(03) 250,000.00
Users wanted to ClLICK on either Meat, Produce or Organic Items field to get the detailed report on that particular dept. and would prefer to Click on the desired field than using department as a prompted field. :(
I did try to use the navigate function on Departments column to get to the detail report, but the results came back with ALL departments. Is it possible to drill down in answers without creating the dimensional hierarchy in BMM layer? If so, please show me how to create the link that would navigate to the detailed report when users CLICK on desired department, ex: Meat (01)? BTW, detailed report may came from different resources (data is in the detailed table...) and I still need to pass the region variable to the detailed report.
I really need a big help on this.
Thanks All in advance!

Hi Matt,
thank you for looking into this problem.
I did use the Navigate function on the 1st report, create a prompted filter on the depatment column (second report) but user can only click on the high lighted Department column header (on the first report) which navigated to the 2nd report and it displayed detail of all departments. Since users cannot click on a particular deptpartment, therefore I cannot pick up the value (01) for Meat department to pass thru the 2nd report. Is the Navigate function just works only when you click on the header column not on the data values in that column? do I need to set any other function to the department column on the 2nd report beside the filter?
thanks for your help!

Problem creating hierarchy in BMM layer

Hi,
We are trying to create hierarchy for one of the dimension which contains 10 LTSs, each LTS represents Bridge-->Dimension join in physical layer. So, each LTS contains inner join between Bridge and Dimension tables.
We performed the following.
Right click on Dimension and select Create logical dimension--> Dimension with Level-Based hierarchy.
The error is "Admintool is unable to create the structure for the dimension <<Dim name>> "
Can anybody help..
Thanks,
Anilesh

Hi,
Here we have created 10 LTSs for supporting 10 bridge tables. We are joining same dimension table with multiple bridge tables in physical layer. And each bridge is joined with corresponding fact table. when id comes to BMM layer, we created single dimension which contain LTSs for each bridge table, and we joined the dimension to fact.
Thanks,
Anilesh

Tables icon displaying yellow in BMM layer.

Hi all,
When i was tring to drag drop tables from physical layer to BMM layer it's showing yellow icons.....
Scenario is as follows:
tables: EMP, DEPT, BONUS, SALGRADE.
I have created complex join in Physical layer between EMP and SALGRADE (condition is "EMP$".SAL BETWEEN "SALGRADE$".LOSAL AND "SALGRADE$".HISAL). Samething i have taken into BMM layer. 4 table icons showing yellow and checked for consistency..giving errors like there is no join of logical tables.
i have created join Physical layer will it not carry to BMM layer? Do i need to create same complex join in BMM layer? After creating the complex in BMM layer will those errors come again??
Please aswer to my questions..asap.
regards
ck

Chandra kanth wrote:
Gurus,
The other two tables (DEPT, BONUS) are not required to join but i just kept it like that in BMM layer.
1. I have created complex join between EMP and SALGRADE in physical layer and i also manually created complex join in BMM layer....it did not come when i drag drop the schema from physical to BMM layer. Do we require to create manually again the complex join in BMM layer?Yes.
>
2. After creating complex join in BMM layer EMP table icon shows white others are yellow. Will complex join not suffice to make error free (Consistent) in BMM layer?
Is it require to join all tables (to maintain a star schema)?
You need to create complex joins to create a star schema in BMM layer. This is needed to create an error free BMM layer.
3. As per the requirement i dont require to join other two tables (DEPT, BONUS).
What is the purpose of these tables?
>
Please advice if i am wrong in the above cases....and also please answer to all my questions.
Thanks in advance
chandra kanth.

Changing the LTS mapping in BMM layer to new Physical Alias table

Experts
I need to change the source table mapping in my BMM layer to new physical tables aliases.
I have finished BMM layer design (column name changes, business friendly names etc.) before actually creating the alias tables in the Physical layer and I know I hv to run for hiding now. I expected changing the logical source mapping to the new aliases will work but it's not the case though it works partially. Since the Column names are changed in the bmm, I have to manually change the Expression, Physical Table in the LTS column mapping tab for each non-matching name logical columns.
Column mapping is intact where both the BMM columns and the new Physical alias names match.
eg: CALENDER_YEAR(BMM) ---> CALENDAR_YEAR(Physical alias) mapping is intact but
Week Day(BMM) ---> WEEK_DAY(Physical alias) need to be changed manually.
Any tips/suggestions will be appreciated.
Regards,
Tom

Hi Tom,
I too do not see any other options here other than manually modifying the individual logical columns. When there is a new logical column, we have to map it manually to the physical column explicitly because the Admin tool will not know which physical column to pick up.
Hope this helps.
Thank you,
Dhar

Regarding BMM layer

HI All,
I am working on designing BMM layer. I have many facts and dimensions, few of the dimensions are confirmed.
1. could you please let me know how the BMM layer. Can i create Fact and related dim joins for each fact or can i create one logical fact table with all facts as LTS and join with all dimensions.
2. Do I really need to create Hierarchies for all Dims or necessary one.
Hope your reply soon.
Regards,
Shaik

create each LTS for each fact. If they are agg Facts they have to be in same logical table.( for optimised query path)
Physically join facts with required dimensions.
If there are facts which have some dimensions not conformed, better to have them as new logical Fact table.
It is a best practice to have dimension hierarchy. If you dont have detailed hierarchy just keep it total->detail -> key.
do also mentions number of elements in dimension that also optimizes the query path.

Sum Aggregation Error in Physical & BMM Layer in OBIEE 11g with Essbase 11

Hi everyone,
I'm using OBIEE 11g with Essbase 11 as the data source. I'm using Sample Basic database from the Essbase as my data source. If I'm using the hierarchy for the measures (so I don't flatten the measures), and when I changed the aggregation in both physical and BMM layer from Aggregate_External to Sum, I can't create a report at all from the Answers.
Does anyone encounter the same thing? Any ideas/solution about this? Please help.
Thanks a lot!

Hi Deepak,
When I picked the "Basic - measure" alone, I got this error.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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: 96002] Essbase Error: Unknown Member Basic - measure used in query (HY000)
SQL Issued: SELECT 0 s_0, "Sample Basic"."Basic"."Basic - measure" s_1 FROM "Sample Basic".
When I picked the "Gen1,Measures" alone from the measure dimension, I got this error:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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: 46008] Internal error: File server\Query\Optimizer\ServiceInterfaceMgr\SIMDB\Src\SQOIMDXGeneratorGeneric.cpp, line 2610. (HY000)
SQL Issued: SELECT 0 s_0, "Sample Basic"."Measures"."Gen1,Measures" s_1, SORTKEY("Sample Basic"."Measures"."Gen1,Measures") s_2 FROM "Sample Basic"
But when I queried the dimensions one by one (only single dimension each), no error was shown.
This only happens if I use Sum in the physical and BMM layer. If I use External_Aggregation, these errors do not happen. And if I flatten the measures, these errors also do not happen.

How to compare data cross 2 different tables in logical layer?

Hello
I have run into a situation where I need to bring in a new column from the status table say 'flag'. This physical column then needs to compare itself with the sales fact's code column. So if the code is '100' and above, then flag column should be '0', else flag.
In the data models, the sales fact joins to status dimension physically and logically.
So in the expression builder of the flag column in my BMM layer, I have something like *(case when Sales Mart. Sales Fact. status > '100' then '0' else Sales Mart. Sales Fact. flag end)*..
However, although the syntax is correct in the expression builder, however the logical column doesn't accept that expression via 'invalid expression'.
I think I know the problem, because flag column and status column are from different physical and logical column therefore it can't be used in the case statement at logical level. Because I tested this theory with '*(case when Sales Mart. Sales Fact. status > '100' then '0' end)'* and it accepted it.
Nonetheless, I can't modify the database table nor the ETL to put both columns in one table, nor am I allowed to defined such expression at answers.
Is there a way I can base the result of flag column on the data of status column from a different logical table?
Please advice!
Thanks

Follow these steps:
1) Bring your first time period in your main report. This will be your first query.
2) Bring your second time period in a subreport. This will be your second query.
3) Bring the values from your subreport into your main report using shared variables.
4) Lastly, compare the results using formulas in your main report.
I hope this information proves useful.
Regards,
Zack H.

Arranging Hierarchy tables in BMM layer

Similar Messages

Maybe you are looking for