Model in BMM

Hi Everybody,
i have following model in physical Layer
I want to build that in BMM.
A -< B
A -< C
A -< D
E -< B
F -< B
B -< D
Actually, B is containing some facts. But if we drag the same physical layer to BMM, B is appearing as Dimension.
B, C, D are facts in other bi tool model.
Can you please tell me how to build the BMM Model
Thanks

Hi,
If B is a mix of dimensions and facts then your physical model is incorrect, it should be one or the other. Make an alias of B which will act as the fact in the physical layer, then it will be something like this:
A -< B_Fact
A -< C
A -< D
E -< B_Fact
F -< B_Fact
B -< D
B -< B_Fact (This will really be a one to one on the primary key for B)
When you drag this to the BMM layer it should work, as it will create a seperate logical table for the dimension and the fact version of B.
Regards,
Matt

Similar Messages

BMM model for subquery

Hi All,
I have a requirement to pull the generate sql for the report.
select distinct T.Sum,A.Region,A.Section
from A
join ( select sum(Amount),Region from B
group by Region)T
B on A.Region=T.Region
What is the best practice to generate this query with sub query in BMM layer?
Do we need to create a view ( select sum(Amount),Region from B
group by Region)with subquery in physical layer and join with Table A
or there is other better way of modelling in BMM layer.
Thanks,
Surya

Hi All,
Thanks for your kind reply. The problem is that there are 3-4 layers of nested queries. How can we tackle these issue on BMM layer?
for example
select distinct X.Amount,C.Amount2,C.Region,C.Section
select distinct T.Sum,A.Region,A.Section
from A
join ( select sum(Amount),Region from B
group by Region)T
B on A.Region=T.Region)X
on X.Region=C.Region and X.Section =C.Section
group by
C.Amount2,C.Region,C.Section
Thanks,
Surya

Data Modeling:Criteria to add a logical column to a DIM or FACT table

Hi,
Scenario:
Physical Layer:
- Table_T has following columns: COL_A, COL_B, COL_C
- COL_C is a measure. COL_A and COL_B refer to dimensions.
- COL_A is primary key of Table_A, COL_B is primary key of Table_B
BMM Layer:
1- Dimension table: DIM_A(TABLE_A), Fact table: contains COL_A, COL_B, COL_C
2- Dimension tables: DIM_A(TABLE_A), DIM_B(TABLE_B), Fact table: contains COL_A, COL_B, COL_C
Additional Information:
We can model the BMM layer using the above-mentioned approaches, but either of the two will have some advantages over the other to model COL_B. Some of the advantages of (2) as highlighted by the OBIEE team:
a). Drill down capability will be supported for COL_B,
b). Useful in scenarios where multiple facts need to refer to TABLE_B.
Concern:
We agree with the above technical comments but if someone can provide us with more insight on both the approaches and how an end user can benefit from either approach, it will help us a lot.
We basically need to understand what are the implications if we leave something as just an attribute on the fact and do not model it as a dimension.
Thank you,
Abhishek
P.S. The OBI Server Admin guide does provide us with useful information on the implementation aspect, but we need more information from the end user's perspective.

Very similar to the question below. In pure terms your FACT table should contain no Dimension attributes, Facts tables should contain measures.
Where you have a Physical table that contains a mixture of aggregates and non-aggregate Dimension Attributes then you should split them out in the logical layer into 2 Logical Tables one for the Fact one for the Dimension.
From an end user perspective (certainly the ones I have coached) it is easy for them to understand the the Measures are all in one place, and then if they need to slice and dice then they select the appropriate attributes from the Dimension folders.

Modeling Star Schema From Transactional Schema

My requirement is to model the BMM from a Transactional Schema. When creating the joins in the physical layer for example between the Customer and Orders table would I join the 2 tables on Customer ID and pay attention to the one to many relationship between a customer and orders or would I need to defined which table is the fact table and which table is the dimesion table before creating the joins in the physical layer.

