Summary and Detail Fact Tables in one Universe ...

We have a classic star Schema with a snapshot( summary table by month) and a detail activity table on Daily activity. What is best way to design a Universe to accomodate this requirement.
1. Seperate Universe for summary Table
This removes the functionality of Drill down, and Drill down can be only available through links in Webi Reports.
2. One Universe for both Summary and Fact, and write logic for aggregate awareness. It will complicate the universe since we have close to 100 odd mesasures.
Thanks

Hi Devendra,
Use aggregate awareness irrespective of the "complicated" matter.

Similar Messages

Issue using one 2 Fact tables with one dimension Table.

Hi,
I have 1 Dimension table X and 2 Fact tables A and B
X is joined to Both A and B for Loan Amount ( with A) and for colleatral amount (with B) when I am selecting the X.Product_Name, A.Loan_Amt, B.Collateral Amount, it is giving an error message
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table EIP Collateral FACT) does not contain mapping for [EIP Reporting FACT.PD ID]. (HY000)
Any clues???
Is there a Inner or Outer join which needs to be created or set in the RPD to get the desired results???

Ok..
I have one table which is Porfolio Details which has Portfolio name, Product Category , Product Name, Product ID, Product sources code.- This is my Dimension table.
I have another 2 set of fact tables : EIP Reporting FACT and EIP Collateral FACT..
These two tables are joined to Portfolio Details table.
EIP Reprting FACT gives portfolio wise Loan Amount
and EIP Collateral FACT gives Portfolio wise Collateral Amount details for same set of customer..
Now, I am selecting Portfolio Name, Product Category, Product Name,SUM( EIP Reporting FACT.LOAN_AMOUNT), SUM(EIP Collaetral FACT.Collateral_Amt) in a report
Now, on selecting these columns I am getting that error message which is related to mapping.
If I take any column from Portfolio details table and any column from EIP Reporting FACT- It works.
If I take any column from Portfolio details table and any column from EIP Colletral FACT- It works.
But if I take any column from portfolio table and columns from both FACT tables it gives mapping error...
Hope I am able to explain the issue in a better way now..
Edited by: help-required on Mar 11, 2010 6:53 PM
Edited by: help-required on Mar 11, 2010 6:53 PM

Hoe top create summary and detail report using ABAP QUERY

Hi ,
Can any one suggest me how to create summary and detailed report using ABAP Quey.
Regards,
Raghu.

Hi,
Table Declaration
tables:mara,mast.
*Declaring the internal table
data: begin of itab_new occurs 0,
      matnr like mara-matnr,     "Material No
      ernam like mara-ernam,     "Material Created by
      mtart like mara-mtart,     "Material Type
      matkl like mara-matkl,     "Material Desc
      werks like mast-werks,     "Plant
      aenam like mast-aenam,     "BOM created
      stlal like mast-stlal,     "Alternative BOM
      end of itab_new.
select-options: p_matnr for mara-matnr.
CODE A : Retrieving the data from the database
     select f~matnr f~ernam f~mtart f~matkl m~werks m~aenam m~stlal
     into table itab_new
     from mara as f inner join mast as m
     on f~matnr = m~matnr
     where f~matnr in p_matnr.
CODE B : Retrieving the data from the database.
    SELECT FMATNR FERNAM FMTART FMATKL MWERKS MAENAM M~STLAL
    INTO TABLE ITAB_NEW
    FROM MARA AS F INNER JOIN MAST AS M
    ON FMATNR = MMATNR
    WHERE F~MATNR = P_MATNR.
    SORT ITAB_NEW BY ERNAM.
loop at itab_new.
write:/5 itab_new-matnr,itab_new-ernam,itab_new-mtart,itab_new-matkl,itab_new-werks,itab_new-aenam,itab_new-stlal.
endloop.
*TABLES: MARA , MAST.
*DATA:BEGIN OF ITAB_NEW OCCURS 0,
             MATNR LIKE MARA-MATNR,
             ERNAM LIKE MARA-ERNAM,
             MTART LIKE MARA-MTART,
             MATKL LIKE MARA-MATKL,
             END OF ITAB_NEW.
   SELECT MATNR ERNAM MTART MATKL
   INTO TABLE ITAB_NEW
   FROM MARA
   WHERE MTART = 'T'
   ORDER BY MATNR ERNAM MTART MATKL.
*DATA: BEGIN OF ITAB OCCURS 0,
     MATNR LIKE MARA-MATNR,
     END OF ITAB.
Thank U,
Jay....

Something about two fact table in one subject

