OBIEE 10G - Repository Business Model adding Fact Table

Hi there,
I've tried to search in the forum for problems similar to this one but didn't find any thread that answered my doubts.
I'll try to explain this well (without images it's complicated). Let's assume we have a schema with the following tables:
Dim_1, Dim_2 , Dim_3, Dim_4, Dim_5, Fact_1, Fact_2
Fact_1 is connected to Dim_1, Dim_2 and Dim_3
Fact_2 is connected to Dim_2, Dim_3, Dim_4 and Dim_5
And on the business model of the repository we already have a model with the following tables:
Dim_1, Dim_2, Dim_3 and Fact_1. This was the state of the repository the last time we saved it.
Now i want to add to the business model the table Fact_2 and the Dims that connect with Fact_2. What should i do here?
If i drag from the physical layer only the tables (Dim_4, Dim_5 and Fact_2 since Dim_1 and Dim_2 already exist in the business model) when i check on the business model diagram the Fact_2 table and direct joins i will only see joins to Dim_4 and Dim_5 and not the joins to the two other dimesion tables (Dim_1 and Dim_2). I don't know if OBIEE will still act like these joins are made or if i will have problems when i work on presentation services.
If i drag from the physical layer the tables (Dim_2, Dim_3, Dim_4, Dim_5 and Fact_2) i will see all joins but i will have on the business model repeated tables, something like this:
Dim_1, Dim_2, Dim_2#1, Dim_3, Dim_3#1, Dim_4, Dim_5, Fact_1 and Fact_2
So what's the solution here? Do i have to redo everything i want to add something and this situation occurs? Doesn't sound smart and there has to be a better solution. I know i can redo the direct joins manually but is that the best solution i can look for in this situation?
I hope i was clear :)
Thanks

Hi,
Follow these steps,
1.Drag Dim_4, Dim_5 and Fact_2 to BMM
2.Select (Press Ctrl to select multiple objects)in BMM: Dim 1 to 5, Fact_1 and Fact_2
3.Right click ->Business Model diagram->Selected objects only
4.Give the necessary joins,
Dim 4,&5 joins to Fact1(as 1,2,3 are already joined)
Dim 2,3,4,5 joins to Fact2
5.Check consistency.
Rgds,
Dpka

Similar Messages

OBIEE 10g repository - Business model - logical table to physical table, column mapping is empty

Hi, I am really new to OBIEE 10g.
I already set up a SQL Server 2005 database in Physical and import a view vw_Dim_retail_branch.
The view has 3 columns: branch_id, branch_code, branch_desc.
Now I want to set up the Business model to map this physical table (view).
I created a new Business model
Added new logical table Dim_retail_branch
In the sources, added the vw_Dim_retail_branch as source table.
But in the Logical table source window, column mapping tab, it's blank. I thought it should be able to identify all the columns from vw_Dim_retail_branch, but not. The show mapped columns is ticked.
What should I do here? Manually type each column?

HI,
Just you can drag and drop the columns from physical layer to BMM layer.
Select the 3 columns and drag and drop it to the created logical column in BMM layer.
for more reference : http:\\mkashu.blogspot.com
Regards,
VG

OBIEE10G repository business model

Hi, I am new to OBIEE 10G.
I created a physical table (a SQL Server 2005 view) vw_Dim_retail_branch, which has three columns: branch_id, branch_code, branch_desc
I then created a new business model: Retail_branch,
I dragged the vw_Dim_retail_branch from physical to the model Retail_branch. A logical table is created with the three columns. Great.
I then dragged the model to presentation layer, a presentation catalogue and presentation table created. But the consistence checking reports an error:
BUSINESS MODEL Retail_branch:
[nQSError: 15001] Could not load navigation space for subject area Retail_branch.
[15013] Logical table, Retail_branch.vw_Dim_retail_branch, does not join to any other logical table
Any idea?

Ok, I think I found the answer:
https://forums.oracle.com/message/3527204

Modelling 2 Fact Tables with Non-Conforming Dimension in OBIEE 11g

