OOTB Fact table contains Employee detailed Dates

Hi Experts,
we Have 4 date columns (pos_entry_dt, grade_entry_dt etc) in HR Fact out of Box fact table(W_WRKFC_EVT_MONTH_F_SNAPSHOT) which are not populated into presentation layer or BMM Layer and is not linked with day dimension. but the dates are needed when users want detailed level reports. as i know, we can not populate dates directly because BI Server assumes them as facts. i tried to created a separate table with only four columns and achieve this...but it will not work as duplicates will come into picture.
what will be the best way to populate this into Presentation layer
is it okay to populate them from Fact table itself? or its good to create as separate dimension
Thanks
Kumar

Hi Turri
thank you
I Can not create a join with day dimension because there is no key from fact table that can explicitly make a join with Day dimension to get this column from DAY Dimension table. its all out of box and if i have to create a key its a lot customization
for example:
I have
event_month_wid and job_entry_dt in fact table
200704     22-DEC-00
200705     22-DEC-00
200710     22-DEC-00
200711     22-DEC-00
200805     22-DEC-00
200806     22-DEC-00
200807     22-DEC-00
200810     01-OCT-08
200811     01-OCT-08
200812     01-OCT-08
200901     01-OCT-08
200902     01-OCT-08
200907     01-OCT-08
and in Day dimension table
ROW_WID CALENDER DATE
20090720     20-JUL-09
20090719     19-JUL-09
20090718     18-JUL-09
20090717     17-JUL-09
20090716     16-JUL-09
20090715     15-JUL-09
20090714     14-JUL-09
if i make join between them, i will get different dates
Please suggest any ideas?
Thank you
Kumar

Similar Messages

Fact table contains how many no. of Dim. ids and Key figures?

Fact table contains how many no. of Dim. ids and Key figures?

Max 233 KeyFigures,Max of (16dimensions*)248 DIM Ids?
dim table doesnt contain Charateristics,but Primaray keys of DIM Ids + SIDs where as Fact table contain corresponding Foreign Keys and keyFiures
Message was edited by: Murali

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

Virsa table containing Risk detailed description

Dear,
I would like to know witch table contains the information related to the Detailed Risk description.
The table VIRSA_CC_RISKT contains the following fields RISKID, LANG, DESCN.
DESCN refers to the short description. I would expect to have in that table a long /detailed description field.
Thank you and kind regards
Vincent

I foud the solution by myself :
I've to look into table VIRSA_CC_DETDESC
Thank you and kind regards
Vincent

Tables containing user details.

Hi,
Which table can I use to view all the users available on the SAP system and their details e.g. Username, user's contact details and etc.
Regards,
Thandi

plz check the table:USR03.
Also,you get the Mail-ID in table ADDSMTP
plz chk this link:
Table for user details.

How to Create Inline Table to Display Detail Data in a Master Table in 11g?

Hi,
I have a requirement to create inline table inside master table to show data.
I found this 10g article for this http://download.oracle.com/docs/cd/B31017_01/web.1013/b28967/web_masterdetail006.htm#BABCDCGE
I couldn't find such option in 11g. Am i missing something? Please let me know where i can find more details.
Required Output:
[+] DepartmentId DepartmentName
[-] DepartmentId DepartmentName
EmployeeId FirstName LastName
EmployeeId FirstName LastName
EmployeeId FirstName LastName
[+] DepartmentId DepartmentName
Also, I tried creating the Page as below (Departments -Employees Relation). i.e I have tried using the ADF treeModel in the bindings and then created a table/inline table manually to populate. The data is available in the iterators (i found using sops in back bean), but the inline table is not showing any data. I tried enabling PPR on detail based on master. But no luck.
<af:table rows="#{bindings.Departments1.rangeSize}"
emptyText="#{bindings.findAllStaff1.viewable ? \'No rows yet.\' :
\'Access Denied.\'}"
var="row" value="#{bindings.Departments1.treeModel}">
<af:column headerText="#{bindings.Departments1.labels.DepartmentId}"
sortable="false" sortProperty="DepartmentId">
<af:outputText value="#{row.DepartmentId}"/>
</af:column>
<af:column headerText="#{bindings.Departments1.labels.DepartmentName}"
sortable="false" sortProperty="DepartmentName">
<af:outputText value="#{row.DepartmentName}"/>
</af:column>
<f:facet name="detailStamp">
<af:table rows="#{bindings.Departments1.rangeSize}"
emptyText="No rows yet." var="detailRow"
value="#{row.children}">
<af:column headerText="#{row.children[0].labels.EmployeeId}"
sortable="false" sortProperty="EmployeeId">
<af:outputText value="#{detailRow.EmployeeId}"/>
</af:column>
<af:column headerText="#{row.children[0].labels.FirstName}"
sortable="false" sortProperty="FirstName">
<af:outputText value="#{detailRow.FirstName}"/>
</af:column>
<af:column headerText="#{row.children[0].labels.LastName}"
sortable="false" sortProperty="LastName">
<af:outputText value="#{detailRow.LastName}"/>
</af:column>
</af:table>
</f:facet>
</af:table>
Thanks in Advance,
Harikiran