Hi all,
when I using two fact table in one subject, it can't make sense as expected.
The problem is describled as follows:
1.about the RPD:
In the presentation layer of Admin Tool, there is a mesure names "A", which is equal to B*C, come from table t1 and table t2 in logical layer respectively.
2. In biee Answeers, I created an answeer which includes some dimesions and the mesure A, another mesuare m1.
but in the the result pane, i saw there is no data in the the colume of mesure A, all other performs well.
3. so, I went for the NQquery for the phisical SQL, and found that,
in Where clause, table t2 is lost.
why? and how can I make it?

This sounds interesting. What would I join there? The dimension keys of the two fact tables?
Unfortunately this Logical Table Source stuff looks quite different in Admintool 11g. What would I need to create there?
Thanks,
Knut

Use different Layouts for Summary and Details in Drill down report

Hi All,
I have a 2 level drill down report in ALV.
The summary report has certain fields and the Detail report has different fields. Now my problem is that when i use a default layout (with all fields of summary report) for the summary report, and drill down to the detail report i'm missing the fields on detail that are not in Summary. And if i save the default layout as default (with all fields of Detail) and go back to sumary, I'm missing the some other fields on summary (which are not on detail report).
Is there a way to make different default layouts for each of those summary and detail reports:
Also as the layouts are choosen by the user, i cannot hardcode any particular layout;
So if the user chooses a layout for detail; it has to stay the same layout for the detail report if he goes to summary and then back to detail; unless the user changes the layout again.
I'm using two different Layout types for each report. but i still cannot get the desired effect.
Data:
 gt_layout_s type slis_layout_alv,
 gt_layout_d type slis_layout_alv,
call function 'REUSE_ALV_GRID_DISPLAY'
 exporting
 i_callback_program = g_repid
 is_layout = gt_layout_s
 i_callback_top_of_page = g_top_of_page
 i_callback_user_command = g_user_command
 i_callback_pf_status_set = g_status
 i_save = g_save
 is_variant = gs_variant
 it_fieldcat = gt_fieldcat[]
 it_events = gt_events[]
 importing
 es_exit_caused_by_user = gs_exit_caused_by_user
 tables
 t_outtab = it_summary.
call function 'REUSE_ALV_GRID_DISPLAY'
 exporting
 i_callback_program = g_repid
 is_layout = gt_layout_d
 i_callback_top_of_page = g_top_of_page
 i_callback_user_command = g_user_command
 i_callback_pf_status_set = g_status
 i_save = g_save
 is_variant = gs_variant
 it_fieldcat = gt_fieldcat[]
 it_events = gt_events[]
 importing
 es_exit_caused_by_user = gs_exit_caused_by_user
 tables
 t_outtab = it_detail_disp.

Here is how you differentiate between the layout of two different grids. There is the parameter, IS_VARIANT in the function. You usually leave it empty or pass only the report name and username. What you need to do is to pass unique string for each grids to the HANDLE field of the parameter IS_VARIANT. You can probably hard code it as HEADER and DETAILS in your case. Once that is done, system identified that these two different layout for different grids.
Regards,
Ravi
Note : Please mark all the helpful answers

How to link a fact table to one dimension many times

I have fact table which contains four date fields and I want to connect all of them to the Time dimension. I think I probably must split this fact table to multiple tables and then link them to dimensions. What is the right way to solve this kind of problem?
Example: Fact table: TimeIn, TimOut, TimeStart, TimeStop, InPlace, OutPlace, StartPlace, StopPlace, Speed, Weight, Width, Height .....
Thank you

Hello Kostis,
thank you for your answer. I don't fully understand you. Can you show me short example, please? I create alias table for time dimension on Physical Layer - original table is TimeDayDim and I create aliases TimeDayDim1, TimeDayDim2, TimeDayDim3, TimeDayDim4. Then I create foreign key Fact.Time1 -> TimeDayDim1, Fact.Time2 -> TimeDayDim2, Fact.Time3 -> TimeDayDim3, Fact.Time4 -> TimeDayDim4. And what now? Must I create these table api Bussines Model and create new time dimensions at bussiness model????
I need in Answers ONE Time dimension. I think I must split my fact table to four tables ... (time1, place1 ...) (time2, place2 ...) (time3 place3...) (time4 place4...) then link those tables to Time dimension (but I dont know where I can split those tables - on Physical Layer or on Bussines Layer).
I suppose that I will have in Answers one time dimension and four facts tables and I will be able to query them. (for example: Time.Days, Fact1.Place1, Fact3.Speed, Fact4.Count Criteria: Time.Year = 2008)
Best Regards Vlada

3 confirmed Dimensions and 2 fact tables

Hi experts,
how can we connect 3 confirmed Dimensions and 2 fact tables without loops and traps please give me a solution

Hi,
Dimensions Tables : Dimension tables are typically small, ranging from a few to several thousand rows. Occasionally dimensions can grow fairly large, however. For example, a large credit card company could have a customer dimension with millions of rows. Dimension table structure is typically very lean, for example customer dimension could look like following:
    Customer_key
    Customer_full_name
    Customer_city
    Customer_state
    Customer_country
