Model with 2 fact tables

Hi all,
i have a model with two fact tables, both of them containing these columns:
- some measures
- foreign keys for dimensional tables
- column year
- column month
I have to build a model with both of these two tables, including a unique time dimension. Do anyone knows how i can do to make a unique dimension for both of the tables?
Thanks in advance,
Regards

A time dimension (or date dimension for that matter) are quite independent and you can find N good generic time/date dim structures out there (with proper Y/M/DAGO keys, calendar vs fiscal rollups etc etc).
But if you only want to create a single common time/date dim based on what you have in your facts, you can just follow (as a quick win before thinking about how to structure a physical time/date dim) Stewarts basic example here:
http://www.rittmanmead.com/2012/12/obiee-transactional4/
"Building a Date Dimension" a bit further down the page.

Similar Messages

Modelling Time Dimension with Fact Table containing Start Date and End Date

Hi Gurus,
I have a time dimension with Year till Date. I have a fact table which consists of Start Date, End Date, Person ID, Department ID.
How do i design Time dimension with fact table the below scenario
In the dashboard i have start Month and End month as prompts.
In the report i need to display Count(Person ID) > Start Date and < End Date along the trend.
For instance, i have selected Jan-2009 as start date and Apr-2009 as End Date, then i need to display Count(Person ID) of Jan-2009, Feb2009, Mar-2009 andApr-2009.
I Can not connect Time dimension with only Start Date or only with End Date to get the trend along the months.
Please advice on the issue which i am having.

Hi,
Thanks for the response, Infact i tried using Complex join in physical layer. I have considered Time table joined with Fact table, and used >= and took and alias of the Time table and joined fact table using <=. When coming to BMM, i am not knowing how do i design this as if i merge the both the time dimensiona and its alias into single table, values will not be correct and if i make them as seperate columns. i can not show the trend as both are different columns.
Can you please let know where i am going wrong.
Thanks

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

Calc problem with fact table measure used as part of bridge table model

