Logical Key for Degenerate Dimension

Hi Gurus,
Need some help on the degenerate dimensions in the BMM layer.
I have one fact table with dimension attributes and I would like to move the attributes into separate logical table and treat it as dimension.
Now my newly created dimension has the Fact LTS and I would like to assign a logical key to the newly created table and then create the logical dimension.
Can anyone provide some inputs on we can assign the logical key to the column?
Thanks

Hi Srini,
Since my main logical fact table consists of two LTS and the dimension being created from this table will also have 2 LTS, the content level will be set to all levels on which the fact is joined.
So I would like to create a logical dimension based out of my dimension and then assign the content level at the detail level.
Please let me know if I am not clear.
Thanks

Similar Messages

Primary Key and Chronological Key for Time Dimension

Could someone please shed light whether it's better to use normal PK or Calendar Date (which is a chronological key on the most detailed level). I tried both and haven't noticed any difference. But my understanding is that I still need to have the PK key on the most detailed level in time hierarchy.
Thanks

Matt,
the PK of the Time Dimension is a regular sequence numeric key. I have it defined as a logical PK for the dimension. However, I guess I was talking about hierarchy key. I tested it either way and the query time is the same. So I guess it doesn't really matter.
--------Year
Year (chronological key and primary key)
------------------Quarter
Quarter (key)
Quarter+Year (primary key, chronological key)
---------------------------------Day Detail
PK (key)
Date (primary key , chronological key)
I hope it makes sense.

How we use Surrogate Keys for snowflake dimension

Hi All,
my question is - How we use Surrogate Keys for snowflake dimension
i heard from some body Surrogate Keys only work with star schema.
please correct me if i wrong.
Regards,
Manish

Hi manishcal16PPS,
According to your description, you can only create natural key in your dimension. But it's not working when using surrogate key. Right?
In Analysis Services, the snowflake schema of the dimensions are represented by more than one dimension table in other words its takes multiple dimension tables to define a dimension. Surrogate key are just some extra, redundant, unique key based on the
natural key. So there's no direct relationship or some limitations between surrogate keys and snowflake schema.
In this scenario, since there's relationship between the two dimensions, you should create natural key. For using natural key or surrogate key. Please refer to an article below:
Surrogate Key vs. Natural Key
For understanding star/snowflake schema, please see:
Understanding Star and Snowflake Schemas
Regards,
Simon Hou
TechNet Community Support

Limit rows for Degenerate dimension in SSAS 2012 Standard Edition

Hi Experts,
I have a fact table consisting of 4 measures and 6 descriptive fields. The Geography and Time dimension are separately palaced. I want to build SSAS cube on this schema.
I have created the dimension from fact table itself for the descriptive fields. The scenario is that we are not loading complete fact table in SSAS. Only recent 2 years out of 10 years is brought into SSAS. But the degenerate dimension is procssesing all
the rows from fact.
I want to limit the dimension processing to only recent two years of data. How will I be able to achieve this?
Please help me out of this.
Thanks,
RuchikaG

Use a view as the source for dimension. Inside that write logic to filter data from the fact for last two years.
ie like
WHERE dateField >= dateadd(yy,datediff,yy,0,getdate())-1,0)
AND dateField < dateadd(yy,datediff,yy,0,getdate()) + 1 ,0)
Then take distinct attributes from it for the dimension
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Problem with unique key for Fiscal_T_Time dimension lookup

Hi,
In my mapping, I use Lookup on Fiscal_T_Time dimension provided by oracle. The validation gives me a warning,saying "VLD-1603:Lookup condition for key lookup Fiscal_T_Time does not contain a complete unique key". I'm using <source_group>.date as input and L_Day_day as lookup column, which is shown as I select the unique key from the drop down list. Both have type matches. The configuration on the dimension also shows the constraint of the unique Key. What can be wrong?

Continue my issue in another thread by Daming Wang on "More constraints need to add to Dimension". Thanks.

Demographics dimension and Logical Key.

Hello,
I have a simple star schema where there is a fact table linked to four dimensions. One of the dimensions is Customer Demographics. Others are Product, Time and Dealer.
Am I correct in using surrogate key of the demographics dimension as Logical Key for Demographics dimension in the BMM layer? Could you please let me know?
Thanks,
Manoj.