Fact Tables :a fact table consists of the measurements, metrics or facts of a business process. It is often located at the centre of a star schema or a snowflake schema, surrounded by dimension tables.
Fact tables contain keys to dimension tables as well as measurable facts that data analysts would want to examine. For example, a store selling automotive parts might have a fact table recording a sale of each item. The fact table of an educational entity could track credit hours awarded to students. A bakery could have a fact table that records manufacturing of various baked goods.
Context Versus Alias Overview :
http://www.dagira.com/2009/07/22/context-versus-alias-overview/
How to create context :
http://www.bidw.org/business-objects/universe-design/understanding-context-and-its-use-in-business-objects-universe/
You can also look on the eFashion universe for more information.
Thanks,
Amit

Multiple fact tables using one measure

Hi Experts,
Multiple fact tables using single measure .For example Measure name is amount . This measure is using 5 fact tables. By using this info , i have to create bmm layer document . In bmm layer documents columns are like logical table name ,column name, logical sourc name . could you please help me out to draft the document ?

Hi ,
My question is five fact tables are there, day level two different fact tables , period and week fact tables are there .
Above all tables are using single measure . how to design these fact tables with measure in bmm layer ?
Please kindly give reply .
Thanks in advance.

F and E Fact Tables

Hi,
What is the difference between F fact table and E fact table?
When we create an Infocube which fact table is generated?
Thanks,
Soujanya

Hi ,
Difference between 'F' fact table & an 'E' Fact table
A cube has 2 fact tables - E and F. When the requests in the cube are not compressed the data exists in the F fact table and when the requests are compressed the data lies in the E fact table.
When the requests are compressed all the request ids are lost (set to NULL) and you would not be able to select/delete the data by request id. The data in the E fact table is compressed and occupies lesser space than F fact table.
When you load a data target, say a cube, the data is stored in the F fact table. If the cube is compressed, the data in the F fact table is transferred to the E fact table.
The F-table uses b-tree indexes the E-Table uses bitmap indexes. Index, Primary Index (The primary index is created automatically when the table is created in the database.). Secondary Index (usually abap tables), Bitmap Index(Bitmap indexes are created by default on each dimension column of a fact table), and B-Tree Index
Bex access the records from F-table or E- Table of InfoCube
Bex access both F and E fact tables. If data exists in both tables, it picks from both.
If the cube is not compressed it takes from F table, if fully compressed it takes from E table, partial compression - both F and E.
Roll-up adds the copy of records from F or E table to the aggregate tables. The records are not moved from F or E.
Also check the below SDN thread.
What is the difference between Fact tables F & E?
Hope the above info is helpful.
Cheers
VA
Edited by: Vishwa Anand on Aug 31, 2010 12:58 PM

Unable to join two fact tables via one common dimension in RPD(Repository)

I have created two fact tables F1 & F2 and one dimension D.
F1 is joined to D and F2 is also joined to D in Physical layer as well as in BMM layer.
I created one report in OBI Answers using these three tables.It Showed me the following error.
**Error Details**
**Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P**
**State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table dfghdfh) does not contain mapping for [Dashboard_Fact.Period_Sgt_Key]. (HY000)**
**SQL Issued: SELECT dfghdfh.Period_Sgt_Key saw_0, "Period Dim".Period_Sgt_Key saw_1, Dashboard_Fact.Period_Sgt_Key saw_2 FROM service_delivery ORDER BY saw_0, saw_1, saw_2**
How to cope up with the issue or can anyone tell me the alternate workaround for this?

That is what i have tried.
I have made a logical table TEST and dragged two fact tables f1 & f2 in source.
Now when i drag different columns from different fact tables(that are in TEST logical table) in report, it gives an error and not making any joins that you are mentioning.
ERROR MESSAGE:--
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Test) does not contain mapping for [Test.SurveyName_Id, Test.SurveyHead_Id, Test.Respondent_Id, Test.SDBusiness_Area_Id, Test.Period_Sgt_Key, Test.OBS_Id, Test.VOCBusiness_Area_Id, Test.Question_Sgt_Key]. (HY000)
The columns mentioned in the error message are all from test logical table..some are from F1 & some from F2.

Two fact tables in one business area

Hi,
Would there be problem if two fact tables, one flat, one with hierarchy, in one business area. Both fact tables are joined to same set of dimension tables except one: region_1 to fact_1, region_2 to fact_2. The consistency check is fine. But I get error in Answers. I don't have the exact error with me, but it is complains about fact_1 is not linked region_2.
Any suggestions ?
Thanks.