I would suggest to write a physical query to generate report like year, customer,product wise #of order and order items. Based on that try to creat joins and the bmm schema. I would say this the best approach.
Or else look for the table which having more foreign keys to other tables that would be the center located table.
Pla mark if helps.

None of the fact sources for [column] are compatible with the detail filter

Hi Experts,
I am using obiee 11.1.1.7.
Getting below error when i add a filter of non conformed dimension column.
Below is the error
Error Details
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: 14023] None of the fact sources for [column] are compatible with the detail filter
Please help in solving an issue.
Regards,
NN

Hi NN
You need to follow steps in below link to model your BMM layer for the report to work with non confirmed dimensions.
http://obibb.wordpress.com/2010/05/31/multiple-fact-reporting-on-non-conforming-dimensions/
Once you have followed these steps you can use the non confirmed dimension in the reports.When you see the logs to see the query generated by obiee,it generated 2 queries 1 with confirmed dimension and other with non conformed dimension.When you filter using non confirmed dimension you will now not notice any error but the results will not be filtering out because the filter will be applied only in 1 query which is valid
Now for this to work what you can do is ,instead of using the filter drag the column you like to filter as a prompt in your view.default it to the value you need using the case statement and hide it.This is one of the work around.
There may be many other work arounds for this but you need to understand that for you requirment to work you need to tweek OBIEE to generate 1 query instead of 2 queries.

Joins with multiple fact tables

Hi Experts,
i have one doubt in joins
we have two dimensions D1 and D2,
D1 is having A1 and A2 columns
D2 is having B1 and B2 columns
two facts F1 and F2 these are joined like D1 to F1 D1 to F2 and D2 to F1, D2 to F2
D1----->F1
D1------>F2
D2-------->F1
D2-------->F2
if i selected A1 and B1 in a request from which FACT table will get the data and why can you please explain
please help me
reg,
Jell

Hi All,
I have a similar requirement where I have 4 multiple fact tables and we can't combine all those facts into one single fact table. In that case how can a query work with multiple common and uncommon dimensions and measures from multiple fact tables, if it doesn't work that way - can you please explain how can we expect a query to work with multiple fact tables.
For eg: D1– Dim
D2 – Dim
D3 – Dim
D4 – Dim
F1 –Fact
F2 – Fact
F3 – Fact
D1 -> F1
D2 -> F1,F2
D3 -> F2
D4 -> F1, F3
In this case if we want to query from D1,D2,D3, F1, F2 or D1,D2,D3,D4,F1,F2,F3. Kindly please explain how it can be modeled in BMM or what are the limitations. I have done with two fact tables in past and didn't had issues but this is kind of a vast implementation. Your help is appreciated.

Creating aggregate tables

Hi gurus,
I have problem with creating aggregate tables. I use Oracle business intelligence 11g R1 cookbook book for help but I think author forget some important things and I can't create it.
I have fact table and dimension (fact_table, group_product_dim). I summery them and now I got fact aggregate table and aggregate dimension (fact_table_agg, group_product_dim_agg):
summary:
fact_table
fact_table_agg
group_product_dim
group_product_dim_agg
After I create physical diagram for base and aggregate combination in physical layer.
Now I need to move this tables in BMM. Which combination I need to bring in BMM layer? Both, basic combination or aggregate combination?
I move basic combination (fact_table, group_product_dim) and try two add two logical table source in dimension group_product_dim. Create a new logical table source by right-clicking on the group_product_dim logical
table and selecting the New Object | Logical Table Source option. This will bring up the new window Logical Table Source.
I select the physical table by clicking the + sign and select (group_product_dim_agg) the aggregate dimension table. Now I make the column mapping on the Column Mapping tab of the same Logical Table Source. Only few columns are mapped and all the others are unmapped. This is because the aggregate dimension table doesn't store all columns from basic dimension group_product_dim. The last modification I do on the Content tab of the Logical Table Source.
I need define the levels at which this logical table source can satisfy queries. This step is very important. Making any kind of mistake will cause the BI server to use a wrong logical table source for the queries.
Here I have a problem because I can't put Logical Level into Aggregation content, group by menu. I can't put anyting else then the default value Column.
Tnx,
best regards