Hi,
After reading the above links end-to-end twice, I'm finally able to establish the relationship in UI. I've used iterator for my specific purpose, although it can be done using a table/forEach.
1) Create VOs for Dept and Emp, i.e. DeptVO and EmpVO.
2) Then a View Link on deptID, i.e DeptEmpVL
3) Drag and drop the Dept as AdfTreeTable, b'coz it will create the treeBinding and also add the emp accessor by selecting it in the binding window. (refer to above doc links from BaiG)
4) In my Page UI, i've created a new table and an iterator in the detailStamp.
Dept Table ->
o Value = #{bindings.Departments1.treeModel}
o Var = dept
o varStaus = deptVarStatus
Add these:
Column1-> OutputText -> #{dept.DepartmentId}
Column2-> OutputText -> #{dept.DepartmentName}
Insert into TableFacets -> detailStamp -> iterator
Iterator ->
o Value = #{dept.children}
o Var = emp
o varStatus = empVarStatus
Add these:
OutputText -> #{emp.EmployeeId}
OutputText -> #{emp.EmployeeName}
OutputText -> #{emp.Salary}
This iterator/forEach comes in handy for having n Number of regions inside a layout.
Thanks,
Harikiran

Table containing Partner Functions Data for a specific Vendor

Hi SDN members
I'm building an iView on our Supplier Portal, and part of our "Welcome iView", we want to show supplier (vendor) relevant information contained in the Vendor Master. One of them is to show their Quality Partners in Read mode, including their phone # and email address. However, I cannot find the tables linking a Vendor to all the "partners" listed in the Display Vendor : Partner Functions Screen. Do you happen to know where this data is? Also, all the details for a given partner is contained somewhere else, which table(s) would that be?
Thanks in advance for your collaboration!
Eric L.

Hi,
Vendor partner functions are stored in table WYT3.
Cheers !

Table containing Query Key Date

Hi experts!
In what query can I find the key date entered for a query?
I need a fast way to check if all queries contain the correct variable for keydate.
Since there are lots of queries in the system, I´m looking for a fast way to find the information.
Thank you!
Angie

use this Fm
RS_BCT_PFI_VAR_KEYDATE

Reg: Fact table and Dimension table in Data Warehousing -

Hi Experts,
I'm not exactly getting the difference between the criteria which decide how to create a Fact table and Dimension table.
This link http://stackoverflow.com/questions/9362854/database-fact-table-and-dimension-table states :
Fact table contains data that can be aggregate.
Measures are aggregated data expressions (e. Sum of costs, Count of calls, ...)
Dimension contains data that is use to generate groups and filters.
This's fine but how does one decide which columns to consider for Fact table and which columns for Dimension table?
Any help is much appreciated.
Pardon me if this's not the correct place for this question. My first question in the new forum.
Thanks and Regards,
Ranit Biswas

ranitB wrote:
But my main doubt was - what is the criteria to differentiate between columns for Fact tables and Dimension tables? How can one decide upon the design?
Columns of a fact table will often be 'scalar' attributes of the 'fact' data item. A dimension table will often be 'compound' attributes of a 'fact'.
Consider employee information. The EMPLOYEE table can be a fact table. It might have scalar attribute columns such as: DATE_HIRED, STATUS, EMPLOYEE_ID, and so on.
Other related information that can't be specified as a single attribute value would often be stored in a 'dimension' table: ADDRESS, PHONE_NUMBER.
Each address requires several columns to define it: ADDRESS1, ADDRESS2, CITY, STATE, ZIP, COUNTRY. And an employee might have several addresses: WORK_ADDRESS, HOME_ADDRESS. That address info would be stored in a 'dimension' table and only the primary key value of the address record would be stored in the EMPLOYEE 'fact' table.
Same with PHONE_NUMBER. Several columns are required to define a phone number and each employee might have several of them. The dimension tables are used to help 'normalize' the data in the employee 'fact' table.
And that EMPLOYEE table might also be a DIMENSION table for other FACT tables. A DEVELOPER table might have an EMPLOYEE_ID column with a value that points to a 'dimension' row in the EMPLOYEE dimension table.