If the requirement is to do lots of "demographic" type queries - like sales amounts by race, gender, age, etc. - then snowflaking it off of a "person" dimension would really hurt query performance. Typically you only have demographic dimensions when either:
1. You don't have a person dimension at all - it's only the demographics you are interested in, or
2. You have a person dimension with millions of members, and splitting the demographics out into a separate dimension (typically a few thousand rows) means you can do a small join between the fact and a 3 thousand row demographics dimenion instead of doing a join between the fact table and a multi million row dimension table
In either case, snowflaking off of a person dimension table is either impossible or very bad for performance.
Thanks,
Scott

Define logical Key on Logical Dimension Table

It's recommended to define a logical key for any logical dimension table - in 10g there was a function on the right mouse button, as far as I remember - but in 11g there is no such functionality ? the foreign key can be added by "green plus" button, but not the primary key ?? you have to type in the name of the key, then you can choose the column and then you select as primary key ... funny.
bug or undocumented feature?

Hi Srini,
Since my main logical fact table consists of two LTS and the dimension being created from this table will also have 2 LTS, the content level will be set to all levels on which the fact is joined.
So I would like to create a logical dimension based out of my dimension and then assign the content level at the detail level.
Please let me know if I am not clear.
Thanks

Best Practice loading Dimension Table with Surrogate Keys for Levels

Hi Experts,
how would you load an Oracle dimension table with a hierarchy of at least 5 levels with surrogate keys in each level and a unique dimension key for the dimension table.
With OWB it is an integrated feature to use surrogate keys in every level of a hierarchy. You don't have to care about
the parent child relation. The load process of the mapping generates the right keys and cares about the relation between the parent and child inside the dimension key.
I tried to use one interface per Level and created a surrogate key with a native Oracle sequence.
After that I put all the interfaces in to one big Interface with a union data set per level and added look ups for the right parent child relation.
I think it is a bit too complicated making the interface like that.
I will be more than happy for any suggestions? Thank you in advance!
negib
Edited by: nmarhoul on Jun 14, 2012 2:26 AM

Hi,
I do like the level keys feature of OWB - It makes aggregate tables very easy to implement if your sticking with a star schema.
Sadly there is nothing off the shelf with the built in knowledge modules with ODI , It doesnt support creating dimension objects in the database by default but there is nothing stopping you coding up your own knowledge module (use flex fields maybe on the datastore to tag column attributes as needed)
Your approach is what I would have done, possibly use a view (if you dont mind having it external to ODI) to make the interface simpler.

Logical level for logical fact table sources

it is clear that for fact aggregates, we should use the Content tab of the Logical Table Source dialog to assign the correct logical level to each dimension.
question is : is it mandatory to assign even for non-aggregates fact tables the logical level for each dimension (which normally should be set to the most detailed level of each dimension) ? is it any known issue if "logical levels"in content tab are not set ?
the reason I'm asking this is a strange bug I have (I'm not going to discuss it here) and then only workaround seems to be NOT setting the logical levels (on content tab) for logical fact table sources.
thank you !

If levels are not set: By default levels are considered as lowest level
It should not matter if you set or not
Generally we set for facts explicitly when we are using Aggregate tables.
Your current issue might be a case by case; I would suggest to check implicit fact, any table mapped to the source to force a join etc
Mark if helps
Let me know how it helps
Edited by: Srini VEERAVALLI on Feb 5, 2013 8:33 AM
Any updates on this?+_
Edited by: Srini VEERAVALLI on Feb 14, 2013 9:09 AM

What is the use of logical key in logical tabls in bmm

hi
can any one tell me why we have to create logical key for logical table in bmm
Thanks
sreedhar

See the links below
why we have to create logical key at levels in Hierarchies
Re: Business Model - Logical Primary key
Regards,
Sandeep
Edited by: Sandeep Saini on 15-Sep-2010 05:17

BAPI_OPPORTUNITY_CREATEMULTI : Logical Key in INPUT_FIELDS

Hi All,
I am trying to create oppurtunity using BAPI_OPPORTUNITY_CREATEMULTI . I need to populate the product details . I need to know what is this Logical Key in INPUT_FIELDS structure? What will be the value of Logical Key for Product? Can somebody help me on this.
Thanks in Advance.

Pratik,
Thanks for your reply.
Can you give me a sample code for both PRODUCT and INPUT_FIELDS parameters. I tried giving product guid but, it does not seem to work.

Can i install logic pro without the cd because my dvd driver of my mac doesn't work . i have the key for logic pro

can i install logic pro without cd ? , i have the key for the logic pro but my dvd driver of my mac doesnt work ?