1.) http://www.amazon.com/Oracle-Business-Intelligence-Cookbook-ebook/dp/B00DHCKTXQ/ref=wl_it_dp_o_pC_nS_nC?ie=UTF8&colid=322X8WO18RFEG&coliid=I13QJ38KK8PYTB
2.) I create NEW business model in BMM and after drag a fact_table and group_product_dim into it. Do I need drag aggregate objects into New business model, also?
I don't, I drag only fact_table and group_product_dim and create New Logical Table Source on group_product_dim where I try make new source.
Can you tell me what I need to do in background? Do I need map columns from dimension to aggregate dimension?

Importance of Global Consistency check

Hello,
I have always checked my rpd for global consistency without knowing the actual meaning behind it. But last night I created a logical column with the following expression:
max(VALUEOF(NQ_SESSION......))
basically i created an aggregation over a logical column that obtains its value from session variable. I know that if we need to use a column as an aggregation column we should use the aggregation tab in the column properties. When we choose an aggregation it disables the editable column formula field.
I put the above formula which violates the rule. The result is perfect so long as I don't check for global consistency. It throws an error that looks something like this:
[38083] The Attribute 'Acceptance Rate Target' defines a measure using an obsolete method.
The question is.. what is the significance of global consistency check.. and what is the consistency criteria.. and is it ok to save the rpd without checking for global consistency (yes this does not cause the BI server to crash when trying to start)
Thanks

First, forget about the variable approach.
Now you need to do the following steps:
1) Import the table to the physical layer
2) Create logical table in existing Business Model in BMM layer with the imported table as logical table source
3) Create another logical table in existing Business Model in BMM layer with the imported table as logical table source
4) Create complex join between both table, now you will get one logical dimension table and one logical fact table
5) In the logical fact table you need to select the column ("Target") and add an aggregation rule, like MAX or MIN
6) Assuming you have a hierarchy for every dimension in your BMM layer, you need to set the logical levels of the new measure to the Grand Total Level of each dimension hierarchy.
By doing this, you get a "level based measure", for more info: read this:
http://oraclebizint.wordpress.com/2007/12/03/oracle-bi-ee-101332-level-based-measures-lbms/
By setting all logical levels to the grand total level, the measure will be "immune" for all dimensions used in your report.
So when you have a report like
Month__Actual___Target
The BI Server will create two queries:
select month, sum(sales) from calendar, sales_table where calendar.id = sales_table.calendar_id
and
select max(value) from target_table
The BI Server will then stitch both results together.
Regards,
Stijn

Degenerate Dimension