Thank you, Stijn, Ced for your kind reply.
I did not explain it clearly.
The fact_1 (flat) table has data in all levels (detailed and aggregated). For example, it has % sales to planned from city, state to national (we were not provided with numberator and demoninator to aggregate the detailed data). The fact_2 table has only city level data and have a dimension region_2 with city, state and national hierarchy. For data in Fact_1 table, we simply want to show them in reports. For data in Fact_2 table, reports can drill-down.
In Answers, the error is "Incorrectly defined logical table source ( for fact table Fact_1) does not contain mapping for region_2.state_id".

Mutiple fact tables for one report?

HI
I have two fact tables like Shipment and Sales. They each have their own star schema but most of the dimension tables are very similar. In one report I have to combine the two fact tables. so my report would have something like date, product Shiptment and Sales.
What is the best way to set this up as shipment and sales have their own fact tables but the dimension tables that are being used in this report are common?
Do i do this in the Physical layer of the rpd and how?

you need to work in BMM layer for this..
In one of your business models where there is Sales Fact Table... bring the shipment Fact Table from the physical layer onto this buisness model , and do a complex join to the Time dimension (common dim)...
Now Bring this Shipment Fact Table from that buisness model to the Presentation Layer under the same Subject Area ( ie now a single Subject Area must have both the Fact Tables under it...
Bounce back ur servers...
Now you are good to go...

HOW CAN I HAVE DUMMY FACT TABLES IN ONE UNION REPORT

Hello developers,
So, I am trying to have a report from 4 different subject areas. Each of these have transaction numbers under Fact-table. B’se these fact tables are under different subject area I can’t have them in one report, (fact table has to be a one to many relationship and not otherwise). How do I make sure I end up with a transaction number from atleast 1 subject area and ignore the other ones or avoid the error
Also in addition, I have to have the last 4 digits of the credit card number which is located in only one of those 4 subject area. How do I make sure its included with my final report eventhough its not in other subject areas? Please please help I am still new in this business
thanks in advance
Chuck

You got two choices:
A. Use OBIEE:
1) Create a OBIEE logical SQL like
SELECT A.s0 field1, C.s2 field2, A.s1 Measure1, B.s1 Measure2, C.s1 Measure3
FROM
(Select "Txn Attributes"."Transaction Number" s0, Measure.Measure1 s1 FROM "Subject Area 1") A,
(Select "Txn Attributes"."Transaction Number" s0, Measure.Measure2 s1 FROM "Subject Area 2") B,
(Select "Txn Attributes"."Transaction Number" s0, Credit."Last 4 digits" s2, Measure.Measure3 s1 FROM "Subject Area 3")
WHERE A.s0 = B.s0
AND B.s0 = C.s0
2) Test this SQL from "Issue SQL" section in answers.
3) Once tested, open a new analysis, go to Advanced tab and put this tested logical SQL in the SQL section and apply it. If you come back to criteria tab, you will see 5 fields are created for you.
This is technically feasible. Pulling this off is hard and this is a maintenance nightmare.
Since you are self-proclaimed newbie, I would suggest you take the alternative: fixing it through ETL. Create a new fact and write an ETL job to load this fact from other facts and dimensions. Then model it in RPD. This is more work but if you mess something up in the process of implementing first option, you may need to apply nearly same effort to fix that. Choice is yours.

E and F Fact Tables

Hi
I recently joined as a Junior BI Consultant after training.
I am going through the SAP material with regards to Data Modelling
Could you please spare some of your valuable to time and shed some light on
Info Cube consists of a Fact Table surronded Dimension tables (Extended Star Schema).
Fact Table is classified as two types
/BI0/F -- Fact Table(Before Compression)
/BI0/E -- Fact Table(After Compression)
Correct me if I was wrong
By default Data will be saved in F Fact Table,If we compress the requests in Info Cube the data is moved from F to E fact Table
Can you please explain me the advantage of accessing data from E fact Table over F Fact Table
Thanks in Advance

Hi ,
In F table data is stored request wise...which is not the case with E table
Refer:-
Re: F & E tables
If you access from E-table you would avoid the aggregation of data as data is already aggregated and hence this puts less load on OLAP engine ..please note that when I say u avoid aggregation this does not mean that by using E table aggregation goes out of picture...the thing is that basic aggregation ( as explained in the above thread ) is avoided...
Hope it helps
Mann

Report to display total and detail from table GLT0 and FBL3N

hi guys,
we have the requirement to show a report with total amount per GL account from table GLT0 and to as well display the detail from tcode FBL3N ..
shall i use normal report via SE38, if yes, what is the table that stores detail from FBL3N or does report painter support the above requirement..pls advice

use report SAPF070 as sample
(compare documentation!)
hope that helps
Andreas

Summary and Detail Fact Tables in one Universe ...

Similar Messages

Maybe you are looking for