Joining a dimension with another dimension

I have a customer dimension, which had the registration date as an attribute. I want to join to this column in the date dimenion so that I can do rollups and drilldowns. Couple of questions:
- Is this design violating the star schema model?
- How do I accomplish this in OWB, if I have customer and date modeled as dimensions?
Appreciate your help.

Hi,
Yes it would be a violation of a pure Kimball design star schema, but my question is do you have a pure customer dimension, or do you have a customer dimension and should there possible also be a fact table with customer related measures(facts) so you can do the slicing and dicing?
When dealing with designing your datamodel or changes to the datamodel, always try to stay true to the architecture you chose at the start. Keep going back to the rules that came with the design decisions. So if you chose star schema, try stick to that and with each change, review the change against the rules for star schema design. In my opinion you may deviate, but in those cases always do that for the right reasons and document the rationale for that in the design.
grts,
Ed

Similar Messages

  • 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 activate Bluetooth ? I cant join my iPhone with another iPad or iPhone

    How activate Bluetooth ? I cant join my iPhone with another iPad or iPhone

    The Bluetooth is meant for earplug, headset, keyboard, car hands-free set and speakers.
    You need 3rd party apps to do file transfer.

  • How to copy data for certain member from one dimension to another dimension

    Dear ,
    I want to copy data for certain member ("511102") from one dimension to another combinations of dimensions ,
    I have the following combinations for "511102" :
    _("Budget2012","FY12","Working.V01","SAR","BegBalance","1011","G_10","custom Grades")_
    I want to copy "511102"  to "salary"
    -salary have the following dimensions :
    _("Budget2012","FY12","Working.V01","SAR","BegBalance","General group","All grades","General Employees")_
    , I don't know if I could do it by datacopy of cross dimensional , But I don't HOW >>>
    Thanks in advance

    FIX("Budget2012","FY12","Working.V01","SAR","BegBalance","General group","All grades","General Employees")
    "salary"="511102"->"1011"->"G_10"->"custom Grades";
    ENDFIX
    or
    FIX("Budget2012","FY12","Working.V01","SAR","BegBalance")
    DATACOPY "511102"->"1011"->"G_10"->"custom Grades" to "salary"->"General group"->"All grades"->"General Employees";
    ENDFIX
    Key thing in datacopy is to place the dimensions in cross dimension in the same order. Both sides (before and after "TO") should have equal number of dimension members specified.
    Cheers,
    Alp

  • Joining Two facts with one dimension

    hi,
    Hello Experts,I am reporting out of 2 fact groups.
    Mailing History and Booking.
    The only common dimension between the 2 is the Person Dimension. I have created the hierarchies and defined the aggregation content in the LTS.This helps me in reporting using any column from the Facts or any one dimension from either of the fact groups. But if i select 2 or more dimensions , one or more from each fact group , then the report gives and error. A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: MailingHistory Campaign.Campaign Name. Please fix the metadata consistency warnings. (HY000)
    For Example : BookingDim--BookingFact-MailingHistoryFact (ok) MailingSourceDim--BookingFact-MailingHistoryFact works (ok) but BookingDim--BookingFact-MailingHistoryFact - MailingsourceDim (Fails ).
    When i am applying the filter from the fact 1 . i am getting this error.(which is the column in the second fact table 2).I checked all the joins in the BMM layer.
    Please help me!!!
    Thanks,
    Surya

    Surya did you set the levels properly for two fact tables and also for metrics.
    When ever you are using two fact groups with non confirmed dimensions you have to make sure all the content levels set for the fact tables and as well as for metrics.
    in your fact tables/ metrics - For related dimensions set the level to Detail. and for the non related dimension set the level to Total. This way obiee server will understand what is related dimension and whats not related..
    hope this works for you.

  • How to find share/rank of one dimension with another

    I am working on OLAPTRAIN schema.
    I would like to find out the share of a product within certain geography. I want to know the share of an item or a category within a country or certain region.
    I am using AWM11.2.0.1.A.

    Create a share type calculated measure in the product dimension (e.g., share to parent, share to total). When you report, the share will be calculated for whichever geographies (and any other dimensions) that you happen to be reporting on. If you are reporting at, for example, a Region level the calculation will apply to those members at that level. If you drill to, for example, a country the calculation will apply to the countries in the report. That's the beauty of the Oracle cube. You just define calculations once and they work anywhere within the cube.
    You can make share calculations in the calculated measure GUI in AWM. Here are two examples:
    Share to Total:
    SHARE(SALES_CUBE.SALES OF PRODUCT.STANDARD TOP) * 100
    Share within parent:
    SHARE(SALES_CUBE.SALES OF PRODUCT.STANDARD PARENT)
    You can specify that the measure to be calculated using specific value of a dimension using the (...) button in the calculated measure GUI. For example, if you wanted the share to parent calculation to be calculated based on the value for North America regardless of what geographies you are reporting on, you can add that to the expression. For example:
    SHARE(SALES_CUBE.SALES[OLAPTRAIN.GEOGRAPHY='North America'] OF HIERARCHY PRODUCT.STANDARD PARENT)
    Note that in this expression I've substituted 'North America' for the actual dimension member '-11' for readability purposes.

  • Replace dimension with renamed dimension

    Hi
    We have the following situation. We are currently in the development stage and use Essbase. We have already developed a set of reports but now some the names and aliases of our dimensions need to be changed. In one case, the name of the dimension is changed from "ACCOUNT" to "Account".
    However, the reports do not seem to pick up the change. They keep referring to ACCOUNT and error out because they cannot find this dimension anymore. Any suggestions on how to deal with this issue?
    yours
    Arie

    First, is this FR or WA. WA does have a renamer utility that can be quite cumbersome to work with, but if you export the WA report and open up in a text editor, you can do a search and replace on your dimension member.
    The same goes with FR, depending on how many objects you have in your report you might have to do a trial and error, but doing an export of the report and doing a search and replaces usually works for me. Any further issues might require a little rework of your reports in there respective design client.
    Hope this helps.

  • Expand Dimension using another dimension Property

    Hi guys,
    My template has Product in the Rows (User Defined) and Time in the Collums.
    The Entity dimension is changed at the context, but I want Currency to show the value of the property "Currency" of Entity dimension.
    I've tryed to do this putting Currency at the collum, and trying to filter it by Dimension Property, but I didnt succeed.
    Any thoughts?
    Thanks in advance.
    Adriano Frossard

    Hi Adriano,
    Simply put currency in the page axis and in the EPMOlapMemberO formula use formula to get a property of entity. Read here: Static report in BPC NW 10
    Vadim

  • Join fact with another fact like a dimension

    Does it work if I join fact table with another fact table as a dimention(created the dummy hierarchy and add the sum() to the measure existed in the table)?
    If I pick the measure value in the fact table(which is configured like a dim), I will get the correct number? Or multiplied number?
    If there is any good way of work around please let me know
    Thanks
    Edited by: user12077461 on Jun 29, 2011 7:39 PM

    Hi,
    You can create an Alias Table in the Physical Layer for the Fact table which you want to use as a Dimension Table. And start using the Dimension Table. And if you want any measure values to be used from the Fact, then you can extract that too.
    This should simplify your work too.
    Regards
    MuRam

  • Join With Date Dimension

    Hi,
    I have one Dimension called Caseheader and Date Dimension. In Date dimension I have date key  yyyymmdd format. I have fact table in which i am getting CaseCreationDate from Caseheader Dimension. in case creationdate it contains time as well because
    there is a requirement to do some reports based on timing.
    When I join case creationdate to date column in a data source view with date dimension i do not get any thing  and get error in cube processing as well because it does not match with case creationdate because of time. What is the best possible approach
    to resolve this issue? Do I need to add time dimension? or have a time field in date dimension?
    Could anyone suggest please?
    MH

    Thanks Christian, I have separated date and time and kept the original field with datetime as well in case if somebody wants it for reporting purpose. Thank you so much for all your help suggestions. Much appreciated. Used this code
    convert(date,ch.CaseCreationDate)asCaseCreationDate
    ,convert(varchar(8),convert(time,ch.CaseCreationDate))as[CaseCreationTime]
    Regards,
    Mustafa
    MH

  • Load hierarchical attribute dimensions with Integration Services?

    Hi everybody,
    I need to load product dimension which is organized in a relational table like this:
    Product (parent_code, member_code, member_alias, brand, consolidation, formula)
    Every product has a brand and I need to load brand as attribute dimension. The thing is Brand is not flat but it has it's own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
    Brand (brand_parent_code, brand_child_code, brand_child_alias).
    I have used in the past Integration Services but with flat attribute dimensions.
    Can I load hierarchical attribute dimensions with Integration Services? If yes, how do I do it, how do I specify the hierarchy?
    Thank you,
    Daniela

    Graham,
    This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
    In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
    Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
    When you run your dim build it will set up your attribute dimension correctly.
    Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
    Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
    Good luck, let me know if you run into trouble.

  • Adding another  dimension on BI Admin layer.......

    hi,
    i already have a cube with few dimensions and its running fine on dashboard. Now i added another dimension in oracle warehouse builder cube (same running cube) now i want to upgrade this cube and its data on BI Admin layer so that i can see results accordingly on BI Answers and dashboard.
    How to add this dimension in BI Admin layer as i don't want to import all the dimensions and cube again on physical layer, then make hierarchies for each dimension on business model and mapping layer and changes on presentation layer (just to avoid rework).
    If i import a single dimension it behave like a fact table (cube) with a yellow color.
    thanks in advance
    Mimran

    Hi,
    As I understood from your query you are importing a new dimension table to the physical layer of your RPD. Once you import the dimension table it will be a stand alone table. So join this table to the existing Fact table with the proper key. Then Drag and drop the same table to the BMM layer. In the BMM layer open the Business model diagram and join it to the fact table and then drag it to the presentation layer. This should solve your purpose.

  • Two Cube dimensions with the same name.

    Hi
    If I have a cube dimension that has the same name as another cube dimension, will this be an issue when quering the cube through 1) Excel 2) SSRS or Cognos Reports?
    For instance: The Database dimension DimOrganization exists in cube A as well as
    DimOrganization_Dep. Both dimension has the same attribute names and the same hierarchy names.
    Their database names are different. (object_ID and Object_name differs) 
    In the cube I change the name of DimOrganization_Dep to DimOrganization.
    This seem to work when I query the cube in Excel, the mdx looks like this;
    SELECT NON EMPTY { [Measures].[AntalNotNull] } ON COLUMNS, NON EMPTY { ([Dim Organization].[Yes- No].[ Yes- No].ALLMEMBERS * [Dim Organization].[Yes- No].[Yes- No].ALLMEMBERS ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME
    ON ROWS FROM [TEST] CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
    Anyone knows if this kind of setup will result in problems when quering from SSRS reports or Cognos?
    And/or if even though I get it right in the cube (quering from Excel) it might as well give me the wrong result the next time?
    Cheers
    /Martin

    Hi
    Thanks for the reply.
    I have tried and yes I can change then cube dimension namn to that of another cube dimension.
    For instance if i have Cube Dimension "DimA" and "DimB" to begin with , then  I change the name of the cube dimension "DimB" to "DimA". So now I have two Cube dimensions with the same name.
    It works to deploy and process and Excel somehow understands which one is which.
    Both is present in the same cube as you can see from the MDX above.
    The tricky part is how does the mdx return the correct result when the mdx looks like this (and it dpoes return the correct result).?
    Cheers
    /Martin

  • 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 Eriksen

    The 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

  • OWB10gR2 - Cube with relations to a dimension with more than one hierarchy

    Hi,
    I have defined a time dimension with two hierarchies. The standard hierarchy with the levels year-> month-> day,
    and a week hierarchy with the levels year-> week-> day.
    When I define the cube i choose dim_time on the dimension tab of the cube and select the level day for that dimension since this is the lowest level of both hierarchies.
    When I validate the cube I get the following error Message: VLD-0398: In the Cube test_cube, the dimension DIM_TIME has 2 hierarchies but Cube does not have reference to all lowest levels of these hierarchies.
    Validation details: The Cube should refer to a leaf levels of all multiple hierarchies of the Dimension.
    Do I have to add the dimension to the cube several times? or is it maybe another way to fix this? To me it seems a bit messy to add a dimension for each hierarchy.
    And just as a comment, Yes i know OWB now has a time dimension wizard but I have chosen not to use this at the moment.. ;)
    Regards Ragnar

    Hi, i assume this logic is for Dimension formula?
    If you have multiple hierarchy like ParentH1 and ParentH2 you should use FormulaH1 and FormulaH2 and not FORMULA column.
    in FORMULAH1
    [Account.H1].[Account_A] / [Account.H1].[Account_B]

Maybe you are looking for