Buy an external USB2 DVD/CD drive..... (Amazon's Basic model works great)
Or..
Borrow someone else's Mac that has a DVD drive fitted and use that via Remote Disk
Note:
There is no legal means of downloading available for Logic Pro 9.. unless you originally purchased it via the App Store..
Therefore, in your case, you must install from the DVDs you have...

Foreign Keys for a Logical Table

Hi All,
I want to know in which scenarios we create the Foreign Keys for a Logical Table. Once we create the foreign key for the logical table, does it mean that it will automatically override if any joins are there.
Physical Table A, B ( no physical joins)
Logical Table A, B (logical join B(Dim)-->A(Fact))
created the foreign key in logical table A with B .(A.1=B.1)
Will the rpd generate sql with A.1=B.1 join condition for reports.
I tried to create the logical foreign key for logical table A, I could not see any corresponding table option.Here is its snapshot
http://tinypic.com/r/jq1gkz/6
Thanks,
Virat

In general when we go complex joins in Physical layer we go for Logical foreign key joins in BMM layer, best examples is SCD Type-II.
Physical Table A, B ( no physical joins)
-->You need to have a physical join so that this can be override by BMM layer
created the foreign key in logical table A with B .(A.1=B.1) Will the rpd generate sql with A.1=B.1 join condition for reports.
-->Yes you can see this join in BI Physical query.
I tried to create the logical foreign key for logical table A, I could not see any corresponding table option.Here is its snapshot
-->2 cases: 1)You need to delete existing logical joins 2) You might not have join in physical layer.
Hope this helps
Let me know for issues
Edited by: Srini VEERAVALLI on Jan 18, 2013 1:29 PM
BTW: You got very good name, why dont you update in your profile to see your name instead of some number
Edited by: Srini VEERAVALLI on Jan 18, 2013 1:29 PM

OLAP query returning "name" rather than "key" attribute for a dimension

Hello,
I am busy with a project that involves drawing data from an OLAP cube (in SAP BW), then transforming and contextualising for use in an EMI environment. The project runs on MII 12.1.
The standard OLAP connector and OLAP queries have been used (would prefer not to go the route of creating a call to the OLAP XMLA web service directly). One of the important dimensions is returned as a name (descriptive text) rather than a key (the cost element code itself), preventing us from reliably applying business rules to classify cost elements. Categorising cost elements based on their text descriptions is not a sustainable solution.
The output needs to allow for two dimensions (cost element and an equipment identifier) against which individual cost values will be listed. It appears that the two dimensions must both be on the "x-axis", as result columns are automatically renamed, e.g. C000001, C000002, etc. If anyone knows of a way to suppress this renaming behaviour, please let me know.
Is it possible to force the "key" attribute to be returned instead of the "name" attribute? I have identified two preferred options:
1. MDX syntax of the query itself
2. configuration of the OLAP connector
I have not found a way to do this through MDX syntax, but would welcome any suggestions.
Alternatively, perhaps there is a non-standard way of configuring the OLAP connector so that the key rather than the name attribute is returned for all dimensions. Has anyone anything, e.g. chosen a non-standard ColumnNameAttribute or DataTypeAttribute, in this regard?
Thanks,
Marc Chaplin

Apologies for the formatting above
Part 1:
Hello,
I am busy with a project that involves drawing data from an OLAP cube (in SAP BW), then transforming and contextualising for use in an EMI environment. The project runs on MII 12.1.
The standard OLAP connector and OLAP queries have been used (would prefer not to go the route of creating a call to the OLAP XMLA web service directly). One of the important dimensions is returned as a name (descriptive text) rather than a key (the cost element code itself), preventing us from reliably applying business rules to classify cost elements. Categorising cost elements based on their text descriptions is not a sustainable solution.
The output needs to allow for two dimensions (cost element and an equipment identifier) against which individual cost values will be listed. It appears that the two dimensions must both be on the x-axis, as result columns are automatically renamed, e.g. C000001, C000002, etc. If anyone knows of a way to suppress this renaming behaviour, please let me know.

I have logic pro studio 8 and the upgrade, however it will not upload on my mac book pro. It says i need a product key for the logic 9 and it come with one.

I have logic pro studio 8 and the upgrade (logic pro 9) and it will not load up to my new mac book pro. Its asking for a product key for the logic pro 9 upgrade and there wasn't one in the box. i need some help

Contact AppleCare... Explain you are a Logic User and you should be transfered to a Product Specialist to assist you with your Issue.

Logical Key for Degenerate Dimension

Similar Messages

Maybe you are looking for