While performing modeling in BMM layer I am hitting an issue.
I have two fact tables Revenue and Charges. Both has Sales Order Number as common column (Sales Order Number) is available in both the fact tables.
Now I want to create a report across both the fact tables.
The approach I am taking is to first create common degenerate dimension from both the fact tables (Sales order Number column is mapped to both the fact tables.
But when I try to create a dimension hierarchy by right clicking on degenerate dimension it throws an error saying 'AdminTool is unable to created a structure for dimension'. I believe this is because Sales Order Number is not unique in any of the fact tables.
Desired model should be able to use Sales Order Number across both fact tables.
Thank you,
DP.
Edited by: BIDeveloper on Nov 22, 2010 4:53 PM

DP,
As you mentioned "Sales Order Number" as degenerate dimension it is confined to a fact table (a standard definition).
Thus dimensional hierarchy cannot be created on facts.
Mandatory conditions for creating a dimensional hierarchy:
1. The logical table cannot be a logical fact table.
2. The logical table on which a dimensional hierarchy is bieng created should not have a hierarchy already created.
mark posts promptly.
J
-bifacts
http://www.obinotes.com

Querying data from two dimensional schemas

Hi,
I have modified 2 star models on Physical layer, then I add three tables from these models into BMM Layer: Fact A, Fact B and Dim C.
Dim C is joined logically (using complex join) with Fact A and Fact B.
In Answers I make a request with fields from tables A, B and C, but got this error:
[nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Fact B) does not contain mapping for [Fact A].
Someone can tell me how can I solve this issue??? or how to get this fields???, join both star models logically or physically is possible???
Thanks
Carlos Hernandez

Venkatakrishnan:
My first post was solved creating a single logical fact table with both physical facts as sources, joining this with all the dimensions that I need, also I created a hierarchy for each one, and finally I define dimension levels in facts sources and metrics.
The BMM has the particularity that involves two dimensional schemas at total and detail level: Order Fact and OrderItem Fact, and is joined with several dimensions: Account, Order, Product, Position, Day, Person, and with two new objects: a view named "Ordenes" and a table named "Item Atributos". Specifically this view has no physical join with OrderItem Fact, so that was my principal headache.
I defined #Order and #OrderLines metrics in the logical fact table and I could create a request with columns from all tables (fact and dim) and seems that it works, but now I have another problem: when I try to filter for a detail dimension column I get this error:
[nQSError: 14023] None of the fact sources for [Table.Column] are compatible with the detail filter [FILTER].
This error only happens when I include columns in request from "Ordenes" dim(physically defined as a custom view).
Could you know the cause of the problem or why this error is happening???
Thanks for your help again.
Carlos Hernandez

Hierarchy with multiple Physical tables

Some time ago there was a post with this subject and I am in need, if you pls, with the same situation:
I am looking for Dim (1) - (1:N)-> Dim (3). And Dim (3) - (1:N)-> Fact.
Suggestion by Mr. Bharath was to, just reduce your snowflake to star in your BMM with Dim (3) as your single LTS. Within the LTS map Dim (1). to Dim (3).
Could someone pls. help me clarifying the suggestion .../
a) Should I use the Dim(3) LTS and how to map Dim(1) ? - I believe we should use a column ? right ? Or just Add the Dim(3) in the LTS tables
Txs. for any hints
Antonio

Hi Antonio,
First of all - try to avoid SNF in BMM.
http://www.oraclebidwh.com/2010/10/obiee-bmm-layer-design-principalsbest-practices/
Comments:
1) You can keep the SNF model in BMM, but if you keep them, then you cannot create an hiearchy with combination of Dim(1) and Dim(3) together as those are two seperate LT.
2) OBIEE will take the shortest path in forming the query. But, if there are multiple shortest path, then OBIEE will use the latest relationship ID in creating the execution plan. For example: Dim (1) is joined with Dim(3) and Dim(4) and your report pulls - Dim(1) and Fact(1), then the shortest path can be either through DIM(3) or Dim(4), and for such scenario's OBIEE will use the ID (latest ID). Say Dim(4) was the latest join - then OBIEE will use Dim(4) in the query to join with Dim(1).
3) I actually do not undertstand your issue here - if you are creating an Hiearchy using Dim(1) and Dim(3) together, then why don;t you pull all the fields from Dim(1) into this LT. And in your presentation create folders if you want both the dimensions to be displayed seperately.
If you are trying to understand and explore OBIEE - then go ahead play with all possible ways you could think off.
Regards,
Bharath

How to set Essbase member alias as level label for hierarchy

Experts,
* I have imported my Essbase cube metadata and see my Essbase Member Aliases as Dimension Properties in the physical layer.
* when I view members of the levels in the physical layer I see them - as I expect - represented by the human readable alias names of the members.
* now drag&drop of the model into BMM layer - I notice the aliases (Dimension Properties in physical layer) are here represented as any other Logical Columns.
* drag&drop into the Presentation Layer and I can build my reports
Problem: in reports my hierarchies display using keys (from Essbase outline) and NOT the member aliases as would make sense.
When I drop the alias column next to the hierarchy column on the report, it does display the alias of the member in the current line - but how can I switch the hierarchy display itself to the alias???
thanks
Edited by: 846780 on May 23, 2011 8:41 AM
Edited by: 846780 on May 23, 2011 8:42 AM