Multiple Date Fields (Fact Table) - Linking with Time Dimension

I have a fact table that has multiple date columns.
I can make a time dimension, but it has to be joined to a particular date column. This becomes difficult because of the limit in having multiple date fields reference one time dimension. I can see possibly
creating a date table which contains all dates, link to fact as well as time dimension table. I am trying to better visualize the table layout on this one. Or are there possibily better ways of looking at this senerio
Any idea's

Figured this one out; going to use one time dimension - what looking too much into the details in regard to this scenerio

[nQSError: 14025] No fact table exists at the requested level of detail:

Hi All,
I am using OBIEE 11.1.1.6.8.
I have below senario...My fact table contains 3 LTS(yearly, Monthly, Weekly) and TimeDim contains3 LTSs(yearly, Monthly, Weekly)
Fact-Weekly joins with (D1,D2,D3) & TimeDimWeekly
Fact-Monthly joins with (D1,D2,D3) & TimeDimMonthly
Fact-Yearly joins with (D1,D2,D3) & TimeDimYearly
I hv also set the Fact source content to appropriate level of TimeDIM and details level of other Dimensions.
when i build a report using only year_code or month_code_or week_code as filter the query is going to appropriate physical sources
ie. if i take week_code as filter then the query firing to FactWeek, TimeDimWeekly & other Dimensions
if i take Month_code as filter then the query firing to FactMonthk, TimeDimMonthly & other Dimensions
Problem is when I use dynamic filter its is giving [nQSError: 14025] No fact table exists at the requested level of detail: error.
My filter is something like this using presentation variable pvTime (filter is prompted)
case '@{pvTime}'
when 'Weekly' Then "Calendar"."Week - WYYYY"
when 'Monthly' Then "Calendar"."Month - MONYYYY"
when 'Yearly' Then "Calendar"."Year ID" end
Please help me if I missed any step
Thanks
Smita

Its a guess but try the below.. As you are using the CASE statement in your filter, use it in the below way.
Store the value that is prompted into a presentation Variable
YOUR WAY
case '@{pvTime}'
when 'Weekly' Then "Calendar"."Week - WYYYY"
when 'Monthly' Then "Calendar"."Month - MONYYYY"
when 'Yearly' Then "Calendar"."Year ID" end
SUGGESTED WAY
(case '@{pvTime}'='Weekly' and "Calendar"."Week - WYYYY" = '@{new PV}' THEN 1
when '@{pvTime}'='Monthly' and "Calendar"."Month - MONYYYY" = '@{new PV}' THEN 1
when '@{pvTime}'='Yearly' and "Calendar"."Year ID" = '@{new PV}' THEN 1 ELSE 0 END) =1
This might correct the way your are using your CASE statement in Filters..

Unable to join 3 fact tables in obiee data model.

Hi,
I am unable to join the 3 fact tables in obiee rpd. If I join with 2 fact tables I got the data in repors, Once I add the one more fact table and join with related dimensions, I am getting nodata error. I am following all joins keys as per datamodel, I am able to see the data in database. anyone pls give me the solution. Thanks in advance.
Edited by: 1007582 on May 23, 2013 2:17 AM

Can you please give some more detail as in what you have model in RPD;
For example, if There are 3 Fact table F1, F2, F3 and two Dimesion Confirmed_D1, Non_Conf_D2. Confirmed_D1 is joined to all three fact tables and Non_Conf_D2 is joined to F2.
Now to implement this model we have to set the logical content level in BMM layer for Non_Conf_D2 in F1 & F2 to Total*. After this only we can report on Confirmed_D1, Non_Conf_D2, F1, F2, F3 whithout any error.
Sometime join with multiple table can also result in No Data, since the join conditions filters out the result data.
Please mark helpful or correct.
Regards,
Kashinath

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.

Unexpected results getting data from two fact tables through conformed dim

