Multiple Date Keys in a Fact Table

Do you guys see a problem with having multiple date keys (all date keys are referencing one date demension table) on a fact table?
RESERVATION_DATE_KEY
SHIP_DATE_KEY
CONTRACT_DATE_KEY
SHIP_DATE_KEY
CANCEL_DATE_KEY
APPLICANT_KEY
BRANCH_KEY
ENLST_CAT_KEY

Nope, this is 100% natural for the type of fact table you are building. Happens all the time.
Scott
use the "role" to define the multiple ways the time dime is used.

Similar Messages

Multiple Date columns in one fact table

hi ,
I have a fact which related to multi date, like bid date, win date, lost date ,etc...,
I have create dimension like dim_bid_date, dim_win_date,
but if I wan to create a report , the value sum by the month (2012.01-2012.08), I don't know how to do in one report which related multi date.
I think I should have a 'common date', how to do, can anyone explain it in detail. thanks.

2 thinks here, do you want to reports based on bid date,win date, lost date etc?
if yes you need to create those many date logical tables and you need to have in Subject area (something like 'Agreement Details' subject area if you have OOB rpd)
Coming to your report requirement 'sum by the month'; I dont think this is complete report requirement, you need to know month type like bid month or win month or lost month or what!!
if user dont want do report by those mentioned dates then just use just date of type( bid,win etc) with out using day dim;
you might have some date like created date, create report based on that for sum by the month.
Hope this helps, if helps pls mark

Multiple 'logical joins' between a fact table and one dimension table

It appears that one cannot create multiple ‘logical joins’ between a fact table and one dimension table in OBIEE using the Oracle BI Administration Tool. For example, considering a Business Model with a dimension table TIMES and a fact table FACT containing START_TIME and END_TIME, we would like to create separate logical joins from FACT to TIMES for the START_TIMEs and END_TIMEs? Obviously, the underlying foreign keys can be created, but as far as I can tell the Oracle BI Administration Tool doesn’t support this. The workaround would be to replicate the TIMES table, but that’s ugly.
I seek an alternative approach.

Try this. Create an two aliases for the TIMES dimension (Start & End) in the Physical Layer and then remove foreign key to the "Parent" Times dimension. Create the Foreign Key in the Physical Layer to the new aliases and then create the complex joins in the BMM Layer to the new aliases as well. This will allow you to present both dates within the same table in the Presentation Layer. Not the most elegant solution but it works.

How to load data to dimensions and fact table is it simialr to sql server

How to load data to dimensions and fact table in a data ware house environment, is it simialr to sql server, oracle?
Never migrated or loaded data to datawarehouse server.
I have an interview and am really confused if they ask anything related to the dataware house side elements.
Coudl you please if you don't mind provide me some steps and dimension and fact table info, an example only.
Atleast for my knowledge.
Thank you very much for the helpful info.

Some discussions in previous forums should help you
http://forums.sdn.sap.com/thread.jspa?threadID=2019448
http://forums.sdn.sap.com/thread.jspa?threadID=1908902
In the SAP tutorial, you can see a sample example of making fact tables.
http://help.sap.com/businessobject/product_guides/boexir32SP1/en/xi321_ds_tutorial_en.pdf
Arun

SSAS 2008 Linking two cubes on the foreign key between two fact tables

Hi, all --
I have two cubes:
Cube 1 has Fact1 (F1, "Events") and 3 dimensions (D1, D2, D3)
Cube 2 has Fact2 (F2, "Sales") and 3 dimensions (D4, D1, D6)
As you can see, two cubes reuse D1 as their common dimension. In addition, F2 foreign keys into F1, e.g. F1 is "Events", and F2 is "Sales". Every "sale" is an "event", but not every "event" is
a "sale".
The question is, how to I link the two cubes and their two respective fact tables on the foreign key?
Thanks, Austin.