Hi all,
I have two fact tables (Fact 1 and Fact 2) and two dimension tables (Product and Rule). The Product dimension table is a conforming dimension and is used in both fact tables, but the Rule dimension is a non-conforming dimension which is used only one fact table. I'm using OBIEE 11g (11.1.1.6.0).
====
Fact 1
====
Sales ID | Product ID | Quantity | Sales Description | Sales Status
S001 | P001 | 100 | bla bla bla bla bla | N
S001 | P002 | 200 | bla bla bla bla bla | N
S002 | P001 | 200 | lab lab lab lab lab | Y
S002 | P003 | 250 | lab lab lab lab lab | Y
Notes for Fact 1:
- One Sales ID can have multiple Product IDs
- Sales Description and Sales Status are the same for one Sales ID (repeating Sales Description and Sales Status for the same Sales ID)
====
Fact 2
====
Sales ID | Product ID | Rule ID | Score
S001 | P001 | R001 | 2
S001 | P001 | R002 | 3
S001 | P002 | R003 | 1
S002 | P001 | R003 | 1
S002 | P003 | R002 | 2
S002 | P003 | R004 | 5
Notes for Fact 2:
- One combination of Sales ID and Product ID can have multiple Rule ID
I'm wondering how best to model these tables so that I can create this report (number of the dimension and fact tables created in the business model, level mapping, aggregation rule, etc)? Any suggestion/advice on how to achieve this?
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
S001 | P001 | 100 | bla bla bla bla bla | N | R001 | 2
S001 | P001 | 100 | bla bla bla bla bla | N | R002 | 3
S001 | P002 | 200 | bla bla bla bla bla | N | R003 | 1
S002 | P001 | 200 | lab lab lab lab lab | Y | R003 | 1
S002 | P003 | 250 | lab lab lab lab lab | Y | R002 | 2
S002 | P003 | 250 | lab lab lab lab lab | Y | R004 | 5
Thank you very much!

Hi Dhar, thanks for the suggestions.
I tested what you suggested, but the result is not as per my expectation mentioned above. Here's what I did:
1. In physical layer:
- I joined Fact 1 table with Product dimension table only
- I joined Fact 2 table with Product and Rule dimension tables
2. In business model layer:
- I created 3 logical tables: Fact, Product, and Rule
- The Product table contains the Product ID and Product Name from the Product dimension table in the physical layer
- I created the hierarchy (logical dimension) for Product with only ProductTotal level (as the grand total level) and ProductDetail level that contains Product ID and Product Name
- The Rule table contains the Rule ID and Rule Name from the Rule dimension table in the physical layer
- I created the hierarchy (logical dimension) for Rule with only RuleTotal level (as the grand total level) and RuleDetail level that contains Rule ID and Rule Name
- The Fact table contains 2 logical tables sources: Fact 1 (which logical level in the Content tab is mapped to ProductDetail and RuleTotal) and Fact 2 (which logical level in the Content tab is mapped to ProductDetail and RuleDetail)
- The Fact table contains Sales ID logical column (mapped to both Fact 1 and Fact 2 logical table sources)
- The Fact table also contains Sales Description and Sales Status logical columns (mapped to only Fact 1), which aggregation rule is the default to None
- The Fact table also contains Quantity logical column (mapped to only Fact 1), which aggregation rule is set to Sum
- The Fact table also contains Score logical column (mapped to only Fact 2), which aggregation rule is set to Sum
OBIEE returns the expected result when I retrieve the report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status
However, OBIEE returns an error when I retrieve the reports:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID
or
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
The error is:
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: 14020] None of the fact tables are compatible with the query request FACT.SALES_STATUS. (HY000)
And the Score column is blank when I retrieved this report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Score
Any suggestion anyone? Please help. Thanks a lot!
Edited by: stewartlife on Nov 29, 2012 4:01 PM

Distinct count of dimension business key in fact table

In my cube I have a fact table which joins to a patient dimension. The patient dimension is a type 2. What I would like to do is get a distinct count of patients who have records in the fact table. The business key in the patient dimension
is the PrimaryMrn. So a SQL query would look like this.
SELECT count(distinct PrimaryMrn)
FROM EncounterFact e
INNER JOIN PatientDim p
on e.PatientKey = p.PatientKey
Is it possible to do this via MDX?
Thanks for the help.

