Multiple granular levels for fact table

My fact table has to incorporate both at Transaction level and Accumulative , my basic design for Transaction level is as follows
CUSTOMER_KEY, LOAN_KEY, TIME_KEY, LOAN_AMT, TOTAL_DUE, LOAN_STATUS, TRANSACTION
9000,1000,1,200,200,Open, Advance
9000,1000,1,200,0,Close, Payment If I aggregate the values then query will take time to execute . How can I provide cumulative information from this fact table? shall i go for one more fact table for Accumulative information ?
Please suggest.
Thanks,
Hesh.

Hi ,
Is it a question of OLAP cube generation using your fact table design ? If not then it is incorrect forum ..If yes , then it should be straighway ur fact and dimension design and no need of another fact table with aggregation because OLAP cube aggregate this which should ideally be tremendous fast
Thanks,
DxP

Similar Messages

  • Logical level in Fact tables - best practice

    Hi all,
    I am currently working on a complex OBIEE project/solution where I am going straight to the production tables, so the fact (and dimension) tables are pretty complex since I am using more sources in the logical tables to increase performance. Anyway, what I am many times struggling with is the Logical Levels (in Content tab) where the level of each dimension is to be set. In a star schema (one-to-many) this is pretty straight forward and easy to set up, but when the Business Model (and physical model) gets more complex I sometimes struggle with the aggregates - to get them work/appear with different dimensions. (Using the menu "More" - "Get levels" does not allways give the best solution......far from). I have some combinations of left- and right outer join as well, making it even more complicated for the BI server.
    For instance - I have about 10-12 different dimensions - should all of them allways be connected to each fact table? Either on Detail or Total level. I can see the use of the logical levels when using aggregate fact tables (on quarter, month etc.), but is it better just to skip the logical level setup when no aggregate tables are used? Sometimes it seems like that is the easiest approach...
    Does anyone have a best practice concerning this issue? I have googled for this but I haven't found anything good yet. Any ideas/articles are highly appreciated.

    Hi User,
    For instance - I have about 10-12 different dimensions - should all of them always be connected to each fact table? Either on Detail or Total level.It not necessary to connect to all dimensions completely based on the report that you are creating ,but as a best practice we should maintain all at Detail level only,when you are mentioning any join conditions in physical layer
    for example for the sales table if u want to report at ProductDimension.ProductnameLevel then u should use detail level else total level(at Product,employee level)
    Get Levels. (Available only for fact tables) Changes aggregation content. If joins do not exist between fact table sources and dimension table sources (for example, if the same physical table is in both sources), the aggregation content determined by the administration tool will not include the aggregation content of this dimension.
    Source admin guide(get level definition)
    thanks,
    Saichand.v

  • Aggregation table - Diffrent agg levels for base table and agg table

    Is it possible to have Different aggregation level for base table and Aggregation. Say sum on a column in AGG table and Count for the same column in Fact table.
    Example
    Region,Day_product,sales person, customer are dimensions and Call is a fact measure
    FACT_TABLE has columns Region, Day, Product, Sales person,Customer, Call
    AGG_TABLE has columns Region, Month,Product, call
    We already have a Logical Table definition for the fact table say FACT_CALL
    We have a Logical column called No of customers.
    For the Data source as FACT_TABLE Formula for the column is "Customer" and Aggregation level is count distinct.
    But agg table we already have a calculated column call TOT_CUSTOMERS. which is been calculated and aggregated in the ETL.
    IF we map this to the logical column we have to set the formula as TOT_CUSTOMERS and we need to define aggregation type as SUM as this is at REGION, MONTH AND Product level. But OBI does not allow to do so.
    Is there a work around for this? Can you please let us know.
    Regard
    Arun D

    The way BI server picks up the table that would satisfy the query is through column mappings and contents levels. You have set the column mappings to TOT_CUSTOMER, which is right. When it comes to aggregation, since its already precalculated through ETL, you want to set the aggregation to SUM. Which I would say - is not correct, you can set the aggregation to COUNT DISTIMCT which is same as that of the detailed fact. But set the content levels to month in date table, and appropriate levels in region etc., So now BI Server will be aware of how to aggregate the rows when it chooses the agg table.

  • Incorrectly defined logical table source (for fact table X

    Hi!
    Imagine the following Physical Diagram:
    - Dim A
    - Dim B
    - Fact A
    - Fact B
    Joins:
    - Dim A is parent of Dim B
    - Fact B has a FK to Dim B
    - Fact A has a FK to Dim A
    Business Layer:
    - Logical Table Dim A
    - Logical Table Dim B
    - Logical Table Fact A
    - Logical Table Fact B
    Joins:
    - same joins (not FK Joins) that Physical Layer
    When we build a report that only has one column of Dim A and one column of Dim B (A is parent of B), the following error appears:
    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 "Fact A") does not contain mapping for [Dim A.col1, Dim B.col1]. (HY000)
    What is wrong?
    Help!
    Thanks.

    Hi,
    The joins of dimensions go via a fact table. In your case there is no common fact table.
    You can solve this by drag/drop a field from the physical table Dim B on the displayed logical table source of the logical table Dim A.
    Now the BI Server knows that Dim A and B have a physical relationship.
    Regards

  • Incorrectly defined logical table source (for fact table Facts) does not

    Hi,
    I have two Dimensions A and B. A is joined to B by a foreign Key.
    The report works if I pull B. Column1, A.Column2.
    The report is throwing an error if i try to change the order of the columns like this. A.Column2, B. Column1.
    error : Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    File: odbcstatementimpl.cpp, Line: 186
    State: S1000. Code: 10058. [NQODBC] [SQL_STATE: S1000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Facts) does not contain mapping for B.Column1
    I am not sure where it is going wrong.
    Thanks
    jagadeesh
    Edited by: Jagadeesh Kasu on Jun 16, 2009 4:22 PM

    did you make joins in LTS or on the physical table.
    try to make join in LTS if they are not there.

  • Define granularity of the fact table

    Hi BW experts,
    Can you explain defining granularity of the fact table when doing data warehousing?
    Thanks,
    Bill

    Data Modeling issue:  want example of Define granularity of the fact table
    http://help.sap.com/bp_biv335/BI_EN/documentation/Multi-dimensional_modeling_EN.doc

  • Granular level of a table

    Hi frnds , in a process , i have been assigned an issue ,,,,below is the requirement given by my client
    We need to configure the Budget Table in the RPD Side.
    The granularity of this table is at : Customer Site Use Id -- Sales Rep Id -- Ent Period Id
    Include the Budget amount, Budget YTD, Budget QTD in the Sales Order Lines/Invoice Lines
    The Aggregation content should be at the Period Level.
    Please note the difference, the Sales Order lines and invoice lines is at Day level, where as the Budget is at the Period Level
    We will have to set the aggregation content accordingly.
    i have a budget table in database and i need to import it to rpd , i need to give joins and copy the BUDGET_Amount column and create YTD , QTD for it and drop it in Sales Order Lines and Invoice Lines fact table .
    This is what i understand .
    Can some one out there please explain what is the granular level , and also about the above issue....
    Thank you

    Hi,
    I dragged the budget_amount measure into sales order lines/invoice lines logical fact tables . I have set the budget LTS at Quarter Level. when i check at front end , i am unable to see any data in budget_amount column.
    Kindly help me in fixing this ,
    Aggregation content should be set at period level
    what does it mean , period level ,wat i understand is Year or Quarter .Is it true?
    Please help me in this
    Thank You

  • Help on  Setting logical Levels  in Fact tables and on Dimension tables

    Hi all
    Can any body provide any blogs or any king of material on what exactly is levelling .
    Like after creating the Dimensional hierarchies we need to set the logical levels for the LTS of fact tabels ri8 .So what is the difference between setting logical levels to fact tabels and also Setting levelling on Dimension tables .
    Any kind of help is appreciated
    Thanks
    Xavier.
    Edited by: Xavier on Aug 4, 2011 10:50 AM

    I have read these blogs ,but what my question is
    Setting the logical levels in LTS of Fact tables i understood .
    But we can also set the logical levels for dimensions also ri8 .I didn't understand why do we set the logical levels for dimensions .Is there any reason why we go with the levelling at dimensions
    Thanks
    Xavier
    Edited by: Xavier on Aug 4, 2011 2:03 PM
    Edited by: Xavier on Aug 4, 2011 2:32 PM

  • How do you handle update and delete rules for fact tables?

    I have a fact table with a composite key of 5 columns. Two of the columns are FKs to the date dimension. I was setting the delete/update rules for the FK relationship in SSMS and it had a problem with me creating cascade action on the FKs that connected
    to the date dimension.
    What is the proper way to set up FK relationships in fact tables with SSMS when  you have composite keys as most fact tables do?

    Yeah I understand all that. What I'm trying to do is to protect my database from RI violations that occur by production support people blowing away stuff in a dimension table but forgetting to blow away related records in the fact table. I want those fact
    records deleted automatically so we don't have orphan records which was a real issue at a previous engagement. Production support is usually just people that know SQL and some relational modeling. It's not too likely they will understand the details of dimensional
    modeling enough such that they would know that they had to blow away the fact record first.
    My problem is I have a FK to a role playing dimension (the date dimension in this case). So basically I have to columns in the fact table that have a FK relationship to the PK of the date dimension. When I create both relationships SSMS and try to have both
    of them cascade delete SSMS has an issue with it.
    The error I get is:
    Unable to create relationship '[relationship name]'
    Introducing Foreign Key constraint '[constraint name]' on table '[table name]' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other foreign key constraints.
    I can go ahead and put no action and the table will save fine. The question now becomes how does the cascade delete actually work. Can I just set one part of the key to cascade delete?
    Actually I just realized that this is an even bigger design issue. What DOES happen to a fact record when one of it's dimensions gets deleted and I've got full RI set up on the table?
    Or am I totally thinking about this wrong. Do you set up cascade deletes in a dimensional model? Is there a way to prevent deletes from the dimension table if there are related fact records?

  • Multiple Revision Levels for a Material

    Today, Tyco Electronics has many manufacturing sites located around the world.  A given material may be manufactured in multiple locations.  When Engineering determines that a given material must change revision level, they determine a date that this new revision level becomes effective.  Unfortunately, not all manufacturing sites can be ready to manufacture to that new revision level.  In fact, based on tooling, one manufacturing site may manufacture to both the old and new revision level for a period of time until all of their tools/dies have been switched over.  In addition, customers may require that only the latest revision be sold to them.  Does anyone else have this requirement/issue today?  If so, how are you handling this within the SAP R/3 system since material revision is at a global level and there is no component revision level field on the bill of material.  Requirements are to sell at a material/revision level, plan to a particular material/revision level, stock at a material/revision level.  Any input you have would be greatly appreciated.

    Which strategy shall I use for picking?
    Can you please guide me what material master data fields are required for these strategies.
    regards,
    VS
    Edited by: vs on Jan 12, 2008 7:01 PM

  • Multiple header rows for one table?

    Using html it's possible to set up multiple table header rows for one table but with APEX Reports I don't see how to implement this. Any ideas?
    I want to use the second header row to provide links to data for the column only (not a row). But I still want sortable columns so I want to maintain the default column header behavior too.
    Thanks,
    Linda

    Mike,
    I tried that and found that indeed the substitution string is working and shows in both debug regions I set up on each page I tested.
    I have tried this on two kinds of pages. It works correctly on standard pages with PPR report regions.
    It is not working correctly on a page based on Carl's tabbed regions with PPR reports. One click and the header disappears. This is the version I really want to get working.
    I'd like to post something but have asked twice for a space on apex.oracle.com and have yet to receive even an email acknowledging my request.
    Perhaps you can help me get a space?
    My new problem on the tabbed page where my multiple headers are working is that when I click on a link in the header, it loads that page below the tab. But if I now click on the tab again, rather than return to the original tab page, I get error "ERR-1777: Page 4042 provided no page to branch to. Please report this error to your application administrator. " This happens on both the tabbed regions pages and on the standard tabbed pages. I guess I need to provide a differently formatted url? It is currently like this -
    -----------------------"<th id="opt-details1" [a href="f?p=&APP_ID.:3001:&APP_SESSION.:::::"] View Details</a></th>" --------------[not really square brackets but I didn't know how to make this show in the forum with proper <> brackets ----------------------
    Thanks again,
    Linda 
    ---sorry for the lack of white space. It seems to happen when I post on forums on Sunday nights - all white space is removed.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Multiple hierarchy levels from single table

    Happy 2014 for everyone!
    Here is my first problem of the year: I got a product table with "coded" hierarchy, like this:
    1
     Level
    11 
    Level
    111 
    Level
    1111 
    Level
    11111 
    Product
    11112 
    Product
    11113 
    Product
    1112 
    Level
    11121 
    Product
    112 
    Level
    1121 
    Level
    11211 
    Level
    112111 
    Product
    112112 
    Product
    112113 
    Product
    How should I go about to create an hierarchy from this table? Keeping in mind that products could be in different levels.
    Any ideas please?
    Thanks very much!

    I think you can model this as a parent-child hierarchy.  More info here: http://technet.microsoft.com/en-us/library/ms174846.aspx
    If you are using multidimensional: http://www.brustblog.com/archive/2008/06/22/analysis-services-2008-wizards-is-the-magic-gone.aspx
    If you are using tabular: http://sqlblog.com/blogs/alberto_ferrari/archive/2011/07/19/parent-child-hierarchies-in-tabular-with-denali.aspx
    Christian Wade
    http://christianwade.wordpress.com/
    Please mark correct responses as answers!

  • Create multiple capture processes for same table depending on column value

    Hi,
    is it possible to create multiple realtime downstream capture processes to capture changes for the same table depending on column value?
    Prakash

    i found it - by using subset rules
    prakash

  • Subcontracting multiple BoM levels for Project Stock

    Hi,
    We are an engineer / make-to-order manufacturer, so we use a lot of "individual" type materials (instead of collective).  We are trying to subcontract several BoM levels of work to different vendors, and we are seeing many false requirements.
    So we have something like this (this is all in project / wbs element stock):
    Make hereSubcontract Requisition
    Make hereRaw material
    Subcontract Purchase OrderMake here
    Raw material
    Raw material
    Make hereRaw material
    The subcontracting items are driving additional false MRP requirements (planned orders and purchase requisitions) for all the raw materials under them.
    I figured out how to fix the subcontract on level 3 by transferring the HALB material from project stock to unrestricted stock (411Q), then transferring it to subcontract stock (541) (Is there a better way to do this?  Now I can't see my project-specific stock line for that item).  But, while that purchase order is still open, there's nothing I can transfer to make the extra, false requirements disappear.  Also, I am getting an MRP exception telling me to cancel the PO because it doesn't see the dependent requirement for the subcontract requisition above it.
    Does this question make sense?  How can we fix it?  I need to get that subcontract requisition to see that its material will come from the subcontract purchase order.
    Thanks!
    Timothy

    Hi All,
    Any thoughts or ideas?
    Thanks very much,
    Timothy

  • Reg: Multiple authorization level for HR Report

    Dear Experts,
    I have a customized report for the payroll area, I need to have authorization for this report.
    The requirement is  as below
    For Ex: i have 5 payroll areas, 1000 personnel numbers, the multiple users and one customized report.
    The user has access for 2 payroll areas, the user should select the personnel numbers which has access to the same payroll area.
    The same user should not be authorized to access the other payroll areas and the personnel numbers.
    One customized report is being executed by the mulitple users, one user will have access only for one payroll area and he needs to select the personnel area for which payroll area he has access.
    Similar concepts follows for the other users.
    Can anyone help me to achieve this authorization concept. It would be grateful.
    Awaiting for your suggestions.
    Thanks in advance.
    Regards,
    Abdur Rafique

    hi,
    You can use sy-uname. Such that if some other user enters you can pop up the message you are not authorized.
    Regards,
    Pawan.

Maybe you are looking for