Master tables  & fact tables

Hi
Can anyone explain the following in detail.
Mater tables an fact tables are linked with Dim id's.
Fact table and dim tables are linked with Sid id's or Sid keys.
Thanks in advance
Satya

Hi Satya,
The Fact table and Dimension tables are linked through the Dim Ids. The Dim Id, as the key of a Dimension table, represents a unique combination of char values in that Dim. These DIM Ids then combine to produce a unique combination in the Fact table of the cube.
Each char value stored in teh system is assigned a Sid, and in a dimension table the unique combination of Sids (depending on the char values in the data records) creates a DIM id.
Take a look at this link:
https://media.sdn.sap.com/html/submitted_docs/Best_Practices/BW/documentation/Multi-dimensional_modeling_EN.doc
Hope this helps...

Similar Messages

  • Size of dimention table  fact table ratio  question..

    Hey Guys !!!
    I have  very basic question regarding the ratio of size of dimention table and fact table..
    its mentioned that the ratio of dim table / fact table  sizes should not be greater than 1:20 for performance reasons .. thats OK..
    now lets say if i have fact table with customer dim_id ,some other dimention ids , and revenue (KF) .. with 1 million records ..
    so ideally my customer dimention table should not have more than  200,000 recods (.ie 200,000 different customers ).
    doesnt this put limitation on number of customers in a cube ?
    if so, how do we handle this ?
    please correct me if i am wrong  in interpreting the concept of dimension table.
    thanks in advance
    swapnil

    Hi ASRao ,
    thanks  for replying ...
    you said exactlly what i know  ..
    sorry i didnt put my question in correct prespective ...
    whay i meant was...
    lets say  , i need to have more than specified (1:20 ) number records in dimension table ,it will definately hamper my reporting performance ...
    so, is there any solution to handle this kind of problem ?
    like how would i maintain my efficiency of reporting in this case ?
    thanks in advance

  • Dimension Table : Fact Table

    Hi,
    I have Y/Z InfoCubes in my BW, somebody telling that Cube Dimension data table is more then Fact Table data. I have some doubts....pls clarify me.
    My system is BW 3.5
    1.How can I find my Dimension table is having more then Fact table data?. I have 7 to 8 dimensions in Cube, so how can I find which diemnsion is having the more data?.
    2. How can re model the cube?. Cube is haing 5 months Data. Without losing data how can I chage the Model?
    3.I know one Program  SAP_INFOCUBE_DESIGNS is there an dit will give the information, how can I use it?.
    Thanks
    Ganga

    Hi Arun, Thanks
    I searched based on the word "how to document on multi dimensional modeling on SAP BI".
    I got lot of thing....
    https://www.sdn.sap.com/irj/scn/advancedsearch?query=howtodocumentonmultidimensionalmodelingonSAPBI&cat=sdn_all
    I hope the below one is correct?.
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84
    Can pls guide me.
    Arun I'm using BW 3.5.
    Thanks
    Ganga.

  • 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!
    Randall

    hi in the capacity fact table remove the level set for the calendar dim and see.

  • Star schema without a fact table?

    Hi,
    I'm preparing my warehouse for using with Discoverer and my question is about the star schema.
    - Is a star schema directly associated with data warehouse?
    - Can I talk about a star schema if a) I do not have a fact table (no summarized values) and b) if I do not have a dimension of time?
    The problem is, I'm thinking of usine Discoverer but should I use it if it's not connected to a data warehouse?
    As I told, I'd like to modelized my data "like" a star schema but my "center table" will contain only the foreign key of my dimensions; no time dimensions, no aggregate data in the center table (fact table).
    Is there another word for the model I'd like to do?
    Thank in advance.

    Hi,
    Is a star schema directly associated with data warehouse?Not really, a star schema is just one where there is one large fact table joined to many smaller dimension tables using key fields. You usually see this in data warehouses.
    Can I talk about a star schema if a) I do not have a fact table (no summarized values) and b) if I do not have a dimension of time?A star schema must have a fact table but it doesn't need contain summarised values or a time dimension.
    You can use Discoverer with any Oracle database, it doesn't have to be a data warehouse.
    Rod West

  • Business Model with 2 fact tables

    Hi there
    I am trying to get a simple business model working , 2 fact tables, 1 dimension, similar to this example :
    http://www.rittmanmead.com/2008/08/resolving-fan-traps-and-circular-joins-using-obiee/
    However I keep getting this: [nQSError: 14025] No fact table exists at the requested level of detail:
    the tables are:
    Incident (dimension)
    PK Sequence
    Incident Detail (fact table 1)
    PK Sequence
    FK Problem #
    Order (fact table 2)
    PK Sequence
    FK HDNum
    I cant figure out why this doesnt work like the rittman mead example? do they need to have the same column name?
    Thanks
    Tim

    It says the model doesnt contains a fact table.Fact table will have foreignkeys and Measure columns.That link shows the circular joins between tables.There fact table is not there.
    See this link for fact and dimensions
    http://www.geekinterview.com/question_details/66773

  • Fact table to Dimension table ratio in RSRV

    Hi all,
    I want to analyze how best the modeling is done, because I came to know that line item dimensions are not being used/designed at all, so want to know the ratio between fact to dim table.  I read in some documentation that we can find that information in transaction rsrv.  I tried in both 'All Elementary tests" and "All Combined tests", but I really didn't get how to find/analyze the data to find the percentage.  Please let me know.
    thanks,
    Sabrina.

    Hi Bhanu,
    What I am seeing is this.  It shows % of dim table to Infocube.  Should i assume this as dim table:fact table as 165:100 resp.  Infocube here means fact table I guess right?
    @5B\QInformation@     Table /BIC/DZNETO_IC7 has 1633060 entries. Size corresponds to 165% of the InfoCube          14:30:35
    By any chance do you know what is the ideal percentage.
    thanks,
    Sabrina.

  • Fact Table with multi billion records.

    Hi ---> Is it advisable to build hierarchies around 3 billion record table Fact table and still growing in OBIEE..I know we can use oracle OLAP Tool and DB and other additional infrastructure will do it. But tryiing to look for a better way with the existing tools and hardware... Please let know the possibilities using obiee..yes I am aware of aggregate tables, materialized views etc.., it takes time to implement and view which is most optimal...
    Edited by: user007009 on Apr 11, 2013 5:49 PM

    Is it advisable to build hierarchies around 3 billion record table Fact tableIs it warehouse table or OLTP table treating as fact table? if it is ware house table then in BI we create hierarchy on dimension table but not on fact! or else you are using a fact table as both fact and dim then it can be but you have to mention as dim instead of fact.
    I dont think there is a limitation, its all how you see the data. I dont think you create a report to show 1 or 2Billion records at once.
    If you didnt convince try to check with Oracle with SR.
    If helps mark
    Thanks
    BTW: You havent mentioned about time period for that 3 billion records! if it is over a period of time then BI can take care of its source using fragmentation.
    Edited by: Srini VEERAVALLI on Apr 12, 2013 7:26 AM

  • Protect fact table in BI with S_TABU_DIS

    Hello all,
    I want to restrict access for particular DSO/Cube tables (fact table) via RSA1, LISTCUBE, SE16 or SM30, searched for a solution and found this thread: <u>Using Wildcard characters in tables in S_TABU_DIS</u> but it did not solve my problem.
    As far as I am informed cube tables are generated automatically when a cube definition is transported from development to production system (as written in the above mentionned thread: they get generated on the fly). Though it is possible to assign a specific authorization group to these tables and to create roles with restricted access for object S_TABU_DIS these authorization groups have to be assigned to these tables on each system (that means development on production!).
    What happens if a cube must be changed and transported again?
    I guess these manual tasks are gone then and one has to redo the assignment to the authorization groups.
    Are there any other things that might be affected of this handling?
    Thanks in advance for your inputs,
    Petra

    Petra,
    Did you find a way to address this issue?  We are trying to figure out how to secure table access without having to add table auth groups to hundreds of tables.
    Regards,
    Janice

  • Fact table and dimension table

    what is the difference b/w fact table and dimension table

    A fact table contains numeric values and also contain composite key(i.e collection of foreign key) e.g.. sales and profit. Typically has two types of columns: those that contain facts and those that are foreign keys to dimension  tables.
    Dimension tables, also known as lookup or reference tables, contain the relatively static data in the warehouse. It contains character values E.g Customer_name,Customer_city.
    Dimension tables store the information you normally use to contain queries. Dimension tables are usually textual and descriptive and you can use them as the row headers of the result set.
    Rachna

  • How to find Size of the fact table?

    hello all
    how do i find out the size of the fact table?
    Is the size of the fact table is same as size of the cube.
    pls let meknow
    regards
    balji

    Hello Balaji,
    To find out size of fact table
    DB02 ->Detailed anaysis -> Fact table name
    It will show you the details.
    The size of cube is not exactly equal to the size of fact table, but usually as fact table is much more larger than dimension tables, fact table size will give you a fair idea about cube size.
    Hope it helps.
    Regards,
    Praveen

  • Get the master table value based on multiple fact tables

    I have an master table which has to filter data based on multiple fact tables
    In the below sample, i need to get the list of MasterTable SId in an single query for fetching data from all the fact tables with an criteria.
    Can u let me know the single query to handle the below situation
    Select count(1) from dbo.DimMaster where sid in
    (Select Master_sid from dbo.factsales where SalesDate < '20141231')
    Select count(1) from dbo.DimMaster where sid in
    (Select Master_sid from dbo.factPurchase where PurchaseDate < '20141231')
    Select count(1) from dbo.DimMaster where sid in
    (Select Master_sid from dbo.factSalary where SalaryDate < '20141231')
    Select count(1) from dbo.DimMaster where sid in
    (Select Master_sid from dbo.factMarket where MarketDate < '20141231')
    ShanmugaRaj

    Please try below:
    SELECT
    (SELECT count(1)
    FROM dbo.DimMaster
    WHERE sid IN (
    SELECT Master_sid
    FROM dbo.factsales
    WHERE SalesDate < '20141231'
    )) as C1,
    (SELECT count(1)
    FROM dbo.DimMaster
    WHERE sid IN (
    SELECT Master_sid
    FROM dbo.factPurchase
    WHERE PurchaseDate < '20141231'
    )) as C2,
    (SELECT count(1)
    FROM dbo.DimMaster
    WHERE sid IN (
    SELECT Master_sid
    FROM dbo.factSalary
    WHERE SalaryDate < '20141231'
    )) as C3 ,
    (SELECT count(1)
    FROM dbo.DimMaster
    WHERE sid IN (
    SELECT Master_sid
    FROM dbo.factMarket
    WHERE MarketDate < '20141231'
    )) as C4
    -Vaibhav Chaudhari

  • Display master data without data in the fact table

    Characteristic 0PROJECT
    Attribute Price
    I want to show in the query all the prices including the projects that don't have registers in the fact table.
    How do I do this?
    Tnks.

    I believe you are describing what SAP referes to as the Slow Moving Item scenario.  Search SDN using that phrase and you'll get hits on documents and  Notes that talk more about this.  Here's something from an old How To
    Slow Moving Item Scenario
    You want to define a query that displays all products that have been purchased only
    infrequently or not at all. In other words, the query is also display characteristic values for
    which no transaction data or only low values exist for the selected period.
    Procedure
    In the Administrator Workbench;
    1. Create a MultiProvider consisting of a revenue InfoCube, containing the InfoObject
    Material (0MATERIAL), and the InfoObject 0MATERIAL. The InfoObject must be set as
    an InfoProvider in InfoObject maintenance. In other words, you need to have assigned
    the InfoObject to an InfoArea. (also refer to Tab Page: Master Data/texts [Ext.]).
    In the BEx Analyzer:
    2. Select your MultiProvider in the Query Designer.
    3. Define a query that contains the InfoObject 1ROWCOUNT in the columns.
    The InfoObject 1ROWCOUNT is contained in all “flat” InfoProviders, that is, in all
    InfoObjects and ODS objects. It counts the number of records in the InfoProvider.
    In this scenario, you can see from the row number display whether or nor values
    from the InfoProvider InfoObject are really displayed.
    4. Save the query and execute it. All values are now displayed, including those for materials
    that were not purchased.
    If you filter by time (0CALYEAR, for example), values from the InfoProvider
    InfoObjects are not displayed since 0CALYEAR is not an attribute of
    0MATERIAL. You can see this from the absence of values in the 1ROWCOUNT
    column in the query. If you want to restrict by time, you need to proceed as
    follows:
    Constant Selection for the InfoObject
    You need to set the constant selection for the 1ROWCOUNT key figure in order to be able to
    set a filter by time in this query.
    1. In the Query Designer, via the context menu for 1ROWCOUNT, choose Edit.
    2. On the left hand half of the screen, under the data package dimension, select the
    characteristic InfoProvider (0INFOPROV) and drag it into the right-hand screen area.
    3. From the context menu for the InfoProvider, choose Restrict, and restrict across the
    InfoProvider InfoObject.
    4. Also from the context menu for the InfoProvider, choose the function Constant Selection.
    5. Save the query and execute it. You can now also set a filter for a time characteristic, the
    materials display remains as it was.
    Displaying Slow Moving Items
    SAP Online Help 05.11.02
    MultiProviders 3.0B, Support Package 07 10
    If you want to display a list of slow moving items, excluding products that are selling well, you
    need to proceed as follows:
    1. In the Query Designer, via the context menu for 1ROWCOUNT, choose Edit.
    2. Via the context menu for InfoProvider, choose the function Display Empty Values. Also
    select Constant Selection.
    3. Save the query and execute it. The result is that the system displays the materials for
    which there was no revenue.
    Displaying Products with Small Revenues
    If you want to display a list of products that have not been sold or have only been selling
    badly, you need to proceed as follows:
    1. Set constant selection as described above, but do not select the display empty values
    function.
    2. In the Query Designer, define a condition for the 0MATERIAL InfoObject. Specify a value
    that is to be the upper limit for a bad sale.
    3. Save the query and execute it. The result is that the system displays all materials that
    have not been sold or have been selling badly.

  • Join between fact table and master data table

    Is it posible to join a Cube with a Characteristic? This is exactly what i need:
    - In my cube i have date (0CALDAY) and (among others) a characteristic (ZCHAR) and a key figure (ZKEYF).
    - I added a key figure (ZKFAT) as an attribute to ZCHAR. So the tables look something like this:
    Fact table:
    <b>0CALDAY | ZCHAR | ZKEYF</b>
    12.10.2006 | CHAR1 | 10
    12.10.2006 | CHAR2 | 20
    12.10.2006 | CHAR3 | 30
    Master data table for ZCHAR:
    <b>ZCHAR | ZKFAT</b>
    CHAR1 | 1000
    CHAR2 | 2000
    CHAR3 | 1500
    I need to make a query with a table that looks like this:
    <b>0CALDAY | ZCHAR | ZKEYF | ZKFAT</b>
    12.10.2006 | CHAR1 | 10 | 1000
    12.10.2006 | CHAR2 | 20 | 2000
    12.10.2006 | CHAR3 | 30 | 1500
    Finally, the query should result in something like this:
    <b>0CALDAY | ZKEYF | ZKFAT</b>
    12.10.2006 | 10 | 1000
    12.10.2006 | 20 | 2000
    12.10.2006 | 30 | 1500
    Adding KFAT to the fact table is not an option, i need to read this information directly from ZCHAR.
    I've tried using MultiProviders but didn't get the result i need.
    Is there any way to achieve this? Please advice.
    Thank you,

    Thank you Ram C. i've tried your solution and it may be it, but i'm having one problem:
    Since i'm reporting in web, i used the second solution you offered and almost got the desiered result. The problem is that some entries are correct but others ar duplicated! Using same example, my result table looks something like this:
    <b>0CALDAY | ZKEYF | Calculated KF (from ZKFAT)</b>
    12.10.2006 | 10 | 1000
    12.10.2006 | 20 | 4000
    12.10.2006 | 30 | 1500
    Second row should be 2000, but instead it shows 4000. I added ZCHAR's attribute ZKFAT as a display attribute in order to compare the results. I found that the display attribute is correct (2000) but the Calculated KF still showed duplicated data (4000).
    By the way, when i execute the query, i get this warning message:
    "Calculated key figure ZRT_C02_2_CKF004 is not defined correctly"
    Any ideas why this could be happening?
    Thank you for your help.
    Message was edited by: Gerardo Gaona

  • Transaction data can be loaded into the Fact table without loading the

    Transaction data can be loaded into the Fact table without loading the corresponding master data (Example : Sales analysis transaction data can be loaded without populating any of its  dimension’s master data)
    a.     True
    b.     False

    Hi Kutti,
    True - You need to select the option in the infopackage - alwyas load even if no master data exists.
    Bye
    Dinesh

Maybe you are looking for