If you have to distinct count an attribute in a SCD 2, you might choose between:
Denormalizing that attribute in the fact table, and the create a classical DISTINCT COUNT measure
Use a many-to-many approach - see the "Distinct Count" scenario in the Many-to-Many White paper here:
http://www.sqlbi.com/articles/many2many (for both Multidimensional and Tabular
If you use Tabular, you might want to read also this pattern:
http://www.daxpatterns.com/distinct-count/
Marco Russo http://www.sqlbi.com http://www.powerpivotworkshop.com http://sqlblog.com/blogs/marco_russo

OBIEE Query not hitting the other fact table

Hi All,
I am trying to create report based on two fact column and one dimension. Dimension is connected with these two facts table. When i create report using one column from dimension and one column from respective facts so i get two scenerio...
For example let say..
D1 is dimension and F1 and F2 are two fact tables.
First i used a column which have aggregation rule from one fact and one column from other fact which also have aggregate column.
That is report like...
D1.c1,Agg(F1.c2),Agg(F2.c3)
When i run the report I get the data from dimension and only from first fact table. When i check the query, Query contain only one fact table and it doesnt hit the other one.
Now in second scenerio i used one column from dimension, one column from first fact which have aggregation rule and one column from second fact which doesnt have any aggregation rule.
like...
D1.c1,Agg(F1.c2),F2.c3
When i run the report i got the error. It says
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: F1 -C2 . Please fix the metadata consistency warnings. (HY000).
But there is no warning in RPD.
I am amazed that it is not taking both the fact columns even the dimension is confirmed dimension and have joined with both the fact tables.
As i am just started to learn OBIEE, So i am find it bit difficult that how OBIEE select the tables and formed physical query.
Waiting for your help.
Regards
Suhail

Aadi-Wasi,
Thumb rule, OBIEE BMM layer must contain a simple star schema.
Did your BMM layer suffice the above condition? If hope, Not.
My prediction of your BMM layer structure contains 3 logical tables, i.e. dimension & 2 logical facts...which is not a simple star.
Thus to make it a simple star collapse 2 logical fact tables into 1 logical fact table. As you mentioned dimension is linked to both facts, collapsing 2 logical fact tables into 1 logical fact table will provide the result for your query1.
regarding your second error:
All aggregations must be contained within Fact tables with few exceptions.
Let us know If I did resolve your issue
mark posts promptly...
J
-bifacts
http://www.obinotes.com

OBIEE 10G - Repository Documentation

Hi all,
When I am generating RPD Documentation for my OBIEE 10G RPD, there are few presentation columns for which there are no physical columns.
These measures are not calculated columns, and when I check the relevant physical columns it directs to correct physical tables and columns.
Since my RPD is very large i tried removing other subject areas as well but still not help..
Any help would be appreciated.
thanks

There might be few columns in BMM with expression as '' or any these may not have direct physical sources. Other than these I dont think any case for that. can you double check by opening document file in Excel?
PS: Update your display name with name

Modeling: Is Fact Table partitioning that important?

I read of how much partitioning a fact table can speed a query. On an upcoming project with specifications for only 4 InfoCubes, how can we take advantage in partitioning to fact tables to speed up queries?
Can this be factored into the design now or, we should wait till queries on Cube begins to perform poorly?
Thanks.