Hi all,
I'm experiencing problems with the calculation of a fact table measure ever since I've used it as part of a calculation in a bridge table relationship.
In a fact table, PROJECT_FACT, I had a column (PROJECT_COST) whose default aggregate was SUM. Whenever PROJECT_COST was used with any dimension, the proper aggregation was done at the proper levels. But, not any longer. One of the relationships PROJECT_FACT has is with a dimension, called PROJECT.
PROJECT_FACT contains details of employees and each day they worked on a PROJECT_ID. So for a particular day, employee, Joe, might have a PROJECT_COST of $80 for PROJECT_ID 123, on the next day, Joe might have $40 in PROJECT_COST for the same project.
Dimension table, PROJECT, contains details of the project.
A new feature was added to the software - multiple customers can now be charged for a PROJECT, where as before, only one customer was charged.
This percentage charge break-down is in a new table - PROJECT_BRIDGE. PROJECT_BRIDGE has the PROJECT_ID, CUSTOMER_ID, BILL_PCT. BILL_PCT will always add up to 1.
So, the bridge table might look like...
PROJECT_ID CUSTOMER_ID BILL_PCT
123 100 .20
123 200 .30
123 300 .50
456 400 1.00
678 400 1.00
Where for project 123, is a breakdown for multiple customers (.20, .30. .50).
Let's say in PROJECT_FACT, if you were to sum up all PROJECT_COST for PROJECT_ID = 123, you get $1000.
Here are the steps I followed:
- In the Physical layer, PROJECT_FACT has a 1:M with PROJECT_BRIDGE as does PROJECT to PROJECT_BRIDGE (a 1:M).
PROJECT_FACT ===> PROJECT_BRIDGE <=== PROJECT
- In the Logical layer, PROJECT has a 1:M with PROJECT_FACT.
PROJECT ===> PROJECT_FACT
- The fact logical table source is mapped to the bridge table, PROJECT_BRIDGE, so now it has multiple tables it maps to (PROJECT_FACT & PROJECT_BRIDGE). They are set for an INNER join.
- I created a calculation measure, MULT_CUST_COST, using physical columns, that calculates the sum of the PROJECT_COST X the percentage amount in the bridge table. It looks like: SUM(PROJECT_FACT.PROJECT_COST * PROJECT_BRIDGE.BILL_PCT)
- I brought MULT_CUST_COST into the Presentation layer.
We still want the old PROJECT_COST around until it get's phased out, so it's in the Presentation layer as well.
Let's say I had a request with only PROJECT_ID, MULT_CUST_COST (the new calculation), and PROJECT_COST (the original). I'd expect:
PROJECT_ID MULT_CUST_COST PROJECT_COST
123 $1000 $1000
I am getting this for MULT_CUST_COST, however, for PROJECT_COST, it's tripling the value (possibly because there are 3 percent amounts?)...
PROJECT_ID MULT_CUST_COST PROJECT_COST
123 $1000 (correct) $3000 (incorrect, it's been tripled)
If I were to look at the SQL, it would have:
 SELECT SUM(PROJECT_COST),
SUM(PROJECT_FACT.PROJECT_COST * PROJECT_BRIDGE.BILL_PCT),
 PROJECT_ID
 FROM ...
 GROUP BY PROJECT_ID
PROJECT_COST used to work correctly before modeling a bridge table.
Any ideas on what I did wrong?
Thanks!

Hi
Phew, what a long question!
If I understand correctly I think the problem lies with your old cost measure, or rather combining that with you new one in the same request. If you think about it, your query as explained above will bring back 3 rows from the database which is why your old cost measure is being multiplied. I suspect that if you took it out of the query, your bridge table would be working properly for the new measure alone?
I would consider migrating your historic data into the bridge table model so that you have a single type of query. For the historic data each would have a single row in the bridge with a 1.0 BILL_PCT.
Best of luck,
Paul
http://total-bi.com

Self join with fact table in Obie 10G

I am a newbie to obiee.I have a development requirement as follows-
I need to find supervisors designation with the existing star RPD design. explanation is below
                                                    DIM_Designation(Desig_Wid)
                                                  |(Row_wid)
                                                  |
DIM_EMPLOYEE--------WORKER_FACT------------DIM_Supervisor
(Row_Wid)-----------------(Employee_Wid)
                                  (Supervisor_Wid)------------(Row_Wid)
3 dimension is joined to fact to get employee, his supervisor and designation of employee. now i want to get the supervisor's designation? how is it possible? already employee and supervisor dimension is same W_employee_d table joined with fact as alias DIM_EMPLOYEE and DIM_SUPERVISOR. how to do self join with fact to get supervisor's designation. i do not have any supervisor_desig_wid in fact table. any help is deeply appreciated.

Yes,Duplicate the fact table create a primary key on the newly fact table alias dimension table.So you can ur data modelling as usual.

Problems with Fact Table in an Infocube

In IC 0CCA_C11 we've seen almost a 50% increase in the row count on the F fact table from about 100 million rows to about 150 million rows. However we are very certain that we really havent had that much growth.
We have a process chain that does a full load of 12 million rows to the cube and then deletes the previous full load. Because this PC is conflicting with a more important PC that loads to the cube, we've been cancelling the step in the PC and manually deleting the previous request out of the cube via the IC "Manage" screen.
Is it possible that what we've been doing has been leaving rows in the cube that we thought were deleted?
If so, is there an Analysis and Repair function in RSRV that will get rid of all these extra rows?
There's no way this cube could have truly grown by 50 million rows in 2 weeks!

Wardell,
Check the data in RSA3 for the extractor that you use to bring data .
You must be using the data source 0CO_OM_CCA_09. Check the data and reconcile and you will get it.
Let me know if you need anything else.
Thanks
Ravi Thothadri
[email protected]

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

Data being dropped after joining Fiscal Time with Fact Table

Hi,
In my RPD, i have jolined the Fiscal Calendar with my fact tables : Fiscal Day is joined to Create Time column in the fact table.
Fiscal Day Data is : 6/6/2006 12:00:00
Creare Time Data is : 6/6/2006 11:45:49
6/6/2006 11:56:50
When i pull the fiscal day column with the other columns fromthe fact table in the report, i only see a subset of my data. I beleive this is due to the timestamp and it is causing to drop records.
Is there anyway, i can join this and not drop records due to the timestamp.
ANy suggestions will be appreciated.
Thanks

I assume that fiscal day table is at the day level. I would suggest that you store the date in an integer format (for example 20060606 'YYYYMMDD') similarly you may store the creation_date_key in fact table which is also in the same format, then do a direct join. This will be provide good performance for your reporting since you are joining integers and not date or char formats.
If you want time of creation date also, you might want to store it in a seperate column in say HHMMSS format, this when joined with time dimension will allow you hierarchical reporting for time too.

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.

Power Pivot Data Model with Linked Table

Can anyone provide me with some suggestions as to how to accomplish the following in Power Pivot?
I have the following Pivot Table fields. I'm trying to create a data model to allow me to filter all of the projects by the selected Fiscal Year. The Fiscal Year table is a dimension I created to group the data by.
I'm considering separating Projects into multiple tables such that 1 table is for Year1 information, another table is for Year2 information (includes Year2FiscalYear, Year2BudgetCAP, etc.).
I think what I need to do is create a measure to allow me to filter the records by fiscal year. Anyone have any ideas?
Thanks,
Roland

Hi Greg,
The data is coming from Project Online (OData feed) and SharePoint lists (all within Project Online). I'm creating an Excel Report.
The reason I can't use Power Query is because refreshing a report that is built using Power Query is not supported via browser. Power BI is needed to do this. On the other hand if I build an excel report using Power Pivot only, the browser refresh functionality
works.
The Year1FiscalYear, Year2FiscalYear, etc. are all enterprise custom fields in Project Online. Therefore I have some control in being able to change the format of the data. I'm looking into what are some options on my side to configure Project Online or
SharePoint lists to make building the model simpler...
Thanks,
Roland

How to obtain the selected rows in the model with af:Table using selectMany

Hi ,
I am using multi select af:Table and it is based on a programmatically populated view. When the table is single select I can use the getCurrentRow at the view implementation. I wonder whether there is a way to get list of selected rows within the view implementation for the multi-select scenario.
I saw some ways of doing it in the page's backing bean but it will be more appropriate if I could do it at the model project.
Thanks
My environment is JDeveloper 10.1.3.3 and jdk 1.4

Thanks for your reply.
What you say makes sense. I thought there might be way of setting the selected rows in the model also as we do woth the current row.
But looks like these two different things.
Anyway I am doing it by passing the values through the backing bean.
Thanks

Join Master Data table with fact table

Hello gurus.
I have a requirement on a characteristic. I have to obtain the description of those values that are not filled with data in the cube, the example looks like this:
Data in the cube:
Characteristic 1 | charactersitic 2 | value
AU                           HPDV              200
TB                           OPPG              500
TC                           HPDV              900
TR                           OPMR             400
                               HPDV              300
                               OPMR             200
                               OPPG             100
Master Data Table:
                            Description
HPDV    AU       Auditoria
OPPG    TB       Servicios Logisticos
HPDV     TC       Occidente
OPMR    TR       Oriente
HPDV     AI        Punta Norte
OPGS    CV       Escandón
HPDV    QR       Barquisimeto
HPDV    MM      Valencia
HPDV    DT        Barcelona
I need to display in the query only the description of the characterstic whose data is not in the cube, according to the example the values that are missing in the cube are:
HPDV     AI        Punta Norte
OPGS    CV       Escandón
HPDV    QR       Barquisimeto
HPDV    MM      Valencia
HPDV    DT        Barcelona
How can i achive this ??
Thank you in advance.

Hi Guillermo,
I think you are trying to achieve this: To display characteristic values for which no transaction data or only low values exist for the selected period.
See here for the solution details:
http://help.sap.com/saphelp_nw04/helpdata/en/3a/d1603d13b5c72ee10000000a114084/content.htm
Hope this helps...

How to get the disco model with all tables and fields ?

Hello !
I have to make a document showing all the tables and fields I have in my EUL ... This would be a good documentation for our company and our clients too !
I haven't find any ways to perform this directly from disco admin and I can't make a query using the EUL tables ...
Please Help ...

Hi,
I am assuming you are using Discoverer 4.1/4i. In the Oracle Home\Discvr4 directory contains an EUL4.eex file. Import this in Admin edition, and it will create a business area on your EUL. Then you can get details on the Folders and Items and use it to create reports....
Cheers
Deepak

Two Fact tables with Different set of Dimension Tables

Here is my scenario:
I got two fact tables: X and Y (actually, they are the same tables, but with different level of data)
and four dimension tables: A, B, C, D
X joins relationship to all dimensions (A, B, C, D).
Y joins relationship to only A, B, C, but no D.
When I select dimension A, B and C together with fact tables X and Y in BI Answer, result is displayed and compared.
However, if I select dimension D together with fact tables X and Y, only data from fact table X is displayed. There is no result displayed for fact table Y. I know that this is because fact table Y does not join to dimension D.
If the above relationship unchanged, how can I display both X and Y's result in BI Answer when dimension D is selected?

Thanks for all your replies.
Actually, I've tried the solutions you guys mentioned. Generally speaking, the result should be displayed. However, my scenario is a little bit tricky.
table Y's figures are not the aggregation of table X for D dimension. Instead, table Y's figures include not only D dimension total, but also others (others do not mean A, B, C dimension). For example, table Y stores all food's figure, while table X stores only drink's figure. D dimension is only about drink's detail. In my scenario, other foods' figure is not provided.
So, even if I set D dimension to all/total for table X, table X's result is still not the same as table Y.
Indeed, table Y does not have a column key to join to D dimension's key. So, if I select D dimension and table Y's measures at the same time in BI Answer, result returns no data. Hence, I can't compare table X and table Y's results with selection of D dimension.
Is there any solution to solve this problem?
Edited by: TomChan on Jun 3, 2009 9:36 AM

Understanding Fact Tables

Hi,
I am new to OBIEE, I have created several dimensions but am a little confused with fact tables and measures. I have a fact table already populated in the database containing dimension keys per each dimension, 3 measures. There are some additional columns(agreement_code, agreement_type, schedule_number). These additional columns do not link to the dimensions. Do these columns have to be included in the fact table inside the OBIEE BM layer or could they be removed. My question is does the fact table have to contain only measures or can there be other non-aggregated columns.
Thanks

Hi
If I'm right, your 3 additionnal columns are attributs but they're in your fact table ?
If so, they are "degenerated dimensions".
If the end-user needs them, you will have to put them somewhere.
You will create a new logical table based on the your physical fact table, but for dimension purpose.
Actually, you will have :
- 1 logical fact table, based on the physical fact table, and contains measures
- 1 logical dim table, based on the same physical fact table, and logically linked to the logical fact table. It contains your 3 attributes.
You can see a deeper explanation here, in my last post :
Table as fact and dimension
Note : you can also put the 3 columns in the logical fact table, it will works, but it's not the "propest" (not sure about this word... sorry, my english is not very good) method.

How to refer to fact table to update the same fact table

Here is my scenario. Fact table is having measures basic_sal, Tax, net_sal with dimension key to employee dimension.
I neet to update the net_sal = basic_sal - tax in fact table.
I tried to do a map with fact_table as source and also target. but after deploying the map, it's not updating the net_sal to the existing rows. It's inserting the new rows with dimension key and net_sal columns. so now fact table is having the double the existing rows.
Thanks,
Srini.

Ola Srini,
We have some experience that updating a table while using that same table as source often takes a lot of time... Specially when the table contains a lot of data (which is mostly the case with fact tables).
You can use two solutions. Expand the mapping u use to fill the fact table... The calculations looks not that complex to me... But I could be wrong.
Other solution is to create a temp table where you store all sal types. You could load the fact table from this temp table. Disadvantage of this solution is maintenance of the temp table...
Regards,
Moscowic

Model with 2 fact tables

Similar Messages

Maybe you are looking for