Hi all,
We are getting an unexpected behaviour in our OBIEE 10.1.3.3.3. We have this scenario:
We have {color:#0000ff}2 fact tables{color}{color:#000000} called F1 and F2. F1 has one measure, f1m1 and F2 has another one, f2m1.
We have {color:#0000ff}4 conformed dimensions{color}, called D1, D2, D3, Date.
When we are requesting for individual fact tables, we are getting:
date d1 d2 d3 f1m1
dt1 - x - y - z - m1
dt1 - x - y - z' - m2
date d1 d2 d3 f2m1
dt1 - x - y - z - m3
dt1 - x - y - z'' - m4
But, trying to obtain a compare scenario, we are getting
date d1 d2 d3 f1m1 f2m1
dt1 x y z m1 m4
Instead of
date d1 d2 d3 f1m1 f2m1
dt1 x y z m1 m3
Looking at query log, we have catched the reason. That's why BI Server is using to solve this request using ROW_COUNT() to join SAWITH0 and SAWITH1 in SAWITH2 result set. So, the order may not be the same in the results sets in every fact table. More or less, generated query is like:
WITH
SAWITH0 AS
(select ....
from F1),
SAWITH1 AS
(select ...
from F2),
SAWITH2 AS
select from (select ...
ROW_NUMBER() OVER PARTITION (....) c10
from SAWITH0.d1 full outer join SAWITH1.d1 ....) D1
{color:#ff0000}where (D1.c10 = 1){color}
select SAWITH2. ....
from SAWITH2
order by c1..c10
The problems seems to be that BI server is ordering the result sets SAWITH0 and SAWITH1 and getting row number to join this results sets, but this is not getting the correct result.
Any ideas?
TIA
Javier
{color}
Edited by: jirazazábal on Mar 13, 2009 2:46 PM

I have done a logical fact table with two fact table source on it.
The Sql performed against the database was this one.
-------------------- Sending query to database named PRODS_AIX (id: <<153418>>):
WITH
SAWITH0 AS (select sum(T21296.CONSUMERS_SALES_EURO) as c1,
     T21309.DIVISION_CODE as c2
from
     DIVISION T21309,
     C_CONSUMERS_SALES T21296
where ( T21296.DIVISION = T21309.DIMENSION_KEY )
group by T21309.DIVISION_CODE),
SAWITH1 AS (select sum(T21356.ORDER_VALUE) as c1,
     T21309.DIVISION_CODE as c2
from
     DIVISION T21309,
     DWH_SALES_ORDER_OVERVIEW T21356
where ( T21309.DIMENSION_KEY = T21356.DIVISION_KEY )
group by T21309.DIVISION_CODE)
select distinct case when SAWITH0.c2 is not null then SAWITH0.c2 when SAWITH1.c2 is not null then SAWITH1.c2 end as c1,
     SAWITH0.c1 as c2,
     SAWITH1.c1 as c3
from
     SAWITH0 full outer join SAWITH1 On nvl(SAWITH0.c2 , 'q') = nvl(SAWITH1.c2 , 'q') and nvl(SAWITH0.c2 , 'z') = nvl(SAWITH1.c2 , 'z')
order by c1As you can see one select (SAWITH0) for the first fact table C_CONSUMERS_SALES and one select for the second fact table DWH_SALES_ORDER_OVERVIEW (SAWITH1 ) and the two statement are joined with a full outer join.
I ask me why you have the three select (SAWITH0,SAWITH1 and SAWITH2). Can you please paste the complete SQL performed ?
Can you tell us also which SQL is performed if you select only the columns from one fact table and not for the other ?
Regards
Nico
http://gerardnico.com

Fact table with different dates

Hello,
In my fact table I have several date columns (order date, payment date, ....) and I have only one time table in my physical model.
For example this model
Fact table
order day
payment day
Timetable
day - pk
I want to create 2 fks in order to have time analyse with order date and payment date
FK1 : fact_table.order_day and timetable.day
FK2 : fact_table.payment_day and timetable.day
validating the model, OBI tells me that i cant' t have various joins between 2 tables
Anyone know how to solve this ? (I think it is a quite common problem)
Thanks in advance

Create an alias for your dimension Timetable and then join that with your fact table. So basically you would have 2 dimensions, one joining with order day the other joining with payment day.
Thanks,
Venkat
http://oraclebizint.wordpress.com

OOTB Fact table contains Employee detailed Dates

Similar Messages

Maybe you are looking for