Spend some time reviewing the links others have provided and serach SDN.
As mentioned, there are two types of partitioning generally talked about with SAP BW, logical and physical partitioning.
Logical partitioning - instead of having all your data in a single cube, you might break into separate cubes, with each cube holding aspecific year's data, e.g. you could have 5 sales cubes, one for each year 2001 thru 2005.
You would then create a Multi-Provider that allowed you to query all of them together.
A query that needs data from all 5 years would then automatically (you can control this) be split into 5 separate queries, one against each cube, running at the same time. The system automatically merges the results from the 5 queries into a single result set.
So it's easy to see when this could be a benefit. If your queries however are primarily run just for a single year, then you don't receive the benefit of the parallel processing. In non-Oracle DBs, splitting the data like this may still be a benefit by reducing the amount of rows in the fact table that must be read, but does not provide as much value to an Oracle DB since Infocube queries are using a Star_Transformation.
Physical Partitioning - I believe only Oracle and Informix currently support Range partitioning. This is a separately licensed option in Oracle.
Physical partitioning allows you to split an Infocube into smaller pieces. The pieces, or partitions, can only be created by 0FISCPER or 0CALMONTH for an InfoCube (ODSs can be partitioned, but require a DBAs involvement). The DB can then take advantage of this partitioning by "pruning" partitions during a query, e.g. a query only needs data form June 2005
The DB is smart enough to restrict the indices and data it will read to the June 2005 partition. This assumes your query restricts/filters on the partitioning characteristic. It can apply this pruning to a range of partitions as well, e.g. 0FISCPER 001/2005 thru 003/2005 would only look at the 3 partitions.
It is NOTsmart enough, however, to figure out that if your restrict to 0FISCYEAR = 2005, that it should only read 000/2005 thru 016/2005 since 0FISCYEAR is NOT the partitioning characteristic.
An InfoCube MUST be empty in order to physically partition it. At this time, there is no way to add additional partitions thru AWB, so you want to make sure that you create partitions out into the future for at least a of couple of years.
If the base cube is partitioned, any aggregates that contain the partitioning characteristic (0CALMONTH or 0FISCPER) will automatically be partitioned.
In summary, you need to figure out if you want to use physical or logical partitioning on the cube(s), or both, as they are not mutually exclusive.
So you would need to know how the data will be queried, and the volume of data. It would make little sense to partition cubes that will not be very large.

After changing OBIEE 10G repository, BI Publisher Admin user lost privileges

Hi,
When I changed the OBIEE repository to a new one in NQSConfig.ini, BI Publisher Administrator User is stripped off access to shared Folder reports and Admin tab. Also the privilege to create a new report is removed.
Can some one suggest a solution for my issue.
Thanks in Advance..

You need to setup SA System in order for BI EE security to work with BI Publisher. Setting this up will fix the error that you are listing below. Couple of options for you.
1. Log an SR on supportweb to get sample RPD and table structure for the SA System
2. check the 7.8.x documentation. It had a better description of the SA System than the 10.1.3.2 documentation does.
3. I can email you an RPD and table structure that I have used.
The only thing BIP needs in SA system is user name, group name and user to group assignment. This is needed for two screens in BIP (Roles and Permissions and JDBC connections). It's a bit annoying to have to set this up, but two good things to note. If you setup SA System, then you have additional options for delivery of iBots (that's what SA System is really designed for). The other is that BIP's dependence on SA System is going away in a future release. So this will get easier soon.
Bryan

Conforming Dimensions - won't appear on the same business model diagram?!

Hi,
this is one of those where you have done something a 1000 times without thinking about it, and then suddenly I find when I have two subject areas with dimensions I want to share in the business model diagram the diagram will not display both sets of tables on the same diagram, no matter which way round I try it...
i.e.
I have 1 fact, 1 dimension in one subject area
I want to join the fact to four other conforming dimensions in another subject area.
I have seen a 10g hit saying go from the physical aliases - but this does not seem optimal, surely there must be a better way??
I am on 11.1.1.5
Anyone help?!
thanks,
Robert.

Hi,
additional info
Physical layer; -
Fact 1 - Dimension 1 - Fact 2 - Dimension 5
- Dimension 2
- Dimension 3
- Dimension 4
Subject Area 1 = Fact 1 and all directly joined Dimensions
Business Model Diagram = Fact 1 and all directly joined Dimensions
Subject Area 2 = Fact 2 and Dimension 5
How do I join Fact 2 to Dimension 1,2,3??
Anyone help?
thanks,
Robert.

Percentile_Disc Function in OBIEE 10g - Help needed at the earliest