1. When you post code, post a minimal example. Did we have to scroll through
all those bloody labels.
2. Can't say much for the quality of code NetBeans generates.
3. To answer your question (sorry, I don't have an autographed copy of the photo):
import java.awt.*;
import java.net.*;
import javax.swing.*;
public class Example {
    public static void main(String[] args) throws MalformedURLException {
        final JFrame f = new JFrame();
        f.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
        Container cp = f.getContentPane();
        cp.setBackground(new Color(0xff, 0xff, 0xee));
        cp.add(new JLabel("set the color on the content pane, not the frame"), BorderLayout.SOUTH);
        URL url = new URL("http://today.java.net/jag/bio/JagHeadshot-small.jpg");
        cp.add(new JLabel(new ImageIcon(url)));
        f.pack();
        SwingUtilities.invokeLater(new Runnable(){
            public void run() {
                f.setLocationRelativeTo(null);
                f.setVisible(true);
}

BMM model problem

Hi experts,
In Physical Layer, I defined 4 tables :
- Product Category
- Product Category Fact
- Product
- Product Fact
I drag and drop all the 4 tables from Physical Layer to Business Model and Mapping Layer. Then I build complex joins among the tables as below:
1) Product Category (Dim) -> Product (Dim) -> Product Fact (Fact)
2) Product Category (Dim) -> Product Category Fact (Fact)
Then I further drag and drop all the 4 tables from BMM Layer to Presentation Layer. Then I use OBIEE Answer to start query.
However , I got error when querying columns from Product Category and Product Category Fact.
Does OBIEE support this kind of logical structure?
Case 2:
Tables:
- Product
- Product Fact 1
- Product Fact 2
Logical Join:
Product (Dim) -> Product Fact 1 (Fact)
Product (Dim) -> Product Fact 2 (Fact)
When I query columns from Product Fact 1 and Product Fact 2 (no column from Product), also fail. Any way to achieve so??
Thanks.

what error are you getting?

Error In BMM model

Hi Everyone,
I am getting a strange problem. When checking consistency of a fairly large BMM model named core - I am getting following error.
ERRORS:
Business Model Core:
[nQSError: 93001] Can not load library, oracore11.dll, due to, The specified module could not be found..
The specified module could not be found.
[nQSError: 15001] Could not load navigation space for subject area Core.
Now nobody else is getting this error. And if I just save the rpd ignoring this error - the reports run fine. However the error still persists and irritates.
I am using Oracle BI Admin tool Version 11.1.1.6.10. Repository Version 320.
Others are on the same version still they do not get it. Any thought please? It is killing me.
Thanks in advance,
Avishek

Just to update.. it is finally resolved.
Issue was oracle 10g r2 client was installed in my machine. I downloaded oracle 11g r2 and started installer - selected custom - then OCI and did the installation.
Once done, did the consistency check again and it worked fine.
Bizarre OBIEE! as it was working perfect till somebody added a column where he did some semi-complex calc and from that point onwards - it started refusing to accept the rpd consistent in my m/c.
Regards, Avishek

Bmm Model

Hi ,
I have a requirement like below.
I have three DIM and two fact.
Ex: D1,D2,D3 - F1,F2
Mapping like below.
D1--F1
D2--F2
D3-F1,F2
How to design bmm layer plz suggest me.
Thanks..

Please see the following rough sketch:-
http://i49.tinypic.com/2v3fnk4.png
The coloured circles represent suggested subject areas for the presentation layer.
Please mark if helpful / correct,
Andy.

Model in BMM

Similar Messages

Maybe you are looking for