Hi Austin,
According to your description, you want to retrieve data from two different cubes, right? In Analysis Services, to query multiple cubes from a single MDX statement you can use the LOOKUPCUBE function (you can't specify multiple cubes in your FROM statement).
The LOOKUPCUBE function will only work on cubes that utilize the same source database as the cube on which the MDX statement is running. For the detail information about it, please refer to the link below to see the blog.
Retrieving Data From Multiple Cubes in an MDX Query Using the Lookupcube Function
If I have anything misunderstood, please point it out.
Regards,
Charlie Liao
TechNet Community Support

Multiple foreign key joins between two tables

Hi,
I have a question about building a repository.
I have a date dimension and one fact. The fact table has about 10 foreign key columns that link to the date Dimension.
In this case should I create 10 aliases to create joins in the Physical and BMM layer or is there any other way to handle this situation.
I am asking this question because 10 aliases can get very confusing for me at the later point of time while creating reports.
Using OBIEE 10.1.3

Hi
I have a follow up question on this.
I am okay with not seeing the different date tables under the Subject area. Even if it just shows a it as a Simple DATE Dimension I am good with it.
In this case which is the efficient way, creating 10 aliases or creating 10 joins in the physical layer. I just figured out that we can create multiple joins between the same set of two tables but do not know how will that effect the way BI server works.
Please help me in understanding this concept.
thanks
This request id for OBIEE 10.1.3

Multiple foreign keys to a single table

Hi,
I need to write an SQL sentence to bring a unique row formed from multiple foreign keys which are dependent on the same table. The two tables as follow:
CREATE TABLE UNIDADMEDIDA (
IDUNIDADMEDIDA NUMERIC(3) NOT NULL,
DESCRIPCION VARCHAR2(128) NOT NULL,
CONSTRAINT PKUM PRIMARY KEY(IDUNIDADMEDIDA)
CREATE TABLE TRANSPORTE (
IDBOLETA NUMERIC(12) NOT NULL,
CORRELAVEHICULO NUMERIC(2) NOT NULL,
TIPOVEHICULO NUMERIC(1),
TIPOGASOLINA NUMERIC(1),
CANTIDAD NUMERIC(8),
RECORRIDOPROMEDIO NUMERIC(10,2),
IDUMRECORRIDO NUMERIC(3),
CONSUMOPROMEDIO NUMERIC(10,2),
IDUMCONSUMOPROM NUMERIC(3),
CONSUMOTOTALANUAL NUMERIC(10,2),
IDUMCONSUMOTOT NUMERIC(3),
CONSTRAINT PKTRANSPORT PRIMARY KEY(IDBOLETA, CORRELAVEHICULO),
CONSTRAINT FKUMRECORRI FOREIGN KEY(IDUMRECORRIDO) REFERENCES UNIDADMEDIDA(IDUNIDADMEDIDA),
CONSTRAINT FKUMCONSUMO FOREIGN KEY(IDUMCONSUMOPROM) REFERENCES UNIDADMEDIDA(IDUNIDADMEDIDA),
CONSTRAINT FKUMCONSTOT FOREIGN KEY(IDUMCONSUMOTOT) REFERENCES UNIDADMEDIDA(IDUNIDADMEDIDA)
The columns IDUMRECORRIDO, IDUMCONSUMOPROM and IDUMCONSUMOTOT depend on the table UNIDADMEDIDA (specifically from the IDUNIDADMEDIDA field). I need to bring back the description (DESCRIPCION field) from the different values stored in TRANSPORTE table.
Thanks for your help!!!
Mario

Welcome to the forum!
Have you thought about joining against the parent table three times to pick up each different description?
SELECT <COLUMN LIST>
,       UNI_A.DESCRIPCION
,       UNI_B.DESCRIPCION
,       UNI_C.DESCRIPCION
FROM    TRANSPORTE
JOIN    UNIDADMEDIDA    UNI_A   ON UNI_A.IDUNIDADMEDIDA = TRANPORTE.IDUMRECORRIDO
JOIN    UNIDADMEDIDA    UNI_B   ON UNI_B.IDUNIDADMEDIDA = TRANPORTE.IDUMCONSUMOPROM
JOIN    UNIDADMEDIDA    UNI_C   ON UNI_C.IDUNIDADMEDIDA = TRANPORTE.IDUMCONSUMOTOT
;It is always helpful to provide the following:
1. Oracle version (SELECT * FROM V$VERSION)
2. Sample data in the form of CREATE / INSERT statements.
3. Expected output
4. Explanation of expected output (A.K.A. "business logic")
5. Use \ tags for #2 and #3. See FAQ (Link on top right side) for details.
You provided #2 partially. If you provide the rest we may be able to help you even further.

Load data from dimensions to fact table

Hi,
I have 10 dimension tables and one fact table. now i want to load data in to fact table from dimensions table. how i can do that.
Regards,
joy

To elaborate on "Mallee"'s answer, it's not good practice to load dimensional data into a fact table.
I guess what you mean is how to refer to dimensions when loading a fact table.
Simply refer to dimensions using lookups on the necessary dimensions, the lookup needs to be on the natural key you have that links facts to dimensions. Don't forget to use the dimension's surrogate key though when populating the fact table's foreign key columns pointing at the dimensions.
Hope this helps.
Cheers, Patrick

Date 01/01/1901 in W_DAY_D when joined to a date wid in a Fact Table

Hi
I noticed when w_day_d joined to a Fact table I am getting a CALENDER date as 10/10/1901. I have checked by joining these tables. When Fact Wid is '0',
Join is getting 01/01/1901 as date.
But I want to avoid this and display a 'NULL' value. How could I conver this date into a 'null' in Answers please.????
Thank you.

Hi,
We are using Dac Build AN 10.1.3.4.1.20090415.0146.
The start date is 01-Jan-1980 and end date 31-dec-2010.
I am interested to change the end date to 31-dec-2020.
For that I have created a custom container.
Design -> Task -> Query on SIL_DayDimension ->Parameters
Click on value, change the end_date to required value.
Save.
Setup -> Physical Datasource
Click on DataWarehouse.
Change W_DAY_D Refresh dates to null.
After running DAC W_DAY_D table is not having any record and end_date is showing as blank in paramter file
So I want to change it to original one that is as it was before.
When I de-clone it, the value for end_date is showing as Custom Format() @MM/DD/YYYY and if I add any value to it the after running dac end_date is showing as blank in paramter file and W_DAY_D table is not having any record.
Any help is greatly appreciated.
Regards,
Bhoomi

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.

Multiple Data Sources In One Logical Table

I am new to OBIEE and I have came accross an issue. I appologize if this information is in the forum somewhere but I have searched and cannot find it.
My situation is that I would like to have one logical table that contains multiple data sources which have all the same columns. I already have session variables setup to differentiate the user's security through a row-wise variable for a specific column and a session variable for another column which determines the user's association to the data source in which they belong to. This security works well when the data sources are seperated in the Business Model and Mapping portion but the issue that arises is that the user's cannot share reports when the data sources are seperated in the BM&M.
I have dragged and dropped a table from the Physical model to the BM&M, I then dragged the second data source (with same meta data structure) over to the "Sources" folder in the first data source table in the BM&M. On the Content tab or each data source table I have defined the WHERE clause as such, where VALUEOF(NQ_SESSION."SCHOOL") session variable is my row-wise column filter and the VALUEOF(NQ_SESSION."GROUP") filter is my data source determinative:
sandbox."".SANDBOX.OBIEE_CROSS_ENROLLMENTS.HOME_SCHOOL = VALUEOF(NQ_SESSION."SCHOOL") AND sandbox."".SANDBOX.OBIEE_CROSS_ENROLLMENTS.DATA_SOURCE = VALUEOF(NQ_SESSION."GROUP")
Unfortunatley this only returns values in the BI Answers for the first drag and drop Pysical table in the BM&M layer and not the second Physical table drug into the "Sources" folder. I have also tried to create a new logical table and drag both tables into the "Sources" folder to no avail. I have experimented with the Fragmentation content on the "Content" tab of the seperate logical tables, checking the "This source should be combined with other sources at this level", which gives me an error in BI Answers that a column does not exist which really does.
What could I be missing? Advanced thanks to those who reply.
Thank you,
Kyle

Stijn,
Thank you for the article link. That was very helpful! It seems that I had a few things off as you do need the "This source should be combined with other sources at this level." checked. In my two table source columns for DATA_SOURCE I defined a literal ('086496' and '085597' for the other) in the Column Mapping tab. I pasted the following in the Fragmentation content, checking the "This source..." box on the Content tab:
eSIS.SANDBOX4_SCHOOLS.DATA_SOURCE = '086496'
And pasted the following into the WHERE clause, checking "Select distinct values" on the Content tab:
sandbox4."".OBIEE.NWOCA_SCHOOLS.SCHOOL_CODE = VALUEOF(NQ_SESSION."SCHOOL") AND sandbox4."".OBIEE.NWOCA_SCHOOLS.DATA_SOURCE = VALUEOF(NQ_SESSION."GROUP")
This took care of my user's security, utilizing the session variables in the WHERE clause. I am now able to generate reports that only one user can access from one data source and share that same report with another user who can only see data from the other data source.
Many thanks!!!

Dimension key in a fact table should be repetitive?

Hi All,
We do have one to one relationship between a FACT table and Dimension table? Is it correct to have this kind of dimensional model.

You may find this link of some help.
How to Model Fact table having 1:1 relationship with key Dimension attributes

OBI Apps Data Not Populated on Fact tables

Hi,
I have installed Oracle BI Applications with Oracle DB 10.2.0.1, DAC 10.1.3.4.1, OBI Applications 7.9.6, Informatica 8.6 Adapters and OBIEE 10.1.3.4.1.
I did the Initial load using DAC for Oracle EBS R12 (General Ledger and Payables) and after that when i checked the data, the data were not available on the Fact tables.
While during Initial load some of the maps shown status as stopped.
Did i misssed out some thing?
Can i go to Informatica and try to rerun those (Stopped) maps again.?
What is the reason for this problem..?
Any suggestions appreciated.
Thanks,
Vino..

Please move this question to the BI Apps Forum: Business Intelligence Applications
Cheers,
Christi@n

Two different dates on a same fact table.

I use OBIEE and I got some difficulties with the times dimensions and the function AGO because I used two differents dates for my measure.
My fact table:
Ordered     Delivered Amount
1/1/2009     2/1/2009     20000
1/1/2009     3/1/2009     10000
*2/1/2009* 2/1/2009     50000
*2/1/2009* 3/1/2009     50000
1/1/2010     2/1/2010     25000
1/1/2010     3/1/2010     20000
1/1/2010     2/1/2010     20000
1/1/2010     3/1/2010     15000
I have two Times Dimensions (Ordered Times AND Delivered Times) and one fact table.
I want to compare the delivered situation (Amount Qty) for the same ordered day last year
I created a prompt with a date (ex.: Ordered date <=1/1/2010 AND Delivered date >=1/1/2010) and I want to compare one year ago with 1/1/2009 (Ordered Date situation…)
I wish the results below:
Delivered Month/Amount/Previous Amount Year Ago
2/     45000/          20000
3/     35000/          10000
I got some problem cause I had the 100 000 in my previous year (Ago) and I don’t want it because it was ordered after 1/1/2009 (Previous year). I know that the ago function concerns the Sum of Amount by Delivered Date, Year -1 ...
Does somebody has a solution for this ? Thank you
Edited by: user8898885 on Feb 8, 2010 1:01 PM
Edited by: user8898885 on Feb 8, 2010 1:05 PM
Edited by: user8898885 on Feb 8, 2010 1:05 PM

Ok, i created two facts table.
But now, what's the way to know this distribution (Delivered date) for the period (Ordered date).
Because, i got the sum of the amount by the deliverd date, and the sum for the ordered date AND i can't obtain the comparaison for the same period of ordered date.
Example:
Date Ordered || Date Delivered || Amount
janv 1, 2010 || feb. 25 2010 || 40 000
janv 5, 2011 || mar 23 2011 || 60 000
I want to compare for the ordered date, the delivered distribution
Promp = Janv. 2011
Delivered || This year || Previous year
Feb || 0 || 40 000
March || 60 000 || 0
That's my situation.
i hope than the explication is correct. I think than 1 fact table with 2 time dimension (Alias) is the way to do. But you have parhaps a best practice.

Add primary key column to fact tables?

Our datawarehouse folks asked me if they could add a primary key column in the BPC fact tables. Anyone know if this is possible??
Edited by: Shawn Freundschuh on Apr 3, 2009 12:27 PM

Well.. based on my expeirence, it is not possible.
When you run admin console, sometimes it will return error message.
I tried it before but you can try it again. Maybe developer changed its behavior.
Thanks.

Multiple Date Keys in a Fact Table

Similar Messages

Maybe you are looking for