Hi All,
I have a requirement of using PERCENTILE_DISC function in OBIEE 10g repository. I tried NTile function, to fetch the percentile. But that is not what am intending to see.
I have a requirement something similar to this, to be implemented in repository. Could anyone throw some light in this regard?
PERCENTILE_DISC(.25) WITHIN GROUP (ORDER BY F.Days asc) OVER (PARTITION BY A.NAME, B.PLACE)
Here F = Fact
A = 1st Dimension
B = 2nd Dimension
Days = Is calculated as TIMESTAMPDIFF(SQL_TSI_DAY, A.DATE, B.DATE). Established Inner Join, to fetch this calculation in to the FACT
Appreciate your responses at the earliest. Thanks once again.
Regards,
Sarat Nallapati

Hi,
I don't have any idea on percentile_disc.
But,in OBIEE we have a function PERCENTILE()
It will give the percentage of each value in the total sum of all the values.
once check it.
Regards,
Lakshmipathi.

Measures in the fact table

Hello,
Can i have measures in the fact table in business layer?
I am using obiee 11g.
like i have a fact table where i have a user i applied aggregation rule of count distinct.
Now i would like to add a lower function to it like count (distinct(lower(username)).
But then it becomes like a measure with fx with the name and not the usual yellow colour.
Wanted to know if its good practice?
Thanks

Hi,
You have two measure columns.
one with lower function
other without lower function.
For your information: Distinct is case sensitive.It will show the difference between 'A' and 'a'.
Regards,
Lakshmipathi.
Edited by: Lakshmipathi on Jul 7, 2011 2:41 PM

Mix source data with different granularity into the same fact table?

I have two transaction tables "Incident (157 columns)" and "Unit (70 Colums)". For every "Incident" that happens there could be one or more records in the "Unit" table.
As part of my data mart design, I have merged both the tables into a single Fact "Incident Fact (227 Columns)" and inserted the records from both the tables with a join condition between them [incident.IN_NUM = Unit.IN_NUM].
Is this correct, is my question? or am I mixing source data with different granularity in the same fact table. Appreciate your help.
Best Regards
Bees

Bees,
Are the measures from 'Incident' , repeated for a given incident where it has more than one record in the Unit table ? If so, then the sum(indicent.measure) will give an incorrect result, no ?
What requirement is there to physically merge the tables together outside of OBIEE? With OBIEE you could have one logical 'fact' table to present to report users, which sourced from seperate Incidents and Units tables and would stop the incorrect aggregations occuring. A common modelling piece in the same way would be Order Headers and Order Lines, quite common in OBIEE to have a logical 'Orders' fact which contained both Order header measures and Order line measures, this translates to your Incidents -> Units relationship.
To do what I've mentioned, is relatively straight forward, you need a 'Dim - Incident' with two levels, Incident and Unit, mapp the unique identifiers in as the level keys and then use these levels to set the content levels correctly in your 2 logical tables sources for logical 'Fact' , ie Incidents LTS at incident level, Units LTS as units level.
Hope this helps, let us know if you get stuck.
Cheers
Alastair

LDAP authentication too slow in OBIEE 10g

Hello ,
For one of our clients we have configured LDAP (Microsoft Active Directory) for authentication purpose in OBIEE 10g repository. The Authentication process takes around 10-15 mins to Login .
Are there any parameters that can help to speed up the process?. Any log which obiee generates through which we can track the root cause?
Any help appreciated!
Regards,
Shruti

Check if Initialization Blocks and are failing, that might be reason for slow log in.
If so give proper connection details or else disable unwanted Initialization Blocks.
Regards,
Srikanth

Adding a single table without a logical join to another table (OBIEE 10g)

Sometimes I want to just display a single table without a logical join to another table in the repository. However, everytime I move it to the Business Model and Mapping layer and perform a Global Consistency Check, it tells me that it needs a logical join and I am forced to create another table to join to it. Thus creating a dimension-fact relationship. There are times I don't need this relationship and just want to display some data. Is there anyway to get around this?
Thanks in advance!

Yes,You have to create a join.You cannot take single table to BMM layer.You can create an alias of the table.Join this alias and base table through any common column and take both tables to BMM and desired table to presentation layer.
Another way is to create a view in physcial layer.Write a select statement like
Select primary_key from Table
Where primary_key is primary key of base table.Join this view ith base table and repeat the steps defined for Alias.
Regards,
Sandeep

OBIEE 10G - Repository Business Model adding Fact Table

Similar Messages

Maybe you are looking for