2 Fact Tables with a same content level
Hi,
I have 2 fact tables F1,F2 joined to the same 4 dimensions D1,D2,D3,D4.The detail level # of elements multiplied for all the dimensions D1,D2,D3,D4 are the same for both dimension.I even set the content level for the 2 fact tables and the content filter is the same in both fact tables F1.Column1=0 in F1 fact table and F2.Column1=0 in F2 fact table.So how does OBIEE decide which fact table to select in this scenario.
I went through the below blog but could not get much information
http://obiee-blog.info/administration-tool/what-rule-is-followed-when-several-fact-are-at-the-same-content-level/
I appreciate if anyone can guide me with the right answers.
How many records retrieving when joining F1 & F2 with dimension ? if the f1 and d1 has 200 records and f2 and d1 is retriving 100 records it chooses shortest path.
thanks,
Saichand
Similar Messages
-
Problem using 2 Fact tables with the same dimension
Hi,
I have noticed a very strange behaviour in Presentation Services / BI Administrator. I have 2 cubes (created in OWB) which are in the same business model, they are set up with foreign keys etc. and works as they should using them separately. Problem is (sometimes!) when I want to use the common dimension (Project) against both of the fact tables (Sales Order and Purchase Order).
Scenario 1:
If I use Project Id, Purchase Amount, Sales Amount I get either an amount in Sales Amount or in Purchase Amount, BUT if the Project Id starts with a letter (not starting with a number) it will show the correct amount for both Sales- and Purchase Amount.
Scenario 2:
I use Project Description (even followed by Project Id or not), Sales Amount, Purchase Amount I get the correct numbers for all projects. Project Description must come before Project Id or else it will not work.
I only noticed this problem when using both of the Fact tables since I want to compare Sales Amount and Purchase Amount in each Project. The Dimension for Project consist of Project, Sub Project and Activity and works fine. If I only use Sales Amount or Purchase Amount with Project Id I don't get this error. Only when both numbers are used.
I would be very happy if anyone have a good solution/explanation to this problem! Seems like could be something in the BI Server memory that goes wrong somewhere.The strange thing is that the results from the queries are correct running them in SQL Developer. This is one that works:
SELECT Project.Project saw_0, "- SalesOrderFact"."Sales Amount" saw_1, "- PurchaseOrderFact"."Purchase Amount" saw_2, REPORT_SUM(saw_1 BY ), REPORT_SUM(saw_2 BY ) FROM SalesOrder ORDER BY saw_0
SALES ORDER:
select T3032.PROJECT_DESCRIPTION as c1,
sum(T161.SALES_AMOUNT_LOCAL) as c2
from
DIM_PROJECT_V T3032,
CUBE_SALES_ORDER T161
where ( T161.DIM_PROJECT = T3032.DIMENSION_KEY )
group by T3032.PROJECT_DESCRIPTION
order by c1
PURCHASE_ORDER:
select T3032.PROJECT_DESCRIPTION as c1,
sum(T3020.TOTAL_BUY_AMOUNT) as c2
from
DIM_PROJECT_V T3032,
CUBE_PURCH_ORDER T3020
where ( T3020.DIM_PROJECT = T3032.DIMENSION_KEY )
group by T3032.PROJECT_DESCRIPTION
order by c1
And this will give the wrong result in Answers (correct in SQL..):
SELECT Project."Project Id" saw_0, "- SalesOrderFact"."Sales Amount" saw_1, "- PurchaseOrderFact"."Purchase Amount" saw_2, REPORT_SUM(saw_1 BY ), REPORT_SUM(saw_2 BY ) FROM SalesOrder ORDER BY saw_0
SALES_ORDER:
select T3032.PROJECT_KEY_NAME_ID as c1,
sum(T161.SALES_AMOUNT_LOCAL) as c2
from
DIM_PROJECT_V T3032,
CUBE_SALES_ORDER T161
where ( T161.DIM_PROJECT = T3032.DIMENSION_KEY )
group by T3032.PROJECT_KEY_NAME_ID
order by c1
PURCHASE_ORDER:
select T3032.PROJECT_KEY_NAME_ID as c1,
sum(T3020.TOTAL_BUY_AMOUNT) as c2
from
DIM_PROJECT_V T3032,
CUBE_PURCH_ORDER T3020
where ( T3020.DIM_PROJECT = T3032.DIMENSION_KEY )
group by T3032.PROJECT_KEY_NAME_ID
order by c1
As you can see the SQL look very familiar, and I cannot see anything in SQL that should be the cause of this error. I think the error must be in the BI Memory or something.
Any ideas? -
OBIEE 11g - No fact table exists at the requested level of detail
My dimesion tables are snow-flake.
Table1 has Key, ProductName, ProductSize, Table2Key
Table2 has Key, ProductDepartment, Table3Key
Table3 has Key, ProductDivision
I have created 2 hierarchies (in same dimension Product). Note: ProductSize is in Table1.
ProductDivision > ProductDepartment > ProductName (shared level)
ProductSize > ProductName (shared level)
There are 2 fact tables
Fact1 is at ProductName level
Fact2 is at ProductDepartment level
When I create a request with columns as ProductSize and some measure; and filter it on ProductDepartment. The request fails with error "No fact table exists at the requested level of detail", but the request can ideally be answered using fact with ProductName level.
I have properly defined logical level keys in the hierarchies and logical level in the LTS (content tab)
Can anyone point me what I am doing wrong here?Since both fact tables are at same granular level I would suggest to map each other (Signon_A maping Signon_B) in BMM layer logical fact @source.
Considering them as Fact and with fact extension.
BTW: Did you try by setting implicit fact at subject area properties?
Edited by: Srini VEERAVALLI on Feb 1, 2013 9:04 AM -
Join fact table with higher dimension level
how do i join fact tables with higher dimension levels with discoverer?
fact with detail at level C
measure X
dimension with
D->C->B->A
E->C
level
A B C
1------1------1
2------2------1
3------2------1
join between fact X and dimension level C
X=3*C because of sum(X) in discoverer and 3xC in dimension
is there a way to get correct values for X without creating a dimension like
D->C
E->another way of asking this is whether you can create a summary table in Discoverer at a higher level than a dimension's fundamental grain. In other words - the summary examples in the documentation all describe leaving out one or more of your dimensions... they are either left in or completely taken out. But, some of the most effective summarization occurs when you summarize daily data to a monthly level. Assuming that I have a sales table (at a daily level, and a key value sales_date), and a table date_dim (primary key sales_date), I would like to create a summary sales_month_summary where the sales are grouped on month_year (which is a field in the sales_date table).
How is this done? I suspect that we can't use the date_dim table with the summary (due to the problems noted by the poster above). Do we have to create another table "month_dim"? Do we have to fold all of the desired date attributes (month, quarter, year) into the summary? Obviously we'd like to re-use all of the pertinent already existing date items (quarter, month, year, etc.), not recreate them over again, which would result in essentially two sets of items in the EUL. [One used for this month summary, and another used for the detail.]
I searched the forum - someone asked this same question back in 2000 - there was no answer provided.
The only other thought I have is to "snowflake" the date_dim into two tables and two folders, one at a date level, another at the month level. Then the detail tables can connect to date_dim (which is linked to month_dim), while the summary data can connect directly to month_dim. -
How to implement fact tables with finest level of detail (fine-grained)?
Hi,
Maybe this is basic knowledge what I'm asking here... I don't know, well, here it goes:
I need to know the way carry my transactional data to a fact table, but keeping the finest level of detail possible (namely, the transactions). I implemented my cubes with MOLAP option for storage (those were the specs that I had to follow) so I can't add a unique constraint to those structures.
I only seem to be able to load aggregated, precomputed data. If I wanted to load the transactions (after the data has been transformed and clenased) where should I do it?
I tried to implement a version of the fact tables as ROLAP but got nowhere (I couldn't add a unique constraint or index on that column either).
I would really, really appreciate your help.
Best Regards,
osvaldo.
[osantos]Hi Veeravalli,
Thanks for your reply :)
Let me explain the problem in more detail. I have one Date dimension(Date_Code,Month_Code,Quarter_Code,Half_Year_Code,Year_Code). Here Date_Code is the PK.
In F1---->Date (Using Month_Code key)
F2-------->Date (Using Date_Code Key)
Level based hierarchy is there starting from Year to Date.Each level has PK defined and chronological key selected.
F1 has level set to Month and F2 has level set to Day.
Now if i am using ago() function on measure of F2 (having day level data) then it's working fine but if i am using ago() function on measure of F1...I am getting an error at Presentation service: Date_code must be projected for time-series functions.
So the whole issue is with time-series functions. As per my research...I think for time series the tables in the physical model containing the time dimension cannot join to other data sources, except at the most detailed level but here i am joining with F1(using Month_Code which is not the most detailed level).
So kindly let me know how to achieve this in rpd? -
[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
SmitaIts 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.. -
No Fact Table Exists at the request level of Detail
Hi,
I'm new to BI.can anybody come across more than one fact table in BMM layer,currently i working with AP module,i am getting the error Error NO:14025 No Fact Table Exists at the request level of Detail.
Even i check with content tab where i have given detail level for confirming tables and total for non-confirming tables.
can any one have document related more than fact table in BMM layer, any body give me the right solution.
Thanks in advance !thanks for your response,i did for the selected measures also. in Account payable model i have two fact.
F1 with dimension D1,D2,D3,D4
F2 with Dimension D5,D6,D7,D8
when i'm trying to generate reports F1 with D1,D2,D3,D4 i am getting the output,but with the non-conforming table D5,D6,D7 i am getting the error. can you give some document to work more than 1 fact table. -
No Fact table exists at this detail level error
Hi All,
I am trying to develop an RPD and was trying to use a simple example of joining two fact tables in OBIEE through confirmed dimension.
This is my example:
Fact A: Student ID (FK)......Measure1, Measure2...
Fact B: Student ID (FK)........Measure A, Measure B
DIM 1: Student ID (PK),.....
I would like to give the users the option of joining Fact A and Fact B through Dim 1( Which is a conforming Dimension)
I tried with out level based hierarchy and got NO Fact exists at this level of detail.
Then I tried creating the level based hierarchy on Dim 1 and selected the detail level for the fact table and I am still getting the error message.
Am i doing some thing wrong here ? Or Am i missing any important setting ?
Is there a way to check whether the dimension is a conforming dimension or not in OBIEE.
Your help is much appreciated.
Thanks
VenuCan we use between operator in physical join. We did that, its successfully checking in, but when we re-open the join, its show in RED color.
So, got doubt, can we use between?When you checkout the rpd object in online mode it would display in red, this is not an error.
"No fact table exists at the requested level of detail"; what does this error meanThis error usually happens if you have not mapped the content level correctly in the logical table source.
Rgds,
Dpka -
Joining two fact tables with different dimensions into single logical table
Hi Gurus,
I try to accomplish in Oracle Business Intelligence 11.1.1.3.0:
F1 (D1, D2 and D3)
F2 (D1 and D2 and D4)
And we want to build a report F1 F2 D1 D2 D3 D4 to have data for:
F1 that match only for D1-D2-D3
and data for
F2 that match only D1-D2-D4
all that in one row, so D3 and D4 are not common dimensions.
I can only do:
F3 (D1, D2)
F4 (D1, D2 and D4)
And report
F3 F4 D1,D2,D4 (all that in one row, and only D4 is not a common dimension)
Here is the very good example how to accomplish the scenario 1
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
But looks like it does not work in 11.1.1.3.0
I get
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 14025] No fact table exists at the requested level of detail: [,,Clients,,Day,ROI,,,,EW_Names,,,,,,,,,,,,,,,,,]. (HY000)
I am sure I set up everything correctly as advised in the blog but it works with only one not a common dimension
Is it a bug in 11.1.1.3.0 or something?
Thanks,
KateThanks 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 -
Using 2 fact tables with different granularity against calendar dimension
Hello gurus,
I have a requirement to provide a report to show the consumption of available capacity per month and also YTD.
I have two fact tables:
Fact table ‘Capacity’ with columns:
- Site_id
- Month_id
- Capacity
Ie.
001, 2010M01, 50
001, 2010M02, 50
001, 2010M12, 75
002, 2010M01, 60
002, 2010M02, 65
002, 2010M12, 80
Etc
Fact table ‘Consumption’ with columns
- Site_id
- Day_id
- Consumption
Ie
001, 20100101, 2
001, 20100102, 3
001, 20100131, 1
001, 20100201, 5
001, 20100212, 6
001, 20100228, 4
Etc
As can be see above, my ‘Capacity’ table contains monthly volumes, and the ‘Cunsumption’ table contains daily volumes.
My Calendar dimension is straightforward:
Year
Quarter_id
Month_id
Day_id
Ie
2010, 2010Q1, 2010M01, 20100101
2010, 2010Q1, 2010M01, 20100102
2010, 2010Q1, 2010M01, 20100103
2010, 2010Q1, 2010M01, 20100104
Etc
The MfgSite dimension is also simple:
Site_id
Site_name
Group
These are the steps I have taken sofar:
- Imported the four tables
- Created following joins:
MfgSite.Site_id = Capacity.Site_id
MfgSite.Site_id = Consumption.Site_id
Calendar.Month_id = Capacity.Month_id
Calendar.Day_id = Consumption.Day_id
- Created Business Model Diagram in BMM
- Created Calendar hierachy:
Year, Quarter, Month, Day
- Created MfgSite hierarchy:
Group, SiteName
- Setup Logical Table Source / Content settings as follows:
Fact table Capacity:
Dimension MfgSite: Logical Level = Site
Dimension Calendar: Logical Level = Month
Fact table Consumption:
Dimension MfgSite: Logical Level = Site
Dimension Calendar: Logical Level = Day
- Set Default Aggregation Rule to Sum on Logical Columns:
Capacity.Capacity
Consumption.Consumption
- Created following YTD Logical Columns:
YTDCapacity = TODATE(Capacity.Capacity, Calendar.Year)
YTDConsumption = TODATE(Consumption.Consumption, Calendar.Year)
- Created Presentaion layer
I then built a few reports to test it out and found that I have an issue with the Capacity object: When I build a simple report to show capacity per month:
SiteName, Month, Capacity
the capacity for each month is multiplied by the number of calendardays in that months, so I get
Site Month Capacity
001 2010M01 1550 (= 31 x 50)
001 2010M02 1400 (= 28 x 50)
Etc
In addition, when I add YTDCapacity to my report, the report fails with the following message:
Unable to navigate requested expression: ToDate(Capacity:[DAggr(Capacity.Capacity by [ Calendar.Year, Calendar.Month_id, MfgSite.Site_id, MfgSite.SiteName] )], [Level Year]). Please fix the metadata consistency warnings. (HY000)
Did I miss any steps? Any help is greatly appreciated!
Thanks!
Randallhi in the capacity fact table remove the level set for the calendar dim and see.
-
No fact table exists at the requested level of detail Error.
Hi Everybody,
Facing a issue on the using Fact less Fact tables.
Scenario:
========
Using two subject areas to develop a report.OBIEE 11g
Fact1 --> Compensation Plan Assignments Real Time
Fact2 --> Participant Detail Real Time"."Participant Details
On both facts we created dummy metrics on respective table id's and aggregated to ROWCOUNT.
As i said in earlier we are using the above 2 subject areas to develop reports.
Logical SQL:
===========
SELECT
0 s_0, "Incentive Compensation - Compensation Plan Assignments Real Time"."Role"."Role Name" s_1,
"Incentive Compensation - Participant Detail Real Time"."Participant Details"."Cost Center" s_2,
"Incentive Compensation - Participant Detail Real Time"."Participant Details"."Country Code" s_3,
"Incentive Compensation - Participant Detail Real Time"."Participant"."Participant First Name" s_4,
"Incentive Compensation - Participant Detail Real Time"."Participant"."Participant Last Name" s_5,
"Incentive Compensation - Participant Detail Real Time"."Participant"."Party Number" s_6
FROM "Incentive Compensation - Earnings Real Time" FETCH FIRST 65001 ROWS ONLY
Error Message:
==============
Expression 'RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]' converted to NULL because [nQSError: 14020] None of the fact tables are compatible with the query request RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]..
[2013-10-21T12:18:45.000-05:00] [OracleBIServerComponent] [TRACE:2] [USER-34] [] [ecid: 004uJx90aHO9lZ73VJJNB80007eh000gl_,0:2:1:9:5] [tid: 457c2940] [requestid: f2e001b] [sessionid: f2e0000] [username: [email protected]] -------------------- Query Status: [nQSError: 14025] No fact table exists at the requested level of detail:
Please share some ideas on this or any guidelines will be very much helpfull.Govardhan,
Did u configured any Dimension Hierarchy please set the levels in that particular Fact LTS.
For more info,check the below thread
https://forums.oracle.com/thread/2134934
Thanks, -
No fact table exists at the requested level of detail
We have two fact tables F1,F2 and D1, D2, D3, D4, D5 dimensions.
They are connected line this.
F1 to D1, D2, D3 and self dimension D_of_F1
F2 to D2, D3 and self dimension D_of_F2
Means D2 and D3 are common dimensions between two facts.
D_of_F1
|
|
D1--F1--D2
| |
| |
D3 |
| |
| |
|-F2-|
|
|
|
D_of_F2
Hierarchies
H1 for D1
H2 for D2
H3 for D3
H_of_F1 for D_of_F1
H_of_F2 for D_of_F2
and pinned LTS of F1 --> H1 detail, H2 Detail,H3 Detail, H_of_F1 Detail
and pinned LTS of F2 --> H2 Detail,H3 Detail, H_of_F2 Detail
We are selecting these columns
D1.C1, D1.C2, D2.C1, D2.C2,D3.C1 and report works perfactly.
But when I add D_of_F2.C1 then report gives this error
Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail
Please help me to solve this error....
I m new in OBIEE concepts so not able to trubleshoot...
Thank you.i'm try to do an analysis between two tables (that have a relatinship), we had inclued first the FACTURA.FACTURA_COD, then columns from COBRANCAS and it work's. When we inclued the FACTURA.COMISSIONISTA_ID it return the fowlling error :check the level set in content tab in fact table.it can happen that FACTURA.COMISSIONISTA_ID is at a lower level than specified in fact table.
Regards,
Sandeep -
No fact table exists at the requested level
Hi,
I have a 3 dimension tables and D_CANDIDATE, D_QUALIFICATION, D_SERIES. D_CANDIDATE is linked with D_QUALIFICATION and D_SERIES. If i create a analysis with all the 3 dimensions i am getting this error. no fact table exists at the requested level. When i remove D_SERIES from the analysis it is fine. What i might have done wrong. Can anyone help me out please.
Regards,
NateshSo I'm assuming your joins are like
D_CANDIDATE--> D_QUALIFICATION
D_CANDIDATE--> D_SERIES
Then treat D_CANDIDATE as logical fact in BMM and use reports, it is nice to have default hierarchies for D_QUALIFICATION and D_SERIES. in this case D_QUALIFICATION and D_SERIES are logical dimension tables in BMM
Edited by: Srini VEERAVALLI on Apr 4, 2013 8:05 AM -
No fact table exists at the requested level of detai error
Hi Gurus,
Gud Evening,
There is a report with 10 columns and its coming fine when ever we are adding new column some date column (Start Date) it is showing the below error
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 14025] No fact table exists at the requested level of detail:
Can any give some suggestions..
RegardsHi,
You have to go to the fact LTS and set granularity for each dimension associated with it. You might be bringing a column from a dimension in your report, for which you didn't set up granularity in the facts LTS.
Thanks
Venkat
OBIEEDeveloper -
Logical fact table with fragmented data sources with different dimensions
Hello.
I have a logical fact table with four logical table sources. Three of the LTS's share the same dimensions, but the fourth LTS has one dimension (called Dim_A) less. In the physical layer the dimension Dim_A is joined to the first three physical fact tables, but not to the fourth fact table (since it doesn't have that dimensionality). In the BMM layer the logical fact table is joines to the logical dimansion Dim_A.
When I run an analysis on this RPD the measures from the logical fact is aggregated correctly (union of all four table sources) as long as I doesn't include Dim_A, but as soon as I include dimension Dim_A I get the error message:
+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: 14052] Internal Error: Logical column Dim_A.Column_X has no physical sources that can be joined to the physical fact table source [Logical table sources (Priority=0): Fact_B.Fact_Y]. (HY000)+
I would like a solution where the analysis returns correctly aggregated measures also for the LTS with the "missing" dimension, but with a dimension value NULL for this LTS. Or something like this.
Is there a way to set this up in the RPD.
Thanks,
Henning EriksenThe SQL could look something like this.
SELECT dim_a.col_1, fact_a.measure_1
FROM db.dim_a
JOIN
db.fact_a
ON fact_a.col_2 = dim_a.col_2
WHERE fact_a.date = '28-nov-2012'
UNION ALL
SELECT dim_a.col_1, SUM (fact_b.measure_1)
FROM db.dim_a
JOIN
db.fact_b
ON fact_b.col_2 = dim_a.col_2
WHERE fact_b.date = '28-nov-2012'
UNION ALL
SELECT dim_a.col_1, SUM (fact_c.measure_1)
FROM db.dim_a
JOIN
db.fact_c
ON fact_c.col_2 = dim_a.col_2
WHERE fact_c.date = '28-nov-2012'
UNION ALL
SELECT NULL, SUM (fact_d.measure_1)
FROM db.fact_d
WHERE fact_d.date = '28-nov-2012'
I would appreciate if you could give me some hints for the RPD.
Thanks,
Henning
Maybe you are looking for
-
I have restarted my ipod touch a countless amount of times, and it is stuck on a screen. on the screen it says, "ipod is disabled, connect to itunes". i have also tried connecting it to itunes, and itunes says i have to type my passcode in for it to
-
Partition map check failed because no slices were found for WD My Book 1140 media
Have been using a WD My Book 3TB HD which was partitioned into three 1TB partitions for almost a year. Now when I try to access it via my MacBook Pro I am getting the following error message "Problems were found with the partition map which might pr
-
Reject Purchase order using abap OO class CL_PO_HEADER_HANDLE_MM
Hi all, We have created a webdynpro application for maintaining purchase order by using class CL_PO_HEADER_HANDLE_MM. With this class we are able to release (method RELEASESTATE_MM~RELEASE) or cancel release.. We are trying, in vain, to reject purc
-
How to send GOS document attached to PO for Printing
Hi, My requirement is as below. My user is creating attachment to the Purchase Order using GOS. For purchase order we have created one Z smart from. So when ever the user print the from for PO, along with the PO form my client want to print all the a
-
Finding data in a datasource/ Business Content Query
Hello, can you help me with this one -- background to this problem is shown below: Question: 1. No data was found in my infocube so I went o R3 to see if the datasource had any data in it by running rsa3 but found no datasource 2LIS_02_S012, although